Transaction Matching

Our system locates transactions in your account using data received from the card networks. This is the foundation for automation and resolution rules.

Depending on your account agreement, available integrations, and connector quality, we offer either strict matching or soft matching.

Strict matching

With strict matching enabled, every alert from the card network is matched to a transaction in your payment processor, and the refund is confirmed as executed.

If the system can't find a match, someone on our team manually investigates using the alert data and transaction records. If we still can't locate it, you're automatically credited for that alert.

Soft matching

If connector data quality or account configuration prevents strict matching, we fall back to soft matching. The system attempts a best-case match, but if it fails, the alert lands in your dashboard as "Action Required" for manual review.

We try to offer strict matching to as many customers as possible at no extra cost. But some setups make it technically impossible, missing data fields, limited query options, or specific configurations. Examples:

• Digital wallet providers like Stripe Link that mask card data

• Network tokens that scramble card data, increasing the risk of invalid matches

Unmatchable transactions

Sometimes the data from the card network isn't enough to produce a definitive match, or any results at all.

If you're on strict matching, these cases are fully creditable. You won't pay for them.

However, if matching issues stem from your specific setup (e.g., using Stripe Link in wallet mode), Mastercard may consider it a problem on your end rather than theirs. In those cases, we likely can't credit every instance.