ADMINISTRATION GUIDE | PUBLIC

Document Version: 1.0 – 2018-10-04

Administration Guide for SAP Digital Payments

Add-On
© 2018 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 About this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1 System Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2 Payment Card Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

3 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1 Consumer Applications: Releases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
3.2 Consumer Applications: Transport Layer Security (TLS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
3.3 Additional Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
3.4 User Account with Payment Service Provider. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4 Setup Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1 Account Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Creating a Subaccount (SaaS Tenant) in your Global Account (GA). . . . . . . . . . . . . . . . . . . . . . . 10
Configuring the Identity Provider (IdP) and Setting Up Authentication. . . . . . . . . . . . . . . . . . . . . 11
Subscribing the SaaS Tenant to the SAP Digital Payments Add-On. . . . . . . . . . . . . . . . . . . . . . . 13
Creating Role Collections and Assigning Them to User Groups. . . . . . . . . . . . . . . . . . . . . . . . . . 13
Enabling Machine-to-Machine (M2M) Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
4.2 Activating PSPs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
4.3 Connecting the SAP Digital Payments Add-On and the PSP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.4 Consumer Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
4.5 Payment Service Provider Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

5 Security and PCI Compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

6 Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Administration Guide for SAP Digital Payments Add-On

2 PUBLIC Content
1 About this Guide

This guide provides an introduction to digital payment services using the SAP digital payments add-on, and
describes the steps your system administrator must take to set up and configure the add-on.

Administration Guide for SAP Digital Payments Add-On

About this Guide PUBLIC 3
2 Overview

2.1 System Landscape

The system landscape for payment scenarios using the SAP digital payments add-on is composed of three
elements:

● Consumer application: The communication between the consumer application, such as SAP S/4HANA
Cloud, and the customer account in the SAP Cloud Platform works using REST Web services and is
generally triggered by the consumer application.
● SAP digital payments add-on on SAP Cloud Platform: The SAP digital payments add-on processes the
requests from the consumer application and routes them to the relevant external payment service provider
(PSP). The add-on contains one 'core' adapter and one adapter for each PSP. In addition, the customer
account establishes the connection to the SAP Fiori UI for the key user. Please note that messages from
the SAP digital payments add-on are issued in English only.

● Payment service provider: The SAP digital payments add-on and the external PSPs communicate using
Web services. Most of this communication is synchronous.

Administration Guide for SAP Digital Payments Add-On

4 PUBLIC Overview
2.2 Payment Card Processes

The consumer application can initiate the following services using the SAP digital payments add-on:

● Payment Card Creation

A user in a consumer application requests the creation of a payment card. This request is sent to the SAP
digital payments add-on. Based on settings made by the key user, the relevant PSP is determined and the
appropriate Web user interface for entering the payment card details is opened. The user enters the
payment card data and saves their entries. The request is sent to the PSP, which saves the payment card
data and creates a token as identification. This token replaces the payment card number. The payment
card data is returned to the consumer application so it can be used.
● Payment Card Deletion
A user in a consumer application requests the deletion of a payment card. This request is sent to the SAP
digital payments add-on. Based on the card token, the relevant PSP is determined and the request is sent
to the PSP in the appropriate format. The result of the request is returned to the consumer application.
It is also possible to simulate the deletion of payment cards. This enables you to check whether payment
cards can be deleted before deleting them permanently.
● Payment Card Payment Authorization
A user orders a product and wants to pay using a payment card. Approval for the amount of the transaction
must be obtained from the card holder's bank. The consumer application sends an authorization request
to the SAP digital payments add-on. Based on the card details, the relevant PSP is determined and the
request is sent to the PSP in the appropriate format. The PSP then processes the authorization and returns
the result to the consumer application via the SAP digital payments add-on.

Administration Guide for SAP Digital Payments Add-On

Overview PUBLIC 5
● Payment Card Payment Authorization Cancellation
A user cancels an order for which a payment card payment has already been approved. The consumer
application sends an authorization cancellation request to the SAP digital payments add-on. Based on the
card details, the relevant PSP is determined and the request is sent to the PSP in the appropriate format.
The PSP then processes the cancellation and returns the result to the consumer application via the SAP
digital payments add-on. Cancellation of the authorization process is not supported for all payment card
types and PSPs. In cases where it is not supported, the authorization remains until it automatically expires.
If cancellation is not possible, the consumer application is informed.
● Payment Card Settlement
The consumer application triggers settlement runs periodically to settle authorized payment card
payments. The authorization and card data are sent to the SAP digital payments add-on. Based on the card
details, the relevant PSP is determined and the request is sent to the PSP in the appropriate format. The
PSP then processes the settlement and returns the result to the consumer application via the SAP digital
payments add-on.
● Payment Card Payment Refund
The consumer application requests a refund when a card payment that has already been settled has to be
paid back to the customer, for example in the case of a return. The request contains reference information
about the payment to be refunded. The relevant PSP is determined and the data is sent to the PSP in the
appropriate format. The PSP then processes the refund and returns the result to the consumer application
via the SAP digital payments add-on.
● Digital Payment Advice
The consumer application executes a report periodically to request advice details about the digital
payments that have been processed. This request is sent to the SAP digital payments add-on. The add-on
requests the advice details from all relevant PSPs. The advice details are merged and returned to the
consumer application.

Administration Guide for SAP Digital Payments Add-On

6 PUBLIC Overview
3 Prerequisites

3.1 Consumer Applications: Releases

The SAP digital payments add-on can be used in combination with various consumer applications. For
information on which consumer application releases are compatible with the SAP digital payments add-on,
please refer to the documentation of the relevant consumer application.

3.2 Consumer Applications: Transport Layer Security (TLS)

If you want to use the SAP digital payments add-on, the relevant ABAP system must be able to make a
connection using TLS 1.2 (or higher). TLS 1.0 or 1.1 connections are not compatible.

If your consumer application is a cloud application from SAP, you do not have to take any measures because
SAP ensures that TLS 1.2 is implemented.

If your consumer application is an on-premise application, please refer to the procedure described in 510007
.

 Example

This is an example of what a TLS 1.2 configuration might look like:

ssl/client_ciphersuites 151:PFS:HIGH:!eRC4:!eNULL:!aNULL:!mMD5

3.3 Additional Software

● Browser
You need a Web browser, preferably Google Chrome, Internet Explorer, or Mozilla Firefox.
● Identity Management
You need an Identity and Access Management (IAM) system.

Administration Guide for SAP Digital Payments Add-On

Prerequisites PUBLIC 7
3.4 User Account with Payment Service Provider

The SAP digital payments add-on connects the consumer applications to services provided by external PSPs.
The PSP licenses, however, are not included with the SAP digital payments add-on. You must obtain the PSP
licenses from the individual PSPs. You will need the PSP user account data to connect the SAP digital payments
add-on to the PSP services.

Administration Guide for SAP Digital Payments Add-On

8 PUBLIC Prerequisites
4 Setup Activities

4.1 Account Setup

This section describes the steps to be performed by an SAP customer to set up a fully functional account for
the SAP digital payments add-on.

Overview

You must perform the following steps (see below for overview graphic and further details of each step):

1. Create a subaccount (SaaS tenant) in your global account (GA).

Once you have access to your SAP Cloud Platform global account, you need to create subaccounts to use
applications and services on the SAP Cloud Platform. The SAP digital payments add-on is delivered with
two tenants: a test tenant for testing integration and a productive tenant for productive usage. We strongly
recommend that you create and configure two subaccounts to distinguish between the usages.
2. Configure the Identity Provider (IdP) and set up authentication.
After you have created your subaccounts, you need to establish mutual trust between your subaccount
and your IdP. You also need to define two user groups in your IdP, one for administrators, and one for key
users, so that after the configuration of role collections in the SAP Cloud Platform cockpit (see below), the
users assigned to these groups can access the SAP digital payments add-on.
3. Subscribe the SaaS tenant to the SAP digital payments add-on.
You need to subscribe to the SAP digital payments add-on in your subaccount in the SAP Cloud Platform
cockpit.
4. Create role collections and assign them to user groups or users.
After you have subscribed to the SAP digital payments add-on application, you need to create role
collections and assign roles to users or user groups in the SAP Cloud Platform cockpit so that you can
manage access to the application.
5. Enable machine-to-machine (M2M) communication.
To enable M2M communication for the applications or systems that consume the SAP digital payments
add-on, for example an SAP S/4HANA system, you need to create a service instance of the service broker
that provides access to the APIs. You have to create this service instance in the Cloud Foundry
environment. To do this, you have to:
1. Enable Cloud Foundry in your subaccounts.
2. Create a Cloud Foundry space.
3. Enable the M2M quota for your subaccounts.
4. Create a service instance of the M2M service.
5. Obtain client credentials for M2M communication.

Administration Guide for SAP Digital Payments Add-On

Setup Activities PUBLIC 9
4.1.1 Creating a Subaccount (SaaS Tenant) in your Global
Account (GA)

Context

The SAP digital payments add-on is delivered with two tenants: a test tenant for testing integration and a
productive tenant for productive usage. We strongly recommend that you create two subaccounts to
distinguish between the usages, for example Digital Payments Test Account and Digital Payments
Productive Account.

For information on creating subaccounts in the SAP Cloud Foundry environment, refer to the SAP Cloud
Platform help topic Create Subaccounts Using the Cockpit.

● As Environment, choose Cloud Foundry.

● As Provider, choose Amazon Web Services (AWS).
● As Region, choose Europe (Frankfurt).

With respect to the Display Name and the Subdomain, we suggest that you add a suffix with your company
name at the end of the subdomain. We strongly recommend that you define the display name and the
subdomain name in such a way that you can easily distinguish between your productive account and your test
account.

Administration Guide for SAP Digital Payments Add-On

10 PUBLIC Setup Activities
For example, you could use the subdomain name <dp-test-yourcompanyname> and display name Digital
Payments Test Account for your test account, and the subdomain name <dp-prod-yourcompanyname>
and display name Digital Payments Productive Account for your productive account.

The respective URLs would then look like this:

● Test account: <dp-test-yourcompanyname>.demo-digitalpayments-

sap.cfapps.eu10.hana.ondemand.com
● Productive account: <dp-prod-yourcompanyname>.digitalpayments-
sap.cfapps.eu10.hana.ondemand.com

4.1.2 Configuring the Identity Provider (IdP) and Setting Up

Authentication

4.1.2.1 Establishing Mutual Trust Between the Subaccount

(UAA) and the IdP

Context

For your existing SAML2-compliant identity provider (IdP), you need to establish mutual trust between your
subaccount's UAA (SAML2 service provider) and your IdP. To do this, you must upload the corresponding XML
metadata files. This process varies depending on the IdP implementation used.

Proceed as follows to establish trust from the UAA to your IdP:

If you are using the SAP Cloud Platform Identity Authentication service, you will find more information under
Establish Trust with an SAML 2.0 Identity Provider in a Subaccount in the SAP Cloud Platform help topic
Establish Trust and Federation with UAA Using SAP Cloud Platform Identity Authentication Service.

If you are using a different IdP, you will find more information under Establish Trust with Any SAML 2.0 Identity
Provider in a Subaccount in the SAP Cloud Platform help topic Establish Trust and Federation with UAA Using
Any SAML Identity Provider.

Proceed as follows to establish trust from your IdP to the UAA:

The metadata (including public key) of your tenant's UAA (service provider) can be found at https://
<subdomain>.authentication.eu10.hana.ondemand.com/saml/metadata

 Note

As <subdomain>, use the subdomain names you defined when creating your test account and productive
account.

Administration Guide for SAP Digital Payments Add-On

Setup Activities PUBLIC 11
If you are using the SAP Cloud Platform Identity Authentication service, you will find more information under
Register SAP Cloud Platform Subaccount in the SAML 2.0 Identity Provider in the SAP Cloud Platform help topic
Establish Trust and Federation with UAA Using SAP Cloud Platform Identity Authentication Service.

Enter DigitalPayments@SAPCloud as the name for the application.

As Assertion Attribute Name for the Groups user attribute, enter Groups with initial capital.

If you are using a different IdP, you will find more information under Register SAP Cloud Platform Subaccount in
Any SAML 2.0 Identity Provider in the SAP Cloud Platform help topic Establish Trust and Federation with UAA
Using Any SAML Identity Provider.

4.1.2.2 Creating User Groups and Assigning Users to

Groups in the IdP

Context

1. Create two user groups.

You need two users groups in your IdP (one for administrators and one for key users). If you already have
user groups like this, you can use them.

 Note

If you are using the SAP Cloud Platform Identity Authentication service, you create the two groups
under Users & Authorizations User Groups .

 Note

If you are using the SAP Cloud Platform Identity Authentication service and you need to create new
users, you do this under Users & Authorizations User Management .

2. Assign users to the groups.

 Note

If you are using the SAP Cloud Platform Identity Authentication service IAS tenant, you must find the
users under User Management and assign them to the groups. It is not possible to open a group and
assign users to it.

Administration Guide for SAP Digital Payments Add-On

12 PUBLIC Setup Activities
4.1.3 Subscribing the SaaS Tenant to the SAP Digital
Payments Add-On

Context

You need to subscribe to the SAP digital payments add-on application in your subaccount in the SAP Cloud
Platform cockpit.

Proceed as described in the SAP Cloud Platform help topic Subscribe to Multitenant Business Applications in
the Cloud Foundry Environment Using the Cockpit.

For your test subaccount, subscribe to the application SAP digital payments add-on Demo. For your
productive account, subscribe to the application SAP digital payments add-on Prod.

4.1.4 Creating Role Collections and Assigning Them to User

Groups

After you have successfully subscribed to the SAP digital payments add-on, you need to create role collections
and assign roles so that you can manage access to the application.

4.1.4.1 Creating Role Collections

Context

For information on maintaining role collections, refer to the SAP Cloud Platform help topic Maintain Role
Collections.

You need to create two role collections, one for administrator and one for key user. We suggest you use the
names <dp-admin> and <dp-keyuser>.

When adding roles, use the following values:

● application identifier: digitalpayments!t16 (for your productive account) or digitalpayments-

demo!t16 (for your test account)
● role template: DigitalPaymentsAdministrator (for administrator) or DigitalPaymentsKeyUser (for
key user)
● role: DigitalPaymentsAdministrator (for administrator) or DigitalPaymentsKeyUser (for key
user)

Administration Guide for SAP Digital Payments Add-On

Setup Activities PUBLIC 13
4.1.4.2 Assigning Role Collections to Users or User Groups

Context

For information on assigning role collections to users or user groups using the SAP Cloud Platform cockpit,
refer to the SAP Cloud Platform help topic Assign Role Collections .

 Note

Note that you must do this for both of the role collections you have created (administrator and key user).

● If you are using the default trust configuration with SAP ID Service, you assign users to role collections
directly. For more information, see the SAP Cloud Platform help topic Directly Assign Role Collections to
Users.
● If you are using a custom trust configuration, for example SAP Cloud Platform Identity Authentication
service, you can either assign users to role collections directly or map role collections to user groups. For
more information about mapping role collections to user groups, see the SAP Cloud Platform help topic
Map Role Collections to User Groups. In the <value> field, provide the name of the user group that you
maintained in your IdP previously.

4.1.5 Enabling Machine-to-Machine (M2M) Communication

To enable M2M communication for your consumer applications, you need to create an instance of the service
broker that provides access to the APIs.

 Note

Currently, service instances can only be created in the Cloud Foundry environment.

4.1.5.1 Enabling Cloud Foundry in Your Subaccounts

Context

 Note

Note that you must perform these steps for both of the subaccounts that you have created.

Administration Guide for SAP Digital Payments Add-On

14 PUBLIC Setup Activities
Proceed as follows:

1. In your global account in the SAP Cloud Platform cockpit, navigate to the relevant subaccount and choose
Overview.
2. In the Cloud Foundry section, click Enable Cloud Foundry.
3. Choose a name for your organization. You can simply use the proposed name and click Create.
4. Wait until the creation process is finished.
5. On the left-hand side, you can see a new item called Spaces.

4.1.5.2 Creating a Cloud Foundry Space

Context

 Note

You must perform these steps for both of the subaccounts that you have created.

 Note

You can only create services within the scope of a Cloud Foundry space.

In the SAP Cloud Platform cockpit, proceed as follows:

1. Go to Spaces.
2. Click New Space.
3. Enter a name of your choice for the space. We recommend using digitalpayments.
4. Click Save.

For more information about creating a Cloud Foundry space, refer to the SAP Cloud Platform help topic Create
Cloud Foundry Spaces Using the Cockpit.

4.1.5.3 Enabling the M2M Quota for Your Subaccounts

Context

Before creating an instance of the service broker for M2M communication, you must first enable M2M
communication for the subaccount in question.

Administration Guide for SAP Digital Payments Add-On

Setup Activities PUBLIC 15
  Note

You must perform these steps for both of the subaccounts that you have created.

1. Go to your global account view in the SAP Cloud Platform cockpit and choose Entitlements in the
dropdown list.
2. At the top of the screen, click Edit.
3. Look for the relevant quota: SAP digital payments add-on M2M for test/demo (for testing purposes) or SAP
digital payments add-on M2M for production (for productive usage), and for the corresponding subaccount,
and select the service plan: standard.
4. Click Save.

For more information about adding quotas to subaccounts, refer to the SAP Cloud Platform help topic Add
Quotas to Subaccounts Using the Cockpit.

4.1.5.4 Creating an Instance of the M2M Service

Context

 Note

You must perform these steps for both of the subaccounts that you have created.

Proceed as follows:

1. In the SAP Cloud Platform cockpit in the relevant subaccount, go to the newly created space.
2. Choose Services Service Marketplace .
3. Select SAP digital payments add-on (for tests, M2M) or SAP digital payments add-on (for productive usage,
M2M) accordingly.
4. On the left-hand side, choose Instances.
5. Click New Instance.
6. Select Plan standard.
7. Click Next.
8. Click Next.
9. Enter an Instance Name for the service instance, such as dp-m2m.
10. Click Finish and the new instance appears in the list.

For more information about creating an instance, refer to the SAP Cloud Platform help topic Create Service
Instances Using the Cockpit.

Administration Guide for SAP Digital Payments Add-On

16 PUBLIC Setup Activities
4.1.5.5 Obtaining Client Credentials for M2M
Communication

Context

To authorize the communication between your consumer application and the SAP digital payments add-on,
client credentials are required. These can be obtained by creating a service key for the service instance you
created.

 Note

Note that you must do this for both of the subaccounts you have created.

Proceed as follows:

1. Click the name of the service you created previously.

2. Choose Service Keys.
3. Click Create Service Key.
4. Enter a name of your choice. We recommend that you use a name that identifies the system where you will
use the credentials, such as the system ID.
5. Click Save.

For more information about creating a service key, refer to the SAP Cloud Platform help topic Create Service
Keys Using the Cockpit.

 Note

The client credentials and other authorization-related details are stored in the service key. The service keys
are permanently stored in the Cloud Foundry environment of your subaccount. The data provided in the
service key created, such as clientid or clientsecret, will be needed to establish the communication
arrangement between your consumer application and the SAP digital payments add-on.

The procedure to establish connectivity between your consumer application and the SAP digital payments
add-on varies depending on the consumer application in question. For more information, please refer to the
documentation of your consumer application.

 Example

The following is an example of what a service key could look like:

"uaadomain": "authentication.eu10.hana.ondemand.com",

"tenantmode": "shared",

"sburl": "https://......-xsuaa.authentication.eu10.hana.ondemand.com",

"clientid": "sb-……345",

"verificationkey": "-----BEGIN PUBLIC KEY-----MABC….XYZ -----END PUBLIC KEY-----",

Administration Guide for SAP Digital Payments Add-On

Setup Activities PUBLIC 17
 "xsappname": "….345",

"identityzone": "<subdomain>",

"identityzoneid": " abc987654-a123-…..-b456",

"clientsecret": "abc……1234=",

"tenantid": "abc987654-a123-…..-b456",

"url": https://<subdomain>.authentication.eu10.hana.ondemand.com

 Note

Replace the placeholder <subdomain> with the subaccount you have created in the account setup
procedure.

4.2 Activating PSPs

Once you have set up your account, you need to activate the adapter(s) for the PSP(s) you want to use with the
SAP digital payments add-on. Each PSP has its own dedicated adapter.

To activate adapters, access the Payment Service Provider Status UI using the URLs below, and provide the
appropriate credentials.

 Note

You will need to replace <subdomain> with the subdomain names you created earlier.

For your test account:

https://<subdomain>.demo-digitalpayments-sap.cfapps.eu10.hana.ondemand.com/
pspStatus/index.html

For your productive account:

https://<subdomain>.digitalpayments-sap.cfapps.eu10.hana.ondemand.com/pspStatus/
index.html

When you access the UI, you will see a list of active/inactive PSPs. Simply select the row of the inactive PSP
you want to activate and click Activate.

The status then changes to and the PSP is ready for use.

Administration Guide for SAP Digital Payments Add-On

18 PUBLIC Setup Activities
4.3 Connecting the SAP Digital Payments Add-On and the
PSP

Context

To set up the connection between the SAP digital payments add-on and a PSP, all you have to do is enter the
account credentials provided to you by that PSP.

The URLs for the PSPs currently supported have the following format:

Stripe

Test account:

https://<subdomain>.demo-digitalpayments-sap.cfapps.eu10.hana.ondemand.com/stripeConfiguration/
index.html

Productive account:

https://<subdomain>.digitalpayments-sap.cfapps.eu10.hana.ondemand.com/stripeConfiguration/index.html

Paymetric

Test account:

https://<subdomain>.demo-digitalpayments-sap.cfapps.eu10.hana.ondemand.com/paymetricConfiguration/
index.html

Productive account:

https://<subdomain>.digitalpayments-sap.cfapps.eu10.hana.ondemand.com/paymetricConfiguration/
index.html

 Note

Replace the placeholder <subdomain> with the subaccount you created in the account setup procedure.

 Note

The user interface is only available in English.

1. Using the relevant URL, enter the user account credentials you received from your PSP and save.
For security reasons, the credentials are saved in a keystore. The secure credentials are masked on the UI.
For Paymetric you require Merchant GUID and Shared Key for the tokenization service, and XiPay User,
XiPay Password, and XiPay Merchant ID for the payment processes, such as authorization or settlement.
For more information on this, see Paymetric's help:
○ Set XiPay WSA Password
○ XiPay Routing
2. Check the connectivity by clicking Check Connection.

Administration Guide for SAP Digital Payments Add-On

Setup Activities PUBLIC 19
4.4 Consumer Applications

Context

Connectivity has to be established between your consumer application and the SAP digital payments add-on.
You have already maintained the technical details and credentials for the SAP digital payments add-on. For
further information, please refer to the documentation of your consumer application.

4.5 Payment Service Provider Determination

Once you have completed all the above setup activities, your key user needs to set up the PSP determination.
For further information on this, please refer to the User Guide for SAP Digital Payments Add-On.

Administration Guide for SAP Digital Payments Add-On

20 PUBLIC Setup Activities
5 Security and PCI Compliance

Please refer to the Security Guide for the SAP Digital Payments Add-On for information about security and PCI
compliance.

Administration Guide for SAP Digital Payments Add-On

Security and PCI Compliance PUBLIC 21
6 Support

If you need support with the SAP digital payments add-on, please create a customer incident using the
following component:

FIN-FSCM-HCP-DP

Administration Guide for SAP Digital Payments Add-On

22 PUBLIC Support
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

Administration Guide for SAP Digital Payments Add-On

Important Disclaimers and Legal Information PUBLIC 23
www.sap.com/contactsap

© 2018 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.

Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.

SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN