Quick answers to the questions we hear most, each linking to the page that covers the topic in depth. Can’t find yours? Email support@sohopay.xyz or ask in the beta integrators’ Slack.

​
Product

Yes. x402 revives HTTP 402 as a machine-native payment handshake: a merchant responds with payment requirements, the agent pays, and the request retries — no checkout page, no human in the loop. SohoPay adds what raw x402 lacks: credit lines, policy enforcement, and compliance screening on every payment.
Prefunded means loading USDC onto every agent wallet up front and topping it up forever. SohoPay agents instead draw on a credit line backed by the operator’s vault collateral — one pool of capital backs all your agents, and each payment settles from credit instantly. See Vault Funding.
No. SohoPay provisions agent wallets inside its MPC infrastructure (2-of-3 threshold: agent key plus Policy Service key). You call the API; key shares, signing ceremonies, and the fail-closed policy check happen inside the platform.
Yes. The sandbox runs on Base Sepolia with test funds and pre-loaded vault collateral, and it skips KYB. Follow the Quickstart — no wallet or USDC needed.
Mainnet is in private beta — join the waitlist via the dashboard. Sandbox is open to everyone today, and sandbox integrations carry over to mainnet with a key and base-URL swap. See Environment Setup.
We target 99.9% uptime, with a maintenance window Sundays 02:00–02:30 UTC announced a week ahead. Critical support issues get a first response under 1 hour, normal issues under 8. Full terms in SLA.

​
Integration

Merchant integration typically takes 3–5 days, agent setup 2–3 days, and a full end-to-end platform 5–7 days. The Quickstart gets you a settled sandbox payment in about 5 minutes; see Integration Paths for the track that fits you.
Yes. SohoPay is an API alongside your existing rails, not a replacement: merchants receive USDC settlements and reconcile via webhooks and settlement exports, which feed into whatever ledger or ERP you already run. See Settlements & Payouts.
No. Agent keys live inside SohoPay’s MPC infrastructure — there is no private key to store, back up, or leak from your servers. Your only secrets are your API key and webhook secret. See Key Management.
A compromised agent can only spend within its credit_limit and daily_limit, only at allowlisted merchants, and only past AML screening — the Policy Service enforces all three on every payment. Pause or revoke the agent immediately and rotate its key. See Key Management and Operator Liability.
Yes, instantly: call agents.revoke (or use the dashboard). Revocation is permanent and takes effect on the next policy check — in-flight requests fail with AGENT_REVOKED. To stop spend temporarily, lower limits or pause via agents.update instead. See Agent Setup.

​
Compliance

PCI-DSS is out of scope: SohoPay never touches card data — payments are USDC transfers on Base. If your stack also processes cards, your existing PCI obligations there are unchanged and SohoPay does not add to them. See Trust Model.
Yes, for merchants on mainnet — Didit-powered verification takes 1–3 business days. Sandbox skips KYB entirely so you can build first and verify before going live. See KYB.
Transaction records and audit logs are retained for the legally required period for payment infrastructure; settlement records are additionally permanent on-chain by nature (Base). For retention specifics relevant to your jurisdiction, contact support@sohopay.xyz.
Yes. Export settlements and transaction history any time via settlements.export or the dashboard, and request a full account data export through support. Deletion requests are honored within the limits of financial record-keeping obligations.
Not yet — SOC 2 is planned post-launch, with Google CASA Tier 2 also on the roadmap. In the meantime we can share our security architecture (trust model, MPC signing) under NDA, and Chainalysis reports are available on request.

​
Next steps

Troubleshooting

Specific error, specific fix — the full symptom table.

Glossary

Every term used across these docs, defined.

Support

Email, Slack, and escalation paths.