For our Seamless Views, the field called
paymentUrl will be used when the
payer is redirected out of the Seamless View (the
iframe). The payer is
redirected out of frame when selecting payment instruments which trigger SCA.
This includes 3-D Secure card payments, credit account, invoice, MobilePay,
monthly invoice payments, Trustly and Vipps.
The URL should represent the page of where the Payment Seamless View was
hosted originally, such as the checkout page, shopping cart page, or similar.
paymentUrl should be set to the same URL as that of the page where
Please note that the
from the same Payment as the one that initiated the payment process
originally, so it should include some sort of state identifier in the URL. The
state identifier is the ID of the order, shopping cart or similar that has the
URL of the Payment stored.
paymentUrl in place, the retry process becomes much more convenient for
both the integration and the payer.
paymentUrl is used by the Seamless View flow and must be used for
WebView-based app implementations. Some payment instruments only work when
owning the full browser page (no use of
<iframe>), this will be solved by
doing a full browser (top frame) redirect out of the Seamless View. 3-D Secure
requires this, for example.
For mobile flows, some payment instruments work best when app-to-app switching is enabled and handled automatically (Swish, Vipps etc). To solve this, it is important that the third party app or site understand where to redirect the payer back to after the flow on their end is completed.
paymentUrl is the URL Swedbank Pay will provide to the third party for
handling the redirect back to your site or app. When receiving the payer back
paymentUrl either in an app or web page, it is important to restore the
Seamless View to let the payment finalize the flow. For in-app it is important
that you either implement the
onPaymentCompleted event or let the Seamless
View redirect to the
completeUrl before intercepting the WebView. If you
intercept the WebView when the payer’s device is redirected to the
it can lead to issues. If you want to handle payment errors in your own code,
you should also subscribe to other events provided by the Seamless View
Events to subscribe to for full control over the payment flow are can be found in Seamless View Events.
When implementing the Seamless View flow into a WebView in your mobile app, you
should use a custom scheme or Universal Link
paymentUrl for handling automatic switching between your app and the
payment app on the mobile device.