Boarding statuses reference
Deprecation notice: legacy boarding
Legacy boarding is deprecated and will be sunset in Q2 2027 (the “Sunset Date”). After the Sunset Date, legacy boarding endpoints, workflows, and documentation will no longer be available or supported, and requests to them may fail. Until then, legacy boarding remains available but will receive only critical security and stability fixes. No new features will be added.
To avoid disruption, migrate to intelligent boarding before the Sunset Date. See the migration guide for instructions. Questions? Contact your account manager.
This notice is provided for informational purposes. Dates and details are subject to change, and Payabli will provide updates here and through direct communication. Nothing in this notice amends any agreement between you and Payabli.
Statuses
These are the available boarding status values. The Key column contains the status code returned by the API.
Substatuses
Some statuses have substatuses to give you more information about where an application is in the process.
Manual Review substatus
These statuses may appear when an application is in the Manual Review (6) status. The Key column contains the status code returned by the API.
Boarding substatus
These statuses may appear when a merchant is in the Boarding (10) status. The Key column contains the status code returned by the API.
Declined substatus
These substatuses may appear when an application has a Declined status (0). The Key column contains the status code returned by the API.
Related resources
See these related resources to help you get the most out of Payabli.
References
- Paypoint statuses - Learn about the different statuses of paypoints
- Pay In TransEvent reference - Learn about TransEvent values for pay in transactions