For open-banking teams · consent & payment initiation

Illustrative sector walk-through — it shows how KYE Protocol™ would govern an open-banking stack and does not imply an existing deployment or commercial relationship with any vendor.

An AI agent just tried to pay a payee the account holder never consented to. KYE™ stopped it.

Built for a platform like yours. Your TPP flows now carry AI finance agents that read balances and move money on a customer’s behalf. KYE Protocol™ checks the account holder’s live consent at the moment of payment — and refuses any initiation to a payee or amount outside that scope. Each refusal is sealed as a receipt your auditor can replay, cutting a disputed-payment investigation from days to minutes.

event Book a 20-minute walk-through account_balance Open-banking authority
AI finance agent
initiate £4,200 → new payee
KYE™consent scope check
Refusedoutside consent · signed Admittedwithin consent · signed
Stopped before the money moves. The initiation is refused because the payee sits outside the account holder’s granted consent — and the refusal is signed and verifiable, so you can prove to the customer and the regulator that scope held.
That refusal, sealed REFUSED · OUTSIDE_CONSENT_SCOPE kye:evidence:b21d… Replay & verify →
1 · What KYE™ governs in your stack

You keep your platform. KYE™ governs the consent boundary.

Your platform already brokers accounts, balances and payment initiation between banks and third parties. KYE Protocol™ adds the one check an AI agent makes it urgent to enforce: at the moment of a consequential act, is this inside the consent the account holder actually granted?

  • Payment initiation — a transfer is admitted only when the payee, amount and window sit inside the account holder’s live consent; a breach is refused, not retried against a stale grant.
  • Data access — reading balances or transactions past the consented data cluster or expiry is refused, keeping PSD2/PSD3 purpose limitation intact.
  • Every act sealed — admit or refuse, the decision packs an Evidence Pack™ and a Replay-Proof™ verifiable from public keys alone — your dispute file, ready before the customer complains.
2 · The honest boundary

KYE™ proves the basis — it does not move the money.

This is a governance layer, not a payment processor. KYE Protocol™ does not hold accounts, execute transfers, run SCA, or stand in for your API gateway.

It checks the consent at the action boundary, admits or refuses, and seals the proof. An act outside the agent’s scope is refused and routed to a human step-up — the refusal is itself evidence. See how the delegation chain is drawn on the authority diagram, then walk a sealed decision on the Evidence Pack™ demo.

3 · See it on your own flow

Seeing is believing. Bring one real flow.

In a 20-minute walk-through we take one of your live flows — a payment initiation, a balance read, a consent renewal — and show the AI action refused or admitted against the account holder’s consent, then hand you the sealed receipt to replay yourself. No credentials to share: the proof verifies against a public key set, the same runtime enforcement KYE Protocol™ uses to govern itself.

event Book a 20-minute walk-through receipt_long Replay a sealed decision