Skip to content

Logo

Payler

Global business account & payments hub

Supports in this guide: Payments

Provider website: payler.com


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

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

Prerequisites: get from Payler

Get the following values for your Payler project/account:

  • Key -> Corefy field key -> where to find: Payler backoffice / issued by Payler account manager
  • Password -> Corefy field password -> where to find: Payler backoffice / issued by Payler account manager
  • API URL -> Corefy field api_url -> required only if your account is connected with API version v1 or v2 (see "Options" below); issued by your Payler account manager as your dedicated processing endpoint. Not used, and can be left blank, when your account is connected with API version v2.1 - that version always calls Payler's own sandbox/production endpoints directly.

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

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Key
  • Password
  • API URL (optional - see Prerequisites)
  • Test Mode -> enable if you are using sandbox credentials
  • API version -> choose v1, v2, or v2.1 (defaults to v2 if left unset)

Choose Currency and Features. You can set these parameters according to available currencies and features for your Payler account, but it is necessary to check details of the connection with your Corefy account manager. Supported currencies: USD, EUR, RUB, KZT.

Success

You have connected Payler H2H Merchant account!


First request to Corefy API (MIN)

What it does: creates a payment-invoice.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "86e68af6-6b95-4cc0-be16-e4df8044604c",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "55041b5b-adfd-4073-a92b-fd8b495a4cc1",
        "email": "johnsmith@gmail.com"
      }
    }
  }
}
customer.email is required when your account is connected with the default API version (v2) - Payler's own request builder returns a local error ("Customer email is required") if it is missing. This check does not apply to API versions v1 or v2.1.

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "08f5e97c-1170-4bda-9625-3bde3c6dcd20",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "bc75bc54-5023-4f98-8c0d-ec5ed7e8f380",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+380677123456",
        "address": {
          "full_address": "Shevchenko St 123",
          "country": "DE",
          "region": "Berlin",
          "city": "Berlin",
          "street": "Shevchenko St",
          "post_code": "10115"
        }
      }
    }
  }
}


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

Options are configured on the Corefy side and affect how Corefy builds provider requests or processes responses.

Currently available options (1):

  • api_version - selects which Payler API generation Corefy uses for Sale, Reconcile, and Refund requests on this connection.
api_version

What it does: chooses the internal Payler API integration path Corefy uses for this connection.

When to use: leave unset to use the default; your account manager may ask you to pick a specific version depending on how your Payler account was provisioned.

Default: v2

Allowed values: v1, v2, v2.1

Note

Refund behavior differs between versions - see "Refunds" below.


Refunds

Supported, one refund per payment (no multiple partial refunds on the same payment).

  • With API version v1 or v2 (the default), a full or partial amount can be refunded in that single refund call.
  • With API version v2.1, only a full refund - exactly matching the original payment amount - is accepted; any other amount is rejected locally as an invalid amount, even though partial refunds are enabled at the account level.

Recurring

Not supported. Payler's integration does not save card/payment data for reuse (card data is sent with saveCard: false on every Sale request), and there is no recurring/Save Instant Token option for this connector.

Reconciliation

Active. Corefy can query Payler directly for a payment's current status at any time (covered for all three API versions), and automatically re-checks status after every callback it receives.


Additional info

  1. Only the H2H Merchant account flow is available for Payler - there is no separate Provider account/Payouts integration.
  2. Payler supports 3D Secure card payments (3DS1 and 3DS2), including the 3DS Method step; the redirect/challenge flow is handled automatically by Corefy.
  3. Real-time callback-based status updates apply only when your account is connected with API version v2.1 - Corefy registers a callback URL with Payler for that version. With API versions v1/v2, final status is obtained through the 3DS completion step plus Corefy's automatic reconciliation; no callback is registered with Payler.
  4. When connected with the default API version (v2), make sure your integration sends full browser/device data (user agent, screen size, color depth, timezone, language) with every Sale request. This is collected automatically if you use Corefy's standard checkout/SDK; a custom server-to-server integration that omits it entirely can cause the request to fail with a server error instead of a normal decline.
  5. Supported currencies: USD, EUR, RUB, KZT - confirm with your account manager which ones are enabled for your specific Payler account.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify Key and Password match the selected environment (sandbox vs production) and API version
  • "Customer email is required" error -> required when your account uses the default API version (v2); add customer.email to the request, or confirm with your account manager which API version your account uses
  • Refund rejected as invalid amount -> if your account is connected with API version v2.1, only full-amount refunds are supported; ask your account manager about using API version v1/v2 if you need partial refunds
  • Currency or service is not supported -> confirm allowed currencies/features in your Payler account and in Corefy
  • Not sure which API version your account uses? -> ask your Corefy account manager or your Payler account manager

Question

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