Sage News and Discussion

Do we have a big L on our forehead? Really Sage? You've known this since at least last year and you've not anticipated that a lack of choice in credit card processing might be an issue for customers in the wholesale distribution industry?

It really will come down to how the spreadsheet calculates the risk of losing customers. That and figuring out how many of their customers don't qualify to get processing from SPS.

How long before they no longer store sales tax codes, or EDI or maybe even ACH. Anything transactional in nature is something that Sage could try to corner the market on and either become the sole provider or charge a transaction surcharge to the developer. Yet they have not been able to work in expiring unlocking keys to their product and they have customers who cancel maintenance and keep using the software year after year.

Social Security and FEINs too.

The issue with the unlocking keys is as much about the EULA and figuring that out as it is the technology. My understanding the technology issue is one of being able to grant historical access with out giving data entry access.

Which would be easy if all the modules were framework - just ignore all the create and modify permissions.

that linked in thread was hilarious - a developer swearing up and down that they have an integrated cc solution right now for V2013 and Lori saying, beware any 3rd parties claiming to integrate.... They really don't know what they are doing - and like you mention, they've had plenty of time to prepare for this.

@EricAnderson If they were talking to the partner channel at Summit 2012 I have to believe they were in design on this removal of CC info well before that. So let's be kind and say Sage have had this on their plate for 2 years.... I do not have a problem with them removing access to CC info. I just want them to communicate their intentions with more candor than they have.

@JimWoodhead Is this essentially (or temporarily) the end of Terms on Time?

Sage also appears to be set to roll out their own TOT competitor.

@BrianRice Good question... Although we use SPS as the back-end processor and don't use CC from inside SAGE 100 so it shouldn't be affected until Sage Releases a product that competes with it.

Boy after reading the linked-in threads I see lawsuits a coming with the Credit card ISV's.

If you read through Sage's mid-year earnings you start to realize the importance that Sage Payments plays in their earnings. I do not think this is a fight that NA can give up. Remember that NA is not really determining global strategy - they are just executing (in my opinion).