Edit Template

Industries Banking and payments

Check each payment instruction before it moves.

Payee enrollment, bank changes and transfers carry a signed Trust Packet™, layered on the controls you run.

For fraud and payments-risk leads at banks and payment providers.

Payment instructiontp_5e02b6d9Illustrative
instruction
enroll_payee
customer
treasury.customer.example.com
payee
Sample Merchant
account
XXXXXXXX0000
rail
ACH, after the check
packet
attached, signed by the customer
APPROVEDAll five checks pass. Written to the ledger as al_000204. The instruction is released.

01 · Where it fits

Layered on the controls you already run.

Banks and payment providers already check who is calling.

UniKey adds a check on what the instruction is allowed to do: this payee, this amount, this account, signed by the customer’s own key.

What the verifier checks

Who signed?
The customer’s key, checked against its Authority Anchor in DNS.
What for?
This payee, this amount, this account.
How many times?
Once. A replayed packet is refused.
For whom?
This bank only.

02 · Approved and refused

The same action, approved and refused.

In scopetp_5e02b6d9
  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
APPROVEDWritten to the ledger as al_000204. The payee is enrolled.
Account differs from the signed packettp_5e02b6d9
  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 signedrefused
REFUSEDThe payee account does not match what was signed. Written to the ledger as al_000205. The payee is not enrolled.
Authorization Ledgerpayments.bank.example.comIllustrative
ChainRecordActionSenderVerdictCommits to
al_000204enroll_payeetreasury.customer.example.comAPPROVEDprev ex-5a10hash ex-b7e3
al_000205enroll_payeetreasury.customer.example.comREFUSED
Account differs from the signed packet
prev ex-b7e3hash ex-2c94
al_000206enroll_payeetreasury.customer.example.comREFUSED
Nonce already used
prev ex-2c94hash ex-d06f

Each record commits to the hash of the record before it, so a changed or missing row shows. Sample ids and hashes.

03 · Where the verifier sits

On top of what you run, in front of the action.

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

04 · What it looks like

A sample packet for a payee enrollment.

A business customer enrolls a new payee. The packet names the action, the customer, the bank and the payee’s account.

The Trust Packet, field by field
Sample Trust PacketIllustrative
{
  "action": "enroll_payee",
  "sender": "treasury.customer.example.com",
  "audience": "payments.bank.example.com",
  "payee": "Sample Merchant",
  "account": "XXXXXXXX0000",
  "expires": "in a few minutes",
  "nonce": "example_nonce_5e02",
  "signature": "example_signature_only"
}

Sample fields, for illustration. RFC-2001 defines the required fields, and a deployment can add its own. Example domains and masked values throughout.

Pilot

Try it in a sandbox first.

No live customer data sits on UniKey systems.

A UniKey property. © 2026 Swoop In Technologies LLC

Edit Template