Mobile app version of vmapp.org
Login or Join
Sherry384

: Determining if a visitor left your server We have an Apache server running a PHP website. The site is an e-commerce shop. We currently use Barclays as the payment provider but are seeing a

@Sherry384

Posted in: #Apache #Logs

We have an Apache server running a PHP website. The site is an e-commerce shop.

We currently use Barclays as the payment provider but are seeing a lot of customers drop out at the point at which we transfer them to the payment gateway (hosted with Barclays)

I can see specific instances in the shop where orders have been created but not paid/failed but I need to ascertain if the user has definitely left our server (or just failed to reach Barclays).

Is there anything in any of the server/access logs that states when a user transferred to a different domain?

Update
When the user clicks on 'Pay now' they are sent to a gateway transfer page which builds a hidden form of the shopping cart details and submits the form (using JS) to Barclays. How do I check the gateway is there before I send them?

10.02% popularity Vote Up Vote Down


Login to follow query

More posts by @Sherry384

2 Comments

Sorted by latest first Latest Oldest Best

 

@Angie530

Since your form uses JS, you can run multiple functions from the onClick action. You could first call a script on your server that will run various tests against the remote payment gateway and then if the result is positive, pass back code to redirect the user to the gateway. If the test is failing, then you could send an error message.

This would provide some insight but to be 100% certain you would need to contact your processor for log details as recommended by @Andrew Lott.

10% popularity Vote Up Vote Down


 

@Lee4591628

As a short-term check you could send a list of offending orders to Barclays and ask them to reply with a status for each one. They'll have a record of any transactions that made it to them, and should even be able to tell you how far into the process they made it before dropping off.

Obviously any orders that don't have a matching transaction in Barclays' system are the ones to focus on then. Perhaps you can look for a common pattern amongst those, like browser/OS version or ISP.

Depending on what integration method you're using, there's probably an API with the payment gateway which will let you query transactions on the fly. This is also really helpful to run regularly (as a nightly cronjob perhaps) to identify any orders which may have even been successful but the authorisation/response never made it back to your server after completion.

10% popularity Vote Up Vote Down


Back to top | Use Dark Theme