Auth.Net accepting Test Cards on Production

Title basically explains my issue..

I have read this on Stackoverflow: http://stackoverflow.com/questions/6151308/authorize-net-production-account-accepts-test-credit-card-numbers

Although that isn’t really geared towards s2member.

The Authorize.Net account is not set to Test Mode, I do login from https://account.authorize.net (It’s not a test account, where you login from https://test.authorize.net)

I have the setting: s2Member > Auth.Net Options > Account Details > Developer/Sandbox Testing? set to ‘No’. Below is the shortcode I am using for my signup form:

[s2Member-Pro-AuthNet-Form level=”1″ ccaps=”” desc=”Monthly Subscriber” cc=”USD” custom=”(domain name)” ta=”0″ tp=”1″ tt=”M” ra=”53.50″ rp=”1″ rt=”M” rr=”1″ rrt=”” accept=”visa,mastercard,amex,discover” coupon=”” accept_coupons=”1″ default_country_code=”US” captcha=”0″ success=”http://(domain name)/registration-success/” /]

Is there something that I’m missing?

–Update–

So it turns out that it is creating a ‘subscription’ in my Authorize.Net account, but the user is being created as a Level 0 (Free Subscriber) instead of Level 1 (Monthly Subscriber). I’m guessing because it’s a test credit card number, but the subscription is still created in Authorize.Net and the user is not notified.

Putting an invalid (non mod-10) number in the CC# box does return an error, but putting a mod-10 valid number in does not return an error and creates a new account.

• This topic was modified 3 years, 4 months ago by  Jennifer Reaves.

Nevermind– I figured out the issue.

For any of those who also are having this issue, be sure to check that your shortcode is not allowing a free trial period in your shortcode (as was my case). Changing the shortcode so that the ‘ta’ and ‘tp’ were both 0 fixed my issue, and now all test cards and invalid cards are being declined as expected.