Outpay documentation
Accept native USDC on Base with a non-custodial hosted checkout, a scoped REST API, and signed payment webhooks.
Outpay v0.1 Beta · documentation
Payments that settle to your wallet.
Create a checkout, send your customer to a hosted Outpay Checkout page, and receive a verified checkout.paid webhook when Outpay detects the matching USDC transfer on Base.
Outpay v0.1 Beta
Outpay is beta software. API routes, response fields, webhook payloads, and payment statuses may change before a stable release, and the payment-verification pipeline has not completed an independent production-readiness review. Use test-mode credentials and a controlled merchant account until your own review is complete. See known limitations.
Who this is for
Developers
Create your first checkout with the public API and redirect a customer to Outpay Checkout.
Merchants
Create a store, verify a payout wallet, and manage payments from the Outpay Dashboard.
API reference
Use the code-verified v1 endpoints, request and response shapes, errors, and retry behaviour.
Webhook handling
Verify a signed checkout.paid event before you update an order.
How a payment works
Outpay is non-custodial: a customer sends native USDC directly to the merchant's registered payout wallet on Base. Outpay watches for the transfer, matches it to the checkout's amount and recipient, waits for the required confirmations, and notifies the merchant.
01
Create
Create a checkout from the Outpay Dashboard or POST /api/v1/checkouts.
02
Detect
Outpay matches a Base USDC transfer to the expected recipient and amount.
03
Confirm
Your server receives a signed checkout.paid webhook once confirmations are satisfied.
What Outpay supports today
| Property | Current release |
|---|---|
| Network | Base mainnet only |
| Currency | Native USDC only |
| Settlement | Non-custodial, direct to the merchant's payout wallet |
| Webhook events | checkout.paid only |
| SDKs | None — integrate with cURL, fetch, or requests |
| OpenAPI specification | Not yet published |
Documentation status
This documentation is derived from the Outpay application's route handlers, validation schemas, and database migrations, and is kept in sync with that code. Dashboard, admin, provider-integration, billing, and future-SDK material is explicitly labelled Available, Partially implemented, Planned, or Not found so that a disagreement between documentation and product behaviour never goes unflagged. See system status for the current capability matrix.
Related documentation
- Getting started — choose an integration path and authenticate your first request.
- API reference — endpoints, schemas, and errors.
- Changelog — what changed, and whether it requires action.