Integrating with Visa Disputes Engine

From PegaWiki
This is the approved revision of this page, as well as being the most recent.
Jump to navigation Jump to search

Integrating with Visa Disputes Engine

Description Describes the steps to integrate SD to VISA
Version as of 7.3
Application Pega Disputes and Payments Exceptions
Capability/Industry Area Financial Services

To enable Smart Dispute interaction with a third party system such as VISA, the integration settings must be updated. This article describes the steps involved in configuring the integration parameters for the application to interact with VISA’s testing environment, MTE2, or to VISA’s production system.

VISA supports two modes of interaction: SOAP and REST. This article provides the details for both modes of interaction. Most steps in the process are common, but one step is configured differently based on which protocol (SOAP or REST) is used.

COMMON configurations

Request for VOL WSI Certificate

The customer must request their VOL WSI certificate. They must send a request email to VISA provides the customer with a CSR form and a CSR generation guide. The CSR form must be filled with the help of the CSR generation guide and sent to VISA as an email to the id above. Two files, CSR and key, are generated. The customer is expected to keep them safe.

Upon submission, the customer is provided with a user id, password, and p7b digital certificates.

Use the p7b digital certificates, csr and key files to generate the pfx file.

Generation of PFX file

Use the following openssl commands to generate the pfx file using the p7b digital certificates and the generated csr and key files. openssl pkcs7 -print_certs -in <p7bFileName>.p7b -out <cerFileName>.cer

openssl pkcs12 -export -in <cerFileName>.cer -inkey <keyFileName>.key -out <pfxFileName>.pfx

Keep the password used while generating the pfx .

Generation of JKS file

You need not generate the JKS file. This is provided by VISA along with the password.

Updating the VCRKeystore

The customer must update the VCRKeystore in the rule type KeyStore in their Pega instance. They must upload the pfx file and provide the password given during generation of pfx file.

Updating the VCRTruststore

The customer must update the VCRTruststore in the rule type KeyStore in their Pega instance. Upload the jks file and provide the password given by VISA.

Updating the Authentication Profile

The customer must update the Authentication Profile in the rule type Authentication Profile in their Pega instance. There are two authentication profiles in SD, for Issuer and Acquirer. The customer must update one or both, based on the requirements. The rules must be updated with the user id and password given by VISA to interact with the VROL portal.

Updating the VCR ROL Endpoint URL

The customer must update the dynamic system settings to update the VCR_RolTI_Endpoint and VCR_RolSI_Endpoint to point it to the correct URL. The customer must contact VISA for these URL values.

SOAP Specific configuration

No specific configuration is required for SOAP communication with VISA.

REST Specific configuration

The following configurations are specific to REST communication with VISA:

Updating REST Endpoint URL

The customer must update the endpoint URL data presented against the service records in the Pega VCR Services data types. The dynamic system setting VCR_REST_Endpoint_URL and VCR_DOC_GET_URL must also be updated.