STATE
Explicit transaction lifecycle
Separate initiated, pending, successful, failed, cancelled and refunded states so the order is not inferred from one ambiguous callback.
Payment integrations
Keep checkout stable
when gateways change.
Thonem payment integrations are designed around adapter boundaries, explicit transaction states, callback verification and idempotent processing rather than gateway logic scattered across checkout.
TH / PAYMENTS
Checkout→Adapter→Gateway↺Callback
provider details stay at the edge
CALLBACK
Idempotent callbacks
Duplicate delivery should be safe. A provider retry must not create a second order-side effect.
ADAPTER
Provider isolation
Gateway-specific payloads are translated at the boundary instead of becoming the commerce data model.
Provider support is implementation-specific.
Thonem can be integrated with selected gateways according to market, merchant account and project requirements. This page describes the integration model; it is not a claim that every provider is enabled in every deployment.