Underwriting and status
How a business is reviewed and how to track it: the boarding status lifecycle, and the in-flight exceptions underwriting surfaces before a business can go live.
Underwriting is Priority's check that it can approve a business before it uses a service, such as taking card payments. It looks at who the business is, who owns and runs it, and how it plans to use the service. Once a business is complete, boarding hands it to underwriting, an asynchronous review that starts by itself once a service has everything it needs.
Track a business by reading it back; there are no status webhooks. Submit-time validation errors live in API error handling; the in-flight requirements and rejections that surface during review are on Underwriting exceptions.
What to expect
Most businesses follow the same happy path. You create the business, add its owners, bank account, address, and location, then enable Accept Payments. PCE reports anything still outstanding on missingFields and missingDocuments. Once those clear, the service moves to PENDING_UNDERWRITING, and on approval the service is enabled and the business can process payments.
A healthy, review-ready business looks like this:
- Every requirement is in place: exactly one control person, at least one location with its processing profile, a bank account, and any required documents.
- The
services.payin.cardservice reports emptymissingFieldsand emptymissingDocuments. - Its status has advanced to
PENDING_UNDERWRITING, so it is waiting only on a decision.
When a business reaches that shape, there is nothing left to do but track it until the service is enabled. The business can then begin accepting payments. See Status lifecycle for how to read those fields and follow status.
In this section
See also
- Businesses: the resources each status applies to
- Create a business: where the lifecycle begins
Updated 9 days ago