Merchant Credit Matching
- Devan Robertson
- Kristafanie Somers
- Jacob Harris
- Nick Facca
When a possible merchant credit is detected, the system will evaluate it to determine if it is a match for a disputed transaction.
Criteria
This rule defines the conditions that are evaluated in when the system attempts to match merchant credits with a dispute. The system will evaluate all potential matches against every iteration, then rank and compare each potential match before setting the resulting action. This table is extendable and can be customized in each implementation. $0 Credits $0 credit transactions will never be considered as a possible match. Expect Credit Details The transaction id, ARN (Acquirer Reference Number), and Authorization Code in the above table are comparing expected credit details received from the association to identify the correct merchant credit in the system of record. Iteration Expected Merchant Credit Description Match Description Contains Description Tokenized Match Amount Transaction Id ARN Authorization Code Action 1 TRUE TRUE Credit Found 2 TRUE TRUE Credit Found 3 TRUE TRUE Credit Found 4 TRUE TRUE TRUE Credit Found 5 TRUE TRUE TRUE Credit Found 6 TRUE TRUE TRUE Credit Found 7 TRUE TRUE Credit Found 8 TRUE TRUE Credit Found 9 TRUE TRUE Refer 10 TRUE TRUE Refer 11 TRUE Refer 12 TRUE Refer 13 TRUE Refer No Credit Found
Conditions
| Condition | Description |
|---|---|
| Expected Merchant Credit | When a merchant credit is promised via Merchant Collaboration, this is set to true. Matching criteria is less restrictive when a credit is expected. |
| Description Match | Compares the dispute transaction description to the credit transaction description. It is true if the match is 100% |
| Description Contains | Compares the dispute transaction description to the credit transaction description. If the value of one transaction description is contained in the other it will be return true. for example if the dispute transaction description is "iTunes" and the credit transaction description is "iTunes 888-888-8888", this would return true. |
| Description Tokenized Match | Compares individual words in the the disputed transaction description to the credit transaction description. Any text string greater than 5 characters will be compared and if a match is found it will be returned true. Additionally special characters are striped out. |
| Amount | This is comparing the amount of the merchant credit and the transaction. This is returned true when both match. |
| Transaction Id | This is comparing the expected credits transaction id to the transaction id from the system of record. This returns true when the expected credit can be identified by matching the transaction id. |
| ARN (Acquirer Reference Number) | This is comparing the expected credits acquirer reference number to the transaction id from the system of record. This returns true when the expected credit can be identified by matching the acquirer reference number. |
| Authorization Code | This is comparing the expected credits authorization code to the transaction id from the system of record. This returns true when the expected credit can be identified by matching the authorization code. |
Actions
| Action | Description |
|---|---|
| Credit Found | The Deny Dispute flow is executed with a deny reason of "Merchant Credit" |
Refer | A Check for Merchant Credit assignment is generated and prompts a user to review transactions with a match probability that is too low for auto-matching. |
| No Credit Found | If pending, the service will try again every 6 hours until the deadline. If the deadline has passed, the flow is exited. |
| Fail | A Merchant Credit Service Failed assignment is generated and prompts the user to retry the service or cancel. This is a fail-safe and should be escalated if seen. |