Skip to end of banner
Go to start of banner

Enrichment

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 43 Next »

The enrichment flow is executed to gather additional details about the disputed transactions.  The Enrich Data Preconditions are evaluated to determine which of the following actions is taken.

Action

Description

AUTO

Executes the Auto Enrichment flow.

MANUAL

Generates a Process Enrichment Manually assignment and prompts a user to complete the action(s).

SKIP

The flow is skipped.

Flow Actions

Page lookup error: page "Manually Enrich Data" not found.

If you're experiencing issues please see our Troubleshooting Guide.

Workflow

When the enrichment process is complete, the Post-Enrichment flow is executed to trigger additional activities.

Extension Points

  • To define what values are required for enrichment, update SetEnrichManuallyConditionGroupsExtension.
  • To override the default result in EnrichDataPreConditionsWrapper, use EnrichDataPreconditionsPreExtension to set a value.  This essentially gives you a place to override product level behavior as a pre condition, whereas the EnrichDataPreConditions rule is a way to set a result if the default product behavior does not return a result.
  • To modify the initial date range search for enrichment update EnrichmentStartWindow and EnrichmentEndWindow dynamic system settings (DSS).  The product default has EnrichmentStartWindow set to -3 and EnrichmentEndWindow set to 3.  
    • The Visa date range search is calculated off of the posted date.
    • The Mastercard date range search has a start window calculated off the transaction date (authorization date) when populate and the end window calculated off the posted date.
  • To disable card number being required on card disputes (CardPinned, CardPinless, ATMWD, ATMDEP); this can be disabled in the client information rule. 
Rule(s)EnrichData



  • No labels