tags:

views:

24

answers:

1

Consider the following use case 1. User selects a product to purchase on seller's site 2. Clicks on net-banking option and redirected to his bank website 3. Successfully makes the payment. 4. But before the payment gateway redirects him back to seller site the browser crashes. 5. Seller site reports that payment is not recived but the bank reports that payment has been made.

What are the best practices to handle such cases?

+1  A: 

Return money to customer or deliver goods. Should be a rare occasion, and I dont really see it possible as automating.

What you could ALSo do is regularly check all open / pending payments from the website (as: the user was sent to the bank, so I can check in an hour whether I simply missed / never got the callback / for the payment.

Imagine 4 is : User closes interface and browser never returns.

The payment gateway should have an API to keep and identify those, including whether the payment was finally aprooved.

TomTom
So ideally there is no silver bullet here and if the site developers have not considered this you might as well lose money?
Akshar Prabhu Desai
Yes, the price of crappy programming - or a sloppy work done by people who dont understand what the site is actually doing. Happens. Customers will call and get upset ;)
TomTom