Note that this topic will continue to grow and change as the Portal changes.
The DI Standalone solution requires a DI SA Org Admin who configures their card types and creates users that log on to the DI Standalone GUI to obtain tokens.
DI SAP (version 2+ with single sign-on) requires a DI SA Org Admin to configure their card types. User accounts are not created as they do not log into the DI Standalone GUI, the authentication is made directly from their login within SAP and the DI SAP GUI is launched based on the template they implemented in SAP.
Technically, if a Client has DI SAP, then their DI SA Org Admin could also create users with the ability to login to the DI Standalone GUI. There is no way to "disable" DI Standalone; however, if they are not contracted for DI Standalone, we can monitor their account for any users. They should only have a DI Org Admin users, no end-users.
As of this publish date, DI SAP CRM is not an option in Merchant Portal. Select one or both of the following services depending upon which User Interfaces they plan to implement.
•DI for SAP - if implementing the CRM SAP GUI interface
•DI for eCommerce - if implementing the CRM Web UI interface
In order for the Fraud Providers to be available for configuration on the XiPay page, you must select the XiVerify checkbox on the Services tab when adding or editing the Merchant.
In order for the Token Exchange Providers to be available for configuration on the XiPay page, you must select the Token Exchange checkbox on the Services tab when adding or editing the Merchant.
To enable either Intercept SAP or Intercept eCommerce (which is used for Oracle and other ERP systems or applications), you would select the appropriate Email Pay for Oracle or Email Pay for SAP option in on the Contract Services tab.
Note that, as of this help publish date, if the Customer is implementing Email Trigger from some other non-Oracle system, you must still select Email Pay for Oracle in order to select the Intercept eCommerce settings on the Services tab.