Help - Search - Members - Calendar
Full Version: Usaepay Fraud Controls
MonsterSmallBusiness Forums > MonsterCommerce > Merchant Accounts
RobVW
USAEpay has several cool fraud control settings that I would like to enable, most of which are based on the users IP address, such as Block By Host or IP, Country Blocker, and Multiple Credit Card attempts on same order.

My store is not yet "live" but I have done a few test transactions, and have noticed that the client IP is not being passed from monstersmile.gif to USAEpay, which makes all of theIP based fraud controls useless. It looks like the IP that is getting passed is the IP address of the hosting server of the store (are the servers in Canada?).

Has anyone noticed this and has it been resolved?
Nuriel
I do not know about that, but since you did not go live yet I suggest to reconsider the use of usaepay, the reason is that monstersmile.gif does not display the error codes from usaepay when a transaction is declined.

The reason can be as stupid as wrong zip code but the customer have no idea why he cannot complete the checkout which result in some orders that are not finalize.

To be fair with usaePay other than that (which is monstersmile.gif fault) it is a great gateway.

We are in a long process of switching, so my suggestion is switch before it becomes an headake!

Nuriel
BCB
QUOTE(Nuriel @ May 12 2007, 04:33 PM) [snapback]124445[/snapback]
I do not know about that, but since you did not go live yet I suggest to reconsider the use of usaepay, the reason is that monstersmile.gif does not display the error codes from usaepay when a transaction is declined.

The reason can be as stupid as wrong zip code but the customer have no idea why he cannot complete the checkout which result in some orders that are not finalize.

To be fair with usaePay other than that (which is monstersmile.gif fault) it is a great gateway.

We are in a long process of switching, so my suggestion is switch before it becomes an headake!

Nuriel


We use USAepay and it's a good system but Nuriel is right, I'm already pretty bummed we listened to monstersmile.gif about using it. I've had a few customer already with the "Your site doesn't work" call only to find out they had entered the wrong info checking out.

At some point I'm hoping monstersmile.gif will fix this problem, seeing as it's the system they tell you to go with and (I think) its part of the network solution family.
Julie
Hi Guys,

Actually that is being addressed and I hope to have that fixed soon. USAePay's servers are located in the US with redundancy in 2 other locations around the country. There up time is phenomenal and once we get this issue addressed, it should be a great solution for everyone. In the meantime, if you need us to switch gateways until this is solved, let me know and I can make that happen.

Thank you,
Julie
1-800-838-9699
Nuriel
Julie,
I agree with you that usaePay is an excellent Gateway.
Unfortunatelly the update that I have got from monstersmile.gif a week ago does not share your optimisem
I gave up and I am switching this week.
Can you elaborate on your comment?

This is the response I have got...

"...we do have this issue logged as a feature request and no further escalation would change the outcome. We can not offer an expectation that fucntionality that has never existed in the software will be added at this time. "

Sincerely,

Nuriel
RobVW
Interesting discussion... But back to my original question!
It is apparent that the monstersmile.gif software does NOT pass the client IP address to USAEpay when completing a transaction. This renders some potentially very useful features of the USAEpay system completely useless. How about passing this info to USAEpay? Please????

I have been using USAEpay for several years, and I already know that they are good (I've used MANY others prior to usaepay). IN FACT, one of the MAIN reasons I decided to try out the monstersmile.gif software was because they support usaepay out of the box and therefore would not require me to mess with new merchant accounts.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.