Skip to main content
GET
Get a cardholder

Overview

Returns the full profile of a single cardholder, including address, KYC status, and which programmes can issue for it. The kycRejectionReason field is only present when kycStatus is REJECTED. The terminatedAt field is only present when status is TERMINATED.

KYC Status

Only an APPROVED cardholder can be issued a card, on every programme, every BIN and under every KYC module (since 7 November 2026). The cardholder is declared to the issuer exactly as their identity document shows — their own document, under the country that issued it. WAIVED is a legacy status that is no longer assigned: we hold no identity document for the cardholder. A cardholder still carrying it keeps the cards they already hold but cannot be issued a new one until their kycDocument is submitted and approved.

Programme Eligibility

programEligibility answers whether this cardholder can be issued a card — per BIN, and summarised per programme. It is returned on this endpoint only, not on GET /cardholders. The BIN is where the decision is made. BINs on one programme do not agree about what they require: a programme can hold one BIN that does not require the identity document at issuance alongside others that do. A programme is eligible when at least one of its BINs is.

A cardholder is registered per BIN

Verification is not held once for your account. The issuers behind different BINs each keep their own record of a cardholder and run their own check, so a cardholder verified for one BIN is unknown to the next and has to be registered there too. That is why the answer is per BIN, and why verificationStatus can differ across BINs of the same programme: one VERIFIED, its neighbour NOT_SUBMITTED. A cardholder’s own kycStatus is our verification of them and answers for neither. Where canSubmit is true, POST /cardholders/{id}/submit registers them on that BIN.

What a BIN expects

A BIN that requires verification takes an APPROVED cardholder and nothing else. Your KYC module decides who verifies the cardholder, never whether they must be verified: PENDING, SUBMITTED, REJECTED and WAIVED are never eligible.
Country restrictions are separate and are applied when a card is issued, not here. A cardholder whose nationality or country of residence is restricted on a product’s BIN is refused with 422 CARDHOLDER_COUNTRY_RESTRICTED, naming the country.

Path Parameters

Example

Success Response (200)

What kycDocument looks like on the way back

Changed on 19 October 2026. The returned kycDocument no longer carries frontUrl, backUrl or selfieUrl, and documentNumber is masked to its last four characters. The fields you send on create and on PATCH are unchanged.
Two reasons, and both of them would apply to your own API:
  • A profile fetch should not be a way to open somebody’s passport. Anything holding one of your API keys could page /cardholders and fetch each record, and every response used to hand back a working link to that person’s identity images.
  • The document number is the field used to impersonate its holder. The last four is enough to confirm the document we hold is the one you sent, which is the only thing you need it for.
For a deleted cardholder kycDocument is null outright, whatever was submitted before. When a cardholder is deleted their identity images stop being reachable to anyone, including through our own admin tools — so there is nothing for us to return and nothing for anyone to ask us to produce. If a review screen of your own genuinely needs to display a document, contact support and say which flow needs it. It is granted per account and through an endpoint that records every read.

Conditional Fields

Legacy WAIVED Example

A WAIVED cardholder (legacy status) has not been identity-verified: kycVerifiedAt is not a verification date. They cannot be issued a card until a kycDocument is submitted and approved.

KYC Rejected Example

Error Codes

Authorizations

Authorization
string
header
required

API key from the FYATU CaaS portal. Pass as Authorization: Bearer <key>.

Path Parameters

id
string
required

Response

Cardholder retrieved

success
boolean
Example:

true

status
integer
Example:

200

message
string
Example:

"Cardholder retrieved"

data
object
meta
object