Welcome to Axys API Gateway

Welcome to the Axys Cards developer documentation. Axys is a turnkey aggregation, automation, and orchestration layer for card issuing — unifying the issuer, program manager, and issuer processor roles, with built-in network, payment, and digital asset rails, so that a single card balance can be funded, held, and spent across both traditional banking and blockchain networks without the integrator needing to build or coordinate separate systems for each.

This page gives you the lay of the land. If you're setting up a new Tenant or Program from scratch, or you already hold program-level API credentials and just want to make your first call, both paths are covered below.

Architecture at a glance

This is a multi-Tenant platform, each running one or more card Programs.

flowchart LR
    A["Platform"] --> B["Tenant"]
    B --> C["Program"]
    C --> D["Cardholder"]
    D --> E["Cards, Accounts & Wallets"]

This is the short version. For the full hierarchy, terminology, and how credentials map to each layer, see Program Architecture. Everything else in these docs assumes you're familiar with that page.

What you can build

What makes the platform different

A few aspects of the platform are worth understanding early, because they shape how several Concepts pages are written:

A card's balance is a single, unified ledger: regardless of whether it's funded by a bank transfer or by a digital asset deposit, both rails land in the same Card Account, converted dynamically to the Program's base currency. Integrators don't need to reconcile separate fiat and crypto balances. See Accounts, Wallets & Deposit Addresses.

Digital asset funding is automatic and zero-integration: when a card is issued, the platform generates its unique deposit addresses (potentially across 80+ chains) immediately. There's no address registration call to make; you simply retrieve and share the address. See Funding & Deposits.

Settlement is T+0: funds move into a card's available balance on a same-day basis rather than the multi-day settlement cycles common in traditional card programs. See Transactions & Fees.

Digital asset custody is institutional-grade: private keys are never held in a single location; key shares are distributed using HSM-backed Multi-Party Computation (MPC) with a Threshold Signature Scheme (TSS) across independently regulated parties. See Security, Compliance & Data Protection.

Currencies beyond USD/EUR/GBP/CAD are supported natively: including emerging-market currencies, without forcing a conversion to a major currency before they can be held or spent.

Express cardholder onboarding and card issuance: aside from edge cases, a cardholder's onboarding process can be completed straightforwardly programmatically in only a few minutes, and cards can be issued instantly.

Issuing is global by default: Programs can onboard cardholders and issue Visa and Mastercard cards without being restricted to specific jurisdictions, beyond standard OFAC sanctions screening and case-by-case compliance matters.

There's no platform-imposed ceiling on loads or spends: beyond whatever transactionLimit a Program chooses to configure for itself, its cardholders, and its cards, the platform does not impose its own limits.

Dynamic currency conversion is built into every deposit and transaction: funds can originate in practically any source fiat currency or digital asset and are converted into the card's base currency automatically.

Compliance and infrastructure assurance is built in: the platform runs on PCI-DSS, ISO 27001, SOC 2, and Uptime Institute–certified infrastructure, with a 99.99% uptime commitment (less than 53 minutes of unplanned downtime per year). See Security, Compliance & Data Protection for the full picture (this page will expand as further detail becomes available).

Where to start

📘

Setting up a new Tenant or Program? Start with Platform Onboarding: Overview & Checklist. You'll need to generate a certificate signing request, receive your mTLS client certificate, and configure IP allowlisting before any API calls (including staging calls) will succeed.

👍

Already holding program-level credentials and a client certificate? Head to Authentication & Environments, then Your First API Call.

How these docs are organized

Environments

The platform provides separate staging and production environments, each with its own base URL, API credentials, and mTLS certificate:

Full details, including how authentication works across both, are covered in Authentication & Environments.

What's next

• Program Architecture — the hierarchy and terminology used throughout these docs
• Platform Onboarding: Overview & Checklist — for new Tenants and Programs
• Authentication & Environments — for developers ready to make their first call