[Mobile Payments] Handle specific Tap on Mobile errors from the Stripe SDK

[joshheald]

Description

In sTAP Away, we're adding support for Tap on Mobile payments using Stripe's SDK. Broadly, the process is the same for connection and payment with a bluetooth reader, however, there are error states specific to Tap on Mobile, some of which we should surface to the user.

Some of these are taken from Apple's ProximityReader.PaymentCardReaderSession, others from Stripe's SDK. In practice, Stripe's SDK errors are the only ones we'll be likely to see. Not all of these need to be shown to the user, it's a list for reference and decision making.

Stripe

• No passcode set
• Not signed in to iCloud
• NFC disabled
• Failed to prepare built in reader
• ToS setup cancelled
• ToS not yet accepted
• ToS acceptance failed
• Invalid merchant
• Merchant blocked
• Device banned
• Unsupported device configuration

Apple

• readNotAllowedDuringCall
• nfcDisabled
• readFromBackgroundError
• readerSessionNetworkError
• invalidAmount
• invalidCurrencyCode
• paymentCardDeclined