Update setup return URL
Changes where the buyer lands after completing an off-site step, up until they return. Accepts either a secret key or the setup’s own client_secret, so the surface that knows the final destination can set it.
Authorizations
An Account API key, account-scoped JWT, App API key, or user OAuth token. Prepend the key or token with Bearer, for example Bearer ***************************.
Path Parameters
The unique identifier of the setup intent.
Body
Where the buyer continues after completing an off-site step. Must be an absolute https URL without credentials (http is allowed for localhost), at most 2,048 characters.
"https://shinetime.example/checkout/thanks"
Response
Return URL updated
The setup this status describes, prefixed sint_.
"sint_xxxxxxxxxxxxxx"
Why the setup ended where it did, or null when nothing has failed. Present on canceled — a buyer who abandoned carries no code, one refused by the provider does.
What the buyer must do next while status is requires_action, otherwise null. type picks the shape and each variant carries only its own data, so switching on type gives you exactly that step's payload.
- Redirect
- Display instructions
- Await confirmation
Always setup_status.
"setup_status"
Where to send the buyer once the setup reaches a resting state, or null to leave them where they are.
"https://shinetime.example/billing/saved"
How far the setup has got. A 200 means we answered, not that the method was saved — always branch on this. requires_action — the buyer has a step outstanding; see next_action. processing — the buyer has done their part and the processor is deciding. succeeded — the payment method is saved, and only this one means saved. canceled — abandoned or refused; see last_setup_error to tell which.
processing, succeeded, canceled, requires_action "canceled"

