Skip to content

Logo

TapBank

Payment solution for online business. Processing of incoming and outgoing payments

Supports in this guide: Payments, Payouts

Provider website: tapbank.info

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

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

Prerequisites: get from TapBank

Send a connection request at tapbank.info ("Get started") or contact your TapBank account manager directly to get your account verified and receive the following credentials.

  • API key -> Corefy field api_key.
  • Signature key -> Corefy field signature_key.
  • Currency -> Corefy field currency -> choose one of KZT, UZS, KGS for your account.

One Provider account is used for both Payments and Payouts.

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

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • API key
  • Signature key
  • Currency
  • Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected TapBank Provider account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice. TapBank returns payment requisites (card or account details) for the customer to pay into; Corefy handles the multi-step init/start/confirm flow with TapBank transparently behind this one request.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "1a2b3c4d-5e6f-4a7b-8c91-2d3e4f5a6b7c",
      "service": "card_transfer_kzt_hpp",
      "currency": "KZT",
      "amount": 100
    }
  }
}

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "2b3c4d5e-6f7a-4b8c-8d02-3e4f5a6b7c8d",
      "service": "card_transfer_kzt_hpp",
      "currency": "KZT",
      "amount": 100,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Doe",
        "email": "test@example.com",
        "phone": "+77001234567"
      }
    }
  }
}

Important

  • If customer.reference_id is missing, Corefy generates one automatically; it does not need to be a real identifier from your side.
  • customer.name, .email, and .phone are optional pass-through - if missing, they're simply not sent.
  • No Options or Constants are configured for Payments.

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

TapBank does not support refunds.

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

Connect Provider account in Corefy Dashboard

Uses the same Provider account connected above - no separate connection step.

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": "e46c311b-bbf3-45e8-ba0f-41c3e45cafe2",
      "service": "payment_card_kzt",
      "currency": "KZT",
      "amount": 100,
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

Important

fields.card_number is required.

Payout - MAX

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "3c4d5e6f-7a8b-4c9d-8e02-3f4a5b6c7d8e",
      "service": "payment_card_kzt",
      "currency": "KZT",
      "amount": 100,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Doe",
        "email": "test@example.com"
      },
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

Important

Same as on Payments: if customer.reference_id is missing, one is generated automatically; customer.name/.email are optional pass-through. No Options or Constants are configured for Payouts.

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

Additional info

  1. Active reconciliation is available - both Payments and Payouts support an active status request in addition to the asynchronous callback.
  2. No recurring - this connector does not support saving/charging a token through Corefy.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify the API key, signature key and currency for the selected environment (test_mode)
  • Currency or service is not supported -> confirm allowed currencies/features in your TapBank account and in Corefy - only KZT, UZS, KGS are available
  • Refund fails -> TapBank does not support refunds through Corefy

Question

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