Skip to main content

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

How to test the functionality?

Updated on June 14, 2023

This section describes the steps for the users to test the functionality:

  1. A cross-network transaction occurs when the card processing network and the transaction processing network are different. The eligibility of such transactions is determined based on the configuration in the decision table EvaluateCrossNetworkRegII, considering criteria such as:
    • The transaction must be performed using a debit card.
    • The transaction must be a card-not-present transaction.
    • The transaction must be performed within the US domestic region

    If the above criteria are met, the transaction is eligible for Reg II regulations, and processing follows the regulations.

  2. To create fraud claims for Visa or Mcom debit cards, use the Search for transactions screen.
  3. To verify the new questionnaire for Reg II transaction disputes, navigate to the Qualify dispute and Qualify fraud disputes screen.
  4. When you create a claim with multiple transactions, and if all transactions are eligible for Reg II, the system displays the Reg II transaction specific questionnaire for each transaction.
  5. When you create a claim with multiple transactions, if one transaction is eligible for Reg II and others are Non-Reg II transactions, the system displays the Reg II transaction specific questionnaire for the eligible transaction and displays the existing scheme-specific questionnaire for the Non-Reg II transaction.
  6. When the dispute is a debit transaction, post Qualify dispute screen, the case routes to the Select charge fees screen to apply applicable charge fees.
  7. If the dispute is Reg II transaction, the case routes to provide verbal attestation. When you click Submit, the case routes to the Process Reg II resolution assignment and assigned to the specific work queue based on the processing network.
  8. On the Process Reg II resolution screen, select the appropriate resolution option and click Submit.
  9. Verify that accounting is handled correctly based on the resolution option, and a correspondence notification is sent to the customer.
  10. After the case is resolved, verify the selected resolution option under the Reg II resolution footer tab.
  11. Generate a comprehensive Reg II Dispute Case Count report that lists all transactions subject to Reg II dispute cases along with their corresponding network-specific queues.

Reg II scenarios

The following table describes the end-to-end Reg II scenarios in Pega Smart Dispute for Issuers application:

IssuerNetwork IDReg II/Non-Reg IIBO/CSRDST/DMTQueue Name
VISA Pinned (Interlink)VISA InterlinkNon-Reg IICSRDSTExisting flow
VISA(Other)Non-Reg IIBODSTExisting flow
MaestroReg IICSRDSTMaestro queue
Mastercard (Other)Reg IIBODSTGeneral Queue
VISA SignatureVISA InterlinkReg IICSRDSTExisting flow
VISA(Other)Reg IIBODSTExisting flow
MaestroNon-Reg IICSRDSTGeneral Queue
Mastercard (Other)Non-Reg IICSRDSTMaestro Queue
MC PinnedVISA InterlinkReg IIBODSTInterlink Queue
VISA(Other)Reg IICSRDSTGeneral Queue
MaestroNon-Reg IIBODSTExisting flow
Mastercard (Other)Non-Reg IICSRDSTExisting flow
Maestro cardOtherReg IIBODSTGeneral Queue
MC SignatureVISA InterlinkReg IICSRDSTInterlink Queue
VISA(Other)Reg IIBODSTGeneral Queue
MaestroNon-Reg IICSRDSTExisting flow
Mastercard (Other)Non-Reg IIBODSTNon-Reg II
VISA PinnedVISA Interlink & MaestroReg II and Non-Reg IICSRDMTN/A
VISA SignatureMaestro & OtherReg II and Non-Reg IIBODMTN/A
MC PinnedVISA Interlink & OtherReg II and Non-Reg IICSRDMTN/A
MC SignatureVISA Interlink & MaestroReg II and Non-Reg IIBODMTN/A
VISA PinnedMaestro & MastercardAll Reg IIBODMTN/A
MC PinnedMaestro & MastercardAll Non-Reg IIBODMTN/A
Reg II ReportingN/AN/ABON/AN/A

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us