Mobile and Offline Developer Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
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

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 will result in the Payments plugin not working properly. See the PaymentsService API for the required fields.