CMX and ETX Sequencing Logic and Examples
Sequencing Logic
A receipt can be matched both with a transaction as well as a consumer attribute. Banyan looks for matches for receipts as they come in. If there is a transaction match with confidence higher than your specific confidence_interval then Banyan will create the transaction match and skip the consumer match. However, if there is no transaction match or there isn't a match that is above your set confidence_interval, Banyan will attempt a consumer match. Consumer matches are also predicated on the attributes that matched being tied to a consumer with a valid "consumer match" grant consent status.
Note: A consumer match can only be made if the consumer token associated with the match has given consent to consumer matching.
Banyan has put a higher value on the transaction match over the consumer match as it is tied to a more precise object. Banyan will continue to create consumer matches if the same receipt comes in with no corresponding transaction match.
Banyan also recognizes that data can arrive at different times, so rules have been set for what type of match should be created in all scenarios:
| Event Sequence | Outcome | |
|---|---|---|
| A | 1. Consent 2. Receipt 3. Transaction that meets confidence threshold | Consumer match will be created (CMX) and then transaction match will also be created (ETX) |
| B | 1. Consent 2.Transaction that meets confidence threshold 3. Receipt | Only transaction match will be created (ETX) |
| C | 1. Consent 2.Transaction that does not meet confidence threshold 3. Receipt | Only consumer match will be created (CMX) |
| D | 1. Transaction that meets confidence threshold 2. Receipt 3. Consent | Only transaction match will be created (ETX) |
| E | 1. Transaction that meets confidence threshold 2. Consent 3. Receipt | Only transaction match will be created (ETX) |
| F | 1. Transaction that does not meet confidence threshold 2. Consent 3. Receipt | Only consumer match will be created (CMX) |
| G | 1. Receipt 2. Consent 3. Transaction that meets confidence threshold | Only transaction match will be created (ETX) |
| H | 1. Receipt 2. Transaction that meets confidence threshold 3. Consent | Only transaction match will be created (ETX) |
| I | 1. Consent 2. Receipt | Only consumer match will be created (CMX) |
Illustrative Examples
Example 1
- FinX REWARDS DEPOT sends in a grant consent for Mary (Phone 555-555-5555) for Merchant SHOES R US on January 1, 2025 at 1PM UTC
- SHOES R US sends Banyan Mary's Phone Number and Consumer Token Match on January 5th 2025
- Mary shops at SHOES R US on January 10th 2025 at 11AM UTC and enters in her rewards number as 555-555-5555.
- REWARDS DEPOT sends Banyan the transaction for Mary on January 11th 2025 8AM UTC
- SHOES R US sends Banyan Mary's receipt on January 12th 2025
Result
Banyan will send REWARDS DEPOT the ETX for Mary's transaction on January 12th 2025.
Example 2
- FinX REWARDS DEPOT sends in a grant consent for Mary (Phone 555-555-5555) for Merchant SHOES R US on January 1, 2025 at 1PM UTC
- SHOES R US sends Banyan Mary's Phone Number and Consumer Token Match on January 5th 2025
- Mary shops at SHOES R US on January 10th 2025 at 11AM UTC and enters in her rewards number as 555-555-5555.
- SHOES R US sends Banyan Mary's receipt on January 11th 2025
- REWARDS DEPOT sends Banyan the transaction for Mary on January 12th 2025 8AM UTC
Result
Banyan will send REWARDS DEPOT the CMX for Mary's transaction on January 11th 2025 and the ETX for Mary's receipt on January 12th 2025
Updated 1 day ago