Client payments
List account-bound payment methods
List the extra account-bound methods, such as Vault, that can fund a receive Payment.
GET
List my account-bound Payment methods
Returns additional account-bound methods for this receive Payment and the UPA fixed by the client bearer token. This catalog is separate from public checkout, which stays limited to Direct crypto, Routing and entitled hosted on-ramp methods.
Vault is returned only when the client token has both Payments and Vault access, this UPA can pay the Payment, and the UPA has an active Vault payment source whose chain, token and amount can satisfy the Payment’s immutable escrow obligation exactly. Send both the client bearer token and the Payment-specific
X-Stableyard-Payment-Secret; neither credential is sufficient on its own.Authorizations
Short-lived account-bound token returned by POST /v2/client/auth/exchange.
Payment-specific secret used together with an account-bound Client bearer token. It proves access to exactly one Payment and must never be placed in a URL, analytics event, or log.
Path Parameters
Canonical receive Payment whose escrow will be funded.
Pattern:
^payment_[A-Za-z0-9_-]+$Example:
"payment_123"
Response
Account-bound methods available to this UPA
Contains vault.stableyard when the token-bound UPA has an eligible active Vault Payment Source; otherwise the request fails closed.
Maximum array length:
1