Online Payments

Scenario overview

Saved payment methods, subscriptions, pre-authorization, profit sharing, and refunds explained by business scenario — concepts, lifecycle, and notifications — with the parameter differences across Checkout, Web SDK, and Direct API.

This section is organized by business scenario and is independent of the integration method: the guides cover concepts, operations, and result notifications. Scenarios that require configuration when creating a payment also compare the parameters across Checkout, Web SDK, and Direct API. The integration flow of each method is described in Checkout integration, Web SDK integration, and Direct API integration; signature verification, acknowledgement and retries, deduplication, status interpretation, and result queries are covered in Webhooks. For profit share notification URLs, verification, and acknowledgement, see Profit sharing.

Scenarios at a glance

Scenario	Typical business	Checkout	Web SDK	Direct API
Saved payment methods	Repeat purchases without re-entering card details	Customer opts in to save	Customer opts in to save	Server-side tokenization, token payments
Subscription payments	Recurring charges, automatic or merchant-initiated	Initial subscription	Initial subscription	Initial subscription, renewal, plan changes
Pre-authorization and capture	Deposits, reservations, securing funds before shipping	Pre-authorization	Pre-authorization	Pre-authorization, capture, void
Profit sharing	Allocate funds after a payment in the platform model	Configure at payment creation	Configure at payment creation	Configure at payment creation

After a successful payment, your server requests refunds through the API. The refund guide covers requests, result notifications, queries, and cancellations.

Whichever integration method creates the transaction, your server initiates self-managed subscription renewals, managed subscription plan changes, and pre-authorization captures and voids through the Direct API.

Three kinds of tokens

Three kinds of tokens appear in the documentation and are not interchangeable:

Card token: the tokenId obtained after the customer opts in to save a card or your server tokenizes one, used for later token payments; see Saved payment methods.
Subscription token: the tokenId returned in the subscription payment webhook, paired with contractId for renewals and plan changes; see Subscription payments.
Encrypted wallet token: the one-time encrypted payload returned by the Apple Pay or Google Pay SDK. Pass it through unchanged as tokenId in the tokenInfo field and name the wallet token provider in provider so that Onerway decrypts it; it cannot be saved or reused.

A subscription that also saves the card produces both a card token and a subscription token; the two token systems must not be mixed.

Local payment methods

How to find which methods Onerway supports and which are available for an order, the differences across integration methods, the three customer actions and delayed settlement, method-specific parameters, subscription-capable methods, and the extra requirements of some regional methods.

Saved payment methods

Let customers save a card for repeat purchases — choosing between customer opt-in and server-side tokenization, the tokenization result webhook, listing and deleting saved tokens, and the parameter differences across integration methods.