The Challenge
With decades of experience providing CRM software to nonprofits, SofterWare saw a growing opportunity to support nonprofit software developers with embedded payments. When SofterWare first launched SafeSave in the early 2000s, the company operated through a direct integration with one of the world’s largest payment processors. While this got SafeSave up and running, as the company grew, it soon became clear that relying on a single processor had major drawbacks. Being tied to a single processor meant SafeSave had limited control over its own payments business, which made it difficult to negotiate better rates and negatively impacted its pricing and profitability. Additionally, SafeSave could only offer a single set of payments products to its ISVs, which wasn’t enough to meet the diverse needs of its customers. If a customer had any issues with the processor, their only options were to accept the service SafeSave had on offer or go elsewhere — not a great position for SafeSave or its customers.
Finally, under its partnership arrangement, SafeSave was carrying the full burden of security and compliance, which made things harder for both the company and its merchants.
“SafeSave basically acts like a consultant for software providers and ISVs, helping them find the right payment solutions and the right ways to integrate them,” said Dan Colbeth, Director of Integrated Payment Services at SofterWare. “Our customers want to monetize payments, but it’s tough when you’re responsible for all the security and integration challenges, especially with so many data breaches happening these days. They absolutely do not want to take on responsibility for that, and frankly, neither do we! So we needed a way to shift some of that burden elsewhere.”