SCPError

The SDK is busy executing another command. The SDK can only execute a single command at a time. You can use the paymentStatus or connectionStatus properties on your SCPTerminal instance (or the corresponding delegate methods) to determine if the SDK is ready to accept another command.

Canceling a command failed because the command already completed.

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

Already connected to a reader.

Your implementation of fetchConnectionToken called the completion block with (nil, nil). Please make sure your integration completes with either a connection token or an error.

processPayment was called with an unknown or invalid PaymentIntent. You must process a payment immediately after collecting a payment method.

collectPaymentMethod or processPayment was called with a nil PaymentIntent.

processRefund was called without calling collectRefundPaymentMethod beforehand.

The RefundParameters object has invalid values. The Charge ID (ch_123abc) can be found on the PaymentIntent object, which you should get from your backend.

A PaymentIntent was referenced using an invalid client secret.

The SDK must be actively Discovering Readers in order to successfully connect to a reader. See documentation on -[SCPTerminal discoverReaders:delegate:completion:] and -[SCPTerminal connectReader:completion:]

Before connecting to a reader, it must have already been discovered in the current discovery session. Trying to connect to a reader from a previous discovery session is not supported.

discoverReaders was called using an invalid SCPDiscoveryConfiguration. Your app selected a discovery method that is either incompatible with the selected device type or attemped to use simulated or locationId with a reader which does not support simulated or locationId. Currently chipper2X is the only reader which supports simulated and verifoneP400 is the only reader which supports use of locationId for location filtering.

No longer used

collectPaymentMethod was called with a nil SCPReaderDisplayDelegate, but the SCPTerminal.connectedReader does not have a built-in display, and requires that your app support displaying messages from the reader to your user.

installUpdate was passed a nil SCPReaderSoftwareUpdate.

-[SCPTerminal connectReader:completion:] 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.

This feature is currently not available for the selected reader.

The command was canceled by your app.

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

• The user disabled location services in the system settings.
• The user denied access to location services for your app.
• The user’s device is in Airplane Mode and unable to gather location data.

This error indicates that Bluetooth is turned off, and the user should use Settings to turn Bluetooth on.

If Bluetooth is on but the app does not have permission to use it, a different error (SCPErrorBluetoothError) occurs.

Scanning for bluetooth devices timed out.

Bluetooth Low Energy is unsupported on this iOS device. Use a different iOS device that supports BLE (also known as Bluetooth 4.0)

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

Updating the reader software failed because the update was interrupted.

The card is not a chip card.

The swipe could not be read.

Reading a card timed out.

The card was removed during the transaction.

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.

Your terminal delegate will receive -[SCPTerminalDelegate terminal:didReportReaderEvent:info:] with SCPReaderEventCardRemoved when the card is removed.

The Chipper 2x and WisePad 3 will beep until the card is removed.

The reader is busy.

An incompatible reader was detected. You can only use the Stripe Terminal iOS SDK with one of Stripe’s pre-certified readers.

Could not communicate with the reader.

Generic bluetooth error.

Among other things, it may indicate that the app does not have permission to use Bluetooth (iOS 13+).

Connecting to the bluetooth device timed out. Make sure the device is powered on, in range, and not connected to another app or device. If this error continues to occur, you may need to charge the device.

The Bluetooth device was disconnected unexpectedly.

Generic reader software update error.

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

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

-[SCPTerminal processPayment:completion:] 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 -[SCPTerminal checkForUpdate:] and -[SCPTerminal installUpdate:delegate:completion:].

The reader returned from discovery does not have an IP address and cannot be connected to. The IP address should have been set by the SDK during registration of the reader. Try registering the reader again.

Connecting to reader over the internet timed out. Make sure your device and reader are on the same Wifi network and your reader is connected to the Wifi network.

Connecting to the reader failed because it is currently in use and SCPConnectionConfiguration.failIfInUse was set to true.

Try to connect again with failIfInUse = false, or choose a different reader.

A reader is in use while it’s collecting a payment.

Unexpected SDK error.

The Stripe API declined the payment. Inspect SCPProcessPaymentError.requestError property for more information about the decline, including the decline code.

The reader declined the payment. Try another card.

The refund failed. The customer’s bank or card issuer was unable to process it correctly (e.g., a closed bank account or a problem with the card)

The SDK is not connected to the internet.

The underlying request timed out.

The underlying request returned an API error.

The API response from Stripe could not be decoded.

Generic network error

Your implementation of -[SCPConnectionTokenProvider fetchConnectionToken:] called the completion block with an error.

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. -[SCPTerminalDelegate terminal:didReportUnexpectedReaderDisconnect:] will be called if the SDK is able to successfully auto-disconnect. If it does not successfully auto-disconnect (didReportUnexpectedReaderDisconnect will not be called and SCPTerminal.connectionStatus will still be SCPConnectionStatusConnected) you can attempt again via -[SCPTerminal disconnectReader:] or you can instruct your user to disconnect manually by turning the reader off.

Note this error will only occur in one of the following calls:

• -[SCPTerminal createPaymentIntent:completion:]
• -[SCPTerminal retrievePaymentIntent:completion:]
• -[SCPTerminal collectPaymentMethod:delegate:completion:] if connected to a Verifone P400 or a BBPOS WisePOS E
• -[SCPTerminal processPayment:completion:]
• -[SCPTerminal cancelPaymentIntent:completion:]
• -[SCPTerminal readReusableCard:delegate:completion:]
• -[SCPTerminal collectRefundMethod:parameters]
• -[SCPTerminal processRefund:completion]