Skip to main content
Use these offer IDs to issue virtual cards in the staging environment. Every virtual card is created against an offer, which determines the card program (network, BIN, and rewards). The offer IDs below are enabled for staging and can be passed straight to createVirtualCard.
Complete KYC firstVirtual cards can only be issued on an account that has completed identity verification. Until the account — and, for a business, its beneficial owners — passes KYC/KYB, getVirtualCardOffers may return empty and createVirtualCard will fail. Run verification before you test. See User KYC Verification for how to submit it, and pull test identities from Testing KYC Flows.
Staging onlyThese offer IDs are accepted only on the staging endpoint (https://transactional-graph.staging.fluzapp.com/api/v1/graphql). They will be rejected in production, where you must retrieve a live offer ID from Get Virtual Card Offers.

​
Staging offer IDs

​
Which offer should you choose?

Each program issues a Mastercard prepaid card, but they differ in where the card can be spent and how it’s funded. Pick the one that matches the behavior you want to test:
The general-purpose program — a standard multi-use prepaid card that can be spent anywhere Mastercard is accepted, within the spend limits you set. Start here if you just want to run the happy path end to end.
A card restricted to a single merchant or brand. Transactions at any other merchant are declined. Use this to test merchant-restricted spend controls — for example, a card that only works at one vendor.
A card funded once, at creation. The balance is loaded up front and spent down — it can’t be topped up afterward. Use this to test fixed-value, disposable card flows like one-off vendor payments or payouts.
A card whose balance can be topped up after creation. Use this to test long-lived cards that get refunded repeatedly — recurring allowances, team cards, or ongoing subscription spend.
Rather than hard-coding an offer ID, we recommend discovering offers at runtime — the returned list reflects exactly what your account is entitled to. It’s a quick two-call sequence.
1

List available offers

Call getVirtualCardOffers and grab an offer_id from the response.
2

Create the card

Pass that offer_id to createVirtualCard. A successful response returns a virtual_card_id with a status of ACTIVE.
Keep spendLimit at or below your available balance — the card is funded from your Fluz balance, so a higher limit fails with an insufficient-balance error. A $5 test is the safest first attempt. You can omit the billing address on your first card to keep the happy path simple; add one later with Add Virtual Card Address.

​
Next steps

Create Virtual Card

The full createVirtualCard reference — inputs, funding, and the card lifecycle.

Testing KYC flows

Test identities that return each verification outcome — approved, declined, and duplicate.
Want to learn more? Contact us at partnerships@fluz.app. Speak with our experts for more info or to request a demo.