Skip to main content
Cardholders are the end users who receive and use cards. Each cardholder belongs to a single partner and must pass KYC before cards can be issued.

KYC methods

Contro supports two ways to submit KYC when creating a cardholder. Choose the method that best fits your integration:

Create a cardholder

Creating a cardholder and submitting KYC happen in a single request. The example below uses the web link method (kycSource: "web"), where KYC is completed via a hosted session. See the individual KYC method pages for other approaches. First, create a KYC session via POST /partner/kyc-sessions and wait for the user to complete it, then create the cardholder:

Required fields

Optional fields

The residence address fields apply to share token methods (kycSource: "sumsub"). Contro reads the address from the shared verification when the document carries one, and falls back to these fields when it does not — a passport, for example, carries no address. Send all five together; a partial address is ignored. See Residence address.

Residence address

Card issuance requires a complete residence address: street, city, state or province, country, and postal code. Where that address comes from depends on the KYC method: For share token methods, the address extracted from the verified document always takes precedence over the one you send. Send the fields when your user verified with a document that carries no address — a passport is the common case. Without them, the cardholder is created, but card issuance later fails because the address is missing. You can supply the address when creating the cardholder, or add it later with PATCH /partner/cardholders/{id}.

Initiate KYC for a card program

After creating the cardholder, initiate KYC verification for a specific card program. Cards cannot be issued until KYC is approved for that program.
Response:

KYC status

Check KYC status

The cardProgramId query parameter is required.
Response:

KYC status lifecycle

In sandbox mode, KYC is auto-approved for testing. In production, verification is performed by the KYC provider.

Update a cardholder

Update mutable fields on an existing cardholder:
Updatable fields: email, phoneNumber, residenceAddressDetail, residenceCity, residenceStateProvince, residenceCountryCode, postalCode. Address fields are merged into the cardholder — sending only the address leaves email and phoneNumber unchanged. Use this to add a missing address when card issuance failed for one, then retry issuing the card.

List cardholders

Retrieve cardholders with optional filtering:

Query parameters

Get a cardholder

Retrieve a single cardholder by ID:

Response fields