Skip to main content
Migo Docs

Card Issuance Flow

Migo's prepaid card vertical is a white-label program: a company can issue its own branded physical prepaid cards to its users (for example, corporate cards for employees). The program is configured per tenant/company, so the cards, branding, and limits belong to the issuing company.

This page describes the end-to-end flow to put a working card in a cardholder's hands. Each step links to the detailed reference.

At a glance​

1. Company environment provisioned for cards   (done at onboarding by Migo)
        │
        ▼
2. Create the cardholder                         POST /users  ──►  userId
        │
        ▼
3. Deliver the physical card (plastic)           logistics
        │
        ▼
4. Cardholder activates the card                 activation webview
        │
        ▼
5. Card management enabled                        block · unblock · movements · details · PIN · CVV · funds

1. Environment provisioned for cards​

Card issuance is enabled for your company during onboarding — Migo provisions the card program for your tenant (branding, currency, and product limits). There is no public endpoint for this step; coordinate it with your account manager before you start creating cardholders.

2. Create the cardholder​

Each card belongs to a cardholder — a user in your company's environment. Register the cardholder with POST /users (passing their personal information); the response returns the userId you will use for the rest of the flow.

curl -X POST https://api.ali.app/rest/users \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{ "firstName": "Example", "lastName": "User", "...": "..." }'

Cardholder management is the canonical reference for this endpoint — it documents both registration modes, the full field schema, and validations.

3. Deliver the physical card​

The printed plastic is delivered to the cardholder through your distribution process. The card arrives inactive — it cannot transact until the cardholder activates it.

4. Activate the card​

The cardholder activates their card through Migo's hosted card-activation webview. Open it with the cardholder's userId:

https://web.migopayments.com/card-activation?client=migoDeveloper&userId=YOUR_USER_ID
Query paramRequiredPurpose
userIdYesThe cardholder created in step 2
clientNoBranding hint for the activation screen (your client slug)

On the webview the cardholder enters the card number and the cardholder name printed on the plastic, and confirms. The webview associates the card with the user and activates it — no API integration is required on your side for this step.

note

Use the sandbox host for testing: https://sandbox.migopayments.com/card-activation?client=migoDeveloper&userId=YOUR_USER_ID.

If you prefer to activate the card from your own backend instead of the webview, an API activation endpoint is also available. See Card lifecycle → Activate a card for both activation paths.

5. Manage the card​

Once the card is active, the management API is enabled for it. From here you can: