Payment Services is powered by Commerce Services and deployed as SaaS (software as a service). You connect your Commerce instance using an API key and a private key, and specify the data space in the configuration. You set up this connection only once.
See Commerce Services Connector in the core user guide for detailed information about this service.
To consume a Commerce SaaS service, you must use your instance’s API keys, which are created and managed in your My Account Dashboard. Two different API key pairs can be created for a Commerce account—one for sandbox and one for production (live payments)—though only one pair can be actively used at a time.
Need help with accessing your My Account dashboard? See Create a Commerce account in the core user guide.
A given API key pair is valid for all Commerce Services in an environment, so if you already have Commerce Services configured for your Commerce instance your API key pair is already present in the Admin. If your private API key is lost, a new API key pair must be generated and applied to the Commerce Services configuration in the Admin.
To learn how to generate an API key for either sandbox or production environments, see Commerce Services Connector in the core user guide.
If you regenerate an API key pair and change the SaaS Identifier, all Commerce Services used by this instance connect to a different data store and your access (including previously stored data) is lost. It is recommended that you do not regenerate an API key pair and change the SaaS Identifier on an active production instance.
Some Adobe Commerce and Magento Open Source features are deployed as SaaS (software as a service)—known as Commerce Services. To use these services, you must connect your Commerce instance to these services using an API key and a private key, and specify the desired data space in the configuration.
When you create a Commerce account, identified by a MageID, you can generate a Commerce API key and private key. To use Commerce Services, such as Payment Services, Product Recommendations, or Live Search, the license-holder must generate these keys in order to pass entitlement validation. These keys can then be passed to the systems integrator or development team that manages the projects and environments on behalf of the license-holder. If you are a solution integrator, you are also entitled to use these services for your own needs. In that case, the signer of the Commerce partner contract should generate the keys.
Log in to your Commerce account at https://account.magento.com/customer/account/login.
Under the Magento tab, select API Portal on the sidebar.
From the Environment menu, select Sandbox, then Production.
API keys are required for both environments.
Enter a name in the API Keys section and click Add New.
This action opens a dialog for downloading the new key.
This dialog is the only opportunity you have to copy or download your key.
Click Download then click Cancel.
The API Keys section now displays your API key.
Copy both the API key and private key when you select or create a SaaS project.
See SaaS in the core user guide for more detailed information.
The same API key can be used across instances, but each instance must have its own SaaS Data Space.
When you create a SaaS project, Commerce generates one or more SaaS data spaces depending on your Commerce license:
If you do not see the Commerce Services Connector section in the Commerce configuration, you must install the Commerce modules for your desired Commerce Service, such as Payment Services.
To select or create a SaaS project, request the Commerce API key from the Commerce license holder for your store.
On the Admin sidebar, go to Stores > Settings > Configuration.
In the left panel, expand Services and choose Commerce Services Connector.
In the API Keys section, paste your key values.
Add key values for both sandbox and production environments.
Click Save Config.
When you save, if there are any SaaS projects associated with your API key, those projects appear in the SaaS Project field in the SaaS Identifier section.
If no SaaS projects exist, click Create Project. Then enter a name for your SaaS project in the Project Name field.
To use for the current configuration of your Commerce store, select the SaaS Data Space.
If you regenerate your keys in the API Portal section of My Account, immediately update the API keys in the Admin configuration. If you generate new keys and do not update them in the Admin, your SaaS extensions will no longer work and you will lose valuable data.
You can change the names by clicking the Rename this Project or Rename Data Space buttons respectively.
The first step in onboarding Payment Services is to configure your Commerce Services in the Admin.
On the Admin sidebar, go to Sales > Payment Services.
Click Configure Commerce Services.
This option is visible if you have not yet configured Commerce Services for your account.
You are directed to the configuration area in the Admin, Stores > Settings > Configuration > Commerce Services Connector, to configure your Commerce Services Connector.
To configure your Commerce Services, follow the steps described in Commerce Services.