Prepaid Card Issuing API

Funds are loaded via Fyatu's Balance Load API — a single API call specifying the card ID, load amount, and currency. The balance is credited to the card in real time and a webhook event is dispatched confirming the load. You can load cards individually or in bulk using the batch load endpoint, which accepts an array of card IDs and amounts in a single request. Your program wallet must hold sufficient balance to cover the loads — Fyatu deducts from your program float at the time of each load operation.

Yes. Fyatu supports single-use card issuance — the card is authorized for one transaction and automatically cancelled after the first successful authorization, regardless of whether the full balance is spent. Single-use prepaid cards are ideal for one-time vendor payments, supplier disbursements, research incentive payments, and any program where re-use by the cardholder would be undesirable. The card number, expiry, and CVV are returned in the issuance API response and can be transmitted to the recipient via your platform.

By default, the balance on an expired prepaid card remains on record and can be refunded to your program wallet via the Card Sweep API. Fyatu also supports automatic sweep rules configured at the card product level — when a card reaches its expiry date, any remaining balance is automatically returned to your program float without requiring manual intervention. This prevents balance leakage across large portfolios where individual card balances may be small but aggregate to significant amounts.

You define an MCC whitelist at the card product level — a list of four-digit Merchant Category Codes representing the merchant types where spending is permitted. When a cardholder attempts a transaction, Fyatu checks the merchant's MCC against the whitelist before the authorization is approved. Any transaction at an MCC not included in the whitelist is automatically declined at the card network level, with no webhook call to your server required. MCC whitelists can be updated via API and apply to all cards issued under the product definition.

Yes. Fyatu supports both virtual prepaid card issuance (instant, digital credentials only) and physical prepaid card production with custom card art, embossing, and global mail fulfillment. Physical card programs require a minimum production run and a longer lead time than virtual issuance, but both card types share the same API for balance management, spend controls, and lifecycle operations. Hybrid programs — where a virtual card is issued instantly and a physical card follows by post — are fully supported.

Going directly to Visa or Mastercard as a principal BIN holder requires a Tier 1 bank relationship, significant capital reserves, extensive compliance certification, and 12–24 months of onboarding. Fyatu's BIN sponsorship model gives you access to both Visa and Mastercard prepaid BINs under Fyatu's pre-approved principal membership, reducing the path to first card issued from over a year to a matter of weeks. The trade-off is that Fyatu operates as the principal BIN holder on your behalf — which is the standard model for virtually every fintech card program that is not a top-tier bank.