Platform

The Payment Service communicates with an external Payment Service Provider. This communication is encrypted and secured by certificates. Those certificates, i.e. Thawte TLS RSA CA G1.pem and DigiCert Global Root G2.pem in the case of Adyen, have to be imported to the application server. Please check the Installation and Update Guide for a detailed description on the import of certificates.

Transaction Backends

The Payment Service communicates with SDC to retrieve and store transactions. The system level configuration for the Payment Service includes the connection settings to those required services. The settings are configured in :

Table 1. payment-service.properties
Property	Description
remote-services.sdc.appUrl	The base URL for communication with SDC (Tx Pool)

In the case of GK GO self service stores, the transactions are handled by the Basket Service. The connection to this service is configured in :

Table 2. payment-service.properties
Property	Description
remote-services.basket-service.appUrl	The base URL for communication with the Basket Service

Fiscalization

A number of countries require that each sales transaction within a store is registered and signed by a fiscal module. Other data may also need to be stored. The country-specific requirements are covered by Fiscalization Service. The country-specific endpoints are configured in payment-service.properties. The Payment Service decides which endpoint to select for each payment request, based on the country information stored in the transaction.

Table 3. payment-service.properties
Property	Description
remote-services.fiscal-service-<country code>.appUrl	This parameter defines the URL to the service

Points Payment

GK Self Scanning supports payments with points from loyalty accounts. To retrieve account information and book the used points, the connection to GK Loyalty Service has to be configured in :

Table 4. payment-service.properties
Property	Description
remote-services.loyalty-service.appUrl	The base URL for the Loyalty Service

Landscape Support

Remote services with landscape support have the default configured URL containing the system-landscape.id property placeholder, e.g. http://localhost:8080/service-name/sl/${system-landscape.id}. This placeholder is resolved automatically by the platform. The resolved value is the current landscape identifier; therefore, the called remote service is within the same landscape as the calling SSS. If the landscapes are disabled, then a default value is filled and the called remote service ignores it.

If a custom project needs landscapes to be handled differently (e.g. the landscape identifier is in the hostname or port number), the URL format can be customized directly in the project using the ${system-landscape.id} placeholder in the appropriate place.