Skip to navigation
Manage payment operationsMerchant boarding

Boarding application statuses

Beta
Learn about the statuses a boarding application moves through and what moves it from one status to the next
View as MarkdownOpen in Claude
Applies to:DevelopersPartners

Intelligent boarding is in beta. To opt in, reach out to your Payabli contact.

A boarding application moves through a series of statuses, from the moment it’s created until its requested services are live. Application responses return the status as a lowercase name in applicationStatus and as a number in applicationStatusCode. Responses from lifecycle actions, such as submitting or withdrawing an application, return the new applicationStatus.

For how applications relate to businesses, people, templates, and paypoints, see the Intelligent boarding overview.

Application statuses

The Status column contains the value of applicationStatus, and the Code column contains the value of applicationStatusCode.

StatusCodeMeaning
draft1Created but not yet submitted. This is the only status where you can update the application.
submitted2Submitted with the signature of record. Verification starts automatically.
verifying3Automated verification is running.
pendingreview4Waiting for underwriting review.
escalatedreview5Escalated to a higher underwriting review tier.
pendingdocuments6Underwriting requested documents. The application waits for the applicant to provide them, then returns to pendingreview.
pendingresponse7Underwriting asked a question. The application waits for the applicant to answer, then returns to pendingreview.
approved8Approved. The requested services are being enabled.
autoapproved9Approved automatically, without manual review.
denied10Denied. This is a final status.
withdrawn11Withdrawn. This is a final status.
abandoned12Reserved. No action moves an application to this status.
error13Processing hit an error. Payabli can recover the application, which returns it to the status it had before the error.
activated14The requested services are provisioned and live. This is a final status.

How an application moves between statuses

Three kinds of actors move an application from one status to the next:

  • You: your integration calls a lifecycle endpoint.
  • Payabli or Enterprise Partner: Payabli’s underwriting team, or an Enterprise Partner’s, acts on the application.
  • Automatic: Payabli’s systems move the application without anyone acting on it.
FromToWhat moves itWho acts
nonedraftThe application is created.You
draftsubmittedThe application is submitted.You
submittedverifyingAutomated verification starts.Automatic
verifyingpendingreviewVerification routes the application to manual review.Automatic
verifyingautoapprovedVerification approves the application without manual review.Automatic
pendingreviewescalatedreviewThe application is escalated to a higher review tier.Payabli or Enterprise Partner
pendingreview or escalatedreviewpendingdocumentsUnderwriting requests documents.Payabli or Enterprise Partner
pendingreview or escalatedreviewpendingresponseUnderwriting asks a question.Payabli or Enterprise Partner
pendingdocumentspendingreviewThe requested documents are provided.You
pendingresponsependingreviewThe requested information is provided.You
pendingreview or escalatedreviewapprovedUnderwriting approves the application.Payabli or Enterprise Partner
pendingreview or escalatedreviewdeniedUnderwriting denies the application.Payabli or Enterprise Partner
approved or autoapprovedactivatedAll the requested services are boarded.Automatic
draft, submitted, pendingdocuments, or pendingresponsewithdrawnThe application is withdrawn.You
submitted, pendingreview, escalatedreview, pendingdocuments, pendingresponse, or approvederrorProcessing fails.Automatic
errorThe status before the errorPayabli recovers the application.Payabli

An application in denied, withdrawn, or activated doesn’t change status again.

Check which actions are allowed

Application responses and lifecycle action responses include an allowedActions array that lists the actions available in the application’s current status. The array can include actions that Payabli or its systems perform, which you can’t call through the API. These are actions, not statuses. For example, provideDocuments is how you respond when an application is in pendingdocuments. Check for one of these values before you call the matching endpoint:

Allowed actionAllowed inWhat it does
submitdraftSubmits the application for review.
withdrawdraft, submitted, pendingdocuments, pendingresponseWithdraws the application. See Withdraw an application.
provideDocumentspendingdocumentsProvides the documents that underwriting requested. The application returns to pendingreview.
provideResponsependingresponseProvides the information that underwriting requested. The application returns to pendingreview.

Track status changes

To see how an application reached its current status, use Get application status history. The response lists every transition, oldest first, with the fromStatus, toStatus, what triggered the change, and any reason recorded with it. The transition that creates the application has a fromStatus of none.

See these related resources to help you get the most out of Payabli.