Introduction
Onboard a business onto PCE through the API — one composite call creates the legal entity, its owners, bank accounts, locations, and services.
Entity Onboarding is how you bring a business onto the Priority Commerce Engine (PCE) programmatically. Instead of a portal form or a spreadsheet handed to an operations team, you send one API call that describes the business — its legal details, the people who own and sign for it, its bank accounts, its physical locations, and the services it wants to use — and PCE creates the whole entity graph and starts it down the underwriting path.
This is the first step before any money moves. A business must exist and be approved on PCE before it can accept a payment. Entity Onboarding is where that business is created.
Scope of this first releaseEntities you onboard through these APIs are provisioned for Accept Payments (card acquiring) only. Turning on Treasury Solutions (banking, accounts, money movement) for an onboarded entity is not part of this release. Where a step is Treasury-specific, this section says so and stops there.
What you can do
Send one composite request to create the business and everything under it — owners, signatories, bank accounts, addresses, locations, and services — then read it back with generated IDs.
Authenticate, learn the scope of this release, and send your first onboarding call. Then read Key concepts to understand the entity model.
Add or update owners, signatories, bank accounts, addresses, and locations after creation, toggle services, and close a business.
Follow an entity from PENDING_REQUIREMENTS through underwriting to ACTIVE, and read the outstanding requirements PCE surfaces inline.
How onboarding works
- Create the business.
POST /v1/businessesaccepts the full nested graph in one request. You can start with just a legal name and fill in the rest later, or send everything at once. See Create a business. - Add the people. Every business needs its beneficial owners and authorized signatories, with exactly one person marked as the control person. People are modelled as shared Individuals that you link into the business.
- Add bank accounts, addresses, and locations. A funding bank account, a registered address, and at least one location with its processing profile are what acquiring underwriting needs.
- Enable a service. Onboarding for payments means enabling the
acquiringservice (and any features it needs). PCE surfaces what's still missing on the service object itself. - Underwriting decides. Once requirements are complete, the entity moves to
PENDING_UNDERWRITING, then toACTIVEwhen approved. Track it with statuses.
New here?Start with Getting Started for authentication, base URLs, and the scope of this release, then read Key concepts to understand the entity model before you send your first call.
Where this fits
Onboarding creates the merchant that then uses the rest of PCE. Once a business is ACTIVE with the acquiring service approved, it can begin accepting payments.
Section naming — decide before publishThis section is drafted under the working name Entity Onboarding. Alternatives on the table: Unified Boarding (the internal/engineering name) and Onboarding on PCE. The folder, slugs (
entity-onboarding-*), and titles all follow the working name and can be renamed in one pass once the name is chosen. Renaming published slugs later requires ReadMe redirects, so settle the name while this section is still hidden.
Updated about 2 hours ago