Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 15 of 15

Thread: New MasterCard and Discover Processing Requirements - Authorize.net

  1. #1
    shaser is offline Junior Member
    Join Date
    Oct 2009
    Posts
    28

    Default New MasterCard and Discover Processing Requirements - Authorize.net

    http://www.authorize.net/support/pafaqs/#do

    MasterCard and Discover are modifying their rules concerning the processing of debit, prepaid and gift cards. This e-mail includes important information about the new requirements and the timelines regarding Authorize.Net's support of the requirements, so please read it thoroughly.

    MasterCard's rule changes go into effect May 1, 2010, and Discover's rule changes go into effect April 16, 2010. However, Authorize.Net, MasterCard and Discover have worked together to extend these dates for all merchants using Authorize.Net solutions. Our merchants will now have until June 30, 2011, to implement support for the requirements within their systems.

    What are the requirements?
    MasterCard and Discover are requiring that all merchants support the following:

    +
    Balance response transactions — For prepaid and gift cards, once the card has been used, the remaining account balance will be transmitted along with the authorization response. The remaining balance must be printed on the customer receipt, displayed on the Web page or point-of-sale terminal, or both.

    +
    Partial authorization transactions — When a customer's transaction amount exceeds the balance available on their debit, prepaid or gift card, instead of declining the transaction, a partial authorization for the amount available to the customer will be returned. This will allow the customer to pay for the remaining amount with another form of payment. This is called a split-tender transaction.

    +
    Authorization reversals — An authorization reversal is a real-time transaction initiated when the customer decides that they do not want to proceed with the transaction, or if the merchant cannot complete the transaction for any reason. Authorization reversals free up the customer's available balance on their debit, prepaid or gift card.


    What steps is Authorize.Net taking to support these requirements?
    Authorize.Net will be updating our systems over the coming months to support the requirements, but will be dependent on each processor's readiness. For a table of when we anticipate we will support the requirements with each processor, please visit http://www.authorize.net/support/pafaqs/#when.

    What do I need to do to support the requirements?
    The steps that you will need to take to support the requirements depend on how you connect to the payment gateway. For example, if you connect using a shopping cart, point-of-sale device, or other solution, you will need to contact your solution provider to confirm that they will be supporting the requirements. If you connect using a direct integration, you should contact your Web developer for assistance. Please direct your Web developer to http://www.authorize.net/support/pafaqs/#do for information on the changes they will need to make.

    Do I have to support the requirements?
    MasterCard and Discover are requiring all merchants to support the requirements with the exception of merchants that exclusively process transactions via batch uploads, mail order/telephone order (MOTO), or recurring payment transactions. Your Merchant Service Provider (MSP) is ultimately responsible for determining if the requirements apply to your business, so please contact them for assistance in determining if your company is exempt.

    Once again, these requirements will not be enforced for Authorize.Net merchants until June 30, 2011. However, we wanted to bring them to your attention now so that you have plenty of time to plan for their implementation.

    For more information on the requirements, including how they affect our value-adding services, please visit our FAQ page at http://www.authorize.net/support/pafaqs/.

    Thank you for your attention to these important changes and for being an Authorize.Net merchant.

    Sincerely,
    Authorize.Net

  2. #2
    Mike The Last Boyscout is offline User
    Join Date
    Nov 2008
    Posts
    254

    Default

    Please take a look at this forums post for more information. We will update this as more information becomes available.

  3. #3
    greensongs is offline Junior Member
    Join Date
    Jul 2009
    Posts
    1

    Question Need more info on MasterCard and Discover changes

    The last update was more than a month ago.

    Will AspDotNetStorefront customers be required to purchase a new software upgrade? Or will the changes be made on your end? I'm very confused.

  4. #4
    AspDotNetStorefront Staff - Scott's Avatar
    AspDotNetStorefront Staff - Scott is offline Administrator
    Join Date
    Mar 2007
    Location
    Ashland, OR
    Posts
    2,390

    Default

    We're going to update the software to take these new rules into account once the majority of our supported gateways have done so. So far, only a couple have even mentioned this change, and those aren't planning to implement them for months at least (see Auth.net's plans for June of next year).

    When the changes are made you will have to upgrade to the version we release them in to get the new functionality. There will be a charge for that, but it'll just be our standard upgrade rates, you won't have to buy a new version of the software.

  5. #5
    Sequencing is offline Junior Member
    Join Date
    Apr 2009
    Posts
    21

    Default

    Scott,

    This may be too far in advance to know for sure but will you have an update specifically for this; or will it be included with other updates? I have a client running v.8 that is heavily customized so an upgrade isn't really an option. However, I will gladly purchase the upgraded source and apply the changes myself. Just wondering if I will need to filter out any other updates.

    Thanks,
    Ryan

  6. #6
    AspDotNetStorefront Staff - Scott's Avatar
    AspDotNetStorefront Staff - Scott is offline Administrator
    Join Date
    Mar 2007
    Location
    Ashland, OR
    Posts
    2,390

    Default

    This will most likely be part of a version update, we will most likely not 'patch' this for older releases. By the time this deadline rolls around, 8.0.1.2 is going to be over 2 years old.

  7. #7
    Sequencing is offline Junior Member
    Join Date
    Apr 2009
    Posts
    21

    Default

    I hear ya - time to upgrade! As a quick digression - do you by any chance have a detailed change log including file / method / line number for upgrades?

  8. #8
    AspDotNetStorefront Staff - Scott's Avatar
    AspDotNetStorefront Staff - Scott is offline Administrator
    Join Date
    Mar 2007
    Location
    Ashland, OR
    Posts
    2,390

    Default

    We generally put out release notes if there are major changes between versions, but those do not include filenames, line numbers, etc - just a high level list of the changes/fixes.

  9. #9
    chese79 is offline Junior Member
    Join Date
    Jul 2010
    Posts
    18

    Default

    Any update to how this will be handled/supported?

  10. #10
    AspDotNetStorefront Staff - Scott's Avatar
    AspDotNetStorefront Staff - Scott is offline Administrator
    Join Date
    Mar 2007
    Location
    Ashland, OR
    Posts
    2,390

    Default

    Not yet, a lot of these plans are being changed/updated as part of the acquisition by Vortx. We'll get it taken care of in time for the deadline.

  11. #11
    danieljlucas is offline Junior Member
    Join Date
    May 2010
    Posts
    5

    Default Any update?

    Hello,

    Do you have more information yet? We are running version 7.1.0.0 but will be upgrading to 8.0.1.4. Will we be compliant with these changes if we do so? If there is a document or page somewhere on your website regarding this, please provide the link.

    Kind regards,

    Daniel

  12. #12
    AspDotNetStorefront Staff - Scott's Avatar
    AspDotNetStorefront Staff - Scott is offline Administrator
    Join Date
    Mar 2007
    Location
    Ashland, OR
    Posts
    2,390

    Default

    We've actually just found out that Auth.net has finished making the changes on their end, so we can start working on implementing them into the software. It's way too early to say when that'll be yet or how all of the changes are going to be implemented, but we'll put up more information as we work things out.

  13. #13
    danieljlucas is offline Junior Member
    Join Date
    May 2010
    Posts
    5

    Default Follow-up

    Hi,

    Just to follow-up: Has this change been made to ASPDNSF? If so, what is the lowest version number that has the change.

    Thanks,

    Daniel

  14. #14
    AspDotNetStorefront Staff - Scott's Avatar
    AspDotNetStorefront Staff - Scott is offline Administrator
    Join Date
    Mar 2007
    Location
    Ashland, OR
    Posts
    2,390

    Default

    Those changes have not been made yet, no. Doing so is going to require some pretty huge changes in the app, which we don't want to do until they can actually be used. So far gateways just aren't picking up on the new 'requirements'. Auth.net adopted some of them, but that's about it from what we've seen.

  15. #15
    danieljlucas is offline Junior Member
    Join Date
    May 2010
    Posts
    5

    Default MasterCard Relaxes Restrictions

    Thanks for the quick reply. I also just checked the Authorize.Net FAQ today and it has been updated. It seems as though MasterCard has relaxed their restrictions:

    http://www.authorize.net/support/paf...=1316023258740

    “UPDATE: E-commerce merchants are now only required to provide support for authorization reversals. Though no longer required, partial authorizations and balance responses are considered best practices, and Authorize.Net still highly recommends that e-commerce merchants provide support for all three requirements. Retail and mobile merchants must still support all three requirements.”