Five moments in the life of a payment
The instruction is formed
Your systems create the payment instruction as they do today: the parties, the amount, the route and the purpose.
One check
The beneficiary and every bank on the route are screened against the authoritative sanctions lists, and your own due diligence on the payer is cited, not repeated. The instruction itself is checked for completeness and consistency.
A record — or a stop
If everything is clear, one record is signed. If not, nothing is cleared: the payment stops before release, the reason is cited, and the case goes to your team.
Release to the rail
The payment goes out over SWIFT, RTGS or the correspondent chain exactly as before. The record accompanies it; nothing is written into the payment itself.
Checked by anyone, at any time
Any bank on the route, an auditor or a supervisor can verify the record offline, without asking us. Change a single character and verification fails.
What a record shows — and what it does not claim
It shows
That the check was made, against which authoritative lists, and with what result — and that nothing in the record has changed since it was signed.
It does not claim
That the payment settled; any view of a party beyond what the cited lists say; or your compliance decision, which stays yours.
Who relies on it
- The sending bank
- Evidence made before release, instead of rebuilt after the fact.
- Every bank on the route
- A record that accompanies the payment and can be checked on receipt.
- Auditors and supervisors
- Records they can verify themselves, offline, years later.