Manage Your Cardholders

The required documents are configurable at the Card Program level. Typically this includes a government-issued photo ID (passport or national ID card), proof of address, and a selfie or liveness check. You can configure different KYC tiers — for example, a lighter flow for low-spend products and full verification for higher limits.

Cardholder PII (name, date of birth, address, identity documents) is stored securely within Fyatu's PCI-DSS and GDPR-compliant environment. Your platform receives a cardholder ID token to reference the record. Raw PII is only accessible via authenticated API calls — it is never stored on your servers.

Yes. A single cardholder profile can be linked to cards issued under different Card Products within your Card Program. For example, the same cardholder could hold a virtual prepaid card for online spending and a physical debit card for in-store use.

You can freeze, unfreeze, or permanently terminate a cardholder via a single API call to the cardholder status endpoint. The change takes effect in real time — all cards linked to that cardholder will reflect the new status immediately, blocking or restoring authorizations accordingly.

When you freeze a cardholder, all cards linked to that cardholder are suspended immediately. Any authorization attempts on those cards will be declined while the freeze is active. Unfreezing the cardholder instantly restores card functionality without requiring you to reissue the cards.

Yes. The Fyatu API provides a transactions endpoint that returns the full history for a cardholder or for an individual card. You can filter by date range, card, merchant category, and transaction status. Webhooks are also available for real-time transaction event notifications.