This guide walks the whole journey for a program that issues cards to its end users — from inviting the user to a funded, ordered card. It spans three surfaces, so it’s easy to lose the thread; the diagram below shows who calls what. The flow has two variants, chosen by how you invite the user:

​
Who calls what

​
Step 1 — Invite the user

Invite the customer with one call to POST /v1/access-management/invite/customer. It creates the user and their application, and Orenda emails the invitee a temporary password. The invite body selects the funding model for the rest of the flow.
Set the sub-role flag and the funding accountId — the program account the invitee draws against:
You get back an applicationId.
Service users are exempt from the step-up; an operator must send a confirmation (passkey or TOTP) or the call returns 422 SCA_MISSING. Which invitee details are required depends on the role — send what you have, and a 400 names any field that’s missing. Full field reference: Invite a customer.

​
Step 2 — The user onboards (Customer API)

Everything from here until the card is the user acting with their own token on the Customer API. The invitee signs in with the temporary password from the invite email (changing it and setting up 2FA/passkey on first login), then moves through onboarding:
  1. Accept legal agreements — POST /v1/applications/{applicationId}/agreements/legal/accept
  2. KYC — fetch the schema (GET /v1/applications/{applicationId}/kyc/schema) and submit answers (POST /v1/applications/{applicationId}/kyc)
  3. Identity verification (Sumsub) — get a token (GET /v1/applications/{applicationId}/webtoken/sumsub) and run the SDK
  4. Poll GET /v1/applications until onboarding completes
The full step-by-step for the user’s side — with request/response detail and the status model — lives on the Customer API docs: Issuing a card, end-to-end.
You don’t need to poll yourself: your program receives a webhook when the application is approved.

​
Step 3 — Order the card

Once approved, the application carries the customerId, and the user’s primary account is created automatically (read its accountId). Order the card:
The user can order their own card on the Customer API, or you can order it on the Management API (POST …/cards) — see Card operations.

​
Step 4 — Fund the card

Load funds onto the card from the program master account:
Use "action": "UNLOAD" to pull funds back to the master account.

Invite a customer

Create the user and their application with one invite call.

Card operations

Issue, status, limits, Load/Unload.

User-side walkthrough

The Customer API steps in full.

Webhooks

Get notified when the application is approved.