Issue Virtual Cards Instantly via API

Virtual card issuance via Fyatu's API completes in under 500 milliseconds in the 95th percentile under normal load conditions. The API returns a fully provisioned card object — including the card number (PAN), expiry date, and CVV — in the synchronous POST response. There is no asynchronous provisioning step, no webhook confirmation required before the card is spendable, and no batch processing delay. This latency profile supports real-time issuance flows where a card must be created and displayed to the user within a single page interaction.

A single-use virtual card is automatically cancelled by Fyatu after the first successful authorization — the card number cannot be used again regardless of remaining balance. A multi-use virtual card remains active and spendable across multiple transactions until its balance is exhausted, its expiry date is reached, or it is explicitly cancelled via the Cards API. Single-use cards are suited for one-time supplier payments and B2B procurement; multi-use cards are suited for employee expense cards, subscription isolation, and recurring spend scenarios.

Yes. Every virtual card issued through Fyatu is eligible for Apple Pay and Google Pay tokenization via the standard device wallet enrollment flow. The cardholder adds the card by entering the PAN, expiry, and CVV into their device wallet app — or your platform can initiate push provisioning via the Token Provisioning API for a seamless in-app enrollment flow. Once tokenized, the card can be used for tap-to-pay at any NFC-enabled terminal worldwide.

Fyatu handles the 3DS 2.0 protocol at the platform level — your virtual cards are enrolled in 3DS automatically, and the challenge flow is managed by Fyatu's Access Control Server integration. When a cardholder completes a 3DS challenge on a merchant site, Fyatu processes the authentication and forwards the result to the card network. From your platform's perspective, you receive a transaction webhook indicating whether the authentication was successful — no separate 3DS SDK integration is required on your side.

Yes. Virtual cards issued via Fyatu support the same spend control capabilities as physical card programs — per-card transaction limits, daily and monthly amount caps, MCC whitelists and blacklists, currency restrictions, and single-merchant locks. Controls are configured at card creation via the issuance API request body and can be updated dynamically via the Card Update API without reissuing a new card number.

Becoming a direct principal BIN holder with Visa or Mastercard for virtual card issuance requires a Tier 1 or Tier 2 bank partnership, extensive PCI DSS and card network certification, and a compliance process that typically takes 12–24 months. Fyatu's BIN sponsorship model provides access to Visa and Mastercard virtual card issuance under Fyatu's pre-approved programme in weeks, without the capital requirements or certification burden of direct participation. This is the architecture used by the vast majority of successful fintech virtual card programs globally.