Please verify able 7 payment situation

[moopa]

We have now spent over a week with 2 developers battling with payment with Ablecommerce, and after searching the forums and trying various things, i need some answers as to why it is proving so difficult to implement...

All we wish to do is verify the card details before we take payment. A prime example being the expiry date of the card. I appreciate that payment gateways differ, but we are doing a simple request to Paypal Web Payments Pro and we get nothing back that would imply an error with completely invalid card details.

Example Code Snippet:-

Code: Select all

if (authTx != null && authTx.TransactionStatus == TransactionStatus.Successful)
               {
                   //SEND THE CUSTOMER TO THE RECEIPT PAGE

// Debug Messages

                   Response.Write("<h1>AuthorizationCode=" + authTx.AuthorizationCode + "<br />ResponseCode=" + authTx.ResponseCode + "<br />AVS=" + authTx.AVSResultCode + "<br />CAVResultCode=" + authTx.CAVResultCode + "<br />CVVResultCode=" + authTx.CVVResultCode + "<br />IsDirty=" + authTx.IsDirty + " TransactionStatus=" + authTx.TransactionStatus + "<br />TransactionType=" + authTx.TransactionType + "</h1>");
                   

I paste this snippet because for 99.9 percent of the transacitons, we get a TransactionStatus.Successful.
Why is this the case? TransactionStatus.Successful for:-

- Any CC that matches the formula
- Any Billing Address
- Any CVV number
- Any expiry date!

Most the time the response would be:-

AuthorizationCode=(A valid code)
ResponseCode=PENDING (Fine)
AVS= Nothing
ResponseMessage = Nothing
CAVResultCode= Nothing
CVVResultCode = M (This happens regardless of the numbers we put in? Paypal says that it will return the correct error on the sandbox)
IsDirty = false
TransactionStatus = Successful
TranscationType = Authorize

So this happens on my own valid Visa card. It also happens with this test card:-

Card: 4366843303086261
08/2018

BUT, if we use this test card:-

5555555555554444 we get
TransactionStatus = Fail
Incorrect billing address (10759)

This is the only card (a test card given by Paypal) that does a fail??

I must stress that by trying this in code, or using the controls that come with Able, we get the same issue.

Along with the null exceptions for standard paypal we are experiencing, this is costing us lots of development time that should be handled entirely for us by the Ablecommerce system. Like many others we have purchased the software to do this stuff for us. I would very much appreciate an answer why this is not functioning as it should.

Thank you

[sohaib]

Well... If what you imply in your post is true then at various AC7 Ablecommerce stores users should be able to get away with checkouts with invalid credit cards; but that's not the case.

All credit cards are accepted only in a test environment. If you are testing your store in a test environment then whatever credit card number you enter with whatever expiry date you will get a successful transaction... unless of course if the test environment has some predefined numbers to simulate failure.

If you are testing on a real live environment and you are still getting invalid credit cards accepted then either the payment provider has gone crazy or something is wrong the the software that interacts with the payment provider.

We haven't received any such complaints from hundreds of live stores so I would assume the software is doing what it is supposed to do.

If there is a 'feature' that you consider 'missing' then you can post a feature request in feature requests forum.

[moopa]

All credit cards are accepted only in a test environment. If you are testing your store in a test environment then whatever credit card number you enter with whatever expiry date you will get a successful transaction... unless of course if the test environment has some predefined numbers to simulate failure.

To quote the paypal sandbox documentation directly:-

"The Sandbox creates all fictitious bank accounts, credit card numbers, and CVV2 numbers you need for development and testing. The Sandbox
simulates the verification of these numbers"

It is fair to say that we have only tested in a sandbox so i will start to test in a live environment Monday, however if what you say is true, it would be good to have known this before. As i said in my original post, i appreciate that you cannot be held responsible for quirks in the gateways, but some more support on the supported ones would be helpful.

As for feature requests. More API documentation and support for developers who do not wish to use your controls would be very welcome.

[AbleMods]

To quote the paypal sandbox documentation directly:-

"The Sandbox creates all fictitious bank accounts, credit card numbers, and CVV2 numbers you need for development and testing. The Sandbox
simulates the verification of these numbers"

It is fair to say that we have only tested in a sandbox so i will start to test in a live environment Monday, however if what you say is true, it would be good to have known this before. As i said in my original post, i appreciate that you cannot be held responsible for quirks in the gateways, but some more support on the supported ones would be helpful.

As for feature requests. More API documentation and support for developers who do not wish to use your controls would be very welcome.

PayPal's (outdated) documentation rarely does what it says it will do. Spend 5 minutes in the support forums and you'll understand. But more importantly, you must understand how sandbox modes work.
Sandbox doesn't use live data. It's not certified, secured or otherwise monitored as a "live" system. It's only purpose is to verify basic communication exchange between systems. You can't use it for real card verification nor should you. The same security systems that protect the live systems are not in place with a sandbox system.
Sandbox mode doesn't know a real card CVV because only the issuing bank knows that information. Sandbox can't determine if an expiration matches the card - again only the issuer has this information.

To test "live" data, you must be running in a "live" gateway mode. There is no other way.

[moopa]

Hi Joe.

Thanks very much for clearing that up. I was talking to a php developer recently who ended up using a live account to do testing and voiding the payments each time because of his frustration with the sandbox. The one thing i will say, is the validation on expiry and CVV also fails to work on the Paypal test card. (Address is validated however). Would you say this is the correct behavior?

My apologies for the confusion on this matter. If it turns out to be a sandbox issue, it could be that the other paypal null reference issue we are having could also be a result of the same thing. (It appears a few people get this problem).

viewtopic.php?f=22&t=8751&p=37546&hilit ... ull#p37546
viewtopic.php?f=22&t=8751&p=37584&hilit ... ull#p37584

Thanks again.

[AbleMods]

The one thing i will say, is the validation on expiry and CVV also fails to work on the Paypal test card. (Address is validated however). Would you say this is the correct behavior?

That is the correct behavior.

[moopa]

The one thing i will say, is the validation on expiry and CVV also fails to work on the Paypal test card. (Address is validated however). Would you say this is the correct behavior?

That is the correct behavior.

This is apparently not the correct behavior. Please check out this link on the Paypal Developer Forum (3rd post from the certified developer).
http://www.paypaldeveloper.com/pdn/boar ... d.id=11729

"CVV2 will be checked within the sandbox, but if it is invalid, it will allow the transaction to be processed, it will just report it as being invalid.
It is of course checked on the live system. "

From this post, i assume that i should get a successful transaction but with the correct CVV2 code (Match, No Match etc).

Any thoughts on this? I must say i am amazed (read as totally annoyed) at how the Paypal sandbox operates so differently from the live one).