Priority can't approve a business until it has everything it needs. Underwriting, Priority's check that it can approve the business, flags what's missing or wrong. Read the business, fix what's flagged, and read it again to confirm it cleared. These in-flight exceptions surface after creation, on each service's errors, missingFields, and missingDocuments. What's flagged here is different from a request error, which comes back straight away on the call you made, for example a badly formatted field. See API error handling.

---

What underwriting still needs

Onboarding has no separate "requirements" resource to poll. Each service object on the business carries three read-only fields that tell you exactly what's outstanding:

Read them on the business and inspect services.payin.card. Empty arrays with status: PENDING_UNDERWRITING mean the service has everything it needs and is waiting on a decision. Non-empty arrays tell you precisely what to fix or add. See Status lifecycle for how to read them and how status advances.

Some checks run as soon as you submit or re-read the business, such as a missing control person or a cardMix that doesn't total 100%. You fix these yourself. Others take longer, so a service can sit in PENDING_UNDERWRITING for a period even when its arrays are empty.

---

Common rejection reasons

Most rejections trace to a handful of causes. Each is reported against the part of the business that produced it, so you correct that part and resend:

• No single control person. Exactly one owner or signatory must be marked as the control person; both zero and two fail.
• Ownership totals break the rule for the business type. Partnerships need at least 50% combined beneficial ownership; government, non-profit, and 501(c)(3) businesses must have 0% beneficial ownership.
• Wrong tax-ID type for the entity. Corporations, S-corporations, LLCs, LLPs, and partnerships must use an EIN.
• Missing owner identification. Every owner and signatory needs a primary ID (SSN or ITIN) and a secondary government ID.
• Duplicate owner. The same SSN cannot back more than one owner on a business.
• Incomplete location processing profile. A location needs an industry MCC and a cardMix that totals 100%.

The rules behind these are owned on Business validation and KYB rules; the exact message each one returns is on API error handling.

---

Resolve and resubmit

To clear a rejection or an in-flight requirement:

1. Read the business back with ?expand=true and inspect services.payin.card for errors, missingFields, and missingDocuments.
2. Correct or add the flagged part on its own page: Owners and signatories, Bank accounts, Locations, or Documents.
3. Read the business again to confirm the arrays cleared. When they do, the service returns to PENDING_UNDERWRITING.
4. While you wait on the decision, re-read on a gentle cadence and apply exponential backoff between reads rather than tight-looping. See Tracking a business.

---

Next steps

See also

• Create a business: the KYB rules behind these exceptions
• Status lifecycle: how status advances and where requirements surface