Built for
Businesses operating Japan-facing wallets, creator support, membership or community products
← All productsMarket blueprint · Private pilot
INFRASTRUCTURE · PRODUCT BRIEF
JGas Japan
Policy-controlled Base gas sponsorship after a third-party JPY on-ramp.
JGas Japan is not a JPY on-ramp. An approved third-party provider would handle fiat payment and KYC and deliver USDC to a user-owned wallet. The shared JGas core would then evaluate the target, selector, account implementation and budget of a separately approved Base UserOperation. The shared control plane is operational, but provider approval, JPY purchasing, Paymaster funding and funded sponsorship are not active.
Base 8453 / 84532ERC-4337 v0.7ERC-7677PostgreSQLAzure Key Vault
SAMPLE UI · NO LIVE TRANSACTION
SAMPLE CONTROL PLANE
POLICYJapan market environment
01production-jp · illustrative
02JPY quote · Provider pending
03Policy version 04
04Sponsored spend · LOCKED
Illustrative UI only; it shows no live JPY quote, purchase or gas spend.
Intended outcome
A clear separation where users retain wallets and assets while the business controls only eligible actions and gas budgets
PRODUCT FLOW
Four steps users can understand
01 · Discover eligibility
The approved provider API would return JPY, asset, payment-method and country eligibility.
02 · Provider checkout
The provider handles fiat payment, fee disclosure and KYC, then delivers USDC to the user's wallet.
03 · Separate product consent
Completing the purchase never triggers a support payment automatically; the user confirms the product action separately.
04 · Policy and verification
JGas evaluates the v0.7 SimpleAccount call and budget, uses a Paymaster only when activated, and reconciles an independent receipt.
INTERFACE TEMPLATE
Sample product interface
A code-native sample for reviewing the product structure without real keys, transactions or customer data.SAMPLE UI · NO LIVE TRANSACTION
SAMPLE CONTROL PLANE
POLICYJapan market environment
01production-jp · illustrative
02JPY quote · Provider pending
03Policy version 04
04Sponsored spend · LOCKED
Illustrative UI only; it shows no live JPY quote, purchase or gas spend.
CAPABILITIES
Designed capabilities
Organization, project and environment isolation
Keys, policies, usage and audit records are isolated by product and deployment environment.
Target and selector policy
SimpleAccount calldata is decoded directly and calls outside the allow-list are rejected.
Atomic gas budgets
Per-operation, daily and monthly limits plus aggregate native value are checked during PostgreSQL reservation.
One-time credentials
Control and Project Key plaintext is shown once; only an HMAC digest is stored.
Intent and finality ledger
An intent is bound to its UserOperation hash and cost is finalized only after independent RPC finality.
INTEGRATION SEQUENCE
Implementation sequence
- Fetch provider support dataAfter approval, query assets, payment methods and quotes in sequence; today this is sample UI only.
- Create provider sessionThe server requests a checkout session with a restricted callback and user-wallet destination.
- Prepare JGas sponsorshipA server-only Project Key evaluates the unsigned v0.7 UserOperation and prepares Paymaster fields.
- User wallet signsThe user's wallet signs the final UserOperation including the Paymaster fields.
- Submit and reconcile the same intentThe signed object is submitted with the same intent and independently reconciled against receipt and ledger.
SERVER-SIDE PSEUDOCODE · NO CREDENTIALS
Server integration sketch
Secrets never enter the browser. Every external response is verified by the server before product state advances.
const coverage = await server.onramp.getCoverage({ market, asset });
const checkout = await server.onramp.createSession({
wallet: verifiedUserWallet, coverageId: coverage.id
});
const prepared = await server.jgas.prepare({ unsignedUserOp });
const signed = await userWallet.sign(prepared.userOperation);
await server.jgas.send({ intentId: prepared.intentId, signed });SECURITY
Security and responsibility
No custody of user assets
No private key, seed, private passkey material or user asset is accepted or stored.
Server-only keys
The JGas Project Key and any future provider secret never enter the browser.
Fail closed
No upstream call occurs when policy, account implementation, chain, EntryPoint or Paymaster response is invalid.
Purchase and product action stay separate
An on-ramp completion never authorizes an automatic support payment or product transaction.
READINESS
Current limitations
Provider approval pending
There is no live on-ramp contract, API key, quote, KYC or webhook integration.
Funded sponsorship locked
The current production control plane rejects every spend route with HTTP 503.
Supported core scope
The current core supports only Base 8453/84532 and ERC-4337 v0.7 SimpleAccount.
Japan operations remain unverified
JPY display, Japan-specific support, legal/tax review, load/recovery proof and independent security audit are incomplete.
Market and operating boundary
This is a Japan-market blueprint. It does not claim Japan launch, licensing, regulatory approval, JPY payment methods or provider availability.
Sample controls on this page perform no payment, wallet or onchain transaction.External product surface