- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
End of PC Charge Support
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
11-02-2011 12:42 PM
I've read that Sage will no longer support PC Charge in the near future.
From the statement they issued it isn't clear if they will continue to support payment processors other then their own.
Does anyone know what the plan is here? We actually have a very good and very long relationship with our payment processor, which is very valuable and aren't willing to give that up.
Does anyone have the whole story?
Re: End of PC Charge Support
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
11-02-2011 01:13 PM
Sage ERP MAS 90 and 200 5.0 will contain a new integration with Sage Exchange. Sage Payment Solutions created this integration to streamline credit card processing across the entire Sage product portfolio. As part of this implementation, credit card numbers will no longer be stored within Sage ERP MAS 90 and 200. Instead they will be stored in the Sage Exchange Vault.
With the introduction of Sage Exchange in Version 5.0, the integration to PC Charge Payment Server will no longer function because it requires that credit card numbers be stored within the ERP system.
Sage Payment Solutions will be the only supported credit card processor for the Sage ERP MAS 90 and 200 product line.
In anticipation of the version 5.0 release, please note the following:
- Effective November 1, 2011, Sage will no longer offer the Credit Card Processing powered by PC Charge Payment Server module for new customer sales.
- For existing customers who wish to continue using PC Charge until their existing credit card processing provider contract expires, supported versions of Sage ERP MAS 90 and 200 will continue to work with PC Charge. This includes version 4.5.
- PC Charge version 5.9.3 will be the last version tested by Sage for compatibility with Sage ERP MAS 90 and 200. While subsequent versions of PC Charge may continue to work, they will not be validated as compatible by Sage.
- As has always been the case, requests for customer assistance for PC Charge should be directed to VeriFone. If a customer purchased PC Charge from Sage within the last 12 months, their purchase included an initial 12 months of VeriFone technical support. If they purchased PC Charge over a year ago, they will need to renew their support agreement directly with VeriFone. VeriFone offers two support plans:
- Telephone support plus software maintenance: $229 annual fee
- Telephone support only: $139 annual fee. If this plan is selected, there is a $120 fee per upgrade for any subsequent releases of PC Charge.
- Customers should contact Lela Reeves at VeriFone by telephone at: 912-527-4576or by email at: Lela_Reeves@verifone.com to renew their PC Charge support agreement if necessary.
- Sage will discontinue telephone support for all versions of the Credit Card Processing powered by PC Charge Payment Server module as of December 31, 2012. Until then, Sage will continue to provide telephone support for the Credit Card Processing powered by PC Charge module, while VeriFone must be contacted for any support for the PC Charge Payment Server application.
Via: Schulz Consulting
Re: End of PC Charge Support
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
11-02-2011 01:15 PM
My understanding is that Sage will no longer have their MAS products certified as PCI Compliant. They will no longer store credit card information locally - which means any enhancements which store CC info will not be compliant.
As of now there is no plan to offer any itnegration to payment processors other than Sage Payments -- and this will happen via a Sage Exchange integration common to most Sage products.
As noted this is presently planned to kick in with version 5.0 of Sage ERP MAS 90 and 200.
Re: End of PC Charge Support
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
11-02-2011 01:35 PM
"Sage Payment Solutions will be the only supported credit card processor for the Sage ERP MAS 90 and 200 product line.
In anticipation of the version 5.0 release, please note the following:"
I guess I had missed that statement!
Is this a trend in the industry?
Re: End of PC Charge Support
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
11-02-2011 02:28 PM
Sorry MAS90Guru but your statement ...
"My understanding is that Sage will no longer have their MAS products certified as PCI Compliant. They will no longer store credit card information locally - which means any enhancements which store CC info will not be compliant"
... Is inaccurate.
The fact that we are no longer storing credit card data will mean we no longer need to be PCI Compliant. The main reason for the change was to concentrate the PCI Compliant requirements in one location (SPS). As a result, once implemented only the SPS group will be required by the PCI Council to go through its audit process.
You can imagine by doing so, we are not only having the group most familiar with the industry handling the issues but removing the audit requirement from every product we are relieving our each of these products from a timely and costly process.
Re: End of PC Charge Support
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
11-02-2011 02:41 PM
See:
As Becky noted, the actual physical change to no longer store credit cards in Sage ERP MAS 90 and 200 will occur with version 5.0, but we did make the decision to stop selling the PC Charge integration to new customers effective November 1, 2011 to keep customer satisfaction up. With ongoing requirements for PCI compliance becoming more stringent, by not storing credit card numbers in our ERP software the ERP products will not be subject to lengthy and costly compliance audits that take resources away from other development efforts. If a third party modifies Sage ERP MAS 90 or 200 to store card numbers locally, that solution will not be able to be PCI compliant because only the manufacturer can submit a product for a compliance audit and Sage will not do that after version 5.0 is released.
The 5.0 roadmap will be updated soon to include more details on what we plan for additional credit card processing functionality in 5.0, but I'll give you a brief preview here. We plan to add Sage Exchange integration to AR Invoice Entry to allow those who don't own Sales Order to have better credit card integration. This allows us to include credit card support for Repetitive Invoices as well. Sage Exchange also provides card swipe functionality integration, which is the number one customer-requested enhancement request for credit card processing today. Also on the roadmap is integration with Sage Mobile Payments, the Sage Payment Solutions offering that allows credit card payments to originate on your smart phone.
Sage is committed to keeping credit card costs down for our customers. Most customers find that Sage either beats or meets competitive rates for card processing. There are occasional rate increases that are dictated by the card brands (i.e. Visa, MasterCard, etc.). When they occur, they are passed on through to our customers, but Sage doesn't have control over those changes.
via: LinkedIN
Re: End of PC Charge Support
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
11-02-2011 02:42 PM
I don't understand what part of my information you are saying is inaccurate since you seem to be essentially rephrasing it. Am I missing something?
Re: End of PC Charge Support
[ Edited ]- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
11-02-2011 07:40 PM - last edited on 11-02-2011 07:50 PM
Saying we aren't compliant implies we must be and something is missing. After we remove storing credit card data we aren't required to be. The PCI council standards are not applicable to us.
IMO, If anyone customizes their system resulting in any regulatory or industry standard requirements that "now" applies on their individual, customized installation, fulfilling those requirements is on them. The fact that we did not do so prior to their customizations because it was not applicable should not be interpreted as we don't comply with them.
This may be semantics but not applicable is not the same as non-compliant. The fact that the customized installation is non-compliant is a consequence of the customization not our base implementation.
BTW, it is possible someone could modify credit card related functionality in their system (say, modify it to use a different CC transaction interface that like SPS Exchange contains a mechanism to store credit card numbers in their data base and complies with the PCI Council audit requirements or does not store credit card numbers so it too does not fall under that standard). As long as the customization does not result in storing credit card numbers in the MAS 90 database, the PCI council regulations would still be not applicable to the MAS 90 installation. As a result, compliant vs non-compliant still does not apply.
Re: End of PC Charge Support
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
11-03-2011 06:36 AM
This announcement appears to me as a win-win for Sage (no PCI complaince dollars to spend + increase SPS business) and customers having to decide who they love more, Sage or the current processor.
Re: End of PC Charge Support
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
11-03-2011 11:14 AM
Phonelady, We certainly appreciate your support and understanding.
![]()


