Skip to main content
POST
Confirm outgoing send action
Send the actionId and exactly the proof type the Payment’s nextAction requests; never guess it from the payment source. Connected-wallet sources submit a transaction hash after signing and sending from the wallet. Managed or Vault-backed sources submit the requested authorization proof. Escrow-funded Payments use their checkout funding method instead: when no outgoing execution exists, this endpoint returns 409 with reasonCode: payment_confirmation_not_supported. A transaction nextAction with depositInstructions describes escrow funding, not a confirm action. A successful response means the proof was accepted, not that settlement is final. See Sending payments.

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

paymentId
string
required

Canonical payment_* identifier. Internal execution identifiers are never accepted by Partner Payment routes.

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

"payment_123"

Body

application/json
actionId
string
required
Required string length: 1 - 128
proof
Submitted transaction · object
required

Submit exactly the proof type requested by nextAction; never guess it from the payment source.

metadata
object

Response

Confirmed payment action

payment
object
required
nextAction
Action required · object
required

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

checkout
object