Payment method integration notes

Different payment methods may have different requirements across Apps, WebViews, iframes, and redirects. This page keeps only the special notes that are easy to miss, so you can scan it quickly when choosing payment methods or designing an integration flow. This page is not a complete payment method availability list. Availability depends on your merchant contract, Portal Payin configuration, and the paymethodconfig/inquiry response. Always use Webhook or active inquiry as the source of truth for payment results. Do not rely only on the user redirect URL.

General capability checks

Topic	Applies to	What to watch	Recommended action
External launch capability	Payment methods that jump to a wallet App or external authorization page; App WebView	Some wallets complete authorization through deeplinks or an external browser	Confirm that the App and WebView allow opening external Apps or browser pages. Use `webUrl` or `deeplinkUrl` based on `orderAction.actionType`
Download, copy, and save capability	QR, OTC, bank transfer; App WebView	These payment methods may depend on QR download, payment-info copy, or long-press save	Implement download listeners, copy support, and save behavior. Do not assume WebViews support these by default
Redirect URL parameter integrity	Payment methods that depend on redirect parameters, such as PayPay Smart Payment; URLs passed between the App and WebView	The payment channel may append parameters to `redirectUrl`	Do not rewrite URLs or drop query parameters. Preserve all appended channel parameters
iframe payment capability	Google Pay, WeChat Pay, and payment methods that depend on browser payment APIs or referrer information; iframe Checkout	These payment methods may depend on browser payment capability or referrer information	Add `allow="payment"` to the iframe and set Referrer Policy to `strict-origin-when-cross-origin`

Payment method exceptions

Payment method	Applies to	Why it is special	Recommended action
PayPay Smart Payment	Merchant App WebView	PayPay states that Smart Payment cannot be used directly inside a merchant App WebView. The redirect appends `one_time_token`	For App WebView scenarios, open PayPay in an external browser or hide PayPay in that environment
Google Pay	Virtual goods, App WebView, iOS WebView	Virtual goods cannot use Google Pay inside an App WebView. iOS WebView may need extra configuration	Open in an external browser. If needed, adjust WKWebView according to Google Pay guidance
Apple Pay	H5 or desktop pages that embed Checkout in an iframe	You must use the Waffo frontend SDK and contact Waffo technical support in advance to complete domain verification and registration	Do not load Checkout in a plain iframe. Follow Apple Pay integration
JKOPAY	iframe Checkout	JKOPAY does not support iframe loading	Use redirect or `window.open` to open Checkout

For payMethodType, payMethodName, and payMethodCountry, see Checkout customization
For quick answers, see FAQ

Getting Started

Core Concepts

Integration

Webhook

SDK

Tools & Reference

Point Topup API

General capability checks

Payment method exceptions

​General capability checks

​Payment method exceptions

​Related references

General capability checks

Payment method exceptions

Related references