Announcing Instant Payments Statuses
We’re updating how payment order states appear in Modern Treasury to better align with real-world settlement and reconciliation.

A Clearer View of Payment States
We’re updating how payment order states appear in Modern Treasury to better align with real-world settlement and reconciliation. This change will make it easier for customers to build downstream processes that reflect what’s happening in real time.
Until now, the completed
state was triggered only after reconciliation, which sometimes lagged behind the actual transfer of funds. Going forward, completed
will reflect confirmation directly from the bank or network, while a new reconciled
event will indicate when a payment has been fully reconciled.
This change applies consistently across payment orders, returns, reversals, and incoming payments.
What’s New
- Faster confirmation: The
completed
event will now trigger when the bank confirms that a payment has been posted to your account. - Dedicated reconciliation signal: A new
reconciled
event indicates when a payment has been fully reconciled with a posted transaction. This webhook is already live to support migration. - Improved handling of returns: When a payment is
returned
, you’ll immediately see bothcompleted
andreturned
events, instead of waiting until reconciliation.
Accurately Reflecting Real-Time Money Movement
With this update, you can now act on events that more accurately reflect real-time money movement. This is especially important for instant payments, where funds complete in seconds but reconciliation details follow later.
By separating completion from reconciliation, you gain:
- Faster visibility into real-world payment states.
- Cleaner downstream logic, with distinct events for completion and reconciliation.
- Consistent event behavior across different payment types.
Rollout Timeline
We’re rolling this out in stages:
- New reconciliation attribute → First, we will introduce the new back end reconciled attribute unlocking more performant reconciliation processing. This will have no impact on customers.
- Instant payments (RTP) → We will migrate instant payment customers, unlocking a truly real-time experience: a completed signal in ~10 seconds.
- Wires → Moving wires and enabling earlier completed signals where available from banks will create a more responsive wires experience.
- All other payment types (ACH, check, etc.) → We will migrate all payment types to have a distinct reconciled and complete signal, opting to refine how complete is triggered at a later date.
Payment Type | Migration Starting |
---|---|
Back-end reconciliation attribute | Early October 2025 |
RTP | End of October 2025 |
Wires | Mid-November 2025 |
Remaining Rails (ACH, check, etc.) | End of November 2025 |
How This Impacts You
- If your use case relies on reconciliation details (e.g., transaction IDs), use the new
reconciled
webhook. - If you need bank confirmation, continue using
completed
. - If you previously subscribed to both
tentatively_reconciled
andcompleted
, you should now rely ontentatively_reconciled
andreconciled
. - Auto-ledgering rules will now trigger on
reconciled
rather thancompleted
. - The Reconciliation Status for payment orders will be available in the UI, API, and push to warehouse. These will appear ahead of the migration.
Next Steps
- Review your webhook subscriptions and update any downstream logic where necessary.
- Test with the new reconciled webhook (available now).
- Connect with your Customer Success Manager for specific migration timelines.
Get Started
Modern Treasury is committed to making payment states more accurate, real-time, and actionable for our customers. If you’d like guidance on migrating to the new model, reach out to us or visit our documentation.
