visitor@x402card:~$ faq

Frequently asked questions

x402card is a wallet-authenticated virtual-card service. Incoming x402 payments settle as USDC on Base and then create separate provider funding jobs. Current availability, fees, and limits are exposed by the production API.

Answers verified: 2026-07-12.

What is x402card?

It is a wallet-native service that connects incoming x402 payments to automatic virtual-card funding. The user manages card and funding state, not a separate app balance.

Do I need an email or password?

No email/password account is used. An EVM wallet signs a short-lived challenge to authenticate ownership.

Which network and asset are supported?

The current production rail is USDC on Base mainnet, identified as eip155:8453.

Is card issuance currently open?

No. The public production configuration currently reports issuePublicEnabled=false. This can change only when operator and provider gates are deliberately opened.

What does a card cost?

The configured provider issue fee for the current BIN is $0, with a $25 minimum first load. That does not mean issuance is currently available. See current fees and limits.

Does x402card promise global or no-KYC availability?

No broad promise is made. Eligibility, geography, provider policy, and card-program rules apply. A provider configuration that does not require email is not the same as a universal legal or availability guarantee.

When does a card receive funds?

Only after the x402 payment settles and the separate provider funding job succeeds. A settled payment can temporarily remain in funding, retrying, or operator-review state.

What happens if the provider times out?

x402card preserves the ambiguous state for safe reconciliation. It does not blindly replay an uncertain money-moving request.

Does x402card store my full card number or CVV?

No. It stores masked/provider metadata. Full credentials are retrieved on demand after fresh wallet proof and are not stored by x402card.

Can an AI agent use it?

Yes. Agents should use MCP first or the HTTP agent contract. Owner actions still require authorized wallet signatures. See the agent guide.