Skip to main content

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

Setting up duplicate scoring rules

Updated on March 21, 2023

Pega Smart Dispute for Issuers can flag transactions as duplicates based on scoring rules that consider data elements such as the transaction amount, transaction date, account number, and acquirer reference number. Pega Smart Dispute for Issuers can also accept close matches, for example, two items dated within three business or calendar days. You can also weight the two conditions so that an amount match is twice as important as a date match.

When a dispute is entered, Pega Smart Dispute for Issuers uses the Duplicate search to locate possible duplicates. The Rule-Search-Scoringrule identifies the critical fields for locating potential duplicates.

For each identified field, you set the conditions and a weighted average to be used when searching for duplicates. Pega Smart Dispute for Issuers tallies a score (weighted average) based on each matching field value and marks the case for review if the score exceeds the defined number. You can also set a threshold, which if not met, allows the case to continue through normal processing

Pega Smart Dispute for Issuers Implementation Guide
  1. In the Dev Studio header search text field, enter DuplicateScore and select the PegaCard-Sd- Dispute-scoring 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. Change the comparison operation by selecting a value from the selection box.
    Exact Match
    A string comparison; values (such as amounts, dates, or text) must match exactly.
    A numeric comparison; values (such as amounts) must match within a certain range.
    Range in Days (C)
    For a date match, the range in calendar days.
    Range in Days (B)
    For a date match, the range in business days, using a calendar to determine valid business days.
  7. Enter new values in the LowerBound and UpperBound fields. For operations other than Exact Match, use values relative to the value of the case being searched. Enter ranges as –x to y.
    For example: For a range of -1 to 1, a match occurs if the potential case has a value ± $1 from the amount of the case being searched.
  8. Enter a value in the Weight field.
    The Weight values are optional but must add up to 100 percentage.
  9. To change the Minimum Confidence Threshold, enter a number from 1 to 100. For example, in the previous rule, the weighted average of the four conditions is 100. If you set the threshold to 75, the system automatically identifies the case as a duplicate and continues processing when three conditions are met.
  10. To add a new comparison, click Add Row. Ensure that any properties you add are valid and that you adjust the weighting correctly. To delete a comparison, click Delete Row.
  11. Click Save.

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