마패MAPAE
KOGitHubOpen Studio
AGENT PAYMENTS ON GIWA · TESTNET

Accept x402 on GIWA in one line.No server? One form.

Builders open a paid route with one line of Hono middleware; a shop with no server gets a payment URL instead. Customers order from a desktop agent and pick up in person. What arrives is tUSDC on GIWA Sepolia — testnet, not real money.

Open StudioSeller guide
OWNER
SETS THE SCOPE
CHAIN
ENFORCES IT
AGENT
ACTS WITHIN

SCOPEASSET + PAYEESpecifies the asset to spend and the payee to pay

BUILT ON OPEN RAILS

GIWASettlement network
x402Payment handshake
ERC-7710Delegated authority
ERC-4337Smart account
THE CONTROL LAYER

What an agent needsis not the whole wallet,but economic authority scoped to its purpose.

WITHOUT MAPAE

Hand over the key and trust

  • Access to the whole wallet
  • A backend promises the limit
  • Problems found after the fact
WITH MAPAE

Set the boundaries and delegate

  • Delegate only the scope needed
  • The chain enforces every payment
  • Revoke the grant at any time
ONE MANDATE · FOUR BOUNDARIES

The owner sets the boundaries. The chain enforces them.

The numbers are not fixed in the product. Each grant is composed for its purpose, and the agent cannot step past the engraved scope.

  1. 01
    ASSET · RECIPIENT

    Asset & recipient

    First narrow which asset can be sent, and to whom.

  2. 02
    AMOUNT · CADENCE

    Amount & cadence

    Set the cap for a single payment and for spending over a period.

  3. 03
    START · EXPIRY

    Validity window

    The chain itself checks when the grant begins and ends.

  4. 04
    OWNER · REVOKE

    Owner control

    When needed, revoke the grant immediately instead of waiting for expiry.

REQUEST · PAY · PROCEED

Payments flow automatically,but the authority check is never skipped.

  1. 01

    Request

    The agent requests a paid resource and receives the 402 payment terms.

  2. 02

    Scope

    The agent builds a one-time permission carrying only this payment's amount and recipient.

  3. 03

    Enforce

    The chain checks that the asset, cap, period, and recipient are within the delegated scope.

  4. 04

    Settle

    Only transactions that pass are settled on GIWA by the relayer.

  5. 05

    Proceed

    Once the settlement receipt is confirmed, the resource opens to the agent.

SECURITY BY REFUSAL

Safety shows not in the payments that succeed,but in the payments that can be refused.

What will execute is simulated as-is before settlement. A payment outside the granted scope is never broadcast — no funds move, no gas is wasted.

See the trust boundaries in the technical docs
01

Pay past the period cap

transfer-amount-exceeded
REFUSED
02

Pay with an expired permission

expired-delegation
REFUSED
03

Send to a payee that was never named

invalid-calldata
REFUSED
GIWA SEPOLIA EVIDENCE

Before the explanation, a record you can verify.

The links below are delegated payments actually settled on testnet. They are public evidence of technical behavior, not fixed product limits or operating metrics.

SETTLEMENT 01GIWA SEPOLIA0xe897fe55…c6aaa97d
SETTLEMENT 02GIWA SEPOLIA0x71d71442…32f46ce4
SETTLEMENT 03GIWA SEPOLIA0x533c5cb2…efd9964c
TESTNET ONLY

The current public evidence was produced with GIWA Sepolia test assets. It does not indicate operational readiness for real-value assets.

PASS · PAY · PROCEED

Set the boundaries.The agent moves within them.

Start autonomous payments without handing over your wallet.

Open Studio Technical docs