The payment gateway object and the allowed CRUD operations on the related resource endpoint
Commerce Layer is integrated out-of-the-box with some of the most common payment gateways, all compliant with the PSD2 European regulation so that you can implement a payment flow that supports SCA and 3DS2 by using the specific gateway official JS SDK.
The currently supported gateways are:
Other types of gateways are also available, such as:
- External gateways — to integrate any other payment service that is not available out-of-the-box (even your custom one).
- Manual gateways — useful to process wire transfers, cash payments, and other kinds of manual payments.
You can set up a payment gateway from the admin UI. All you need to do is select the type of gateway you want to use and provide all the credentials requested by the selected payment service.
Configuring a payment gateway for a market lets you safely process payments through the API. You can connect different gateways to different markets through the available payment methods.
Check the related ER diagram and explore the flowchart that illustrates how the payment gateway resource relates to the other API entities.
Check the related guide to learn more about how Commerce Layer handles the server-side part of the integration process with each specific gateway.
This is an immutable API, meaning that create, update, and delete operations are not allowed on this endpoint. You can only fetch a list of payment gateways or a specific single one.