Processing Digital Payments - Sales (‏1Z1‏)

The SAP digital payments add-on enables you to connect SAP and non-SAP consumer applications with non-SAP payment service providers (PSPs). Its function is to facilitate secure, end-to-end processing of digital payments.

The diagrammatic overview, SAP S/4HANA Cloud Consumer Applications, shows which SAP S/4HANA Cloud consumer applications can currently be used with the SAP digital payments add-on.

The SAP digital payments add-on can be used for the following:

• Credit card payment processing: Card creation, card deletion, payment authorization, payment authorization cancellation, payment settlement, or payment refund.
• External payment processing digital payment advice.
• PSP activation: You can choose which of the available PSPs you want to activate.
• PSP determination: You can define routings to determine which PSP is used for each payment.

The scope item illustrates the use of electronic payments while creating a new sales order. This is enabled via the S/4HANA Cloud Platform application for SAP digital payment, called Payment Hub which provides an integration between payment service providers (PSP) and SAP components, solutions, or applications that process incoming credit card payments.

Payment card information available in the business partner master data can be used when creating the sales order or new payment card data (one-time payment card) can be used in the sales order. When you save the sales order, the authorization of the payment card is executed through the payment hub service.

The credit card authorization can be canceled by deleting the authorized amount in the sales order. Then, a re-authorization can be completed after changing the order quantity. The SAP digital payments add-on offers a service for the cancellation of credit card authorizations, which is now called in the sales order. If the authorization in sales order is canceled, the service is called so that the corresponding authorizations of the payment service provider are canceled as well. The benefit for the end user and retailer is that the canceled amount will not block the credit card. The employee can check the authorization history within the order to see the current status of the authorizations and the response from the SAP digital payments add-on

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

• Consumer application: The connection between the consumer application, such as SAP S/4HANA Cloud, and the SAP digital payments add-on is set up here, for example using a communication arrangement. These connections are always machine to machine. 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.
• Another integration point is the card entry user interface provided to the end user (your customer), who has no dedicated user in the SAP systems.
• SAP digital payments add-on: The connectivity between the SAP digital payments add-on and the external payment service providers (PSPs) is set up here.
• Payment service provider: The SAP digital payments add-on and the external PSPs communicate using Web services. Most of this communication is synchronous.

The SAP digital payments add-on does not set up the connectivity to the consumer applications. The consumer applications connect to the SAP digital payments add-on by means of OAuth 2.0 authentication. Basic authentication is used until the OAuth 2.0 client server can be used.

The SAP digital payments add-on is designed in such a way that neither the add-on itself nor the consumer application that is connected to it, such as SAP S/4HANA Cloud, stores or even processes credit card numbers. The SAP digital payments add-on solution uses PCI DSS-certified external partners known as payment service providers or PSPs, which process and store the original card data. The PSPs replace the credit card number with a token. The token is the only identification that is processed and stored in the SAP software.

The consumer application sends a request to the SAP digital payments add-on. Based on the details of the request, the SAP digital payments add-on determines the relevant PSP in a process called routing. The request is then forwarded to the relevant PSP adapter where it is mapped into the appropriate format. Then, the connection to the PSP is established using the credentials already maintained by the system administrator and the request is sent using the technical protocol required by the PSP.

The process starts with the creation of a customer business partner master record in which the applicable credit card details are entered. This authorizes the card data via the payment hub service. The customer's sales order is captured and depending on the customer and the material, various special events take place during order entry, such as route determination and material pricing. A job is scheduled to check and release the authorized sales documents.

If enough material exists in the required storage location, the delivery process proceeds normally. Picking slips are generated to stage the product for shipment to the customer. When picked, the physically shipped quantity must be registered in the system to ensure that there are no differences between the sales order and the delivery document.

After the completion of picking, the shipping specialist releases the inventory. This inventory release is the actual recording of the physical quantity that is being shipped to the customer. The cost of goods sold is recorded in financial accounting.

When the inventory is issued, you can invoice the delivery and record the revenue and the cost of goods sold in management accounting.

This is the process diagram for scope item 1Z1, Digital Payments - Sales.

The following are the main steps of the process:

• The Add & Register Credit Card Data in Business Partner step prepares the customer master data required for credit card based order processing.

• The Create Sales Documents step initiates the ordering process in the SAP S/4HANA Cloud system and the SAP Digital Payments Add-on.

• The Release Sales Documents with Payment Card step schedules the sales document for processing.

• The BD9 - Sell from Stock step represents all succeeding steps until the billing document can be created.

• The Create Billing Document step sends the invoice to the customer for payment.

• The step in ancillary process 1S2 applies the electronic payment from the customer's credit card.

• Provide customers the option of using electronic payments using an integration with the payment hub.
• Use electronic payments securely and simply

This table lists the Fiori Apps used in each of the main process steps.

The Master Data Specialist adds the credit card data in the Business Partner master record using the app Manage Customer Master Data.

The Internal Sales Representative creates the Sales Order using the app Manage Sales Orders.

The Internal Sales Representative releases the Sales Documents using the app Resolve Payment Card Issues - Schedule Job.

Finally, the Billing Clerk creates the Billing Document using the app Create Billing Documents.

With the Manage Customer Master Data app, you can manage customer master data centrally for departments involved with sales. You can create, change, search, display, and copy customer master data.

By integrating with SAP Digital Payments Add-On, you can use payment cards in the Manage Customer Master Data app. This feature offers integration with various Payment Service Providers (PSPs) in which the payment card data get validated. You can create, edit, and delete payment cards data of the Credit Card type.

• Create Customer Master Data: use the Create Person or Create Organization buttons to create new customer master data.
• Edit Customer Master Data: Open a customer master data record from the List Report screen and use the Edit button to open the customer data in draft mode for you to change the values.
• Copy Customer Master Data: You can use the copy option to create a new customer master record if a customer master record already exists with similar data. You can copy all (default) or predefined fields (Copy with Preselection) of the selected customer, except the Business Partner number. Note that when you copy a master data record, the attachments are not also copied.
• Copy at Facet level: You can copy the facet level data such as Address, Bank Accounts, Sales Area, and Company Code of a customer, when in the draft mode while creating or editing a master data record.
• Delete at Facet level: You can delete the facet level data for a customer when in the draft mode while editing or creating the master data record.

• Time dependency: If Time Dependency is enabled, you can set validity start date and validity end date for the fields such as Roles, Address, Address Usage, Bank Accounts, and Contacts. If Time Dependency is not enabled, the system considers the default values. The default values are current date (validity start date) and 31.12.9999 (validity end date).
• Address usage: You can manage different addresses (for example, Home Address, Business Address, Holiday Home) according to your preference.
• Attachments: The attachments feature enables you to provide related attachments for customer master data records. The app supports only General Object Services (GOS) type attachments. When you create a new role, you must add the service CV_ATTACHMENT_SRV to the Z - catalog, in order to use the attachment feature.
• Customer Account Group: Flexible Account Group, if enabled, provides you the flexibility to choose a customer account group from the value help. You can choose customer account groups when creating a customer master record. With Account Group Change, if authorized, you can modify the customer account group even after the customer master data record is saved.
• Customer Authorization Group: is based on the authorization group(s) that are assigned to users to create and view customer master data records.
• Withholding taxes: enable you to maintain withholding tax data for customer master company codes. Withholding tax is the tax that is charged at the beginning of the payment flow in some countries.

With the SAP Fiori Resolve Payment Card Issues app, you can schedule jobs to list and process open sales and distribution (SD) documents with payment cards. The documents are then reauthorized in batches based on the credit check. You can also display, cancel, and copy these jobs.

You can start the creation of lists immediately or schedule the job to run in the background. Note that you can reduce system load and processing times by running jobs during periods when system usage is lower (at night, for example).

The initial screen (application jobs list) provides an overview of all jobs. Here you can:

• display all jobs that exist for a given date range. 
• filter jobs by their status (for example, to show jobs that are scheduled, cancelled, or in process).
• filter by job ID, run ID, description, or the user ID of the user who created a job.
• save your filter settings together with your view settings as a page variant and manage these saved page variants.
• access the application log from the log status field on the job details screen or by choosing the icon displayed in the log column of the application jobs list.

You can view the details of a job by choosing the respective row. The job details vary according to how you set up the job. If you have specified a recurrence (every day, for example) you can view the recurrence details here. Single run indicates that no recurrence has been set.

With this app, you can:

• Schedule a recurrence so that jobs will run at regular intervals (such as every minute, hour, day, week, or month, or at custom intervals you have set, such as every five days).
• Choose the appropriate calendar to include the public holidays for your country or region.
• Select parameters to determine which SD documents are to be included in your new job based on:
  • Organization data
  • Document info such as the next shipping date and next credit check as well as a specific SD document ID,
  • Status of last authorization such as the requirement status, the call status, the response, and the overall credit status.
• Choose if you want to write an application log and specify how many days this application log is available in the system.
• Schedule the creation of lists of SD documents that are open and blocked for credit reasons from the application jobs list by creating a new job. SAP delivers a default template that you can use. You can also save your scheduling options as a new template.
• Choose to run your job immediately or at a later point in time. If you want to schedule the job for a later point in time, you can enter a start date and time manually or select them from the calendar.