Visa Mandates and Auth.net CIM

I just got an email from auth.net regarding a change that VISA is implementing that affects charging a penny to see if a CC is valid. I don't fully understand all the changes and just want to see if amember is going to break with these changes and/or needs to change accordingly. I currently use the auth.net CIM payment module so this would potentially affect me. Im sure other gateways will need to make similar changes as well to support VISA Mandates so this could be applicable to others.

--------------------------------snippet explaining changes from the email --------------

The following is a brief description of each mandate followed by a listing of when Authorize.Net will support the mandates with each processor. Please note that Authorize.Net is dependent on each processor's readiness to fully support the mandates. All mandates are applicable only to Visa transactions.
Zero ($0) Dollar Account Verification / $0 Authorization
Any merchant currently processing $0.01 (or any other low amount) authorizations as a means of verifying a Visa card are now permitted to process a zero ($0) dollar account verification request (a.k.a a $0 authorization). Zero dollar authorizations provide merchants with an effective means of validating account numbers and other authentication elements such as CCV and AVS.
+ Merchants will be charged an Account Verification Fee for each $0 authorization.
+ The fee applies only to transactions processed by U.S.-based merchants and does not apply to partial or full authorization reversals.
+ Merchants that process $0.01 or other low amount authorizations as a means of validating a card, run the risk of being assessed a "Misuse of Authorization System" fee by Visa (more information below).
Zero Floor Limit
Visa requires that all transactions submitted for clearing (capture or settlement) be properly authorized, regardless of the amount. The "Floor Limit" is the smallest amount a merchant may accept payment for without obtaining an authorization. By specifying a zero floor limit, Visa is saying that all transactions must be properly authorized, no matter how small.
+ Visa recently instituted a Zero Floor Limit fee for each transaction submitted for clearing that did not receive a proper authorization (including authorization code).
+ This fee applies only to transactions processed by U.S.-based merchants.
Misuse of Authorization System
Visa requires all authorization transactions to be followed by a clearing (capture or settlement) transaction or, in the case of a cancelled order, for the authorization to be fully reversed.
+ Visa is now charging a fee for each authorization transaction that is not followed by a clearing transaction. In the case of a cancelled order, the transaction must be fully reversed within 72 hours.
+ The fee applies only to transactions processed by U.S.-based merchants and does not apply to partial or full authorization reversals.
+ Merchants submitting low-amount authorizations as a means of verifying card data may be charged a fee. Merchants should instead be submitting zero dollar authorizations as specified above.
Authorize.Net Mandate Support
As a reminder, Authorize.Net is dependent on each processor's readiness to fully support the mandates. As such, the support dates listed below may change. Once support has been added for the processors above, we will notify you via e-mail.
Currently, Authorize.Net supports $0 authorizations and full authorization reversals for Visa transactions submitted through the Chase Paymentech Tampa platform. We also support full reversals on the TSYS platform.
By November 1, 2009, we are planning to support both $0 authorizations as well as full authorization reversals with the following processors (any exceptions are listed next to the processor):
+ TSYS
+ Global Payments (GPN)
+ Elavon
+ First Data Nashville - Full authorization reversals only. First Data Nashville has no plans to support $0 authorizations with Authorize.Net.
Additionally, by the end of Q1 2010, we are planning to support both $0 authorizations and full authorization reversals with the following processors:
+ RBS WorldPay
+ CardWorks Processing
+ Heartland
+ First Data Omaha
Please note that we have no plans to support the mandates with the First Data EFSNet platform as this is a legacy First Data platform. If you process with First Data EFSNet and need the ability to process $0 authorizations or full authorization reversals, you will want to contact your Merchant Account Provider for information on changing processors.
To look up your processor, log into the Merchant Interface at https://account.authorize.net and click Merchant Profile under Account in the main menu on the left. Your processor is listed under the Payment Methods section.
Visa Mandates and the Customer Information Manager (CIM)
Currently, CIM provides you with the option of performing an authorization for account verification purposes before creating a customer profile. The authorization amount that is automatically submitted is $0.01. To ensure that you comply with the new Visa mandates, we are modifying this functionality as follows:
+ If you are performing account verification using the CIM API, once your processor supports $0 authorizations (see the timeline above for when that will be), the API will use a $0 authorization instead of the $0.01 authorization it previously used. You will not need to do a full authorization reversal.
+ If you are performing account verification using the CIM API, but your processor only plans to support full authorization reversals, the API will submit a $0.01 authorization, and then Authorize.Net will automatically initiate a full authorization reversal on your behalf. This will be applicable to all merchants on the First Data Nashville platform.
+ If you are performing account verification using the CIM API, but your processor does not support $0 authorizations or full authorization reversals, the API will submit a $0.01 authorization as usual and there will be no full authorization reversal. This means that if your processor does not support the Visa mandates, or you perform $0.01 authorizations before your processor is ready to support the mandates, your Merchant Account Provider could charge you the associated Visa mandate fees. Please contact your Merchant Account Provider for more information on these fees.
One last item to note, if you are using CIM along with the Fraud Detection Suite (FDS) or the Advanced Fraud Detection Suite (AFDS), once your processor supports $0 authorizations, you may want to reconfigure your Amount Filter to set a lower limit of $0, so that your CIM verification transactions do not trigger that filter.

I got this same response from Alex, however, we are not talking about a plugin here.

The aMember system charges a $0.01 "test" charge, as seen here:

========= ORDER INFORMATION =========
Invoice : none
Description : Test transaction for ValidateCustomerPaymentProfile.
Amount : 0.01 (USD)

According to the new mandate:

If you are performing account verification using the CIM API, once your processor supports $0 authorizations (see the timeline above for when that will be), the API will use a $0 authorization instead of the $0.01 authorization it previously used. You will not need to do a full authorization reversal.

and...

or you perform $0.01 authorizations before your processor is ready to support the mandates, your Merchant Account Provider could charge you the associated Visa mandate fees.

So is aMember going to change?

I know this is an old thread but I'm having this problem today. I spoke with Authorize after a transaction was declined and the potential customer called to process the payment. Authorize tells me that I have to set the software to not execute a test transaction and that the .01 is not on their side but mine. Please advise.

Was there a resolution to this? Was the $.01 being charged by aMember or by Authorize?