Skip to content

Logo

Antrpay

Supports in this guide: Payments, Payouts

Provider website: antrpay.com

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

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

Choose account type

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

  • If you do direct card payments (RUB, UZS) -> choose H2H Merchant account
  • If you do redirect-based card or SBP payments, or card/bank transfer payouts -> choose Provider account

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

Prerequisites: get from Antrpay

Contact your Antrpay account manager to get your account verified and receive the following credentials. H2H Merchant account and Provider account are separate connections with independent credentials.

For H2H Merchant account:

  • Public key -> Corefy field public_key.
  • Secret key -> Corefy field secret_key.

For Provider account:

  • Public key -> Corefy field public_key.
  • Method type -> Corefy field method_type -> one of ACQUIRING_ANTRPAY, FPS_ANTRPAY, P2P_ANTRPAY -> confirm with your Antrpay manager which one applies to your account; it determines which currencies/services are available on this connection.
Payments processing (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Public key
  • Secret key
  • Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected Antrpay 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. Antrpay may return a 3D Secure challenge redirect depending on the card.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "bb756e15-428b-47f8-81dd-90014d5eb607",
      "service": "payment_card_rub_hpp",
      "currency": "RUB",
      "amount": 1200
    }
  }
}

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "9c005348-0bd2-4e7f-aa64-b50d0660c01d",
      "service": "payment_card_rub_hpp",
      "currency": "RUB",
      "amount": 1200,
      "customer": {
        "reference_id": "cff9b603-8c74-454f-9b66-73f349f12aec"
      }
    }
  }
}

Important

  • A CVV is required for all currencies except UZS - for UZS, a payment without CVV is accepted and a placeholder value is sent to Antrpay instead.
  • No Constants are configured for this connector - if a customer field is missing, it's simply not sent.

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

Refunds

This connector does not support refunds.

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

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Public key
  • Method type
  • Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected Antrpay Provider account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice; the customer is redirected to Antrpay's hosted page to complete the payment.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "bb756e15-428b-47f8-81dd-90014d5eb607",
      "service": "sbp_rub_hpp",
      "currency": "RUB",
      "amount": 1200
    }
  }
}

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "9c005348-0bd2-4e7f-aa64-b50d0660c01d",
      "service": "payment_card_rub_hpp",
      "currency": "RUB",
      "amount": 1200,
      "customer": {
        "reference_id": "cff9b603-8c74-454f-9b66-73f349f12aec",
        "metadata": {
          "ip": "192.168.72.1"
        }
      }
    }
  }
}

Important

  • customer.metadata.ip is forwarded to Antrpay as the customer's IP address (not required for sbp_rub_hpp).
  • Only the services allowed by the account's Method type are usable on a given connection (card acquiring/P2P services require ACQUIRING_ANTRPAY or P2P_ANTRPAY; sbp_rub_hpp requires FPS_ANTRPAY).

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

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.

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 -> Antrpay parameter)

  • PAYMENT_COMMENT -> comment / message (payment description sent to Antrpay; defaults to Payment if not set)

Refunds

This connector does not support refunds.

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

Connect Provider account in Corefy Dashboard

Payouts use the same Provider account connection as Payments above - no separate connection is needed.

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": "27b3f369-f789-428a-b846-dcee3e3a0eff",
      "service": "payment_card_rub",
      "currency": "RUB",
      "amount": 500,
      "fields": {
        "card_number": "4276******7864"
      }
    }
  }
}

Important

fields.card_number is required for all card-based payout services.

Payout - MAX

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "65c2a15c-2219-4c2b-a0c9-d138f601b25f",
      "service": "payment_card_rub",
      "currency": "RUB",
      "amount": 500,
      "customer": {
        "reference_id": "ffbb1f59-4da2-4c64-8816-8f13df7bdc93"
      },
      "fields": {
        "card_number": "4276******7864"
      }
    }
  }
}

Important

For payout service payment_card_try routed to a TRY bank transfer method, fields.card_number is not used - send fields.account_number (IBAN) and fields.beneficiary_full_name instead. For payment_card_inr, also send fields.ifsc and fields.beneficiary_full_name together with fields.card_number.

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

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.

Currently available constants (constant -> Antrpay parameter)

  • PAYOUT_MESSAGE -> message (payout description sent to Antrpay; defaults to Payout if not set)

Additional info

  1. No callbacks on the H2H Merchant account - Antrpay does not send callbacks to Corefy for H2H payments; payment statuses are updated via active status requests (reconciliation) only.
  2. No refunds - neither the H2H Merchant account nor the Provider account support refunds for this connector.
  3. Method type gates availability - a Provider account connection is configured for one Method type (ACQUIRING_ANTRPAY, FPS_ANTRPAY, or P2P_ANTRPAY); only the currencies/services matching that type can be used on that connection.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify the credentials for the selected account type and environment (test_mode) - H2H Merchant account and Provider account use entirely different credential sets
  • Service/currency not available -> check that the Provider account's Method type matches the service you're trying to use
  • Payment fails without CVV -> a CVV is required for all currencies except UZS
  • Not sure which account type to use? -> H2H Merchant account is for direct card payments (RUB, UZS); Provider account covers redirect-based card/SBP payments and payouts

Question

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