Reason Codes

Successful response.

Capture context created.

400

- Capture Context API

Bad request.

The

Unified Checkout

configuration rejected the request due to invalid values.

Checkout failed.

This reason is returned when the UI cannot be successfully rendered. For example:

Network failures (CDN unavailable, blocked, or timed out)
Browser or device restrictions are preventing the SDK from loading.
Incorrect or missing configuration causes
Unified Checkout
not to request the SDK asset.
The merchant site CSP is blocking the SDK.
Any runtime error that prevents
Click to Pay
JS initialization.

The token creation timed out. This reason is returned when the

Unified Checkout

JavaScript SDK cannot generate the transient token within the expected time-frame.

This reason is returned when the system attempts to create a token, but a network / XHR-level failure occurs before the token can be created. This is a client-side SDK network failure, not a timeout or back-end validation error.

Encrypt card for SRC enrollment failed. This reason is returned when

Unified Checkout

attempts to encrypt a card to enroll it in the SRC /

Click to Pay

system and the encryption step fails. This causes the SRC enrolment to abort.

Returned when the API key that is used in the server‑side capture context request is invalid.

The launch SRC checkout failed. This reason is returned by the

Unified Checkout

JavaScript SDK when it cannot initialize or open the SRC checkout flow.

SDK failed to load. This reason is returned when the JavaScript SDK fails to load due to an XHR/network error during

Unified Checkout

initialization.

The specified DOM element cannot be found. Returned when the DOM element specified in the

show()

configuration cannot be found. This is a client-side JavaScript SDK error thrown during rendering of the payment selection UI.

There was a problem encountered when loading the payment screen. Returned when the Unified Payments UI fails to load the payment selection screen (iframe/UI) during the

.show()

step

The supplied container parameter is invalid. Returned when the container provided to

up.show()

exists but is invalid—wrong type, not suitable to host UC UI, unsupported context, or malformed in configuration

The supplied container parameter is invalid when sidebar is selected. Returned when

sidebar = true

and the

containers

supplied to

up.show()

are not valid for the sidebar layout (wrong type, unsupported container, or structurally incompatible).

Occurs when an error is encountered during the handling of a payment option. Returned when UC cannot progress the user’s selected payment option in time:

No payment types could be presented to the customer. This could be due to browser/device support or errors encountered during the checkout. Returned when

zero

payment methods can be presented in the

.show()

phase — typically due to browser/device incompatibility, disabled payment types, or internal errors while loading payment options.

Occurs when the createToken call was unable to proceed. Returned when the

createToken

call cannot proceed within the expected time while rendering the payment selection UI

Occurs when a network error is encountered while attempting to create a token. Returned when the

createToken

step within

.show()

fails due to an actual network/XHR error (blocked request, CORS/CSP violation, extension interference, unreachable endpoint).

Tokenization failed. Returned when tokenization of the selected payment method fails — due to invalid payment data, a failed internal tokenization call, network issues, or an unsupported/blocked payment environment.

Trigger is not supported for this payment type. Returned when

up.trigger(paymentType)

is called with a payment method that does not support trigger mode, is not enabled, not available on the device/browser, or not recognized by UC.

Occurs when no valid payment parameters exist when initializing button. Returned when the merchant calls

VAS.UnifiedCheckout(sessionJWT)

without providing valid payment parameters — meaning the SDK cannot initialize the payment buttons because the supplied configuration is missing, empty, or malformed.

A validation error occurred. Missing or invalid values in required fields

Trigger is not supported for this payment type. Returned when

up.trigger(paymentType)

is called with a payment method that does not support trigger mode, is not enabled, not available on the device/browser, or not recognized by UC.

The specified resource not found in the system.

Unexpected server error.