Payment provider configurations
Target Audience: Administrators, Integration Managers, Superusers
This section describes how you can set up integrations between different PSP's and Payway.
PSP – Payment service provider¶
A Payment service provider, PSP, is a service to handle payments online. To be able to handle online payment a specific certificate is required.
Getting these certificates requires a lot of processes so the most common way is to integrate your service to an existing PSP. This is the case for Payway, we control the lifetime of a subscription but we use different PSP to charge the end-customers credit card.
The process is that a customer initiates an order, we communicate with a PSP, either by sending the customer to a page controlled by the PSP (see picture below) or through APIs. The customer supplies their card information on an input-form controlled by the PSP and Payway gets a token, representing the customers’ credit card. The token is used when charging the credit card. Payway doesn’t store the CCV code or a full credit card number.
To setup up a payment provider configuration you go to PAP => Security => Payment provider configurations. From there the setup can vary from provider to provider. But it follows the same basic flow.
Each configuration is connected to n number of titles and requires some form of authentication credentials, a.k.a. API keys.
It is important to realize that the configuration is the connection between Payway and the PSP.
This enables purchases and recurring payments in Payway for the titles connected to the configuration.
Removal of a configuration¶
Removal of payment provider configuration will in effect remove the ability to perform purchases and recurring payments on those titles connected to the configuration.
Removal of a title from a configuration¶
Removal of a title from a payment provider configuration will in effect remove the ability to perform purchases and recurring payments on that title connected to the configuration.