Skip to main content
This guide walks you through the full flow to issue a card for a customer.

Overview

A customer can receive a card before their KYC is approved, within limits: 5,000 USD loaded per calendar month across all their cards, plus the level 1 limits of the product. Approving the KYC lifts these limits. Some products require a higher level (required_level / required_kyc_level). See KYC levels. Browse the card product catalog to see available products, their limits and fees.

Step 1: Browse card products

Start by consulting the catalog to find the right product for your use case:
Each product specifies its required_level, its required_kyc_level (1, 2 or 3), its limits per KYC level (max_balance, max_reload, then spend_limit_monthly_kyc_level_1 and max_card_per_user_kyc_level_1 for KYC level 1, spend_limit_monthly_kyc_level_2 and max_card_per_user_kyc_level_2 for KYC level 2 and above), features (google_pay, apple_pay, atm_available, three_d_secure, addons), initial load requirements (initial_load.required, initial_load.min, initial_load.max) and the fees of your plan (fees.creation_fee, fees.reload_fee, and fees.annual_fee for the 493 ATM card).

Step 2: Create a customer

The customer is created with verification_level: basic.
Response includes a verification_url — redirect your customer there. You can call this endpoint again at any time to get the link back, or a new one if it expired.

Step 4: Wait for KYC approval

Listen for the kyc.approved webhook, or check the status endpoint:
Once approved, the customer automatically upgrades to verification_level: verified.

Step 5: Create a card

Pick a card product from GET /cards/products and create the card with its code:
You do not send a name: the card carries the customer’s first and last name (the identity verified by KYC when available), returned as name_on_card.
amount is the initial load. It is required when the product has initial_load.required: true, within its min and max.
Card creation debits your ops balance (cards_mastercard or cards_visa, depending on the product brand) of total_charged: the initial load, the creation_fee of your plan (card_fee) and its reload_fee applied to the initial load (service_fee). The fees of your plan are listed on each product in GET /cards/products. Example on Découverte (5 USD creation, 1 USD + 1.9% reload): a card loaded with 100 USD costs 100 + 5 + 2.90 = 107.90 USD. For the 493 ATM card, card_fee also includes the first year of its annual fee.
On the free Découverte plan, only virtual cards can be created, with no limit on the number of cards or the amount loaded. A physical card returns 403 PLAN_LIMIT_REACHED. See Plans and Pricing.

Step 6: Card activated

The card is issued asynchronously. You receive a card.activated webhook when it is ready, or card.creation_failed if it could not be issued — in that case total_charged is refunded to the same cards_visa or cards_mastercard balance. Once the card is active, get its number, CVV and expiry from your server:
Call this endpoint only when your customer needs to see the card, and never store or log its response. Every other endpoint only returns last_four.

Step 7: Top up the card

The top-up is applied asynchronously: you receive card.topup.completed, or card.topup.failed with a refund. See Top Up a Card.

Step 8: Follow the card

KYC levels

Every customer has a KYC level, and a customer is never anonymous: level 1 is reached as soon as the customer is created. Each card product states the level it requires and its limits per level. The full rules — how a customer moves up or down, what each level allows, and the minimum level for each product (cards, gift cards, wallets, virtual bank accounts) — are in KYC levels.