Use the right component
Choose an SDK, hosted field, wallet sheet, or redirected experience based on channel and compliance scope.
Use mobile SDKs, hosted components, tokenized credentials, wallets, and app-aware authentication to create secure in-app payment journeys.
Choose an SDK, hosted field, wallet sheet, or redirected experience based on channel and compliance scope.
Preserve cart, customer, transaction, and return context through authentication and asynchronous events.
Use tokenization and device-appropriate controls for returning and recurring customers.
Design for approval, challenge, cancellation, timeout, pending, duplicate, and retry states.
The interface turns configuration, transactions, and performance into something teams can inspect and act on.

Final availability and configuration are confirmed against the business model, markets, providers, and implementation scope.
Talk with a team that understands the commercial, technical, risk, and operating sides of payments.