A cardholder is the user or responsible party for a card. Before creating a card, merchants usually need to create a cardholder and link the card to that cardholder.
In general:
In the issuing flow, the cardholder is used to define card ownership and support later management. Creating the cardholder first helps:
The required fields may vary depending on product rules and account activation status. Common information includes:
| Field | Description |
|---|---|
| Name | Cardholder name, usually matching the submitted information |
| Used for contact or receiving related notifications | |
| Mobile number | Used for contact or verification |
| Nationality / country or region information | Used for verification and compliance processing |
| Billing address / contact address | Used for cardholder records, billing information matching, or compliance processing |
After a cardholder is created, the following statuses are common:
| Status | Description |
|---|---|
| Active | The cardholder can be used to bind and create new cards |
| Disabled | The cardholder cannot continue to bind new cards |
When a cardholder is disabled, new cards cannot currently be bound to that cardholder. The actual status name and display method depend on the platform page.
In some scenarios, the cardholder must complete the corresponding agreement confirmation before using the card. For API integrations, the merchant should also ensure that the required confirmation process has been completed in its own system or business flow.
Confirm the following:
Cardholders can be created through the Dashboard or API. Available methods depend on the account capabilities.
For API integrations, create the cardholder through the corresponding endpoint and monitor status changes through callbacks or query endpoints.