Error codes

Last updated: October 6, 2025

See the definitions of the error codes you may receive when integrating Flow for mobile.

Error	Description
`base64EncodingFailed`	Encoding the `sessionData` passed to the `handleSubmit` callback failed.
`callbackNotProvided`	You must provide the `onTokenized()` callback before you call the `tokenize()` method.
`cardAuthenticationFailed`	The customer failed or canceled the 3DS authentication challenge for a card payment.
`componentIsAvailableNotChecked`	The `isAvailable()` method was not called before rendering the `Component`. The component may not be supported by the customer's device. After you create the `Actionable`, call the `isAvailable()` method to verify that the device supports the payment method. This does not apply to the `CheckoutComponent`.
`componentInvalid`	The selected component's inputs are invalid. For the `Flow` component, this is also called if there are no embedded components selected.
`componentNotSupported`	The name specified when creating the `Actionable Component` using the `create()` method is not supported. If you provide `enabled_payment_methods` or `disabled_payment_methods` options when you create the payment session, ensure you also include the payment method that you want to offer. If you provide `enabled_payment_methods` or `disabled_payment_methods` options when you create the payment session, ensure you also include the payment method that you want to offer. You must also ensure that the `currency` and `billing.address.country` values you provide to the payment session match the payment method's requirements.
`configurationInvalid`	The `Configuration` provided when initializing Flow for mobile was invalid. After you create a payment session in your server-side integration, ensure you return the public key and the entire payment session response object to the client-side and provide it to Flow for mobile.
`invalidSetup`	The SDK was initialized or invoked with an invalid setup. For example: Missing or malformed `publicKey` Missing or partial payment session Calling methods in the wrong order Using unsupported configuration combinations Review your initialization of Flow for Mobile and payment session payload, then re-create the session and retry.
`merchantHandleSubmitCallbackFailed`	The payment session submission using the `handleSubmit` callback failed.
`merchantRejectedTokenDetails`	The merchant rejected the token using the `onTokenized` callback.
`methodNotSupported`	The `tokenize()` method is not supported for the selected component. For the `Flow` component, this is also called if a card component is not embedded.
`paymentMethodAttemptFailed`	The payment attempt for the payment method specified in `details.type` encountered an unexpected failure. Unexpected failures may occur when Flow integrates with a payment method's client-side library, or makes network requests to the payment method's endpoints. If you persistently encounter the error for a specific payment method, this could be caused by your account configuration. For example, incomplete onboarding to a payment method. Contact your account manager or request support.
`paymentRequestDeclined`	The payment request was declined. The payment's ID is provided in the `details.paymentId` property. You can fetch the details of the payment by calling the Get payment details endpoint, or searching for the payment record in the Dashboard. The `paymentRequestDeclined` enum case contains one of the following messages: `not_enough_funds` – The customer does not have enough funds for the transaction. `invalid_payment_session_data` – You provided invalid details when creating the payment session. See the API reference for additional field details. `invalid_customer_data` – The customer provided invalid details. `merchant_misconfiguration` – Your account has invalid configurations. `try_again` – The payment request was declined due to technical issues. Contact your account manager or request support. Flow for mobile automatically displays these error messages to the customer, with suggested next actions to improve retry success.
`paymentRequestFailed`	The payment request failed due to an unexpected error or network issue. Any additional error codes from the network requests are provided in the `details.requestErrorCodes` property. See the possible error codes for the Request a payment endpoint for more information. Customers can typically complete their payment after a retry. If you persistently encounter the error for a specific payment method, this could be caused by your account configuration. Contact your account manager or request support.
`paymentSessionFailed`	The payment session request failed due to an unexpected error or network issue. If you persistently encounter this error for a specific payment method, contact your account manager or request support.
`serverCommunicationError`	A required backend response could not be retrieved due to a network or server issue. Check connectivity and server availability, inspect any attached request error details, and retry. If the issue persists, contact your account manager or request support.
`serverCommunicationError`	A required backend response could not be retrieved due to a network or server issue. Check connectivity and server availability, inspect any attached request error details, and retry. If the issue persists, contact your account manager or request support.
`updateParametersInvalid`	The `updateDetails` passed to the `CheckoutComponents.update()` method contains invalid values.
`validationFailed`	One or more input values failed client-side validation for the selected component. Ensure all required fields are present and correctly formatted, update the inputs, and retry the operation.
`validationFailed`	One or more input values failed client-side validation for the selected component. Ensure all required fields are present and correctly formatted, update the inputs, and retry the operation.