Submit partner KYC fields (legacy)
Legacy: submit an External QR Payment’s missing KYC fields from your backend.
collectionSessionId comes from the Payment’s next action, and the fields keys must exactly match the keys returned in nextAction.fields. It remains temporarily available for existing backend integrations.Authorizations
HTTP Basic auth. Username is the Stableyard app ID. Password is the app secret. The optional Stableyard-Version request header must match the environment pin.
Headers
Optional contract-version assertion. Omit it to use the app environment's pinned version. A different supported version is accepted only after that environment is explicitly migrated.
2026-09-09 Path Parameters
Partner KYC collection session returned by an External QR Payment next action.
^info_req_[A-Za-z0-9_-]+$"info_req_123"
Body
Field keys must exactly match the keys returned in nextAction.fields.
Response
Partner KYC state
requires_kyc, requires_information, ready_to_submit ^acct_[A-Za-z0-9_-]+$"acct_123"
Provider-neutral readiness profile identifier.
"external_payout""external_payout@2026-09-02"
The exact action the caller must complete. Null means Stableyard needs no action from the partner right now.
- Action required
- Start account KYC
- Verify UPA email
- Complete hosted compliance
- Wait for partner KYC
- Contact support
- No provider action