The Web Payments SDK has a set of errors that can be thrown from a variety of methods. This reference documents every error that can be thrown, and where it can be thrown from, while using the SDK.
Exception thrown when the total amount is greater than, or less than, the allowed Afterpay/Clearpay transaction limits. This exception will be thrown on initialization of the Afterpay/Clearpay payment method and on tokenization if the total amount for the PaymentRequest was updated.
Exception thrown when a Payment Request is invalid for Afterpay/Clearpay specifically. These are cases where a field/value combination is expected for Afterpay/Clearpay which would not be required for other payment methods.
Exception thrown when Afterpay/Clearpay is not enabled for a merchant. This exception will be thrown on initialization.
Exception thrown when the PaymentRequest used with Afterpay/Clearpay causes a failure during initialization of the payment method, or tokenization of the payment method.
Exception thrown when the currency provided is not supported for use by Afterpay/Clearpay. This exception will be thrown on initialization of the Afterpay/Clearpay payment method and on tokenization if the currency for the PaymentRequest was updated.
The hosting client browser is not supported by the Web Payments SDK
Exception thrown when a Payment Request is invalid for Cash App Pay. This can happen when an unsupported currency code is provided or an invalid payment request is used.
Exception thrown when a tokenize validator is not a function. This can happen when a user passes a non-function to the cashAppPay shouldTokenize option.
Exception thrown when a redirect url is not provided on initialization.
This can happen when the user calls cashAppPay without the necessary options.
The specified element was not found
Exception thrown when use of a disabled feature is attempted
Occurs when the developer passes an invalid type in the Cash App Pay button options
Occurs when the developer passes an invalid value in the Cash App Pay button options
The specified option name does not exist
The specified option has an invalid value
The specified amount is not expressed in a valid format for the provided currency.
The developer has an element with a forbidden/clashing ID on the page.
The developer attempted to attach a payment method with an invalid selector or element type.
An eventListener callback is throwing an unexpected error.
The specified field name is invalid
A provided style property is invalid for the payment method.
A provided style selector is invalid or unsupported.
A provided style value is invalid for the property.
Invalid method parameter errors.
A PaymentRequest object is malformed
A PaymentRequestUpdate object is malformed.
Exception thrown when a Payment Method instance is attached more than once.
Exception thrown when a Payment Method instance is already destroyed.
Exception thrown when a method was called on a payment method before a needed listener was added
A method was called on a payment method before it is attached to a page HTML DOM element.
The payment method is not supported, and cannot be used.
Thrown when accountHolderName is not provided to the ACH payment tokenize
method
A generic error to handle internal error conditions unrelated to the state or of the application that is integrating the Web Payments SDK.
Strong customer authentication error
The Web Payments SDK requires HTTPS and a secure context