
Paytently
Supports in this guide: Payments
Provider website: paytently.com
What you need to do for start processing transactions (brief summary)
- Choose account type
- Get your credentials (from Paytently)
- Connect in Dashboard
- Send an API request
Choose account type
Paytently can be connected in different ways (depending on your needs):
- If you process card payments directly, without redirecting the customer to a Paytently-hosted page to enter card details -> choose H2H Merchant account
- If you want Paytently to host the payment page, including Apple Pay and Google Pay -> choose Provider account
Paytently does not currently support payouts through either account type. If you're not sure which one to use, confirm with your Corefy account manager.
Prerequisites: get from Paytently
Contact your Paytently account manager to get your account verified and receive the following credentials. H2H Merchant account and Provider account are separate connections with independent credentials.
For H2H Merchant account:
- Merchant ID -> Corefy field
merchant_id - API Version -> Corefy field
api_version-> optional, chooseV1orV2; defaults toV1if left blank - Application ID -> Corefy field
application_id-> optional; required if you use API v1 - Public key -> Corefy field
public_key-> optional, uploaded as a file; required if you use API v1 - Private key -> Corefy field
private_key-> optional, uploaded as a file; required if you use API v1 - Client ID -> Corefy field
client_id-> optional; required if you use API v2 - Client Secret -> Corefy field
client_secret-> optional; required if you use API v2 - Route ID -> Corefy field
route_id-> optional; required if you use API v2 - Test Mode -> Corefy field
test_mode-> only applies to API v2; API v1 always runs against Paytently's production environment - there is no API v1 sandbox
For Provider account:
- Client ID -> Corefy field
client_id - Client Secret -> Corefy field
client_secret - Route ID -> Corefy field
route_id - Test Mode -> Corefy field
test_mode-> enable if you are using sandbox credentials
Payments processing (connect H2H Merchant account, create payment-invoice)
Connect H2H Merchant account in Corefy Dashboard
Step 1 - Open connection form
Open Paytently in the provider directory and press Connect at Paytently Provider Overview page in the New connection section. Choose H2H Merchant account.
Step 2 - Fill in fields and select settings
- Merchant ID
- API Version (optional,
V1orV2) - Application ID (optional, API v1 only)
- Public key (optional, API v1 only)
- Private key (optional, API v1 only)
- Client ID (optional, API v2 only)
- Client Secret (optional, API v2 only)
- Route ID (optional, API v2 only)
- Test Mode -> (API v2 only; enable if you are using sandbox credentials)
Success
You have connected Paytently H2H Merchant account!
First request to Corefy API (MIN)
What it does: creates a payment-invoice and submits the card directly to Paytently; card data itself is collected and submitted separately by Corefy's checkout/SDK layer, not as part of this request. Paytently may return a 3D Secure challenge redirect depending on the card/issuer.
Payment - MIN
POST /api/payment-invoices
{
"data": {
"type": "payment-invoice",
"attributes": {
"reference_id": "2b369d7e-b3a5-42db-9132-9dfb387a2e55",
"service": "payment_card_eur_hpp",
"currency": "EUR",
"amount": 15
}
}
}
Payment - MAX
POST /api/payment-invoices
{
"data": {
"type": "payment-invoice",
"attributes": {
"reference_id": "3c47a681-9d2a-4f6b-9a1e-5b6c7d8e9f01",
"service": "payment_card_eur_hpp",
"currency": "EUR",
"amount": 15,
"customer": {
"reference_id": "cus_123",
"first_name": "John",
"last_name": "Smith",
"email": "john.smith@example.com",
"phone": "+15551234567",
"date_of_birth": "1990-05-20",
"address": {
"full_address": "742 Evergreen Terrace",
"country": "DE",
"city": "Berlin",
"post_code": "10115"
}
}
}
}
}
Important
customer.reference_idis only used when API Version isV2- API v1 ignores it.- If a
customerfield is missing, Corefy falls back to the matching Constant below (if one is set); otherwise that field is simply not sent to Paytently.
Extended request (MAX)
Why add extra fields (typical reasons): - Provide additional customer details for compliance/reconciliation - Positively influence conversion rate - Include optional fields required by your specific flow
Constants (fallback fields)
Constants are static values that Corefy can send to Paytently instead of dynamic data from your API request, when those fields are missing in the request.
Priority (predictable rule): 1. If a value is present in the request -> Corefy uses the request value 2. Else if the constant is set -> Corefy uses the constant 3. Else -> provider may reject the request or apply its defaults (depends on provider)
Currently available constants (constant -> Corefy API field)
FIRST_NAME->customer.first_nameLAST_NAME->customer.last_nameEMAIL->customer.emailPHONE->customer.phoneCITY->customer.address.cityCOUNTRY->customer.address.countryADDRESS->customer.address.full_addressPOST_CODE->customer.address.post_code
Refunds
Paytently supports partial refunds, but only one refund per payment (no multiple partial refunds against the same payment). A refund request requires the original payment's provider-side ID, which Corefy tracks automatically.
Payments processing (connect Provider account, create payment-invoice)
Connect Provider account in Corefy Dashboard
Step 1 - Open connection form
Open Paytently in the provider directory and press Connect at Paytently Provider Overview page in the New connection section. Choose Provider account.
Step 2 - Fill in fields and select settings
- Client ID
- Client Secret
- Route ID
- Test Mode -> (enable if you are using sandbox credentials)
Success
You have connected Paytently Provider account!
First request to Corefy API (MIN)
What it does: creates a payment-invoice and redirects the customer to a Paytently-hosted payment page. The payment method shown on that page (card, Apple Pay, or Google Pay) depends on the Route ID/service your account manager configures for this account.
Payment - MIN
POST /api/payment-invoices
{
"data": {
"type": "payment-invoice",
"attributes": {
"reference_id": "5e7f8a9b-1c2d-4e3f-9a0b-1c2d3e4f5a6b",
"service": "payment_card_eur_hpp",
"currency": "EUR",
"amount": 15
}
}
}
Payment - MAX
POST /api/payment-invoices
{
"data": {
"type": "payment-invoice",
"attributes": {
"reference_id": "6f8a9b0c-2d3e-4f5a-8b1c-2d3e4f5a6b7c",
"service": "payment_card_eur_hpp",
"currency": "EUR",
"amount": 15,
"customer": {
"reference_id": "cus_123",
"first_name": "John",
"last_name": "Smith",
"email": "john.smith@example.com",
"phone": "+15551234567",
"date_of_birth": "1990-05-20",
"address": {
"full_address": "742 Evergreen Terrace",
"country": "DE",
"city": "Berlin",
"post_code": "10115"
},
"metadata": {
"ip": "203.0.113.5"
}
}
}
}
}
Important
If a customer field is missing, Corefy falls back to the matching Constant below (if one is set for the service you use); otherwise that field is simply not sent to Paytently.
Extended request (MAX)
Why add extra fields (typical reasons): - Provide additional customer details for compliance/reconciliation - Positively influence conversion rate - Include optional fields required by your specific flow
Constants (fallback fields)
Constants are configured per service - each payment route enabled on your Provider account has its own set.
Priority (predictable rule): 1. If a value is present in the request -> Corefy uses the request value 2. Else if the constant is set -> Corefy uses the constant 3. Else -> provider may reject the request or apply its defaults (depends on provider)
Currently available constants (constant -> Corefy API field)
customer_first_name->customer.first_namecustomer_last_name->customer.last_namecustomer_email->customer.emailcustomer_phone->customer.phonecustomer_city->customer.address.citycustomer_country->customer.address.countrycustomer_address->customer.address.full_addresscustomer_post_code->customer.address.post_codecustomer_reference_id->customer.reference_idcustomer_date_of_birth->customer.date_of_birthcustomer_metadata_ip->customer.metadata.ipmerchant_profile_website_url-> fallback for your website URL, normally taken from your Corefy merchant profile automatically
Refunds
Paytently supports partial refunds, but only one refund per payment (no multiple partial refunds against the same payment).
Additional info
- Both account types share the same modern API - API v2 on the H2H Merchant account and the Provider account both call Paytently's
api.paytently.ioREST API (sandbox:sandbox.api.paytently.io); only API v1 on the H2H Merchant account uses a separate, production-only endpoint with no sandbox. - Active reconciliation is available - both account types support an active status request to Paytently, in addition to the asynchronous callback.
- No recurring - this connector does not support saving/charging a token through Corefy.
- Callback routing is automatic - Corefy generates the callback/return URLs per transaction, nothing to configure in Paytently's own back-office.
- Apple Pay and Google Pay are Provider-account only - the H2H Merchant account only processes card payments; Apple Pay and Google Pay are available through the Provider account's hosted payment page.
FAQ / Troubleshooting
- Invalid credentials / auth error -> verify the credentials for the selected account type, API version, and environment - H2H Merchant account (API v1 or v2) and Provider account use entirely different credential sets
- Currency or service is not supported -> confirm allowed currencies/features in your Paytently account and in Corefy
- Refund fails on a second attempt -> only one refund per payment is allowed
- Not sure which account type to use? -> H2H Merchant account processes card payments directly; Provider account redirects to a Paytently-hosted page and additionally supports Apple Pay and Google Pay
- Not sure which API version to use on the H2H Merchant account? -> API v2 is the current REST API and supports a sandbox; API v1 is the legacy signed API and is production-only
Question
Still looking for help connecting your Paytently account? Please contact our support team!