Using Intercept SAP
This section discusses using Intercept SAP with single sign-on (SSO) implemented. This means you do not require separate login credentials for the Intercept SAP GUI that is launched in your web browser from SAP.
The procedure for generating and/or retrieving tokens using Intercept for SAP first requires some knowledge of how the feature is implemented. It is recommended that you review this entire section at least once to gain an understanding of how it works and the information you need from your System Administrator to use Intercept SAP.
Intercept SAP solution allows you to integrate SAP with the Intercept SAP UI to obtain tokens so that credit card numbers are never entered in your SAP systems.
This section contains the following topics on how to use Intercept SAP. Basic integration information is provided so you will understand the information you need from your System Administrator in order to use this functionality.
The Intercept SAP solution allows you to launch the Intercept SAP GUI to obtain tokens so that credit card numbers are never entered in your SAP systems. There are a couple of ways to integrate Intercept SAP and multiple configuration options to affect how the tokens are retrieved.
This section contains the following topics on how to use Intercept SAP. Basic integration information is provided so you will understand the information you need from your System Administrator in order to use this functionality.
General Notes about the Intercept SAP UI
The fields that display for payment input are determined by the template ID that your System Administrator configured.
A Luhn check is performed when you click the Generate Token button unless it is disabled by your Organization Administrator. If the Luhn check is enabled and you are tokenizing an eCheck account number or non-standard credit card, you will receive an error message that the number is not valid. Contact your Intercept-SA Organization Administrator.