Content of this pageHow to create a purchase path that can be closed within the app (a purchase path that does not open in an external browser)
In PayPay (Online Payment) One-time billing, it is possible to avoid appearing in the external browser of the end-user purchase lead (Screen transition) by setting the parameter of the freecsv item "TRANSITION_TYPE" of Purchase request (A01-1).
This will be an improvement for merchant who are concerned that being redirected to an external browser is an impediment to UIUX.
Purchase flow (Screen transition) when "TRANSITION_TYPE" is not used
Purchase flow (Screen transition) when using "TRANSITION_TYPE"
Cautions
- For information on how to set up the TRANSITION_TYPE, see Link Type Purchase request.
- When using "TRANSITION_TYPE", after Payment completed in the PayPay app and returning to merchant app, in principle merchant should prepare a landing page after the SBPS screen WebView.
In addition, when using this function on Android, the launchMode of merchant app's Activity must be set to singleTask or singleInstance. Normally, this is set to Standard, so please be sure to set this when implementing merchant side app.
App-related troubleshooting
In SBPS's PayPay (Online Payment) offering, we have created the following troubleshooting for problems such as not being able to start the PayPay app and not being able to return to the merchant app after Payment. When introducing PayPay (Online Payment), please refer to it if you have any problems with the application linkage.
| trouble case | End-user Payment devices | Trouble incident | Assumed cause | Measures※1 |
|---|---|---|---|---|
| 1 | iPhone | When Payment the PayPay app does not start and Transition to the web login screen. Furthermore, even if you log in, you may not be able to make Payment. | In iOS, WebLink (UniversalLinks) may cause an error due to continuous redirect processing. | This can sometimes be avoided by inserting a "user tap screen (for launching the PayPay app)" on the SBPS side. |
| 2 | iPhone | After Payment completed, I can't Transition to merchant app. | Cause ① If the default browser is not Safari, you may not be able to return to merchant app. Cause 2 It's like a continuous redirect process on iOS. WebLink (Universal Links) may cause an error. | Cause ① Countermeasure: As this is unavoidable at this time, please advise users to change their default browser back to Safari. Cause 2 Countermeasure: This can sometimes be avoided by inserting a "user tap screen (for launching merchant apps)" on the SBPS side. |
| 3 | Android | After Payment completed, I can't Transition to merchant app. | This may occur when a DeepLink (custom URL scheme) is set in the "success_url" field of Purchase request (A01-1). This occurs because DeepLink (custom URL scheme) does not work properly in POST requests. | Please avoid setting DeepLink (custom URL scheme) in the "success_url" field. Prepare and link WebLinks (AppLinks) or a landing page for your app |
*2: If you use the user account linking function in Recurring billing(fixed term/pay-as-you-go), Recurring billing(fixed term/pay-as-you-go) is also subject to this troubleshooting.
Cautions
- Trouble Case 1 can also occur when merchant platform is online. The causes and solutions are the same.
- The images of "User Tap Screen (for launching the PayPay app)" and "User Tap Screen (for launching merchant app)" are as shown below. Instead of the usual SBPS screen (a white screen that appears for an instant), this screen (Screen transition when the end user taps) will be displayed. Please contact the SBPS sales department when using this service.
- If you are using the "User Tap Screen (for launching the PayPay app)" or "User Tap Screen (for launching the merchant app)", both One-time billing and Recurring billing(fixed term/pay-as-you-go) under the same MSID are applicable.
