PayDo

Supports in this guide: Payments

Provider website: paydo.com

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

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

Choose account type

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

• If you do redirect payments (customer redirected to a hosted payment page) -> choose Provider account

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

Prerequisites: get from PayDo

Get the following values for your PayDo project/account:

• Public Key -> Corefy field public_key -> example: pk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx -> where to find: PayDo backoffice / issued by PayDo manager
• Secret Key -> Corefy field secret_key -> example: sk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx -> where to find: PayDo backoffice / issued by PayDo manager. Used to sign invoice creation requests; never transmitted in the request body.
• Application Identifier -> Corefy field application_identifier -> example: app_123456789 -> where to find: PayDo backoffice / issued by PayDo manager. Identifies your PayDo application; used to fetch available payment methods and auto-provision payment routes on connect.
• JWT Token -> Corefy field jwt_token -> example: eyJhbGciOiJSUzI1NiJ9.eyJzdWIiOiJ... -> where to find: generated in the PayDo dashboard. Required for route provisioning — when generating the token, whitelist the Corefy IP addresses in PayDo so the token has the necessary permissions. The token has a mandatory expiry; regenerate it when you need to reconnect the account or re-sync routes.

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "d290f1ee-6c54-4b01-90e6-d701748f0851",
      "service": "applepay_eur_hpp",
      "currency": "EUR",
      "amount": 100,
      "customer": {
        "reference_id": "cust-ref-001",
        "email": "john.doe@example.com"
      }
    }
  }
}

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "d290f1ee-6c54-4b01-90e6-d701748f0851",
      "service": "applepay_eur_hpp",
      "currency": "EUR",
      "amount": 100,
      "customer": {
        "reference_id": "cust-ref-001",
        "email": "john.doe@example.com",
        "name": "John Doe",
        "phone": "+44123456789"
      }
    }
  }
}

Additional info

1. IPN callbacks — PayDo sends payment status notifications from IP addresses 54.76.199.219 and 34.250.152.204. Corefy accepts callbacks only from these addresses; callbacks from other IPs are ignored and do not change the payment status. The callback endpoint must return HTTP 200 OK; otherwise PayDo retries delivery for up to 24 hours. Callbacks fire only on terminal payment states — do not rely on them for intermediate statuses.

2. Callback URL configuration — The IPN callback URL is configured in the PayDo dashboard, not passed in the payment request. Before going live, set /paydo/callback as the callback endpoint in your PayDo account.

3. Route auto-provisioning — When a Provider account is connected, Corefy automatically calls GET /v3/instrument-settings/payment-methods/available-for-application/{applicationIdentifier} using the JWT token and provisions payment routes for the available Apple Pay and Google Pay methods. Each route's external identifier (the PayDo method ID) is set automatically and must not be modified manually.

4. JWT token expiry and route re-sync — The JWT token has a mandatory expiry. It is used only for account connection and route provisioning: payment creation, reconciliation, and IPN callbacks do not use it, so payments through already provisioned routes keep working after the token expires. An expired token blocks only reconnecting the Provider account, re-syncing routes, and connecting a new merchant account. If the application identifier changes or PayDo's available payment methods change, generate a new token and reconnect the Provider account to re-provision the routes. Payments will fail with INVALID_METHOD if a route's external identifier is missing or is not a numeric value.

FAQ / Troubleshooting

• Payment rejected with INVALID_METHOD / route has no external ID -> The payment route's PayDo method ID is not set. Reconnect the merchant account to trigger route re-provisioning.
• JWT token expired -> Payments through already connected routes are not affected — payment creation, reconciliation, and callbacks do not use the JWT token. A valid token is needed only to reconnect the account, re-sync routes, or connect a new merchant account. When you need to do any of these, generate a new JWT token (with Corefy IP addresses whitelisted in PayDo) and reconnect the account.
• Route provisioning failed on connect -> Make sure the JWT token is valid and was generated with Corefy IP addresses whitelisted in PayDo, then reconnect the account.
• Payer email is missing -> Supply customer.email in the request or configure the email route constant on the connection.
• Invalid credentials / auth error at payment time -> Verify that public_key and secret_key match the selected environment (test/production). These credentials are not validated during account connection — only at payment time.
• Currency or service is not supported -> Confirm allowed currencies and payment methods in your PayDo account settings and in Corefy.
• Not sure which account type to use? -> ask your Corefy account manager.