Issue Debit Cards at Global Scale

A Fyatu debit card is linked directly to a cardholder's account balance and draws funds in real time at the point of transaction — functioning like a traditional bank-linked debit card. A prepaid card is pre-funded before use and typically has a fixed or reloadable balance that is not connected to an underlying account ledger. For neobanks and digital wallets with a running balance per user, debit cards are the natural fit; for controlled-spend programs like employee benefits or gift cards, prepaid cards offer more structural flexibility.

When a cardholder initiates a purchase, Fyatu routes the authorization request to a webhook endpoint you configure. Your server receives a structured JSON payload containing the transaction amount, merchant details, MCC code, and cardholder ID — and must return an approve or decline response within the authorization window. This gives your platform real-time spend control without pre-funding card balances or relying on static limits set at card creation. JIT authorization is especially valuable for programs where available balance fluctuates frequently, such as payroll cards or multi-user wallet products.

Yes. Fyatu provides BIN access for both Visa and Mastercard debit card programs. You can configure your card product to issue on a specific network, or offer cardholders a choice of network at account creation. Dual-network access is important for programs targeting markets where one network has stronger merchant acceptance than the other, particularly across Africa, Southeast Asia, and Latin America.

Fyatu's spend control API supports per-card and per-cardholder limits across multiple dimensions: daily and monthly transaction count and amount limits, MCC whitelist and blacklist rules, geographic restrictions by country or region, currency restrictions, and single-merchant locks. All controls can be set at card creation or updated dynamically via API without reissuing the card. Changes take effect immediately — the next authorization attempt reflects the updated rule set.

Yes. Apple Pay and Google Pay tokenization is native to every card issued through Fyatu's platform — no separate wallet partnership, no additional API calls, and no cardholder enrollment flow required. The token provisioning happens at the BIN and network level, which Fyatu manages. Your cardholders can add their debit card to Apple Wallet or Google Wallet immediately after issuance using the standard device flow.

Most programs complete KYB onboarding in 3–5 business days. Fyatu's sandbox environment is available immediately upon registration, so your engineering team can integrate the card issuance, JIT authorization, and webhook APIs in parallel with compliance review. Total time from API registration to first live card issued is typically 2–4 weeks for programs with standard configurations — significantly faster than the 6–18 months required to obtain direct bank sponsorship.