Skip to main content

Card management

The Card management API is about how to create and manage your cards through OpenAPI.

All card transactions will be deducted from your Business Account balance.

API

Create a card

When creating a card, you will need to provide card holder information as well as a limit policy. You can add one or more card holders, the information provided in the card holder will be used for 3DS verification and other scenarios, please provide true and valid information.

Card number/expiration date/cvv Randomly generated by backend.

info

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.
info

which is used to terminate the card. Unlike the Lock Card API, terminating a card is permanent and unrecoverable.

Remote trading decisions

If you want to approve each transaction by yourself, you can use this feature to send each transaction authorization to your server, and you will decide whether to approve the transaction or not. Note that we will send it to your server for decision-making after our decision-making logic (card limits/risk controls, etc.) has been approved.

To use this feature, you need to provide a webhook endpoint, and develop it according to our specification.

POST
Create Card
>
PUT
Edit Card Limit Configure
>
PUT
Card Lock
>
PUT
Card Unlock
>
PUT
Card Termination
>
GET
Get Card
>
GET
Get Card List
>
GET
Get Full Card Number
>