The PayPay login URL can be obtained from pp.getLoginUrl or /v2/smartpayment/qr/sessions API. Since pp.getLoginUrl automatically controls the return URL and browser on the PayPay side, it reduces the implementation burden on merchants, and we recommend the use of pp.getLoginUrl.
pp.getLoginUrl obtains the UserAgent on the PayPay side. When using the /v2/smartpayment/qr/sessions API, the merchant must obtain the UserAgent and set it in the request parameter.
The following behavior will occur depending on the type of browser the user is using.
- If the browser is a supported browser, redirect to the browser used
- If the browser is not supported, the user is redirected to the default browser.
Note: If you are using Smart Payment in your merchant app and the return destination is a deep link (Custom URL Scheme), please use /v2/smartpayment/qr/sessions API. pp.getLoginUrl does not support deep links. pp.getLoginUrl does not support deep linking.
Note: Even if the user's browser is different from the default browser, if the browser is a supported browser, the user will be redirected to the browser used.
Note: Safari guarantees the operation of SmartPayment itself, but for technical reasons, it is not possible to redirect to Safari. Therefore, if you are using Safari but it is not your default browser, you will be redirected back to your default browser.
Specifically, they are as follows
| Default Browser | Browser used by user | Browser to redirect | Account Linkage Results |
| Safari | Chrome | Chrome | Success |
| Chrome | Safari | Chrome | Failure |
| Safari | Safari | Safari | Success |
| Safari | Browser in merchant's app | Browser in merchant's app | Success (*1) |
| Safari | Browser in 3rd Party app | Safari | Failure (*2) |
※1 : Please specify a universal link or deep link for the return URL. In some cases, it may be necessary to use Webview in the merchant's application.
※2: If a browser in a 3rd party app is used, it cannot be returned by either pp.getLoginUrl or /v2/smartpayment/qr/sessions API.