A merchant application is the onboarding record for a new merchant.

A partner creates an application on a merchant's behalf.
The partner can complete as many of the application fields as needed.
Uncompleted fields can be filled in by the merchant.
The merchant completes, signs and submits the rest.
Flute then reviews the application and boards the approved merchant with the processor.

Each application is attributed to a partner user.
That user's Schedule A, Split Profile and residuals apply to the application.
The pricing templates offered to the merchant can also be chosen.

The application link reaches the merchant in one of three ways.

* Flute emails the merchant an invitation.
* The partner delivers the link directly.
* The partner embeds the application in an iframe on its own page.


The `applicationStatus` field shows where each application stands in onboarding.
The application lifecycle webhooks report the individual events that move an application between statuses.

For more information about Onboarding merchants, see Onboarding.

These endpoints require a partner API token.

This Applications group consists of the following endpoints:

* To list applications, see GET /v2/applications
* To create an application, see POST /v2/applications