Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Cross Domain Payment Gateway Transaction

  • No replies
  • 3 have this problem
  • 1 view
more options

We use firefox for Online Payment transactions.User starts from Merchant Website (Say Domain 1, Tab name - A, Window Name in javascript is A),User is then redirected to Payment Gateway Website (Say Domain 2, opens on Tab name A, Window Name in javascript is A).Then User is directed to Bank Website for debit (Say Domain 3, a pop-up window, Window name - B).When user completes debit at Bank (Window B), Bank site redirects instruction (message) to Payment Gateway (Domain 2) instructing the browser to open response from Payment Gateway on Window A or Tab Name A.Window C (Bank Window) closes.It is noticed in Firefox that the response from Payment Gateway DOES NOT open on Window A but opens a new tab say Window C confusing customers.Other browsers the response opens on Window A or Tab A.

All Replies (1)

more options

Hi Everyone !! I thought to rephrase the above issue to make it easier to understand

Transaction Flow REQUEST

Step 1 When user performs payment transaction, User is directed from Merchant site (Domain 1) to Payment Gateway Site (Domain 2).

Step 2 At payment gateway site user selects Bank for making payments. User is then directed to Bank POP-UP Window (Domain 3) The current Payment Gateway page refreshes to verify if transaction is complete via direct channel.

Step 3 Once user authorizes transaction at Bank Window (Domain 3). Bank window sends payment response via browser redirection to Payment Gateway.

[RESPONSE] Step 4 Payment gateway is expected to process instruction and display status on the same tab window on which it is showing refresh status to customer

Step 5 Payment gateway displays transaction status on the Payment Gateway refresh page

ISSUE During request cycle Payment Gateway Page opens on top of Merchant Page and in a same tab as it should. The refresh page also is displayed in the same tab window. But the response (say R) from Bank (Domain 3) after being processed by Payment Channel (Domain 2) is displayed in a new tab instead on top of Refresh page.

The javascript or form post of the Bank Window clearly instructs the response (R) to be displayed on top on the current tab (Payment Gateway refresh tab) by using the same window name as the request tab window.

Hence the user ends up seeing 2 pages 1. Transaction refresh page 2. Payment Gateway response page

instead of only Payment Gateway response page

On other browsers like IE and Google Chrome the user sees only one response page i.e Payment Gateway Response page.