Post Application
Submits a new financial-service account application to Marqeta
Submit an application
Send a POST request to/applications with the applicant’s identity details to submit a new application. Authenticate with your API key credential over HTTP Basic auth; this endpoint requires WRITE authority.
Marqeta screens the applicant against sanctions and politically exposed persons (PEP) lists for their region, then returns a kyc_url once the application reaches KYC status. Redirect the applicant to that URL to complete Know Your Customer (KYC) or Know Your Business (KYB) verification through a hosted webview that walks them through ID capture and a selfie.
The user object is required and must include id, name, email, and phone_number. You can optionally include national_id, address, shipping_address, tax_profile, financial_profile, terms, and device to reduce how much information the applicant has to provide during KYC.
kyc_url only if status is KYC.Application lifecycle
An application only moves forward through its lifecycle, never backward, with status changes only occurring from a perivous state to a subsequent state in the list. For example, an application can transition fromSUBMITTED to KYC or APPROVED. Once a state is reached, it cannot move back to a previous state.
/applications.
Outbound application events
Marqeta sends application status-change events to your configured webhook endpoint. Every event payload includesapplication_id and user_id. The payload also includes kyc_url if the event type is APPLICATION_KYC. Some events are optional, which means that the you can opt to not send these.
Authorizations
Token used to verify user identity and also authorize user to use service.
Body
Information on the user that is applying for an account.
Information about the user's national ID.
Information about the user's address. Note that depending on the country, some of the address components may not be available.
Information about the user's address. Note that depending on the country, some of the address components may not be available.
Information about the user's tax profile.
Information about the user device used to submit the application.
Options for application creation.
Information about the user's financial profile.
Response
Successful operation
Partner-generated application ID.
"16c4fb2d-3321-46b3-acf6-567ceba2d3fc"
The status of the application. It can be used to determine the next steps in the application process.
Status changes only occur from a previous state to a subsequent state in the list.
For example, an application can transition from SUBMITTED to KYC or APPROVED.
Once a state is reached, it cannot move back to a previous state.
Some events are optional, which means that the partner can opt to not send these.
For asynchronous flows, the initial state is SUBMITTED, and status changes are delivered to the partner via Application event webhooks.
SUBMITTED, KYC, MANUAL_REVIEW, APPROVED, REJECTED, EXPIRED "KYC"
The webview URL for starting the KYC flow with the user. This must be present if the status value is KYC.
"https://bank-partner/kyc_webview?user_id=8E13_EWEF5a9GuatLqwm5eD6kQRFloKKxIkHM14YiIbkrxpfSNft8_-AyiMUmZHkd-zp7qrhiJITsCBlOeJ4db0NOfG5kas5QDcVR1cxU36EGwaxcgB0Qk4xgj-ViS-TMw=="