Edit Template

Solutions Payments and ACH

One check, before a payment is released.

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.

Verifier consoleheld · tp_7f3a91c2Illustrative
REVIEWHeld for an approver
action
update_supplier_bank
sender
ap.supplier.example.com
payee
Sample Merchant
account
XXXXXXXX0000

Checks so far

signature
valid, key found in DNS
window
inside
replay
first use
approver
packet missing

Approver packet

approver
approver.buyer.example.com
action
approve_supplier_bank
for
tp_7f3a91c2

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

Start where one bad transfer is the expensive one.

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.

  • ACH payee change
  • Supplier bank update
  • Outgoing transfer

02 · One change, start to finish

A supplier asks to change bank details.

Illustrative One supplier bank update, checked before anything changes in ERP. Sample data.

1Request and Trust Packet

Trust Packettp_7f3a91c2
action
update_supplier_bank
sender
ap.supplier.example.com
audience
erp.buyer.example.com
payee
Sample Merchant
account
XXXXXXXX0000
expires
in a few minutes
nonce
example_nonce_7f3a
signature
example_signature_only

2Five checks, in order

Verifier
  1. Signatureagainst the Authority Anchor in DNSpass
  2. Time windowinside the short validity windowpass
  3. Not replayednonce not seen beforepass
  4. Audiencenamed for this recipientpass
  5. Scope and chainaction and limits inside what was signedpass

3Verdict, ledger, rail

APPROVEDAll five checks pass.
ledger
al_000418 written
rail
ERP update runs
REVIEWSigned and valid. Approver packet missing.
ledger
al_000416 written
rail
held for an approver
REFUSEDNonce already used. This packet was presented before.
ledger
al_000419 written
rail
ERP update does not run

03 · The held change

The approver signs a packet of their own.

  1. 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.

  2. An approver confirms. They confirm by email, signing a packet of their own.

  3. The update runs. Both packets are in the Authorization Ledger.

Approver packettp_b84c1f07APPROVED
action
approve_supplier_bank
sender
approver.buyer.example.com
audience
erp.buyer.example.com
for
tp_7f3a91c2
payee
Sample Merchant
expires
in a few minutes
nonce
example_nonce_b84c
signature
example_signature_only

The approver packet names the packet it confirms. Both are written to the ledger.

04 · What your verifier checks

Five questions, before any money moves.

Who signed?
The key is checked against the sender’s Authority Anchor in its own DNS.
What for?
This payee, this amount, this account.
When?
A short window you set: a few minutes, then void.
How many times?
Once. A replayed packet is refused.
For whom?
This recipient only.

Valid, unused and in scope runs. Anything else is refused or sent to a person.

05 · The record

A record your dispute team can actually use.

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.

Authorization Ledgererp.buyer.example.comIllustrative
ChainRecordActionSenderVerdictCommits to
al_000416update_supplier_bankap.supplier.example.comREVIEW
Approver packet missing
prev ex-9d02hash ex-a41f
al_000417approve_supplier_bankapprover.buyer.example.comAPPROVEDprev ex-a41fhash ex-c3b8
al_000418update_supplier_bankap.supplier.example.comAPPROVEDprev ex-c3b8hash ex-e52d
al_000419update_supplier_bankap.supplier.example.comREFUSED
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

Your rails stay. The check sits in front of them.

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.

UniKey limits and contains what a stolen credential can do: one action, one recipient, one use.

Pilot

Try it on one payment process first.

No live customer data sits on UniKey systems.

A UniKey property. © 2026 Swoop In Technologies LLC

Edit Template