Mobile and Offline Developer Guide

Mobile App Development with Lightning Web Components and LWC Offline
Create Mobile-Ready Components
Use Mobile Device Features in Mobile Apps
Request App Review
Scan Barcodes
Access Device Biometrics
Manage Calendar Events
Access Contacts
Scan Documents
Monitor Geofences
Use Location
Interact With NFC Tags
Tap to Pay
PaymentsService User Experience
Use the PaymentsService API
PaymentsService Example
Compatibility and Requirements
Considerations and Limitations
Offline Considerations and Limitations
Offline Environment Details
Use Salesforce Features While Offline
Development Tools and Processes
Quick Start Tutorials
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

PaymentsService User Experience

Your component can deliver any user experience you want, but you must follow a common flow for any component that calls for a Payment Service.

The user performs an action that triggers a collect payment flow. The operating system provides messages for the user to tap their credit card in the right direction. If the collect payment method isn’t successful, the plug-in provides an error message. If it’s successful, a PaymentIntent object is returned to the user, so they can perform any other follow-up actions on the Stripe dashboard, such as refund or cancel the payment, if needed.