Skip to main content
POST
Submit partner KYC fields (legacy)
Deprecated. New integrations must open the complete_compliance URL returned by the Payment and let the Stableyard-hosted page collect the fields.
This legacy server-rendered integration submits the KYC fields an External QR Payment is missing. The 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

Authorization
string
header
required

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

Stableyard-Version
enum<string>

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.

Available options:
2026-09-09

Path Parameters

collectionSessionId
string
required

Partner KYC collection session returned by an External QR Payment next action.

Pattern: ^info_req_[A-Za-z0-9_-]+$
Example:

"info_req_123"

Body

application/json
fields
object
required

Field keys must exactly match the keys returned in nextAction.fields.

Response

Partner KYC state

status
enum<string>
required
Available options:
requires_kyc,
requires_information,
ready_to_submit
accountId
string
required
Pattern: ^acct_[A-Za-z0-9_-]+$
Example:

"acct_123"

partnerId
string
required

Provider-neutral readiness profile identifier.

Allowed value: "external_payout"
requirementProfileVersion
string
required
Example:

"external_payout@2026-09-02"

kycVerification
object
partnerSubmission
object
collectionSession
object
missingFields
object[]
requestPayloadHash
string
payloadPreview
object
nextAction
Action required · object

The exact action the caller must complete. Null means Stableyard needs no action from the partner right now.