Skip to main content
Once a cardholder’s application is approved, you can issue them a card. This page covers creating virtual and physical cards, setting spending limits, shipping and activating physical cards, and adding cards to a mobile wallet. Create a card with the Create a card endpoint.

Virtual vs. physical cards

Both card types use the same endpoint. The type you pass determines the setup:
  • Virtual cards are available for immediate use. Display the full details by decrypting them on the client. See Access card details.
  • Physical cards are shipped to the cardholder and require activation after delivery.
The response includes the card id, last4, and status.

Set spending limits

Set an initial spending limit at creation with the limit field, then adjust it later with the Update a card endpoint. The amount is in the smallest currency unit, for example cents. The frequency sets the window the limit applies to: per24HourPeriod, per7DayPeriod, per30DayPeriod, perYearPeriod, allTime, or perAuthorization. For example, to cap a card’s spend at $500 per 30-day period:
How a limit’s window is measured, as a rolling period or one that resets on a fixed schedule, depends on your card program. Contact your Implementation Manager to confirm how limits work for your program.

Ship a physical card

Physical cards need a shipping object with the recipient’s address and phone number. For shipping methods, address requirements, and personalizing the card, see Ship a card.

Activate the card

By default, activation is not required and a new card is active. To enforce an activation step, create the card with status set to notActivated. To activate it, confirm the cardholder’s last four digits, expiry date, or both with the Get a card endpoint, then set the status to active with the Update a card endpoint. For what each card status means and how to lock, unlock, or cancel a card, see Manage cards.

Add to Apple Wallet or Google Wallet

Let cardholders add their card to Apple Wallet or Google Wallet from your app with push provisioning, implemented through the MeaWallet SDK. Push provisioning must be tested with production cards. For the integration steps and decline troubleshooting, such as wallet risk-engine blocks and region mismatches, see Set up push provisioning.

What’s next

Set a PIN

Let cardholders set and retrieve their card’s PIN securely.

Fund the card

Add collateral so the cardholder’s credit limit reflects their available funds.

Access card details

Decrypt a virtual card’s PAN and CVC on the client so the cardholder can start spending.