Payments Method

EasyCash is designed to support multiple payment types so it can function like a real neobank.

Payment Categories

EasyCash supports 4 payment categories:

Direct Merchant Payments (Invoice / QR)

The user pays a merchant invoice without revealing wallet identity.

Flow:

1. Merchant creates invoice / QR

2. User scans and approves amount

3. ZK proof confirms solvency

4. AI selects best settlement rail

5. Merchant receives stablecoins

This is the main “Invisible Spending” path.

P2P Transfers (Private Send)

Users can send stablecoins to other users privately.

This can include:

• stealth address receiving

• protected memo references

• optional recurring payments

Use cases:

• paying friends

• paying contractors

• sending allowance

Recurring Payments (Subscriptions)

EasyCash supports recurring payments like:

• SaaS tools

• memberships

• rent or bills

Key privacy advantage: A normal wallet subscription creates predictable patterns. EasyCash can break the public pattern linkage.

Salary / Payroll Streams (Private Salary Mode)

Employers or DAOs pay contributors monthly.

EasyCash ensures:

• stable monthly inflow behavior (for user UX)

• without revealing totals publicly

Settlement Rails (How Payments Actually Move)

EasyCash can settle merchant payments through multiple rails:

Rail 1: Same-Chain Stablecoin Settlement

Best when:

• merchant and user are on same chain

• cheapest and fastest

Agent selects:

• minimal fee path

• avoids high MEV ris

Rail 2: Cross-Chain Settlement

Best when:

• merchant wants USDC on Chain A

• user has liquidity on Chain B

Agent tasks:

• bridge stablecoins

• perform swap if needed

• settle invoice

Users do not need to manage bridging complexity.

Rail 3: Swap-Then-Pay

If merchant requires a specific stablecoin:

• merchant requests USDT

• user holds USDC

EasyCash auto-swaps and pays in one flow.

Rail 4: Liquidity Buffer Settlement (Instant Merchant UX)

EasyCash can optionally maintain a settlement buffer:

• merchant receives payment instantly

• protocol settles final net transfers later

• reduces latency and improves UX

This model is useful for:

• high-frequency merchants

• real-world POS payments

Privacy Layer in Payments

EasyCash payments protect:

• user wallet identity

• balance totals

• history graph

• payroll totals

• merchant linkage to user address

How privacy is preserved during payments:

• the vault is separated from public spending identity

• proof is used instead of showing balance

• execution uses relays or protected paths

• user’s “main account” never touches merchant address directly

Payment Confirmations & Receipts

EasyCash provides:

• merchant confirmation receipt

• user receipt record

• internal ZK-verified balance update

Receipts can be:

• public proof (merchant side)

• private record (user side)

• optionally exported for tax/accounting without wallet leakage

Payment Policy Controls (User Safety)

Users can set:

• daily spending limits

• merchant allowlist

• category rules (future)

• require biometric confirmation (frontend level)

• auto-deny suspicious invoice patterns

• time delay for large payments

AI agent enforces policies during execution.