OutpayDocs
API reference

Schemas and field stability

The objects exposed by the verified public v1 routes.

Checkout object

FieldTypeDescription
idstringCheckout reference, for example chk_4f21a9c3b7e04d18.
amountstringDecimal amount — never a floating-point number.
chainstringbase in the current catalog.
currencystringUSDC in the current catalog.
statusstringpending_payment, payment_detected, paid, cancelled, or expired. See payment lifecycle.
customerEmailstring or nullSet only if supplied at creation.
expiresAtISO 8601 timestampServer-enforced expiry.
successUrl / cancelUrlstring (URL) or nullMerchant redirect targets.
paymentUrlstring (URL)The hosted checkout URL.
recipient.addressstringMerchant payout wallet address.
recipient.tokenContractstringBase USDC contract address.
metadataobjectMerchant-defined JSON metadata, round-tripped verbatim.
paymentobject or nullnull until a transfer is detected; see the payment object below.

Payment object

FieldTypeDescription
idstringPayment reference, for example pay_9d21f7.
checkoutIdstringPresent on GET /api/v1/payments list items; implicit (omitted) on the payment embedded in a checkout response.
statusstringpending, paid, failed, or expired.
amountstringObserved transfer amount, as a decimal string.
currencystringUSDC.
chainstringbase.
txHashstring or nullnull until a transaction is matched.
fromAddressstringCustomer's sending address; empty until a transfer is detected.
toAddressstringMerchant payout wallet address.
confirmedAtISO 8601 timestamp or nullSet once confirmation requirements are met.
createdAtISO 8601 timestampWhen the payment record was created.

Network and asset

PropertyValue
NetworkBase mainnet, chain ID 8453
AssetNative USDC
Contract0x833589fCD6EDb6E08f4c7C32D4f71b54bdA02913
Decimals6

Beta contract

Field names and status values above reflect the current Beta implementation and may change before v1.0. Pin only fields you have verified against your own deployment, and watch the changelog for breaking changes.

  • Checkouts — request and response examples for every field above.
  • Payments — the list endpoint that returns payment objects.
  • Payment lifecycle — the meaning of every status value.

On this page