OutpayDocs
Resources

Glossary

Outpay terms in plain language.

TermDefinition
BaseThe Ethereum layer-2 network used by the current payment matcher.
CheckoutA payment request and its hosted customer-facing flow. Also called a checkout session internally.
Checkout referenceThe opaque identifier (chk_...) returned when a checkout is created.
ConfirmationAdditional block depth confirmed after a transfer is included on-chain.
CurrencyThe token being transferred; v0.1 uses USDC exclusively.
FinalityConfidence that a transaction will not be reorganized off the canonical chain. Outpay's automated reorg handling is not verified.
Idempotency keyA merchant-generated key that lets checkout creation safely replay its original response instead of creating a duplicate.
Live modeThe API-key environment used for real, production-style merchant configuration.
Merchant webhookA signed, outbound event delivered from Outpay to the merchant's server.
Non-custodialOutpay does not hold funds; settlement is direct to the merchant's own wallet.
OverpaymentA transfer above the requested amount; a small tolerance is accepted, but remediation for a large overpayment is a beta concern — see payment lifecycle.
Payout walletThe merchant-controlled address that receives every payment directly.
Test modeThe API-key environment intended for controlled integration testing. Not a separate blockchain sandbox.
Transaction hashThe blockchain identifier for a specific transfer.
UnderpaymentA transfer below the requested amount.

One canonical term per concept

This glossary uses one preferred term per concept throughout the documentation — for example, "payout wallet," not "withdrawal address" or "settlement wallet." If you see a synonym elsewhere, treat it as referring to the same thing defined here.

  • Core concepts — the subset of these terms most relevant to a first integration.
  • FAQ — short answers using this same terminology.

On this page