Solutions · Payments and ACH
Layer UniKey on top of your payment controls. Payee changes, supplier bank updates and outgoing transfers each carry a Trust Packet™, checked by your verifier before they run.
Checks so far
Approver packet
Mock buttons: Approve and Decline. Not interactive.
Approve signs a second Trust Packet. Decline writes REFUSED to the ledger. Nothing changes until that packet is verified.
01 · Where teams start
Payment origination is where a single forged instruction costs the most. Most teams protect payee changes and supplier bank updates first, then outgoing transfers, then the next process on the same verifier.
02 · One change, start to finish
Illustrative One supplier bank update, checked before anything changes in ERP. Sample data.
1Request and Trust Packet
2Five checks, in order
3Verdict, ledger, rail
03 · The held change
The request arrives. The supplier emails new bank details with a Trust Packet. The signature checks out, but there’s no approver packet yet, so the change waits.
An approver confirms. They confirm by email, signing a packet of their own.
The update runs. Both packets are in the Authorization Ledger.
The approver packet names the packet it confirms. Both are written to the ledger.
04 · What your verifier checks
Valid, unused and in scope runs. Anything else is refused or sent to a person.
05 · The record
Every allow and every refusal goes into the Authorization Ledger, with the packet that decided it. When someone asks who approved a payee change, the answer is a signed record, not a search through old email.
| Chain | Record | Action | Sender | Verdict | Commits to |
|---|---|---|---|---|---|
| al_000416 | update_ | ap.supplier.example.com | REVIEW Approver packet missing | prev ex-9d02hash ex-a41f | |
| al_000417 | approve_ | approver.buyer.example.com | APPROVED | prev ex-a41fhash ex-c3b8 | |
| al_000418 | update_ | ap.supplier.example.com | APPROVED | prev ex-c3b8hash ex-e52d | |
| al_000419 | update_ | ap.supplier.example.com | REFUSED Nonce already used | prev ex-e52dhash ex-f09a |
Each record commits to the hash of the record before it, so a changed or missing row shows. Sample ids and hashes.
06 · Keep what you run
UniKey doesn’t replace ACH, your bank’s controls or your logins. A stolen credential alone isn’t enough to move money wherever your verifier checks. Each action also needs a Trust Packet, checked before it runs.
Authority Anchor
The sender’s public key, in its own DNS
Identity you run
Logins, bank controls, approval workflows
UniKey per-action check
Checks each action before it runs
Rails you run
ACH, wires, card, ERP payment runs
Authorization Ledger
Every approval and refusal, hash-linked
UniKey limits and contains what a stolen credential can do: one action, one recipient, one use.
Related
Pilot
No live customer data sits on UniKey systems.
A UniKey property. © 2026 Swoop In Technologies LLC