Platform

Integration and API

What your engineering team connects, in what order, and what they do not have to build.

What you integrate

Create cardholders, issue virtual cards instantly, and request physical cards into the fulfilment workflow.

Initiate and track balance funding from supported cryptocurrencies and stablecoins through on-ramp connectivity.

Set limits, apply MCC restrictions, freeze and unfreeze cards, and manage PIN and regional settings.

Subscribe to webhooks for authorisation, settlement, funding, dispute and card-status events rather than polling for state.

Pull transaction, balance and programme reporting for reconciliation and regulatory submissions.

A test environment with simulated authorisations, so flows can be proven before any real card exists.

Capability	Built by you	Provided by Zen Card
Customer identity and KYC decisioning	Yes, under your regulated process	Technical hooks to attach the outcome
Customer-facing app or portal	Yes	APIs and, optionally, reference UI
Card issuance and personalisation	No	Yes
Authorisation and settlement	No	Yes
Scheme connectivity and certification	No	Yes
FX and local-currency conversion	No	Yes
Ledger of programme balances	Optional shadow ledger	Yes, authoritative
Dispute case management	Customer comms	Initiation and scheme process

The short version

You build the customer experience and own the compliance decision. Everything downstream of "this customer is approved and wants a card" is ours.

1
Sandbox credentials
Your team receives sandbox API keys and the reference documentation, and can begin building before commercials are finalised.
2
Cardholder and issuance flows
Implement cardholder creation and virtual card issuance first; it is the shortest path to a demonstrable end-to-end flow.
3
Funding and on-ramp
Connect funding, confirm asset support for your jurisdictions, and validate balance behaviour against the authoritative ledger.
4
Webhooks and reconciliation
Subscribe to authorisation and settlement events, and prove your reconciliation against platform reporting.
5
Controls and edge cases
Implement freeze, limits, MCC restrictions, reissuance and dispute initiation. These are what support teams actually use daily.
6
Production certification
Move to production credentials once flows are proven in sandbox and programme onboarding has completed scheme approval.

Full API reference

Detailed endpoint documentation is provided to institutions under programme onboarding. Contact us for sandbox access and the current reference.

We will provision test credentials and share the API reference so your team can scope the build.