Skip to content

Logo

Paydoo (Paynt)

Discover Acquiring-as-a-Service to power your growth. With our complete payment solutions infrastructure and our long-term relationship mindset - we got you covered.

Supports in this guide: Payments, Payouts

Provider website: paynt.com

Note

"Paydoo" is the connector name on Corefy's side; the provider itself has rebranded to Paynt - the live API domains used below (paynt.com) confirm this is the same company.

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

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

Choose account type

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

  • H2H Merchant account -> card Payments, two independent sub-flows selectable per connection via the API Type field:
    • ECP (default) -> the current, full-featured Paynt API - supports completing a sale, asynchronous callbacks, and Recurring.
    • V1 -> an older/generic API type - does not support completing a sale or receiving callbacks; relies on active reconciliation only.
  • Provider account -> card Payouts (also on the Paynt API).

If you're not sure which API Type to use, confirm with your Corefy account manager - ECP is recommended for new integrations.

Prerequisites: get from Paynt

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

For H2H Merchant account (Payments):

  • Merchant account ID -> Corefy field merchant_account_id -> used by the ECP API Type.
  • Password -> Corefy field password -> used by the ECP API Type.
  • Access Token -> Corefy field access_token -> used by the V1 API Type (Bearer authentication).
  • Entity ID -> Corefy field entity_id -> used by the V1 API Type.

For Provider account (Payouts):

  • Account ID -> Corefy field account_id.
  • Password -> Corefy field password.

EUR, USD, RUB, GBP, PLN, CHF (card Payments); EUR, USD, RUB, GBP, PLN, CHF, MXN (card Payouts).

Payments processing - ECP API Type (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

Open Paydoo in the provider directory and press Connect at Paydoo Provider Overview page in the New connection section. Choose H2H Merchant account.

Step 2 - Fill in fields and select settings

  • API Type -> choose ECP
  • Merchant account ID
  • Password
  • Save Instant Token -> (enable to allow saving a token for Recurring)
  • Test Mode -> (enable if you are using sandbox credentials)

Choose Currency and Features. You can set these parameters according to available currencies and features for your Paynt account, but it is necessary to check details of the connection with your Corefy account manager.

Success

You have connected Paydoo H2H Merchant account (ECP)!

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.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "09fed794-a604-4261-9762-ade5ff0bd764",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 1
    }
  }
}

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "d4a6f1e3-7b2c-4e9d-8f3b-1a2c5d6e7f8a",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10.5,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com",
        "address": {
          "country": "FR"
        }
      }
    }
  }
}

customer is entirely optional - anything you don't send falls back to the Constants below.

Important

This module has no Dashboard-configurable Constants mechanism at all (no constants.php). If customer.address.country, customer.email, or a customer identifier are not sent in the request, Corefy sends fixed placeholder values to Paynt instead of leaving them blank: country code GB, email email@email.com, customer ID user123. There is no way to change these defaults from the Dashboard.

Extended request (MAX)

Why add extra fields (typical reasons): - Avoid the hardcoded placeholder values described above - Positively influence conversion rate - Include optional fields required by your specific flow

Refunds

This connector supports refunds on both API Types: partial refunds are allowed, and multiple refunds per payment are allowed. The original transaction ID is required to process a refund.

Payments processing - V1 API Type (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

Open Paydoo in the provider directory and press Connect at Paydoo Provider Overview page in the New connection section. Choose H2H Merchant account.

Step 2 - Fill in fields and select settings

  • API Type -> choose V1
  • Access Token
  • Entity ID
  • Save Instant Token -> (enable to allow saving a token for Recurring)
  • Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected Paydoo H2H Merchant account (V1)!

First request to Corefy API (MIN)

What it does: creates a payment-invoice. The request shape is identical to the ECP flow above (same service/currency/amount/customer fields) - only the API Type selected on the connection changes how Corefy talks to Paynt behind the scenes.

Important

  • Completing a sale is not supported on the V1 API Type.
  • Asynchronous callbacks are not supported on the V1 API Type - Corefy relies entirely on active reconciliation to learn the final status of a payment.

Options

Options are configured on the Corefy side and affect how Corefy builds provider requests. These 2 options apply only to the V1 API Type - they have no effect on ECP.

Currently available options (2)

  • include_sender_data - adds sender (your own merchant profile) details to the request.
  • include_customer_data - adds customer billing/contact details to the request.
include_sender_data

What it does: adds sender.country, sender.city, sender.name, sender.street, and sender.accountNumber (with an IBAN-formatted sender.accountNumberType when applicable) to the request, sourced from your own Corefy merchant profile - not from the API request.

When to use: enable if Paynt requires sender-of-funds details for your V1-connected account.

Default: false

Allowed values: true, false

include_customer_data

What it does: adds billing.street1, billing.city, billing.postcode, billing.country, customer.givenName, customer.surname, and customer.email to the request, sourced from the customer object of your API request.

When to use: enable if Paynt requires billing/customer details for your V1-connected account.

Default: false

Allowed values: true, false

Refunds

Refunds work the same way as described in the ECP flow above - the same connection-level Refund call dispatches to whichever API Type the payment was originally made on.

Payouts processing (connect Provider account, create payout-invoice)

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

Open Paydoo in the provider directory and press Connect at Paydoo Provider Overview page in the New connection section. Choose Provider account.

Step 2 - Fill in fields and select settings

  • Account ID
  • Password
  • Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected Paydoo Provider account!

First request to Corefy API (MIN)

What it does: creates a payout-invoice for a card payout.

Payout - MIN

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "a1c9f6a0-2d5e-4a7b-9b1e-6a3f0d8c7b2a",
      "service": "payment_card_eur",
      "currency": "EUR",
      "amount": 100,
      "customer": {
        "reference_id": "cus_123"
      }
    }
  }
}

Important

Card Payouts are available in MXN on this account type only - it is not one of the currencies supported by Payments above.

Extended request (MAX)

Why add extra fields (typical reasons): - Include optional fields required by your specific flow

This connector has no optional request fields beyond MIN - every other supported currency is just a different service value (payment_card_usd, payment_card_rub, payment_card_gbp, payment_card_pln, payment_card_chf, payment_card_mxn).

Refunds

Paydoo (Paynt) does not support refunds on the Provider account / Payouts side.

Additional info

  1. Recurring is supported - enable Save Instant Token on the H2H Merchant account connection (works for either API Type); Corefy then saves a token on an initial sale that can be charged again later.
  2. V1 has no active callback support - if you select V1, make sure active reconciliation is relied upon for status updates, since Paynt callbacks are not processed on that API Type.
  3. Account types are independent - the H2H Merchant account (Payments) and Provider account (Payouts) are two separate Dashboard connections with their own credential sets, even though both ultimately reach the same Paynt infrastructure.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify you're using the credential set that matches your chosen API Type (merchant_account_id/password for ECP, access_token/entity_id for V1; account_id/password for Payouts)
  • Currency or service is not supported -> confirm allowed currencies/features in your Paynt account and in Corefy
  • Sale never completes / stuck pending -> if connected via V1 API Type, this is expected - completion relies on active reconciliation, not a callback
  • Customer fields look wrong on Paynt's side -> see the hardcoded fallback values under the ECP Payments flow above, or enable include_customer_data if using V1
  • Not sure which account type or API Type to use? -> ask your Corefy account manager

Question

Still looking for help connecting your Paydoo account? Please contact our support team!