Sage 100

You know when a reply starts with ""Thank you"" that there's some good Sage stuff coming. Via LinkedIn -- Thank you for your comments on Credit Card Processing with Sage 100 ERP. In order to clear any misconceptions I would like to state our policy and the reason for the decision, which affects all Sage ERP products. Because of the increased complexity of PCI compliance and the associated risks for both Sage and our customers, Sage has decided to only offer Sage Payments and Sage Exchange as its PCI compliant payment processing solution. By storing credit card data in the Sage Exchange ""Vault"" instead of within the ERP application, we reduce the risk and simplify the process of obtaining PCI compliance. As a result of this policy, with Sage 100 ERP 2013 release, we are using Sage Payment Solutions exclusively, with credit card information stored in the Sage Exchange ""Vault"". Customers upgrading to this release have two choices if they are not already using Sage Payments: 1. Move their merchant account to Sage Payment for their processing. Customers can continue to maintain their relationship with their bank, but will need to go through the underwriting process with SPS. In most instances Sage Payments will match or even beat customer's current rates. 2. Alternatively, customers can continue processing credit cards with their current processor; however, credit card data cannot be integrated with Sage 100 ERP. A number of processors and ISVs claim to have integrated to Sage 100 ERP or other Sage products. Customers and resellers should be aware that Sage either has de-authorized, or is in the process of de-authorizing, any Development Partner (ISV) that integrates payment functionality directly with Sage ERP products. Sage no longer allows third party integrations for payment processing due to the fact that we cannot control how the integration would adhere to PCI compliancy regulations. Development Partners have the option to integrate their solutions with Sage Payments -see http://na.sage.com/sage-payment-solutions/developers/program-overview for details. For more information on Sage Payments and PCI compliance, see http://na.sage.com/erp/~/media/site/erp/lp/sps/index.html For more information on Sage Exchange, see http://na.sage.com/sage-payment-solutions/products-services/payment-consolidation-and-administration/ TL;DR: Sage is not allowing any developers to create 3rd party links to payment processors other than Sage Payments or they will de-authorize the developer.

Is Sage really going to kick IIG out of the Developer program? I feel bad for Lori having to be the public face of Mr Fucus' short-sighted greed.

I wouldn't feel too sorry for her. She seems to have drunk the Kool Aid.

I think its been made abundantly clear at Sage that it's either drink the Kool Aid or get Tebowed.

My guess is that the integration which exist can stay - but that nobody can make CC integration for 2013 or higher.

Also I find very few people actually understand this issue fully. Be careful on upgrades. don't become the unpaid complaint department for Sage.

I would also assume that they are going to try and shut down ODBC access to the required components otherwise people will develop and just not sell it as such. Our experience with SPS was that it was more expensive than other options every time a customer priced it. I don't like the bait and switch game.

@WayneSchulz - Your comment about the messages starting with ""thank you"" are so spot on. I was recently going back and forth with some of the execs about the Sage CRM and Sage 100 link and I received an email back from Doug LaBahn that started with ""Thank you for your email."" The rest of the email read pretty much as a dismissal of my point of view. I printed it out and curl up next to it when I want to feel some love from Sage.

It's interesting to read some of the vendor replies. Most of them don't seem as if they are going to stop offering the integration which I'm guessing will wind up in some type of legal case with Sage.

The reasoning for this is pure flim-flammery. Kind of like raising the Sage CRM prices ""to match Canadian pricing"" and ""because top Sage CRM partners requested it"" (really? really???).

Dismissive is the right word.

@PeterWolf Thank you for comment.

If I thought I could get an extra $200/user I wouldn't tell Sage to raise the price, I would pocket the whole $200 myself...

The main comfort in all this is the Sage executive team EVP tends to turn over in 3-5 year cycles. Can you think of any of the recent leaders who have been here longer?