EasyTransfer

Supports in this guide: Payments, Payouts

Provider website: not reliably confirmed at the time of writing (the website on file for this provider currently belongs to an unrelated car-transfer company; confirm the current website with your account manager before sharing it with anyone)

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

Choose account type
Get your credentials (from EasyTransfer)
Connect in Dashboard
Send an API request

Choose account type

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

If you do H2H card payments (card data sent directly) -> choose H2H Merchant account
If you do card/card-transfer/crypto payments via a hosted page, or payouts -> choose Provider account

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

Prerequisites: get from EasyTransfer

Contact your EasyTransfer account manager to get your account verified. You'll also generate an RSA key pair (PEM, pkcs8) yourself - EasyTransfer signs every request/response with it.

For H2H Merchant account:

Client Code Name -> Corefy field client_code_name.
Private Key -> Corefy field private_key -> the key you generated; used to sign every request.
Public Key (optional) -> Corefy field public_key -> only needed to (re)register a brand-new key pair with EasyTransfer; if your account's key pair is already registered on EasyTransfer's side, leave this empty.
API Type -> Corefy field api_type -> Ecommerce, P2P, or Direct Flow.
Fee Calculation Type -> Corefy field fee_calculation_type -> Inner or Outer.
Terminal ID (optional) -> Corefy field terminal_id.
Account ID (optional) -> Corefy field account_id.
If you use Apple Pay: Apple Pay Flow (3rd party/Self hosted), Apple Pay Merchant ID, Apple Pay Display Name, Apple Pay Merchant ID Certificate (file) and its Certificate Password.

Note

During the connection test, Corefy automatically fetches EasyTransfer's own public key and stores it for verifying EasyTransfer's responses - you don't need to supply it yourself.

Important

API Type = Direct Flow uses a different credential pair - Merchant ID and Secret Key - instead of Client Code Name/Private Key, and routes transactions through a different provider-hosted checkout flow. Confirm with your account manager before using this mode; Ecommerce/P2P cover the standard integration.

For Provider account:

Client Name -> Corefy field client_name.
Private Key -> Corefy field private_key.
Public Key (optional) -> Corefy field public_key -> same rule as above (only for a brand-new key pair).
Fee Calculation Type -> Corefy field fee_calculation_type -> Inner or Outer.
Terminal ID (optional) -> Corefy field terminal_id.
Account ID (optional) -> Corefy field account_id.
Default Language (optional) -> Corefy field default_language -> UK, RU, or EN; controls the language of EasyTransfer's hosted payment page. If not set, EasyTransfer applies its own default.
API URL (optional) -> Corefy field api_url -> leave as default unless your account manager tells you otherwise.

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

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

Client Code Name
Private Key
Public Key (optional)
API Type
Fee Calculation Type
Terminal ID (optional)
Account ID (optional)
Test Mode -> (enable if you are using sandbox credentials)
Apple Pay fields, if you use Apple Pay (optional)

Choose Currency / Features; check with your Corefy account manager which are enabled for your account.

Success

You have connected EasyTransfer H2H Merchant account!

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. For Ecommerce/P2P API types, this is a direct card submission with a possible 3D Secure (v1 or v2) redirect; browser/device data for 3DS2 is collected automatically by the checkout layer, not sent in this request.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
      "service": "payment_card_uah_hpp",
      "currency": "UAH",
      "amount": 10
    }
  }
}

This connector also supports RUB.

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "payment_card_uah_hpp",
      "currency": "UAH",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith"
      }
    }
  }
}

customer is entirely optional. customer.name is only used as a fallback - by default the name embossed on the card is sent instead, if available.

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

strict_card_holder_validation -> optional, boolean - rejects the sale upfront with "Card holder name is required" if neither the card's embossed name nor customer.name is available, instead of letting EasyTransfer decide.

Refunds

EasyTransfer supports partial refunds, but only one refund per payment (no multiple partial refunds against the same payment).

Apple Pay / Google Pay

Both are supported for this account type once the relevant Apple Pay fields are filled in (Google Pay uses your platform-level Google Pay configuration, no EasyTransfer-specific fields). Confirm with your Corefy account manager whether these are enabled for your account before relying on them.

Payments processing (connect Provider account, create payment-invoice)

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

Client Name
Private Key
Public Key (optional)
Fee Calculation Type
Terminal ID (optional)
Account ID (optional)
Default Language (optional)
API URL (optional)
Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected EasyTransfer Provider account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice and redirects the customer to an EasyTransfer-hosted page to complete the payment.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
      "service": "payment_card_uah_hpp",
      "currency": "UAH",
      "amount": 10
    }
  }
}

This connector also supports card_transfer_uah_invoice (UAH) and three crypto services: bitcoin_btc_hpp, ethereum_eth_hpp, tether_erc20_usdt_hpp.

Note

For every service except card payments, the hosted page shows the customer a QR code to complete the transfer/crypto payment.

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "payment_card_uah_hpp",
      "currency": "UAH",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123"
      }
    }
  }
}

customer is entirely optional - it's only used for your own reconciliation, EasyTransfer's hosted page doesn't need any of it.

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

No Options or Constants are configured for this flow.

Important

This flow does not support refunds - use the H2H Merchant account if you need refunds.

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

Connect Provider account in Corefy Dashboard

Uses the same Provider account connection as Payments above - one connection covers both directions, nothing extra to fill in for payouts specifically.

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends funds directly to a card.

Payout - MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "0dde9e79-2c64-4703-adaf-93d710633401",
      "service": "payment_card_uah",
      "currency": "UAH",
      "amount": 10,
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

Important

fields.card_number is required for card payouts. This connector also supports card payouts in EUR, bank transfer payouts (fields.account_number as IBAN, plus fields.beneficiary_full_name and, for UAH only, fields.beneficiary_itn) in UAH/EUR, and crypto payouts (fields.wallet_id) in BTC/ETH/USDT.

Payout - MAX (card payout in EUR)

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "3c6d2f8e-8a2a-4e7a-9b1a-2f6a7b9c0d1e",
      "service": "payment_card_eur",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "date_of_birth": "1990-01-01",
        "address": {
          "country": "FR"
        }
      },
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

customer is required only for card payouts in EUR (first/last name, date of birth, country) - card payouts in UAH, bank transfer, and crypto payouts don't need it. Anything you don't send for a EUR card payout falls back to the Constants below.

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

No Options are configured for this flow.

Constants (fallback fields)

Constants are static values that Corefy can send to the provider instead of dynamic data from your API request, when those fields are missing in the request. These are only used for card payouts in EUR.

Priority (predictable rule): 1. If a value is present in the request -> Corefy uses the request value 2. Else if the constant is set -> Corefy uses the constant 3. Else -> provider may reject the request or apply its defaults (depends on provider)

Currently available constants (constant -> Corefy API field)

FIRST_NAME -> customer.name (first part)
LAST_NAME -> customer.name (second part)
COUNTRY -> customer.address.country
DATE_OF_BIRTH -> customer.date_of_birth

Additional info

Callback routing is automatic - Corefy generates the callback/return URLs per transaction, nothing to configure in EasyTransfer's own back-office.
Bank transfer and crypto payouts are transliterated/formatted automatically where needed (e.g. the beneficiary name for a UAH bank transfer is sent in Cyrillic, for a EUR one in Latin) - send real customer data for best results.

FAQ / Troubleshooting

Invalid credentials / auth error -> verify the credentials for the selected account type and environment - H2H Merchant account and Provider account use entirely different credential sets
"Card holder name is required" on sale -> only happens if strict_card_holder_validation is enabled and neither the card's embossed name nor customer.name is available
Refund fails on the Provider account flow -> refunds aren't supported there - use the H2H Merchant account instead
Currency or service is not supported -> confirm allowed currencies/features in your EasyTransfer account and in Corefy
Not sure which API Type to pick? -> Ecommerce/P2P cover standard card processing; Direct Flow is a separate, less common mode with its own credentials - ask your account manager if unsure

Question

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