Define Your Card Product

A Card Program is the top-level container that defines program-wide settings like network access, compliance policies, and global limits. A Card Product sits one level below and defines the configuration for a specific type of card — such as a virtual prepaid card or a physical debit card — including its spend controls, MCC rules, and 3DS behavior.

Yes. You can create as many Card Products as you need under a single Card Program. For example, you could have a virtual single-use product for online payments, a physical debit product for everyday spending, and a corporate expense card product — all sharing the same program-level KYC and compliance configuration.

Cardholders are linked to individual cards, and each card is issued under a specific Card Product. If you need to move a cardholder to a different product configuration, you can issue them a new card under the new product. Existing cards remain active on their original product until you deactivate them.

You can define daily, weekly, and monthly transaction count and volume limits. You can also set per-transaction maximums and minimums. These act as defaults for all cards issued under the product and can be tightened or relaxed for individual cardholders via the API.

Typically yes. Virtual and physical cards have different configuration requirements — physical cards require PIN management, embossing rules, and courier integration. It is best practice to create separate Card Products for virtual and physical card types, even if they share the same Card Program.

Fyatu provides a sandbox environment where you can create Card Products, issue test cards, and simulate authorizations and declines without touching live networks. All API calls are identical between sandbox and production — you simply swap API keys when you are ready to go live.