Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Reviewing VCR data transform rules

Updated on March 21, 2023

Pega Smart Dispute for Issuers sends an XML request by using a service to VCR-VROL (Visa Resolve Online). Once the response from VROL is received, the application resumes the respective flow and continues the dispute process.

When VCR simulation is enabled, Pega Smart Dispute for Issuers does not connect to Visa with a request XML. Instead, the application simulates the outcome by using the simulated data transforms.

For example, while submitting the SISubmitDisputeQuestionnaireRequest dispute, questionnaire is triggered from the application as a request that is sent to Visa in real time with the dispute questionnaire details. VCR-VROL sends SISubmitDisputeQuestionnaireResponse as the response for the request.

When using the simulation mode, VCR-VROL is not connected online. Instead, a simulated response within the application gets triggered for the submitted request. The mapping for the simulated responses for respective requests is maintained in the VCR services data type as mentioned above.

Review the simulated responses, such as the SimulateVCR_SubmitDisputeQuestionnaireRes transform.

Note: There are multiple simulated data transforms that are shipped with the application in thePega VCR Services data type. In the absence of Visa connectivity, these services can be used to simulate various responses from Visa for testing purposes, and updated to simulate different responses.
Pega Smart Dispute for Issuers Implementation Guide
  1. In the Dev Studio header search text field, enter the name of a data transform rule you want to review, for example SimulateVCR_SubmitDisputeQuestionnaireRes and select the PegaCard- Sd-Dispute-Visa data transform rule from the results.
  2. Click Save As.
  3. In the Apply to field, select the appropriate implementation class for your application.
  4. In the Add to ruleset list, select the ruleset for your application.
  5. Click Create and open.
  6. Review the data transform with the bank.
    • If the VROLFinancialSentInd field has a True/False value, then accounting is required which implies that the acquirer is liable for the dispute initiated.
    • If the VROLFinancialSentInd field is blank, no accounting is required which implies that the issuer is liable for the dispute initiated.
    • To simulate an Issuer liable scenario for one of the transactions with ARN 24610432650004020160841, leave the VROLFinancialSentInd field empty. For all others, this field carries the value of true which makes the acquirer responsible.
  7. Click Save.

Tags

Smart Dispute for Issuers 8.7

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us