Concord Pay

Supports in this guide: Payments, Payouts

Provider website: pay.concord.ua

What you need to do for start processing transactions (brief summary)

1. Choose account type
2. Get your credentials (from Concord Pay)
3. Connect in Dashboard
4. Send an API request

Choose account type

Concord Pay can be connected in different ways (depending on your needs):

• If you do direct card payments (H2H, no redirect) -> choose H2H Merchant account
• If you do payouts (card, bank transfer, or crypto) -> choose Provider account

If you're not sure which one to use, confirm with your Corefy account manager.

Prerequisites: get from Concord Pay

Register at the Concord Pay portal, set up your account, and contact your Concord Pay support manager to get your account verified. You generate an RSA key pair (public and private, PEM/pkcs8 format) on your side, and Concord Pay issues you a client code identifying your account.

• Client code name -> Corefy field client_code_name -> H2H Merchant account only.
• Client name -> Corefy field client_name -> Provider account only.
• Private key -> Corefy field private_key -> uploaded as a file, used by both account types.
• Public key -> Corefy field public_key -> uploaded as a file, optional -> only needed if you didn't already set up the account entirely on Concord Pay's own side.
• API type -> Corefy field api_type -> H2H Merchant account only -> choose Ecommerce, P2P, or Direct Flow.
• Fee calculation type -> Corefy field fee_calculation_type -> choose Inner or Outer -> used by both account types.

Optionally, to get more control over specific accounts/balances within your Concord Pay client (for example for P2P processing), request from Concord Pay and provide:

• Terminal ID -> Corefy field terminal_id.
• Account ID -> Corefy field account_id.

UAH, RUB (H2H Merchant account); UAH, EUR, BTC, ETH, USDT (Provider account Payouts).

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6be05631-8710-4b14-a369-1928a2b70eda",
      "service": "payment_card_uah_hpp",
      "currency": "UAH",
      "amount": 10
    }
  }
}

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "efbf0a2b-5590-42b7-b10b-94d49452147d",
      "service": "payment_card_uah",
      "currency": "UAH",
      "amount": 150,
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "a1b2c3d4-5e6f-4789-8a02-5b6c7d8e9f0a",
      "service": "bank_transfer_uah",
      "currency": "UAH",
      "amount": 150,
      "customer": {
        "reference_id": "cus_123",
        "name": "Ivan Petrenko",
        "individual_tax_id": "1234567890"
      },
      "fields": {
        "iban": "UA213223130000026007233566001"
      }
    }
  }
}

Additional info

1. Active reconciliation only, no callback - Concord Pay does not send asynchronous callbacks on either flow; status is resolved via the payment's own completion step (for 3D Secure) and active status requests (both flows), including crypto payouts.
2. No recurring - this connector does not support saving/charging a token through Corefy.

FAQ / Troubleshooting

• Invalid credentials / auth error -> verify the client code name (H2H) or client name (Provider account), and that the Private Key file matches the key pair registered with Concord Pay
• Payment rejected for missing cardholder name -> only relevant if strict cardholder validation is enabled on your account; otherwise this check doesn't apply
• Refund fails with multiple attempts -> only one refund per payment is allowed on the H2H flow
• EUR card payout rejected for missing details -> customer.name, customer.date_of_birth, and customer.address.country are all required for EUR card payouts specifically
• Not sure which account type to use? -> ask your Corefy account manager