01
Merchant onboarding
What approval gating is for, how rails get enabled, and what a serious integration discussion covers—without promising timelines you cannot keep publicly.
Guides
These pages are intentionally short: answer-first explanations you can quote in design docs, security reviews, and onboarding playbooks. They are not a substitute for your merchant agreement, environment-specific signing contracts, or legal advice.
Canonical definitions: Glossary. Technical overview: /docs. Illustrative walkthroughs: /operations. Step-by-step procedures: Playbooks. Integration matrices: References.
01
What approval gating is for, how rails get enabled, and what a serious integration discussion covers—without promising timelines you cannot keep publicly.
Conceptual operational diagram for this guide. Not live merchant data or metrics.
02
What Pending, Paid, Confirmed, and Expired mean operationally—and how teams align finance, support, and engineering without over-claiming finality.
Conceptual operational diagram for this guide. Not live merchant data or metrics.
03
Why raw-body verification matters, how retries interact with idempotency, and what security teams should expect from a mature integration.
Conceptual operational diagram for this guide. Not live merchant data or metrics.
04
How to avoid collapsing “detected funds” into “final” when your accounting depends on confirmations—without inventing universal chain guarantees.
Conceptual operational diagram for this guide. Not live merchant data or metrics.
05
Where secrets belong, what “server-to-server” implies for checkout UX, and common anti-patterns that create preventable incidents.
Conceptual operational diagram for this guide. Not live merchant data or metrics.
06
Operational checklist for three-plane matchers, exception queues, period close, and finance-ready evidence—without inventing universal posting rules.
Conceptual operational diagram for this guide. Not live merchant data or metrics.
07
Decision paths from detection through policy confirmation, exception handling, and books-ready gates—aligned with bounded lifecycle vocabulary.
Conceptual operational diagram for this guide. Not live merchant data or metrics.
08
Layered server-side boundaries: API authority, webhook verification, lifecycle mapping, reconciliation, and treasury controls—architecture-first, not feature lists.
Conceptual operational diagram for this guide. Not live merchant data or metrics.
09
How treasury posting differs from lifecycle Confirmed states—recognition gates, allocation discipline, and separation from payout orchestration.
Conceptual operational diagram for this guide. Not live merchant data or metrics.
10
Inbound settlement rails, merchant balance semantics, and payout orchestration—why conflating them creates treasury and support incidents.
Conceptual operational diagram for this guide. Not live merchant data or metrics.
11
Replay windows, duplicate suppression, out-of-order delivery, and provider retry semantics—with an illustrative verification walkthrough.
Conceptual operational diagram for this guide. Not live merchant data or metrics.