TerminalErrorCode

Error reported when a timeout occurs while processing a collect inputs operation.

The device is offline and the PaymentIntent was created with OfflineBehavior.REQUIRE_ONLINE.

Error reported when a PaymentIntent was created with OfflineBehavior.FORCE_OFFLINE and the reader in use is not configured to operate offline. Use the Terminal Configuration API to enable the functionality or retry with another value for OfflineBehavior.

Error reported when forwarding stored offline payments. The fetched connection token was generated with a different account ID than the stored payment.

Error reported while forwarding offline payments when the connection token provider returns an error.

The reader failed to read the data from the presented payment method. If you encounter this error repeatedly, the reader may be faulty.

Error reported when processing a PaymentIntent that doesn't have a corresponding create request. In this situation, the PaymentIntent should be created again. This would typically happen if:

Error reported when a livemode payment attempts to forward while the SDK is operating in testmode.

Error reported when a testmode payment attempts to forward while the SDK is operating in livemode.

Error reported when collectPaymentMethod was called while online and processPayment was called while offline. Retry the payment by calling collectPaymentMethod() again.

Processing a payment while offline and the card's verification failed. Please try a different card.

Processing a payment while offline and the card was identified as being expired.

Error reported when processPayment was called while offline and the presented card was authenticated with an online PIN. Retry the payment by calling collectPaymentMethod() again.

Error reported when collectPaymentMethod or processPayment was called while offline and the presented card was an Interac card. Retry the payment by calling collectPaymentMethod() again.

Error reported when collectPaymentMethod or processPayment was called while offline and the card was read using the swipe method. Payment method data collected using the swipe card read method cannot be processed offline. Retry the payment by calling collectPaymentMethod() again.

Error reported when the PaymentIntent's currency is not configured as a valid currency for offline transactions.

There is no stored account with which the SDK can associate offline operations. Connect to a reader while online to save an account for offline operations.

Connecting to the reader failed. To connect to a reader offline, the SDK must have connected to a reader of the same type within the last several weeks.

Error reported when the offline payments database has too many records. The Terminal should be brought back online to forward payments before collecting more.

Failure in Terminal.processPayment, reported when the PaymentIntent's amount exceeds the configured allowable maximum amount for offline transactions.

The SDK is running on an unsupported version of Android. This occurs when an integrator overrides minSdkVersion.

The current session has expired and the reader must be disconnected and reconnected. The SDK will attempt to auto-disconnect for you and you should instruct your user to reconnect it. TerminalListener.onUnexpectedReaderDisconnect will be called if the SDK is able to successfully auto-disconnect. If it does not successfully auto-disconnect, TerminalListener.onUnexpectedReaderDisconnect will not be called and connectionStatus will still be ConnectionStatus.CONNECTED and you can attempt to disconnect via Terminal.disconnectReader or you can instruct your user to disconnect manually by turning the reader off.

Failure to fetch a connection token from the ConnectionTokenProvider

The API response from Stripe could not be decoded.

The underlying request returned an API error.

Failure to connect to Stripe's API.

The underlying request timed out.

The reader declined the payment. Try another card.

The Stripe API declined the payment. If this error code is returned, .getApiError will return more details on the decline.

Unexpected SDK error

Terminal.processPayment was called from a reader with an unsupported reader version. You will need to update your reader to the most recent version in order to accept payments. We suggest you prompt your user update the reader via the update flow that you have implemented using Terminal.checkForUpdate and Terminal.installAvailableUpdate.

NFC must be enabled on the device to allow COTS payment processing.

Updating the reader software failed because there was an error communicating with the update server.

Updating the reader software failed because there was an error communicating with the reader.

Generic reader software update error.

The reader cannot be reached because it is already connected to a different device.

The USB device was disconnected unexpectedly, reconnecting.

The USB device was disconnected unexpectedly.

The Bluetooth device was disconnected unexpectedly, reconnecting.

The Bluetooth device was disconnected unexpectedly.

Generic bluetooth error.

Could not communicate with the reader.

The reader is busy.

The connected account is not enabled to use the specified feature. Retry without the parameter in question or contact Stripe support to enable the feature on this account.

Scanning for USB devices timed out.

A card can only be used for one transaction, and must be removed after being read. Otherwise, subsequent collectPaymentMethod attempts will fail with this error.

Customer is required to give consent for this operation, such as card collection.

The card was removed during the transaction

Reading a card timed out

The swipe could not be read.

The card is not a chip card.

Updating the reader software failed because the update was interrupted.

Updating the reader software failed because the reader's battery is too low. Charge the reader before trying again.

Scanning for bluetooth devices timed out.

Access to location services is currently disabled. This may be because:

The operation was cancelled by the user

The SDK is running on a version of Android older than M/SDK 23.

The SDK is running in a debuggable application. This is not supported for security and compliance reasons. Please test the Tap to Pay on Android SDK with a simulated version of the reader by setting DiscoveryConfiguration.isSimulated to true.

The Android device the SDK is running on has been tampered. Some examples of tampering include:

The SDK is running on a version of Android older than 10/SDK 29.

The Android device the SDK is running on is unsupported by the local mobile library. Reasons for this might include:

The local mobile library hasn't been included with the SDK.

A tipping parameter is misconfigured or invalid

A required parameter is misconfigured or invalid

A parameter that is required for your Terminal configuration is missing.

User denied USB access when requested by the SDK.

Terminal.connectBluetoothReader was called from an unsupported version of the SDK. In order to fix this you will need to update your app to the most recent version of the SDK. We suggest you prompt your user to update their app, assuming there is an update app version with a supported version of our SDK.

The Terminal operation shouldn't have been called at this time.

The Terminal operation that was called isn't supported for this device type

A PaymentIntent was referenced using an invalid client secret.

Terminal.processPayment was called with an unknown or invalid PaymentIntent. You must process a payment after collecting a payment method. Successfully processed payments may not be processed again.

Either android.permission.BLUETOOTH_CONNECT or android.permission.BLUETOOTH_SCAN must be enabled.

Already connected to reader

No reader is connected. Connect to a reader before trying again.

Cancelling an operation failed