Skip to main content
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

TopicApplies toWhat to watchRecommended action
External launch capabilityPayment methods that jump to a wallet App or external authorization page; App WebViewSome wallets complete authorization through deeplinks or an external browserConfirm that the App and WebView allow opening external Apps or browser pages. Use webUrl or deeplinkUrl based on orderAction.actionType
Download, copy, and save capabilityQR, OTC, bank transfer; App WebViewThese payment methods may depend on QR download, payment-info copy, or long-press saveImplement download listeners, copy support, and save behavior. Do not assume WebViews support these by default
Redirect URL parameter integrityPayment methods that depend on redirect parameters, such as PayPay Smart Payment; URLs passed between the App and WebViewThe payment channel may append parameters to redirectUrlDo not rewrite URLs or drop query parameters. Preserve all appended channel parameters
iframe payment capabilityGoogle Pay, WeChat Pay, and payment methods that depend on browser payment APIs or referrer information; iframe CheckoutThese payment methods may depend on browser payment capability or referrer informationAdd allow="payment" to the iframe and set Referrer Policy to strict-origin-when-cross-origin

​
Payment method exceptions

Payment methodApplies toWhy it is specialRecommended action
PayPay Smart PaymentMerchant App WebViewPayPay states that Smart Payment cannot be used directly inside a merchant App WebView. The redirect appends one_time_tokenFor App WebView scenarios, open PayPay in an external browser or hide PayPay in that environment
Google PayVirtual goods, App WebView, iOS WebViewVirtual goods cannot use Google Pay inside an App WebView. iOS WebView may need extra configurationOpen in an external browser. If needed, adjust WKWebView according to Google Pay guidance
Apple PayH5 or desktop pages that embed Checkout in an iframeApple Pay does not work inside an iframeDo not use Apple Pay inside an iframe. Use a top-level redirect, window.open, or an App WebView instead
JKOPAYiframe CheckoutJKOPAY does not support iframe loadingUse redirect or window.open to open Checkout