Onerway provides two core payment APIs for different levels of customization and control:
The choice depends on what features you need and how much custom code you're willing to maintain long-term.
Key points:
Recommended for:
Integration approach: Use the API to create a session and integrate the checkout page. Many capabilities can be enabled through parameters and Dashboard configuration
UI format: (Onerway-hosted)
Payment method support:
Complexity positioning: Scales smoothly from simple use cases to complex ones, suitable for most business scales and stages.
Recommended for:
Integration approach: Implement the payment flow through the Onerway SDK. You need to calculate the final amount and handle business logic yourself. The SDK provides a unified payment UI to simplify front-end integration
UI format:
Payment method support:
Complexity positioning: Better suited for large enterprises with complex and highly customized business logic and payment experiences.
| Feature | Checkout API | Payment Intents API (SDK) |
|---|---|---|
| Best for | Complete checkout flows including product information, subscriptions, discounts, etc. | Complex scenarios requiring custom business logic and fine-grained payment control |
| Payment methods | Credit cards, multiple local payment methods, Apple Pay / Google Pay | Credit cards, Apple Pay / Google Pay |
| Branding | ✅ Supports custom logo (Dashboard configuration) | ❌ Not supported |
| Save payment methods | ✅ Built-in support (enabled in Dashboard) | ⚠️ Requires separate Tokenization API integration |
| Subscription features | ✅ Built-in support for creating subscriptions | ⚠️ Requires separate Subscriptions API integration |
| UI flexibility | (Onerway provides complete UI) | SDK provides payment form components, other UI needs to be built by yourself |
| Address collection | ✅ Built-in collection of customer/billing/shipping addresses | ✅ Built-in collection of customer/billing/shipping addresses |
| Session expiration | Automatically expires after 30 minutes | |
| Webhook events | Mainly provides payment status events |