A cardholder is the user or responsible party for a card. Before creating a card, merchants usually need to create a cardholder and associate the card with that cardholder.
In general:
In the issuing flow, the cardholder defines card ownership and supports later management. Creating the cardholder first helps to:
Required fields may vary depending on product rules and account activation status. Common information includes:
| Field | Description |
|---|---|
| Name | Cardholder name, usually expected to match submitted information |
| Used for contact or related notifications | |
| Phone 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 cardholder usually has one of the following statuses:
| Status | Description |
|---|---|
| Active | The cardholder can be used to create and bind new cards |
| Disabled | The cardholder cannot be used to bind new cards |
When a cardholder is disabled, new cards cannot currently be bound to that cardholder. Actual status names and display methods depend on the platform page.
In some scenarios, the cardholder must complete the required agreement confirmation before using a card. When integrating through the API, make sure the corresponding confirmation flow is completed in your own system or business process.
Confirm that:
Cardholders can be created through the Dashboard or API. Available methods depend on the account capabilities.
When integrating through the API, use the Create cardholder API to create a cardholder and track status changes through callbacks or query APIs.