Skip to main content
PATCH
JavaScript

Authorizations

Authorization
string
header
required

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

setup_intent_id
string
required

The unique identifier of the setup intent.

Body

application/json
return_url
string
required

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.

Example:

"https://shinetime.example/checkout/thanks"

Response

Return URL updated

id
string
required

The setup this status describes, prefixed sint_.

Example:

"sint_xxxxxxxxxxxxxx"

last_setup_error
object | null
required

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.

next_action
Redirect · object
required

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.

object
string
required

Always setup_status.

Example:

"setup_status"

return_url
string | null
required

Where to send the buyer once the setup reaches a resting state, or null to leave them where they are.

Example:

"https://shinetime.example/billing/saved"

status
enum<string>
required

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.

Available options:
processing,
succeeded,
canceled,
requires_action
Example:

"canceled"