- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Any and all card numbers declined with response code #3 in sandbox
Hello,
I've written a service to integrate with Authorize's API. We are testing using a sandbox account and it is set to live transactions. No matter what credit card number we've tried we get a decline with code #3 and responsereasoncode of #123. Even actual card numbers are throwing a #3 declination. Does anyone have any ideas what could be happening? I've got to go live with this service by Thursday.
Thanks!
Mike
โ02-26-2018 01:33 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @mikegar
Response Code 123 suggest you're using our sandbox login id and password instead of an API Login and Transaction key for authentication.
https://developer.authorize.net/api/reference/responseCodes.html?code=123
Richard
โ02-26-2018 01:47 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Richard,
Thanks for the prompt response! You're right, I am using my sandbox login. Do I want to use my production login and trankey against the test URL?
Thanks!
Mike
โ02-26-2018 01:57 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I used my login and transaction key and I'm still getting an error #3 but the reasoncode is now 13.
โ02-26-2018 02:25 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorted my issue out by using the proper login credentials for the sandbox.
โ02-27-2018 08:30 AM

