Board a new business with the API
Intelligent boarding is in beta. To opt in, reach out to your Payabli contact.
To board a business that’s new to Payabli, create its paypoint first, with the business created in the same request. Then add the business’s owner, open an application that lists the services the business needs, validate it, and submit it for review. This quickstart walks through each step. For how the business, its people, its paypoint, and its applications fit together, see Boarding overview.
Considerations
- The boarding API uses OAuth2. Send a Bearer token on every request. See OAuth2 authentication.
- Each service has its own requirements. Validate reports fields that are missing or invalid, so you can fix them before you submit. For the fields boarding asks for, see Required fields for boarding applications.
- Every application needs a signer, and the signer must be an owner. The business also needs a primary controller. Unless its legal structure is
governmentornon-profit, it also needs at least one owner with 25% ownership or more.
Create the paypoint and business
Send a POST request to /v2/paypoints with the paypoint’s details and a business object that describes the business. Payabli creates both, and the paypoint starts in pending. Only doingBusinessAs and business.legalName are required to create the paypoint. Validate tells you what else the requested services need. To set up the business’s bank accounts in the same request, add them to business.paymentMethods, as described in Manage payment methods with the API. See the API reference for this endpoint for full documentation.
The response returns the new paypoint. Note the businessReference and paypointReference for the next steps:
Add the owner
Send a POST request to /v2/people with the owner’s details and a businessRelationship object that links them to the business. In businessRelationship, set personType to Owner with their ownershipPercentage, set isPrimaryController to true, and set isSigner to true to make them the person who signs the application. To add more owners or other people, send one request for each person. See Manage people with the API. See the API reference for this endpoint for full documentation.
The response returns the new person, with their link to the business:
Create the application
Send a POST request to /v2/requests with the businessReference and a services object that lists the services the business needs. List Pay In services under moneyIn and Pay Out services under moneyOut. Include requestTemplate with the reference of your organization’s boarding template, because Payabli reviews the application with the template’s underwriting settings. The application boards the paypoint you created in the first step. An application needs a paypoint, so this request fails with 404 if the business doesn’t have one. See the API reference for this endpoint for full documentation.
The response returns the new application in draft. The requestsReference identifies the application in the next steps:
Validate the application
Check that the business, its people, and its payment methods have everything the requested services need, and that their values are valid. Send a POST request to /v2/requests/{requestsReference}/validate. Validation doesn’t change the application. See the API reference for this endpoint for full documentation.
When valid is true, the records have everything the requested services need:
When valid is false, each section lists its missingFields. The field value is the path on the record to fix, such as business.taxReference. Update that record, such as with a PATCH request to the business, then validate again. If a field starts with documents., it’s a required document, not a record field: upload the file to the application instead. See Upload documents. For an example response with missing fields, see the API reference for this endpoint.
Submit the application
Send a POST request to /v2/requests/{requestsReference}/submit with a signer object that holds the signature details. Payabli records the signer’s identity from their person record and business link. See the API reference for this endpoint for full documentation.
The response returns the application’s new status:
After you submit the application, it moves through review. To answer underwriting, see Respond to underwriting requests. To follow the application’s progress, see Track status changes.
Related resources
See these related resources to help you get the most out of Payabli.
References
- Required fields for boarding applications - Learn more about the Know Your Customer (KYC) and Know Your Business (KYB) fields required for merchant boarding
- Boarding application statuses - Learn about the statuses a boarding application moves through and what moves it from one status to the next