1. Payment Link URL handling recommendation
Use a new window with minimum layers of code:
Extract the payment link (from the API) and follow that link in a new tab (aka browser window). Browsers typically block pop-ups when they do not believe they were initiated by a human, therefore we recommend using as few layers of code as possible between the click event and call to window.open() when launching a new pop-up. The likelihood of the browser blocking the pop-up increases with additional code, as the browser starts losing the connection between the events. Refer to this article to learn more pop-up blockers in the browser.
Use a fallback link:
We recommend that implementers also add a fallback link on the area the user clicked - that would allow them to “manually” load the page in the same window. This way, if there are issues with showing the pop-up, the user is still able to complete the payment journey. However, if this circumstance occurs, then the user will have to manually navigate back by clicking the back button in the browser.
Do not use iframes:
The use of iframes is prohibited by both Interac and financial institutions. Therefore, you may not use any iframes in your payment journey process.
2. Check transaction status
Use our GET Payment Request Status endpoint to confirm the status of a new or past transaction at any time.
Learn more about the endpoint here
Updated 10 months ago