Built for
Teams building Base wallets, community, creator or consumer applications for US users
← All productsMarket blueprint · Private pilot
INFRASTRUCTURE · PRODUCT BRIEF
JGas United States
Connect a provider-led USD on-ramp to a policy-controlled Base experience.
JGas United States does not directly handle USD or offer money transmission or exchange. An approved third-party provider would determine payment methods, US availability, fees and KYC and deliver USDC to a user-owned wallet. The shared JGas core would govern only the subsequent v0.7 SimpleAccount UserOperation. There is no US-specific provider approval, data region, live purchase or funded sponsorship today.
Base 8453 / 84532ERC-4337 v0.7ERC-7677PostgreSQLAzure Key Vault
SAMPLE UI · NO LIVE TRANSACTION
SAMPLE CONTROL PLANE
POLICYUnited States market environment
01production-us · illustrative
02USD eligibility · Provider pending
03Daily budget · SAMPLE
04Sponsored spend · LOCKED
Illustrative UI only; it shows no US eligibility, live quote, KYC or gas spend.
Intended outcome
A separated operating model where the provider handles fiat and KYC, users hold assets, and the business manages only downstream gas policy
PRODUCT FLOW
Four steps users can understand
01 · Check region and payment method
The approved provider determines USD, user-region and payment-method eligibility.
02 · Quote, KYC and purchase
The provider discloses fees and expected receipt before handling KYC and purchase.
03 · Delivery to user wallet
USDC is delivered to a user-controlled wallet, not an intermediary JunleeBuild wallet.
04 · JGas-governed action
After separate user consent, JGas evaluates the v0.7 call and budget and sponsors only an activated route.
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
POLICYUnited States market environment
01production-us · illustrative
02USD eligibility · Provider pending
03Daily budget · SAMPLE
04Sponsored spend · LOCKED
Illustrative UI only; it shows no US eligibility, live quote, KYC or gas spend.
CAPABILITIES
Designed capabilities
Multi-tenant control plane
Keys, policies, ledger and audit are separated per organization, project and environment.
Decoded call allow-list
Actual SimpleAccount targets and selectors are evaluated instead of client-provided hints.
Per-operation, daily and monthly budgets
Worst-case cost is atomically reserved inside a PostgreSQL row lock.
Intent binding
Chain, EntryPoint, sender, nonce, factory and callData are bound to one intent.
Finality ledger and audit
Only independently finalized cost is recorded once, alongside secret-free audit events.
INTEGRATION SEQUENCE
Implementation sequence
- Fetch support matrixAfter provider approval, assets, payment methods and quotes are queried in order for the user's region.
- On-ramp transaction sessionThe server creates a session bound to an allowed destination and callback and receives provider status only.
- JGas prepareAn unsigned UserOperation is policy-checked with a server-only Project Key.
- Wallet signatureThe user signs the final object including its Paymaster fields.
- Submission and finalityThe same intent is submitted and reconciled against a Bundler receipt and independent Base RPC.
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 fiat or KYC handling
The integration boundary assumes JunleeBuild receives neither USD payment instruments nor KYC documents.
User-owned wallet
USDC and signing authority remain with the user; JGas stores no private key.
Least-privilege server credentials
Project Keys and future provider secrets stay in a secret store and out of browser bundles.
Provider success is not payment proof
A provider status alone never completes the downstream product transaction; an onchain receipt is verified independently.
READINESS
Current limitations
No US provider approval
API access, payment methods, state availability, KYC and fees are not confirmed.
No US data-region deployment
The current shared private control plane is a single-owner pilot in Japan West.
Gas spend inactive
The data plane remains locked pending a Paymaster provider, contract audit, deposit and balance alerts.
Base v0.7 only
Chains and account types outside Base 8453/84532 and SimpleAccount v0.7 are unsupported.
Market and operating boundary
This is a US-market blueprint. It does not claim US money transmission, exchange, state availability, licensing, regulatory approval or a provider relationship.
Sample controls on this page perform no payment, wallet or onchain transaction.External product surface