Considerations and Limitations

Consider these guidelines and limitations when developing features that use the PaymentsService API.

PaymentsService Considerations

Be aware of the following considerations when using PaymentsService in your Lightning app.

PaymentsService is built on top of mobile operating system and device features. PaymentsService’s capabilities therefore depend on Android or iOS features, which are subject to change beyond our control. When mobile operating system features change, the behavior of PaymentsService can change without notice.
Calling getSupportedPaymentMethods or collectPayment requires passing in an options object.
The options object has some required fields and missing those fields results in the Payments plugin not working properly. See the PaymentsService API for the required fields.
Tap to Pay on Android devices must be on Android 13 or higher.
The Android device’s KeyStore must support hardware-backed key agreements.
- This requirement depends on the hardware capabilities of the device. An Android device on Android 12 or lower, even if the device is upgraded to Android 13, might not meet the requirement. Most modern Android devices should already support this capability, but older or lower-end devices may not.
- For example, devices like the Samsung Galaxy Tab Active4 Pro are no longer supported in Stripe SDK versions 5.0.0 and higher (according to official Stripe documentations).
Developer Options must be disabled to start and complete a Tap to Pay transaction. If Developer Options are enabled, an error message is shown indicating they must be turned off.
- If Developer Options are enabled, the user must quit the app, disable Developer Options, and then relaunch the app.