Expand your payment ecosystem by bringing in externally tokenized payment methods into
your Salesforce org. Bring in external payment method tokens generated by using buyer-facing
portals or the Self-Service Billing portal, and save them as payment methods in your Salesforce
org. These externally saved payment methods are immediately available for use in payments batch
processing.
Required Editions
Available in: Lightning Experience
Available in: Enterprise, Performance, Unlimited, and
Developer Editions with Revenue Cloud
The Salesforce Payments feature is available with the Revenue Cloud Billing license, with a cost per transaction model
for both native and Bring Your Own payment gateways. Contact your Salesforce account
executive for more information.
If you purchased the Revenue Cloud Billing license on or before July 2025, contact your
Salesforce account executive to add the Salesforce Payments feature to your existing
license.
User Permissions Needed
To import payment method tokens:
Payment Admin
OR
Payment Operations User
permission set
To embed third-party UI components on the self-service Billing portal:
Billing Portal User permission set
Import Existing Tokenized Payment Methods
Migrate your customers’ existing payment data into your org as saved payment method records.
Import payment method tokens from native or third-party payment gateways, either individually
or in bulk.
To import an existing payment method token, include the existing payment token and related
tokenized details in your SavedPaymentMethod sObject API request.
To import multiple payment method tokens at once by using CSV files, use the Bulk API.
After importing the payment method tokens into your org, use the saved payment methods,
without any further configuration, for both batch payment processing and in the Sale, Authorize,
and Capture APIs.
Create Saved Payment Methods from Buyer-Facing Client-Side Components
Bring in saved payment methods into your Salesforce org by tokenizing your customers’
payment details using buyer-facing client-side components. You can use this method to bring in
tokens for payment method categories such as alternative payment methods, digital wallets, and
credit cards.
Get your customers to save their payment details on your storefront or client-side
component. The client-side component tokenizes the payment information by using a third-party
payment gateway. The payment gateway then returns a payment method token and related payment
metadata. Using the tokenized payment details, create a saved payment method synchronously or asynchronously.
You can also bring in saved payment methods by customizing the Self-Service Billing
portal to add third-party UI components.
After creating saved payment methods from buyer-facing portal or the Self-Service
Billing portal, you can use the newly added saved payment methods for payments
processing.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.
