Configuration Options
- 10 Jan 2024
- 1 Minute to read
- Print
- DarkLight
Configuration Options
- Updated on 10 Jan 2024
- 1 Minute to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
The Mobile Payments app can be customized in the following ways:
Lock an Amount
On a Salesforce Transaction record, if you set the Mobile Lock Amount = "Yes", the Mobile Payments app will not allow the Amount value to be changed for that Transaction.
Skip the Intro Screen
On a Salesforce Transaction record, if you set the Mobile Skip Intro Screen = "Yes", the Mobile Payments app will not show the Intro screen (Description, Amount, Currency, etc) for that Transaction.
Set Payment Methods
Using Tap to Pay
Users can now set Accepted Payment Method = "Tap to Pay" on the Payment Gateway, Transaction, and Payment User Override objects.
If values are set on the Transaction record Accepted Payment Methods field or the Payment Gateway record Accepted Payment Methods field, only the set Payment Methods will be available for the selected Payment Gateway or Transaction.
The Accepted Payment Methods fields are evaluated in the following order:
- If the Transaction Accepted Payment Methods field is set, use those values for the Transaction.
- Otherwise, if the Payment Gateway Accepted Payment Methods field is set, use those values for the Transaction.
- If neither of those fields are set, all Payment Methods are available for use.
Require an Existing Transaction for Mobile
The Require Existing Transaction for Mobile field on the Payment Gateway record is available in the Mobile Payments app for Android devices. This setting blocks users from processing a payment in the app if there isn’t an existing Transaction in Salesforce before the app is launched.
If this field is checked and a user tries to capture a payment from the Mobile Payments app, the user will get an error.