Agentic Execution Flow (High-Level)

ElizaPay is built around “intent-based automation” rather than manual transaction authoring.

Payment Flow (Private Merchant or Peer Payment)

Step-by-step

1. User Intent “Pay 120 USDC to Merchant X.”

2. Policy Check (Enclave)

   • daily spend remaining?

   • merchant allowlisted?

   • chain restriction?

3. Context Resolution (Private)

   • available stablecoin sources across chains

   • gas budget availability

   • preferred settlement rails

4. Route Optimization (Private Decision Engine) Agent selects:

   • chain

   • bridge (if required)

   • swap path (if required)

   • fee-minimized settlement

5. ZK Proof Generation (If Required) Produce proof:

   • “≥ 120 USDC available”

   • “compliant with policy”

   • optionally: “credit-backed authorization valid”

6. Transaction Intent Signing (Enclave)

   • deterministic transaction created

   • signed inside enclave

7. Broadcast / Relay

   • direct to chain OR privacy relayer

   • minimal metadata

8. Receipt Verification + State Update

   • confirm finality

   • update private vault commitments

   • adjust policy counters

What external observers see: settlement only. What counterparties verify: a proof, not your balance.

Loan Qualification Flow (Proof-Based Underwriting)

1. User Request “I want a 2,000 USDC loan.”

2. Private Solvency Computation Agent evaluates:

   • asset commitments

   • repayment capacity

   • risk constraints

3. Generate Underwriting Proof Example proof:

   • solvency ≥ threshold

   • debt ratio within safe band

   • user meets loan parameters

4. Counterparty Verification Lender verifies proof validity.

5. Loan Contract Execution Loan disbursed without revealing user’s full portfolio.

Cross-Chain Asset Rebalancing Flow

1. Scheduled Trigger “Every Friday: rebalance stablecoin allocation.”

2. Policy & Risk Check

   • max exposure per protocol

   • bridge restrictions

   • slippage ceilings

3. Optimization

   • allocate liquidity to safest yield

   • minimize fees

   • avoid risky pools

4. Execution

   • atomic routes where possible

   • fallback if state changes

5. State Update

   • commitments refreshed

   • strategy baseline updated

Fraud Detection & Emergency Lock Flow

1. Anomaly Detection Signals:

   • unexpected approval request

   • repeated micro-drains

   • new contract interactions outside norm

   • suspicious bridge route

2. Automatic Response (Policy Action)

   • freeze outgoing transfers

   • deny approvals

   • require user co-sign

   • rotate session keys

3. User Notification “Blocked transaction due to policy violation.”

This is how ElizaPay behaves like a private bank security system.