Onboarding by account type
subjectType, fixed when the account is created, decides which path an account takes. See Universal Payment Account.
The steps run in this order. A KYC session without a verified email is refused, and an individual’s capability activation without current identity eligibility is refused.
A crypto-only integration stops at step 1. Crypto rails depend only on your app’s product access and work whether or not anyone has been verified.
The gates
Partner KYB gates all fiat
Until your organization’s KYB is approved, no fiat product works for you or for any of your accounts. You complete it with Stableyard, not through the Partner API. Read its standing at runtime:compliance.requirements states what each party passes:
Your organization’s KYB also covers Your Business UPA, the one
business account you designate as your own operating identity. It needs no separate verification.
What each flow needs
An account created before explicit classification may report
subjectType: "unclassified". It remains usable for non-regulated activity, but cannot start verification: those calls return 422 account_subject_unclassified.
Related
Email verification
Verify an individual’s email with a Stableyard code, or assert one you already verified.
Individual KYC
Send the customer to a provider-hosted page and read the result.
Business KYB
Verify a business for US bank rails through a hosted application.
Capability activation
Turn a verified customer into one who can use a bank rail.