Card management
The Card management API is about how to create and manage your cards through OpenAPI.
Cards are divided into B2B cards and B2C cards, suitable for different business needs:
B2B Card
cards are suitable for internal use within enterprises. All cards are registered under the company's Business Account, and all cards share the balance.
API
Create a card
- For B2B cards.
Card number/expiration date/cvv Randomly generated by backend.
For security reasons, we do not return card detail data in the standard API, if you need to access the full card information, please view it through the Get Full Card Information API. We strongly discourage you from storing full card information in the database.
Lock a card
If you want to temporarily deactivate the card, then please change the card status to Locked via the card lock API, the Locked status of the card will not allow any transactions.
Unlock a card
If the temporary deactivation is expected to be terminated, then the card can be brought back into normal use via the Unlock Card API.
Terminated a card
If it is decided that the card is no longer to be used, the card is terminated via the Card Termination API.
Edit card limit configure
In addition to specifying the limit policy when creating the card, it can be modified through the Edit Card Limit Configure API. We support 4 different rules at the same time, if you want to disable a rule, set the amount to 0.
- Transaction: Maximum limit per transaction.
- Daily: Aggregate limit within a single natural day.
- Monthly: Aggregate limit within a single natural month.
- Lifetime: Aggregate limit within whole lifetime.
which is used to terminate the card. Unlike the Lock Card API, terminating a card is permanent and unrecoverable.
Get card list
- For B2B cards, you can query all the cards of the business.
- For B2C cards, you can query all the cards under a certain user.
Get card transaction list
- For B2B cards, you can query all cards or single card transactions.
- For B2C cards, you can query all user cards or single card transactions.
Process 3DS Verification
When a card is used for an online transaction, 3DS verification may be triggered. We support sending the verification code to your server via webhook, and you can then send it to your users in any way you like. We will send the webhook in the following format.
{
"p_business_id": "35cc45cc-c418-4154-8f12-2dda715d0433",
"card_reference_id": "33cc2ca1-b4bf-4516-9962-31c67a885eeb",
"verification_id": "03e69dd9-a70c-4b0f-b084-c0ee077772fb",
"business_name": "speed pay",
"card_num": "356772******8213"
"transaction_currency": "HKD",
"transaction_amount": "-101",
"merchant_id": "666666660057123",
"merchant_country": "HK",
"merchant_city": "",
"merchant_name": "Bindo Simulator Test",
"p_created_at": "2025-03-04T03:32:11.051702Z"
"otp_code": "123456" // 验证码
}
Realtime Webhook
If you would like to receive real-time notifications of transactions via webhook, please contact us to configure the webhook url.
For each transaction we will send the following transaction notification:
Actions
| Action | Description |
|---|---|
| Authorization | When new transaction authorized |
| Reversed | When transaction void from acquirer side |
| Settled | Settled an authorized transaction |
{
"action": "Authorization",
"card_transaction": {
"id": "33cc2ca1-b4bf-4516-9962-31c67a885eeb",
"p_business_id": "35cc45cc-c418-4154-8f12-2dda715d0433",
"card": "03e69dd9-a70c-4b0f-b084-c0ee077772fb",
"status": "Declined",
"type": "Sales",
"transaction_currency": "HKD",
"transaction_amount": "-101",
"local_currency": "HKD",
"local_amount": "-101",
"final_local_amount": "-101",
"calculated_fee": "0",
"merchant_id": "666666660057123",
"merchant_country": "HK",
"merchant_city": "",
"merchant_name": "Bindo Simulator Test",
"p_created_at": "2025-03-04T03:32:11.051702Z"
}
}