Approve a mandate with a wallet
Customer-initiated. Approves a mandate on a wallet source using the customer’s signed payloads from Get wallet approval options. The customer signs the payloads themselves, so this call is unauthenticated. The mandate must be in created or approval_failed status, not expired, and have no approval or revocation in flight.
Returns a pending approval and moves the mandate to approval_pending. On success the mandate’s source is set and status becomes approval_succeeded; it can then be used by Authorize a payment session with a mandate. On failure status becomes approval_failed and a new approval can be submitted. Follow progress with Get a mandate approval or the acceptance.mandate.approval_* webhooks.
Headers
An optional string request header for making requests safely retryable. When included, duplicate requests with the same key will return identical responses. Refer to our Idempotency docs for more information on using idempotency keys.
1 - 128Path Parameters
Body
A request to approve a mandate on a wallet source. Submit the optionId the customer chose from Get wallet approval options along with the signed payloads. This creates a pending approval; the mandate becomes approval_succeeded once the approval succeeds.
Optional metadata as key-value pairs. Use this to store additional structured information on a resource, such as customer IDs, order references, or any application-specific data. Up to 10 key/value pairs may be provided. Keys and values are both strings. Keys must be ≤ 40 characters; values must be ≤ 500 characters.
Response
Successfully created mandate wallet approval.
An attempt to attach a funding source to a mandate and make it usable. A successful approval sets the mandate's source and moves the mandate to approval_succeeded; a failed one moves the mandate to approval_failed and can be retried by submitting a new approval. A mandate holds at most one active source, so at most one approval ever succeeds. The network transactions that grant the spending allowance are on onchainTransactions.
Optional metadata as key-value pairs. Use this to store additional structured information on a resource, such as customer IDs, order references, or any application-specific data. Up to 10 key/value pairs may be provided. Keys and values are both strings. Keys must be ≤ 40 characters; values must be ≤ 500 characters.