After you’ve created a PaymentIntent, the next step is to collect a payment method with the SDK.
In order to collect a payment method, your app needs to be connected to a reader. The connected reader will wait for a card to be presented after your app calls
This method collects encrypted payment method data using the connected card reader, and associates the encrypted data with the local PaymentIntent.
You can cancel collecting a payment method using the
Cancelable object returned by the iOS or Android SDK, or calling
Collecting a payment method happens locally and requires no authorization or updates to the Payment Intents API object until the next step, process the payment.
When collecting a payment method using a reader like the BBPOS Chipper 2X BT, without a built-in display, your app must be able to display events from the payment method collection process to users. These events help users successfully collect payments (e.g., retrying a card, trying a different card, or using a different read method).
When a transaction begins, the SDK passes a
ReaderInputOptions value to your app’s reader display handler, denoting the acceptable types of input (e.g., Swipe, Insert, Tap). In your app’s checkout UI, prompt the user to present a card using one of these options.
During the transaction, the SDK might request your app to display additional prompts (e.g., Retry Card) to your user by passing a
ReaderDisplayMessage value to your app’s reader display handler. Make sure your checkout UI displays these messages to the user.