Synthetic data only. Every invoice, supplier, purchase order, approval, grant and account reference on this page is a committed synthetic fixture. No real SME records, no real customer data, no bank integration, no money. The founding pilot with the Institute of Digital Economy Foundation (Armenia) is zero-budget and applied research; no funding, procurement, regulatory approval or endorsement by any central bank, ministry or public body is requested or implied.

KYE SME Payment Authority Pack™: pre-execution demonstrator

An AI payment assistant prepares supplier payments for a synthetic Armenian SME. Before any instruction reaches the synthetic rail, KYE™ resolves the assistant’s authority against the live decision endpoint and returns ALLOW, DENY or REQUIRE_APPROVAL with explicit reason codes, sealed as an Evidence Pack™ you replay yourself. Authority Finality™ before payment finality: the rail decides whether a payment settles; KYE™ decides whether the agent was entitled to request it.

Every verdict below is made by POST /api/v1/pdp/decide, the same deterministic engine behind the Authority API, over the declared kye:rule-pack:sme-payment-authority rules. Nothing on this page decides anything on its own.

Step 1 · KYE Chain of Authority™ and the authority matrix

Who may do what, before the assistant touches anything

Authority flows from the SME owner to a delegated approver, to the AI payment assistant, to the tool it uses to reach the rail. Each link holds no more than the link above granted it.

    Execution grants

    Step 2 · Pick a synthetic instruction

    Six instructions, one of them the IoDE core denial

    Each tile is a payment instruction the assistant is about to submit. Its facts (invoice, purchase order, supplier record, any approval, the execution grant) are read from the synthetic seed data below the tiles. The expected outcome on the tile was asserted against the real engine when the scenario was registered; the verdict you get in step 3 is the live one.

    Choose an instruction.
    Step 3 · The synthetic workflow

    Eight steps; the rail is the seventh and the decision is the fourth

      —

      Reason codes on the sealed Decision Map™

      The synthetic rail

      The instruction has not been decided yet; nothing has reached the synthetic rail.

      Outcome receipt

      A separate post-execution artefact (shape kye.execution_receipt.v1) describing what happened after synthetic execution, distinct from the Authority Finality™ receipt. It exists only when something executed.

      No outcome receipt: nothing has executed.
      Step 4 · Evidence Pack™ and independent replay

      The Authority Finality™ receipt, and the auditor’s view of it

      The Evidence Pack™ binds the authority decision, the inputs, the state, the applicable rules, the Decision Map™, the execution-context seal, the verification material, the replay logic and the outcome. Open it, then replay it: the seed is re-derived from the pack’s own inputs and the seals are checked with public keys, with no KYE™ participation.

      Resolve the instruction to seal its Evidence Pack™.

      Evidence Pack™ (sealed JSON) 
      
      
      
      
      
        
      
      
      
      
      
      
      
      Published verification key for the sealed scenario maps: , the same entry as kyeprotocol.com/trust/self-audit-jwks.json. The live pack carries its own Ed25519 public half; binding the sandbox signer to a published production key is a Phase Two credential step, stated honestly rather than faked.
      
    
      

    
      
      Honest scope
      
      What this demonstrator proves, and what it does not
      
      
      It proves that an AI agent’s authority to request an SME payment can be checked, limited, evidenced, denied, held or allowed, and independently replayed, before any real financial action is considered. It does not settle payments, verify a real bank account, or connect to a rail. Production-data admission is a separately governed second phase with its own obligations (tenant isolation, write-once audit with framework-justified retention, a data-subject access and withdrawal route, a live rail only after authority-before-rail is proven, incident and kill-switch duties, monthly joint review). Read the product page: KYE SME Payment Authority Pack™.