🛠️
Integration Guide
  • 🔎Overview
    • 👋Welcome to XGateway
      • Integrate with XGateway
      • Supported currencies
      • KYC
  • ⚙️Integration Guides
    • Crypto Payments using Checkout
    • SEPA Secure payments using Checkout
    • Alternative Payment Methods using Checkout
    • Crypto Payments using API
    • Advanced features of Invoice creation
  • ❔Miscellaneous
    • Keys and authentication
    • Check transaction status
    • Environments
    • Invoice currencies
    • Deposit data confirmation
    • Callbacks
      • Transaction callback
      • Bank Account callback
      • KYC callback
    • Withdrawal initiation with API
    • Disputes resolution
  • 💱Payment flows
    • Transaction flowchart
    • KYC checks diagram
    • Confirmation subprocess
    • User flow for Crypto Payments
    • User flow for SEPA Secure
    • Fees structure
      • Adjustable BTC Minimum Deposit Fee Framework
  • 🏤Back office
Powered by GitBook
On this page
  1. Miscellaneous
  2. Callbacks

Bank Account callback

Once you create a bank account for your customer within the SEPA Secure flow, there may be a delay between the account being created and activated. Usually this happens only with the USD accounts. To keep you informed, we will send you a callback once the bank account is activated and ready to receive fiat deposits.

For the time being, SEPA Secure is provided only within the Checkout flow. There is no need to receive this type of callbacks.

Sends the bank account details to you

POST https://your-callback-url-here.com/endpoint-to-handle-bank-accounts

Request Body

Name
Type
Description

callbackType

"bank_account"

The type of callback

accountNumber

String | null

The Bank account number

bic

String | null

The Bank Identifier Code

country

String

The Bank account country

currency

String

customerId

String

The unique customer ID in the merchant system

hash

String

The base64-encoded hash is generated using the sha512 algorithm and includes the customer ID, currency, and secret key.

The string that will be hashed: {customer ID}.{currency}.{secretKey}.

iban

String | null

The virtual International Bank Account Number

sortCode

String | null

The six-digit number used in the UK and Ireland to identify the specific bank and branch. Used for GBP

status

String

The status of the Bank account. "PENDING" or "ACTIVE"

The callback URL is the URL you provide during the sign-up process.

The callback you get after a confirmed or failed transaction might look like this:

{
  "callbackType": "bank_account",
  "accountNumber": "00386255",
  "bic": "CFTEMTM1",
  "country": "GB",
  "currency": "USD",
  "customerId": "demo_customer_id",
  "hash": "[HASH]",
  "iban": "MT36CFTE28004000000000003225049",
  "sortCode": "040679",
  "status": "ACTIVE"
}

The callback data here is presented only for the demo purpose.

You may then handle this information as necessary. You don't need to send us anything back other than a success status so that we know the callback has been received and handled on your side.

PreviousTransaction callbackNextKYC callback

Last updated 6 days ago

The Bank account

❔
currency