> ## Documentation Index
> Fetch the complete documentation index at: https://www.marqeta.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# White Label App Getting Started 

Onboarding a cardholder into the White Label App (WLA) through Managed Onboarding happens with a simple step on the customer-facing API, and all other required steps occurring automatically.

## Onboarding steps

<Steps>
  <Step title="Identity verifications for Know Your Customer/Business (KYC/KYB)">
    The applicant's identity is verified through an intake form plus a regulated ID and selfie capture. This step requires you to create an intake form that calls the Marqeta KYC or KYB API, as Marqeta hosts the KYC and KYB webviews. 
  </Step>

  <Step title="Account setup">
    Marqeta provisions the user's entities, a checking or current account, and rewards enrolment behind the scenes. This step is entirely managed by Marqeta. 
  </Step>

  <Step title="App setup">
    The cardholder signs in, secures their device, and finishes card setup inside WLA. This step is handled by the cardholder and Marqeta. 
  </Step>
</Steps>

## Identity verification for Know Your Customer/Business (KYC/KYB)

Know Your Customer/Business (KYC/KYB) verification confirms the applicant's identity before Marqeta creates an account.

<Steps>
  <Step title="Collect applicant info">
    Your intake form collects the applicant's information, then you call `POST /applications` to submit it.
  </Step>

  <Step title="Receive the KYC URL">
    Marqeta returns a `kyc_url` once the application status is `KYC`.
  </Step>

  <Step title="Redirect to the hosted webview">
    Redirect the applicant to `kyc_url`. Marqeta's hosted webview walks them through choosing an ID type, capturing the front and back of the ID, capturing a selfie, and confirming success.
  </Step>

  <Step title="Screening">
    In parallel, Marqeta screens the applicant against sanctions and politically exposed person (PEP) lists for their geography (EU and UK), at onboarding and daily thereafter.
  </Step>

  <Step title="Decision">
    Marqeta sends `APPLICATION_APPROVED` (or `REJECTED`/`EXPIRED`) when a decision is reached.
  </Step>
</Steps>

<Warning>
  A confirmed sanctions or PEP hit holds the application. Marqeta never creates an account or card for a sanctioned applicant.
</Warning>

### User intake and integration options

<Note>
  If an applicant drops off mid-capture (for example, after the front-of-ID step but before the selfie), they resume from that exact step rather than starting over. This applies only to Marqeta-hosted surfaces. With the partner-owned intake option, resuming your own intake form is your responsibility.
</Note>

| Option                | Who builds the intake form                                                                                                                                         | Status      |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------- |
| Partner-owned intake  | You build and host the personal info, review details, and terms steps, then call the Applications API directly. Marqeta hosts only the regulated KYC capture step. | Available   |
| Marqeta-hosted intake | Marqeta hosts the entire experience, including intake and KYC capture, themed to your brand, behind one redirect URL.                                              | Coming soon |

## Account setup

The Account setup step happens automatically — no action is needed from you.

On approval, Marqeta creates the user's entities, opens their checking or current account (firing the `ACCOUNT_ACTIVATED` and deposit-account webhooks), and registers them for rewards. There is no customer-facing API for this step today.

## App setup

This step happens from inside WLA.

<Note>
  Drop-offs anywhere in the app setup step resume from the exact screen where the cardholder left off.
</Note>

<Steps>
  <Step title="Sign in">
    The cardholder signs in with Google single sign-on (SSO), which adds a one-time passcode (OTP) step, or your customer SSO, which doesn't. Their device is verified and registered, and they set a password.
  </Step>

  <Step title="Enable biometrics">
    The cardholder can optionally enable Face ID, Touch ID, or fingerprint sign-in. This step is skippable, and the password serves as a fallback.
  </Step>

  <Step title="Set up their card">
    The cardholder provides a shipping address and PIN if your program issues physical cards, or chooses a digital-wallet tokenization option if it doesn't.
  </Step>

  <Step title="Confirm and enable notifications">
    The cardholder sees a confirmation screen, then opts in to push notifications, then lands on the app home screen.
  </Step>
</Steps>