What are Unmatched Deposits and why did my payment land there?

Last updated: June 9, 2026

The Unmatched Deposits table is where incoming funds are routed when Ivy is unable to link them to an existing payment order. This is a safeguard designed to prevent orphaned funds from being held without context - and to ensure clear visibility into any deposits that require manual review or return.

While most payments are matched automatically, some can still land in Unmatched Deposits due to common mismatches or user behavior.

Common Reasons for Unmatched Deposits

Missing or Incorrect Payment Reference
The payment reference is the key identifier used to match incoming funds to the correct order. If the customer enters a wrong or incomplete reference, or if they omit it entirely, Ivy cannot match the payment.
Wrong Payment Amount
If the user sends more or less than the expected amount, the system may treat it as an unexpected transaction — even if the reference is correct.
Transfer from a Different Name or Bank Account
For some integrations, Ivy also verifies the sender’s name or IBAN. If the payment comes from an account that doesn’t match the expected identity, this can cause a mismatch.
Order Expired Before Payment Arrived
If the order has expired (e.g. the payment window timed out), incoming funds will no longer be recognized as linked to that session.
Technical Issues on the Sender’s Bank Side
Occasionally, banks may send incorrect metadata or fail to transmit the reference properly, resulting in a mismatch despite correct user input.