A 30-day shadow pilot beside your wire desk.
Your desk still releases every wire, as today. At the end you get a report of what the gate would have held.
- Week 1Set up in stagingAdd the signing step to your staging portal. Run the gate in log-only mode. Enroll the approvers you choose.
- Weeks 2 and 3Sign in parallelPilot approvers sign wires on their phone. Your callback desk still decides every release.
- Week 4Report and decideReview the results with your fraud, InfoSec and legal teams. Continue, change scope or stop.
What changes for you.
Nothing on the railNo core or payment hub changes. The gate only logs during the pilot.
Callback staysEvery wire still goes through your desk. Approvers without a phone are unaffected.
Exit any dayRemove the snippet and the pilot ends. No contract lock-in for the pilot.
What you provide.
- Access to a staging portal and payment hub log
- A pilot group of commercial approvers you choose
- A fraud or InfoSec contact to run the shared red-team script
Measured in the pilot, not promised up front.
Sample pilot report synthetic data
Wires seen1,284
Would have held3
Median tap4.2s
Callback fallback6%
Red-team cases held14 / 14
- Each tamper and replay case in the shared red-team script, held or listed in the report
- Approver tap time on your approvers' own phones
- Gate check time on your hardware
- How often callback was still needed (the weak link)
- Receipt review by your audit and legal teams
Limit: a shadow pilot shows what the gate would have held. It does not hold anything until you turn enforcement on. Threat model and limits
Scope your pilot with an engineer.
20 minutes. Bring the wire flow you want to test first.