Cards

Card payments are the most common payment method on Zenith. Cards are supported across every integration path.

Supported schemes

• Visa
• Mastercard
• American Express
• JCB
• Union Pay

Scheme availability may depend on your merchant account configuration and program.

Tokenisation

Tokenisation lets you store a card for later reuse without holding card data yourself. Zenith returns a token that you can charge later through your normal payment flow.

Card tokenisation is available on two surfaces:

• Hosted Checkout (Mode 1) — launch the JavaScript Plugin in Mode 1 and the customer is prompted to capture card details; a token is returned via redirect and callback. See Hosted Checkout → Cards.
• REST API — the /v2/cardproxies endpoint provides a direct card-tokenisation surface for backend-led integrations. See /openapi for the exact contract.

note

/v2/cardproxies only tokenises cards. It does not tokenise bank accounts. For real-time bank account tokenisation, use PayTo.

3D Secure (3DS)

3DS is handled as part of the hosted payment flow when the issuer or scheme requires authentication. Merchants do not implement 3DS challenge handling directly — the hosted flow presents the challenge and returns the outcome through the normal result path.

Card category reporting

The callback payload returns a cardCategory field (for example International Cards or Domestic) so you can report on card geography and adjust fees or reconciliation accordingly. See Callbacks and Validation — Payload Reference for the full payload shape.

Availability

Integration	Supported?	Notes
Hosted Checkout	✓	One-off, tokenise (Mode 1), preauth (Mode 3), custom (Mode 2)
Payment Links	✓	Enabled at merchant-account level
REST API	✓	Card tokenisation via /v2/cardproxies

Related

• Payment Methods
• Hosted Checkout → Cards
• Hosted Checkout
• Test Cards
• /openapi — REST API reference