Transaction match MCP reference

Confirm or reject auto-matched transaction pairs produced by account links.

When two family members connect the same credit card (primary cardholder + authorized user), transactions appear in both feeds. An account link pairs matching transactions by date and amount, excludes the dependent’s copies from totals, and attributes matched primary-side transactions to the dependent user.

Auto-matches start with confidence="auto". Use confirm_match to promote a correct pairing to confirmed, or reject_match to remove a false pairing.

All tools on this page are Write scope.

---

confirm_match

Confirm an auto-matched transaction pair as correct. Changes match confidence from auto to confirmed. The pairing and the dependent-user attribution remain intact.

Parameters

match_id · string · required

The transaction match ID (UUID or short ID).

Example input

{
  "match_id": "M4Xp9mQr"
}

Example output

{ "status": "confirmed" }

---

reject_match

Reject a false auto-match between two transactions. Removes the match record and restores the primary transaction’s original user attribution. Use this when the matcher paired transactions that look similar but are actually distinct charges.

Parameters

match_id · string · required

The transaction match ID.

Example input

{
  "match_id": "M4Xp9mQr"
}

Example output

{ "status": "rejected" }