Salesforce Billing Developer Guide
jNote: 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.
Guidelines for the Hosted Card Payments Lightning Component
When you set up the wrapper and design for your hosted payment component, consider
important guidelines.
| Available in: Salesforce Billing Winter ‘20 and later |
- Customers can pay only against an account.
- In multicurrency orgs, customers can make payments only in the account’s currency. In single-currency orgs, the component uses the org's currency. When handling currency, the component retrieves SavePaymentCard or PaymentSale’s currency from the customer’s account. It won’t accept CurrencyIsoCode as an input parameter.
- Component field positions can’t be changed.
- The component doesn’t support custom fields.
- To prevent fraudulent activity, we recommend developing guardrails around the users that can access your payments page. We also recommend that your payments page is not the first page in your Experience Cloud site or Lightning page.