Online
Online integration covers checkout in websites and mobile apps: customers browse, order, and pay in a browser or app without using an in-store terminal. This section provides two primary integration paths plus payment-method add-ons.
Suggested reading order: pick a primary path below based on whether SUNBAY hosts the payment UI and whether you build your own payment front end, then open a payment-method guide (e.g. Google Pay or Apple Pay) for channel-specific steps.
With the Hosted Payment Page, the checkoutUrl from Create checkout session is valid for 30 minutes (see expiresAt in the response). After expiry the link cannot be used—create a new session before redirecting the customer again.
Integration paths
| Path | When to use |
|---|---|
| Hosted Payment Page | SUNBAY hosts the payment page (HPP). You focus on creating a session, redirecting to checkoutUrl, and handling return URL + Webhook.Best when you want minimal payment UI work and faster launch. |
| API Only | Customers authorize Google Pay or similar wallets on your own checkout page; your front end receives the wallet encrypted payload, and your backend calls SUNBAY direct payment. Covers transaction results, Webhook, and security baselines.Best when you already own checkout UI and need wallet integration with server-side completion (public path does not include merchant-collected plaintext card data). Apple Pay is not yet supported through this path. |
| Google Pay | Payment-method guide: card brands, auth methods, 3DS / AVS notes, and how Google Pay fits the Hosted Payment Page vs API Only. Combine with either path above—not a third parallel “architecture”. |
| Apple Pay | Payment-method guide: availability, merchant validation, certificates, encrypted payment data, and how Apple Pay fits the Hosted Payment Page. API Only support is not yet available—this guide will be updated when it is released. |
More online payment-method guides may be added over time using the same “primary path + payment method” layout.