Skip to main content
PATCH
cURL

Authorizations

Authorization
string
header
required

Access token from POST /v1/auth/token, sent as Authorization: Bearer <token>. Treat it as opaque.

Path Parameters

session_id
string
required

Tokenization session identifier.

Maximum string length: 64

Body

application/json

Set the amount the card will be charged on an existing checkout session.

billing
ThreeDsBillingData · object | null

Cardholder billing data for 3-D Secure (replaces any set earlier). Same fields and limits as on create.

net_payable_amount
integer | null

Minor units the CARD will be charged -- the amount 3DS authenticates. For a redemption flow, the order total minus the redemption the shopper selected. Must not exceed the session's gross order amount.

Required range: x >= 0

Response

Successful Response

Standard success envelope. Every successful response has this shape, with the operation's own payload under data.

data
SessionUpdatedResponse · object | null

The operation's result. Its shape is documented per operation; omitted on responses that carry no payload.

message
string | null

Optional human-readable note. Omitted from the response when not set, which is the case for every payment operation today. Never parse it.

request_id
string | null

Correlation ID for this HTTP request, for logs and support. Send your own in the X-Request-Id header (letters, digits and hyphens, up to 36 characters -- other characters are stripped) or the gateway generates one. This is NOT the request_id idempotency key you send in a transaction body; the two are unrelated.

status
string
default:ok

Always ok on a successful (2xx) response. Errors use a different body shape entirely (RFC 9457 problem details), so branch on the HTTP status code, not on this field.