Issue Cards That Self-Destruct After One Use

After a one-time card is authorized for its first transaction, Fyatu cancels the card and automatically sweeps any remaining balance back to your program wallet. For example, if you issue a card loaded with $100 and the cardholder spends $73, the remaining $27 is returned to your float immediately after the authorization event — no manual sweep call required. The sweep is atomic: it happens in the same processing step as the authorization, so there is no window where funds are stranded on a cancelled card.

No — the auto-cancel trigger fires only on a successful authorization (an approved transaction), not on a decline. If a transaction is declined for any reason (insufficient balance at the merchant, network error, 3DS failure), the card remains active and can be retried. The card is only cancelled and its balance swept after Fyatu records an approved authorization response from the card network. This ensures the card remains usable until the intended payment has actually succeeded.

Yes. Fyatu's batch card issuance endpoint accepts an array of card creation objects in a single API call and returns all generated credentials in one response. Each card in the batch can have an individual load amount, currency, and expiry window — so you can issue 10,000 uniquely valued reward cards in a single request. Batch results are returned synchronously for batches up to 1,000 cards; larger batches are processed asynchronously and delivered via webhook when ready.

Yes. Like all Fyatu card types, one-time cards inherit the spend controls defined on their card product — including MCC whitelists, merchant ID locks, currency restrictions, and geography filters. You can also override any of these controls at the individual card level via the card creation API. A one-time card locked to a specific merchant ID, for instance, can only be authorized by that merchant — combining single-use semantics with merchant specificity for maximum control.

One-time cards are digital-only — they exist as card credentials (PAN, expiry, CVV) without a physical form factor. Physical card production inherently involves a fulfilment lead time that is incompatible with the single-use, instant-issuance model. For use cases where a physical card is needed for a single purpose (for example, a travel expense card for a specific trip), Fyatu's prepaid card product with a short expiry window and spend lock is the recommended approach.

Transactions on one-time cards appear on the merchant's acquiring statement exactly like any other Visa or Mastercard transaction — the single-use nature is invisible to the merchant and to the card network. On your platform side, each card has a unique card ID that you can attach to metadata (order ID, campaign ID, employee name) at issuance time. Fyatu's transaction webhook includes this metadata, allowing your platform to reconcile each charge against the business context you defined when the card was issued.