Maxpay
An international payment gateway designed to help your business.
Supports in this guide: Payments, Payouts
Provider website: maxpay.com
What you need to do for start processing transactions (brief summary)
- Choose account type
- Get your credentials (from Maxpay)
- Connect in Dashboard
- Send an API request
Choose account type
Maxpay can be connected in different ways (depending on your needs):
- If you do direct card payments (with recurring, no refunds) -> choose H2H Merchant account
- If you do card payments via a hosted redirect page -> choose Merchant account
- If you do card or wallet payouts -> choose Provider account
These are three separate, independent connections with their own credentials. If you're not sure which one to use, confirm with your Corefy account manager.
Prerequisites: get from Maxpay
Contact your Maxpay account manager to get your account verified and receive the following credentials.
For H2H Merchant account:
- Account -> Corefy field
account. - Password -> Corefy field
password. - Signature key -> Corefy field
signature_key.
For Merchant account:
Log into the Maxpay merchant portal, go to the Payment Pages section, and create a page (ask your Maxpay support manager to upgrade it from Test to Live). On that page, set https://psp-ext.paycore.io/maxpay/callback as the Callback URL, then copy:
- Public key -> Corefy field
public_key. - Secret key -> Corefy field
secret_key. - Test public key -> Corefy field
test_public_key. - Test secret key -> Corefy field
test_secret_key.
For Provider account:
- Merchant account -> Corefy field
merchant_account. - Merchant password -> Corefy field
merchant_password. - Signature key -> Corefy field
signature_key.
UAH, RUB, EUR, USD (availability depends on account type - see each flow below).
Payments processing via H2H Merchant account (connect H2H Merchant account, create payment-invoice)
Connect H2H Merchant account in Corefy Dashboard
Step 1 - Open connection form
Open Maxpay in the provider directory and press Connect at Maxpay Provider Overview page in the New connection section. Choose H2H Merchant account.
Step 2 - Fill in fields and select settings
- Account
- Password
- Signature key
- Currency / Features -> choose values available for your account (UAH, RUB, EUR, USD)
Success
You have connected Maxpay H2H Merchant account!
First request to Corefy API (MIN)
What it does: creates a payment-invoice; card data itself is collected and submitted separately by Corefy's checkout/SDK layer, not as part of this request. CVV is always required, and a 3D Secure challenge is always used for the initial sale (3DS mode is not configurable for this connector).
Payment - MIN
POST /api/payment-invoices
{
"data": {
"type": "payment-invoice",
"attributes": {
"reference_id": "6f7a8b9c-0d1e-4f2a-8b13-6c7d8e9f0a1b",
"service": "payment_card_uah_hpp",
"currency": "UAH",
"amount": 10
}
}
}
Payment - MAX
POST /api/payment-invoices
{
"data": {
"type": "payment-invoice",
"attributes": {
"reference_id": "7a8b9c0d-1e2f-4a3b-8c24-7d8e9f0a1b2c",
"service": "payment_card_uah_hpp",
"currency": "UAH",
"amount": 10,
"customer": {
"reference_id": "cus_123",
"name": "John Doe",
"email": "john.doe@example.com",
"address": {
"full_address": "Main street 1",
"country": "UA",
"city": "Kyiv",
"post_code": "01001"
}
}
}
}
}
Important
customer.email, customer.address.post_code, customer.address.full_address, customer.address.city, and customer.address.country are all optional from Corefy's side - but if a field is missing from both the request and its matching Constant, Maxpay's own connector code falls back to a hardcoded non-empty value of its own (a placeholder email, a placeholder ZIP code, and a placeholder Kyiv address) rather than leaving the field empty. See Constants below.
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
Options
dynamic_flow_available-> optional, boolean - enables a dynamic 3D Secure flow for this connection.
Constants (fallback fields)
Constants are static values that Corefy can send to the provider 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 -> a built-in placeholder value is used (see note above) - unlike most connectors, Maxpay's own Constants always carry a non-empty default, so this connector never actually sends an empty field here
Currently available constants (constant -> Corefy API field)
EMAIL->customer.emailZIP->customer.address.post_codeADDRESS->customer.address.full_addressCITY->customer.address.cityCOUNTRY->customer.address.country
Refunds
Maxpay does not support refunds on the H2H Merchant account.
Payments processing via Merchant account (connect Merchant account, create payment-invoice)
Connect Merchant account in Corefy Dashboard
Step 1 - Open connection form
Open Maxpay in the provider directory and press Connect at Maxpay Provider Overview page in the New connection section. Choose Merchant account.
Step 2 - Fill in fields and select settings
- Public key
- Secret key
- Test public key
- Test secret key
- Currency / Features -> choose values available for your account (UAH, USD, EUR, GBP)
Success
You have connected Maxpay Merchant account!
First request to Corefy API (MIN)
What it does: creates a payment-invoice; the customer is redirected to a Maxpay-hosted payment page to enter card details.
Payment - MIN
POST /api/payment-invoices
{
"data": {
"type": "payment-invoice",
"attributes": {
"reference_id": "8b9c0d1e-2f3a-4b4c-8d35-8e9f0a1b2c3d",
"service": "payment_card_usd_hpp",
"currency": "USD",
"amount": 10
}
}
}
Payment - MAX
There is no MAX variant - customer is not used by this flow; Corefy generates its own synthetic user/order identifiers for the hosted page.
Options
No Options are configured for this connector.
Refunds
This flow does not support refunds.
Payouts processing (connect Provider account, create payout-invoice)
Connect Provider account in Corefy Dashboard
Step 1 - Open connection form
Open Maxpay in the provider directory and press Connect at Maxpay Provider Overview page in the New connection section. Choose Provider account.
Step 2 - Fill in fields and select settings
- Merchant account
- Merchant password
- Signature key
Success
You have connected Maxpay Provider account!
First request to Corefy API (MIN)
What it does: creates a payout-invoice and sends funds to a card or wallet, depending on the service.
Payout - MIN
POST /api/payout-invoices
{
"data": {
"type": "payout-invoice",
"attributes": {
"reference_id": "9c0d1e2f-3a4b-4c5d-8e46-9f0a1b2c3d4e",
"service": "payment_card_uah",
"currency": "UAH",
"amount": 10,
"customer": {
"reference_id": "cus_123"
},
"fields": {
"card_number": "4111111111111111"
}
}
}
}
Important
fields.card_number is required for card payouts. The RUB card payout service (payment_card_holder_rub) additionally requires customer.name (split into first/last name) and the card's expiry date. QIWI (qiwi) and YandexMoney (yandexmoney) wallet payouts are also available in RUB and use a wallet account identifier instead of a card number.
Payout - MAX
POST /api/payout-invoices
{
"data": {
"type": "payout-invoice",
"attributes": {
"reference_id": "0d1e2f3a-4b5c-4d6e-8f57-0a1b2c3d4e5f",
"service": "payment_card_uah",
"currency": "UAH",
"amount": 10,
"customer": {
"reference_id": "cus_123",
"email": "john.doe@example.com"
},
"fields": {
"card_number": "4111111111111111"
}
}
}
}
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
Options
No Options are configured for this connector.
Refunds
Maxpay does not support refunds for payouts.
Additional info
- Three independent connections - H2H Merchant account, Merchant account, and Provider account use entirely separate credentials and serve different flows; connecting one does not affect the others.
- Recurring is only available on the H2H Merchant account - a saved card token can be charged again through Corefy; the Merchant account (hosted redirect) and Provider account do not support this.
- Reconciliation differs per flow:
- H2H Merchant account: active status request available, used automatically on return from the 3DS challenge.
- Merchant account (hosted redirect): asynchronous callback only, no active status request.
- Provider account (Payouts): both an asynchronous callback and an active status request are available, but the active check only starts working 30 minutes after the payout was created and searches a narrow 5-minute window around the creation time - a payout checked earlier simply won't be found yet.
- There is a separate, unrelated Maxpay-family connector with its own OFT code
maxpayment("Maxpayment") that is not covered by this guide and currently has no Dashboard nav entry of its own.
FAQ / Troubleshooting
- Invalid credentials / auth error -> verify the credentials for the selected account type - all three account types use entirely different credential sets
- Refund fails -> Maxpay does not support refunds on any of its three account types
- Currency or service is not supported -> confirm allowed currencies/features in your Maxpay account and in Corefy - each account type supports a different currency set
- Payout status check returns nothing -> wait at least 30 minutes after creating the payout before relying on the active status request; the callback can still arrive sooner
- Not sure which account type to use? -> H2H Merchant account is for direct card Payments with recurring; Merchant account is for hosted-redirect card Payments; Provider account is for card/wallet Payouts
Question
Still looking for help connecting your Maxpay account? Please contact our support team!