{{ emptyBody }}
Every exception carries the amount exposed, the count of your users affected, and who it is assigned to. A queue without those three is a notification list.
{{ incidentNote }}
{{ incidentBody }}
{{ askAnswer }}
The customer script is written from the transfer's real state, so two agents give the same answer and neither of them guesses. It is never more optimistic than the timeline supports.
A cutoff you missed is not an error we can retry away. This is the one clock in the product that we surface before it matters rather than after.
$18,640 short against 31 scheduled payouts. Wire details do not rotate.
Close is blocked only by an unexplained variance. Nothing else.
{{ closeVerdict }}
Every break carries an established cause before it appears here. An unexplained variance stays open and blocks day close — it does not get written off into a rounding account.
Where each institution's statement came from, and when it landed
Two of these institutions still send a file rather than expose an API. We say which, because a treasury team that does not know where its truth comes from cannot sign off on it.
Connection, request, payout, user reference or session. We resolve it to the institution, state whose fault it was, whether a retry will work, and what it cost.
{{ probeBody }}
{{ probeAlso }}
The institution's own response is shown verbatim. We do not translate a bank error into a generic code and leave you guessing which it was.
Filtered by whose fault it was, because that is the question you are actually asking. Every row names the institution reached, so a bank-side failure is never filed under a generic upstream error.
We show your endpoint's own response body, not just the status code. Most webhook debugging is one glance at that string, and most providers throw it away.
Rotate the secret without dropping a delivery — both keys verify during overlap.
Ordered by how often teams regret not subscribing.
Two you are not subscribed to are the two that matter most in an incident: payout.held and cover.short. Without them your users find out before you do.
Turn one on and the next matching sandbox call fails that way, with the real error surface and the real timeline. Test the paths you cannot summon in production without waiting for a bad night.
This screen ignores the environment selector. Injection exists only in sandbox, and no switch on this page can arm a failure against real money.
{{ scnSummary }}
{{ keyNote }}
Your real ceiling, not a marketing number. Sandbox is uncapped.
At 80% of any ceiling we write to you rather than waiting for the 429 to find your users.
The list version is the line an examiner asks for and most providers cannot produce. We record which published version each screen ran against, so a decision made last March can be defended with the list as it stood last March.
Revocation is one call and takes effect immediately, including mid-session. A consent you cannot withdraw was never consent.
Set these yourself. No account manager, no coordination call, no support tier.
Roles, SSO and directory sync on every plan. What each person can move is stated, not implied.
What a regulator or an auditor will ask for, exportable in one action.
Who did what, from where. Immutable, and not billed separately.
Demonstration console on synthetic data. Institution counts are read live from the public directory; balances, variances, latencies and exceptions are illustrative.