Show how a SWIFT payment's tracking results changed over time.

Returns the DISTINCT tracking results recorded for a payment (by UETR or reference), deduplicated so ten identical re-tracks collapse to one entry while any change — a new last-update, a status change, or new bank data — appears as its own entry. Each entry includes what was ENTERED when the search was run (amount, currency, date) alongside the banks that reported data and their confirmed amount / value date.

WHEN TO USE THIS:

• The user says the page shows different data than you see, or asks why a bank line (e.g. JP Morgan) "disappeared" or a value date differs.

• You need to reconcile an amount or date discrepancy. JP Morgan returns its line only when the entered date and amount are close to its own record (seen: value dates up to 3 days apart, amounts mostly within 1%), so a search run with a wrong date or amount can silently drop its line. When it does answer, amount_exact_match is false if its value date OR its amount differs from what was entered, despite the name, and amount_exact_match_detail names which. Comparing entries here — same UETR, different entered dates or amounts, different bank data — is how you spot which entry was the problem.

• Before concluding "the record was consolidated" or "the bank stopped reporting", check the history: the earlier result you're being asked about is usually still here, under a different entered amount.

Each bank entry's source names the tracking SOURCE that reported it (e.g. "Standard Chartered"), not the bank at a step of the payment; track_payment names the same data by the bank at each step, so the two names differ.

Only results for the current user (plus system tracks with no owner) are returned; other users' searches of the same UETR are never shown.

Requires an API key with an active FI subscription.