Errors

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.

Error objects

BrowserNotSupportedError

The hosting client browser is not supported by the Web Payments SDK
CashAppPayInvalidPaymentRequestError

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.
CashAppPayMissingRedirectUrlError

Exception thrown when a redirect url is not provided on initialization. This can happen when the user calls cashAppPay without the necessary options.
InvalidCashAppPayOptionsFieldTypes

Occurs when the developer passes an invalid type in the Cash App Pay button options
InvalidCashAppPayOptionsFieldValues

Occurs when the developer passes an invalid value in the Cash App Pay button options
InvalidFieldNameError

The specified field name is invalid
InvalidPaymentRequestError

A PaymentRequest object is malformed
MethodNotAvailableError

Exception thrown when trying to call a method that is not available
PaymentMethodAlreadyAttachedError

Exception thrown when a Payment Method instance is attached more than once.
PaymentMethodAlreadyDestroyedError

Exception thrown when a Payment Method instance is already destroyed.
PaymentMethodNotAttachedError

A method was called on a payment method before it is attached to a page HTML DOM element.
PaymentMethodUnsupportedError

The payment method is not supported, and cannot be used.
PlaidMissingNameError

Thrown when accountHolderName is not provided to the ACH payment tokenize method
ScriptLoaderError

Thrown when a script tag injecting a global fails to load the global.
TokenizationError
UnexpectedError

A generic error to handle internal error conditions unrelated to the state or of the application that is integrating the Web Payments SDK.
VerifyBuyerError

Strong customer authentication error