Submitted through the providers you use
Approved work reaches your own banks and providers, unchanged.
| Reference | Entity | Provider | Amount | Attempts | State |
|---|---|---|---|---|---|
| ACT-54001 | Acme UAE | pv-enbd | $3.0K | 1 | BLOCKED |
| ACT-54002 | Acme US | pv-jpm | $100K | 1 | SETTLED |
| ACT-54003 | Acme UAE | pv-enbd | AED 486K | 2 | UNKNOWN |
| ACT-54004 | Acme DE | pv-citi | €215K | 1 | SETTLED |
| ACT-54010 | Acme NL | pv-citi | €41.9K | 1 | PREPARED |
| ACT-54011 | Acme US | pv-jpm | $98.5K | 1 | PREPARED |
Your bank does. We submit, and then we wait like everyone else.
Submitting is where VadoRail’s part ends. Confirmation comes back on the provider’s timetable, not ours — which is why the stage after Execute is drawn as yours, and why “submitted” is never rendered as “paid”.
Unknown is a state, not a blank cell.
A submitted instruction with no acknowledgement is the single most dangerous row in a payments system, because the two wrong answers — assume it worked, or retry it — are both one click away. It is held as an explicit state with its own uncertainty recorded, and a retry needs the same idempotency key that went out the first time.
“We have not established this” must never look like “this is fine”. It is drawn slate, never green and never empty.
- Entity
- Acme UAE
- Provider
- pv-enbd
- Amount
- AED 486,200.00
- Submitted
- 28 Sept 2026 · 16:20 UTC
- Last heard
- 29 Sept 2026 · 06:20 UTC · 9d ago ago
- Attempts
- 2
- Idempotency key
- pay-ap-0003:7b9d84504c3137b9
The narrowest layer, deliberately.
Govern decides, Secure binds the decision to this exact action, and Execute carries it. Reconcile then compares what came back against what was instructed, and Ledger posts the result.
Provider coordination
Instructions carried through the bank or provider that already holds the relationship.
Approved-action binding
An instruction that differs from the approved decision is refused, not adjusted.
Status tracking
What was sent, what was accepted, and what the provider reported back.
Return and failure handling
A failed or returned action becomes an exception with an owner, not a silent gap.
Bring your financial operations into one intelligent system.
Connect the ERPs, banks and providers you already run, establish one view of financial reality across them, and govern, reconcile and prove the work on top.
Onboarding is sales-led with company verification — there is no anonymous signup.