Authorize.Net CIM: Explaining Validation Types

Modified on Mon, 28 Oct at 8:29 AM

Validating card details is an important step in securing your checkout. From version 5.0 of our extension, we offer two validation methods that are handled by Authorize.Net as they removed the "none" option that existed in the past:


  • Test Mode: Validate fields and expiration date
  • Live Mode: Run $0.01 test transaction first (*extra transaction fee)


Test Mode

The test mode will query Authorize.Net but will not submit a transaction. If you have email receipts enabled you will see these come in with the following information:


************* TEST MODE *************
... ========= ORDER INFORMATION ========= Invoice : none Description : Test transaction for ValidateCustomerPaymentProfile. Amount : 1.00 (USD) Payment Method: Visa xxxxXXXX Transaction Type: Authorization Only


As this does not create an actual transaction, there are no fees involved and the customer will not see any charge nor will you see it in your Authorize.Net dashboard.


NOTE: At this time for the Hosted form, especially for Payment Options and 'save info' forms, this will run at least once regardless of your validation mode settings. This may mean you see it run twice if set to test mode, or alongside live mode if that is set.


Live Mode

The live mode will create an actual test transaction with Authorize.Net, the amount will vary based on the card type or MSP. This amount will be voided and will offer more sufficient validation of the card being submitted, at the cost of paying for an additional transaction per order. If you have email receipts enabled you will see a similar message as the one shown above but it will not include the "TEST MODE" line at the start of the email.


Suggestions

If you are seeing the test mode requests, this means you have email receipts enabled. We would recommend turning email receipts off as they are redundant in the scope of Magento and will not be seen anywhere else nor by any customers. Otherwise, some additional suggestions we can provide:

  • Create an email filter for "Test transaction for ValidateCustomerPaymentProfile"
  • Reach out to Authorize.Net about these validations causing an email receipt in the first place, as they ideally should not given no transaction actually occurs.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article