- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
API rejecting all credit cards
The sandbox environment is currently rejecting every credit card we try to send. This has effectively shut down our test environment and is a serious issue. Is anyone else seeing this issue? How do I go about getting this addressed ASAP?
โ03-21-2016 12:43 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
โ03-21-2016 01:33 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We're using the 'create_transaction' endpoint. The programming language is Python.
I called support and was able to resolve the issue by changing our CCV filter settings. We had to allow "P is NOT Processed".
However, the concern is that we didn't change this setting in the past. Frankly, today was the first time I've logged into the sandbox account for as long as I can remember because we'd misplaced the password.
โ03-21-2016 03:01 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @valkolovos
Hello
I've reported your issue to the product team for analysis. What value were you expecting instead of "P"?
I'd recommend subscribing to this topic so that you'll be alerted via email if there are updates. To subscribe, click Topic Options at the top of this thread and then select Subscribe. You'll then receive an email once anyone replies to your post.
Thanks,
Richard
โ03-21-2016 03:20 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This also started happening to us.
All cards with payment informaiton on file are now being declined.
It appears to begun on March 22 2016 at about 2:30AM, USCentral.
We are using the the anet-java-sdk-1.8.5.jar SDK.
โ03-23-2016 07:27 AM - edited โ03-23-2016 07:31 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @pgarvie
Is this with your sandbox or production account. And can you share the specific reasons response codes returned?
Richard
โ03-23-2016 07:30 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's in the sandbox.
We originally created the payment record with a CVV of 900
RESPONSE_REASON_CODE is 65
CARDHOLDER_AUTHENTICATION_VERIFICATION_RESPONSE is 2.
โ03-23-2016 07:43 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are you looking at the cvvResultCode? Cardholder Authentication Verification is related to Verified by Visa and MasterCard Secure code.
Richard
โ03-23-2016 08:01 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry, not sure what you mean.
What we detailed before are the key/value pairs returned by the Java API call to the merchant.postTransaction(transaction) method.
We don't see a key for a cvvResultCode.
We are testing in the sandbox. According to the Testing Guide, a CVV of 900 is always a successful match, so we are confused as to why two days ago our test transactions would start being declined because of a CVV issue.
โ03-23-2016 09:20 AM - edited โ03-23-2016 09:21 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is happening with all card types too, not just Visa and MasterCard.
โ03-23-2016 09:46 AM - edited โ03-23-2016 09:47 AM