Paytend

Supports in this guide: Payments

Provider website: paytend.com

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

1. Get your credentials (from Paytend)
2. Connect in Dashboard
3. Send an API request

Prerequisites: get from Paytend

Contact your Paytend account manager to get your account verified and receive the following credentials.

• Agent ID -> Corefy field agent_id.
• Merchant ID -> Corefy field merchant_id.
• Agent private key -> Corefy field agent_rsa_pri_key -> a file (your own RSA private key); used to sign every outgoing request and to decrypt Paytend's responses. Updatable after connection.
• Paytend public key -> Corefy field paytend_rsa_pub_key -> a file (Paytend's RSA public key); used to encrypt the AES key sent with every request.

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6be05631-8710-4b14-a369-1928a2b70eda",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 100
    }
  }
}

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "199be985-c243-478a-86a8-4b8c902e5bb6",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 100,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Doe",
        "email": "johndoe@email.com",
        "phone": "+441234567890",
        "address": {
          "full_address": "123 Baker street",
          "country": "GB",
          "city": "London",
          "post_code": "NW16XE"
        }
      }
    }
  }
}

Additional info

1. Request/response encryption - every request body is AES-encrypted; the AES key is itself encrypted with your Paytend public key before sending, and the full payload is signed using your Agent private key. Paytend's responses are encrypted and signed the same way, and are decrypted using the same Agent private key you provided - no separate key is needed to read responses.
2. Active reconciliation - a callback from Paytend only signals that something happened; Corefy does not trust the callback payload's authenticity or its status on its own, and always sends an active reconciliation request to Paytend to confirm the real transaction status before finalizing it.
3. No recurring - this connector does not support saving/charging a token through Corefy.
4. Service naming - services follow the pattern payment_card_{currency}_hpp (e.g. payment_card_eur_hpp); confirm with your Corefy account manager which currencies/services are enabled for your Paytend account.

FAQ / Troubleshooting

• Invalid credentials / signature or decryption errors -> verify that Agent ID, Merchant ID, Agent private key, and Paytend public key are an exactly matching set issued by Paytend, and that Test Mode matches the credential environment
• Payment stays pending -> Corefy actively reconciles the transaction once Paytend's callback arrives; no action is normally needed on your side
• Refund fails -> Paytend allows only one refund per payment; confirm no refund has already been issued for this payment and that the amount is valid
• Currency or service is not supported -> confirm available currencies/services with Paytend and your Corefy account manager
• Is Paytend still accepting new connections? -> Paytend's Electronic Money Institution Licence was revoked by the Bank of Lithuania effective 3 March 2026; confirm current availability directly with Paytend and your Corefy account manager before connecting