If you’re currently using Boyum iPayment with SAP Business One, you’ve likely already heard the news: iPayment is being sunset, with end-of-life on the horizon after a transition period extending through 2026 for North American customers. While the software won’t stop working tomorrow, iPayments support is winding down and customers are being encouraged to plan their next move. For many SAP Business One users, the real question isn’t if they should migrate—it’s what they should migrate to. Third Wave CreditCard could be the right product to support all of your business requirements coming off of iPayment.
At Third Wave, we built CreditCard specifically for this moment. Our team at Third Wave has been helping customers move off of iPayment onto an evergreen solution. Here’s why CreditCard is the best 1:1 payments processing solution replacement for Boyum iPayment on the market right now for SAP Business One companies.
A Familiar Situation for SAP Business One Customers
If you’ve been around the SAP ecosystem for a while, sunsets and transitions are nothing new. Business One (and ByDesign before it) span almost three decades of software history. During this time, we’ve seen add-ons evolve, publishers change strategy, often leaving customers navigating complexity they didn’t ask for—new vendors, new pricing models, and new workflows layered on top of critical financial processes.
At Third Wave, what our SAP Business One customers consistently ask for out of their payments solution is simple:
- Keep payment processing inside SAP
- Preserve existing functionality and streamline workflow
- Gateway flexibility — if you like a gateway, software shouldn’t stop you from using it
- Control long-term costs
That’s exactly where Third Wave CreditCard shines.
Going from iPayments to Third Wave CreditCard
Current iPayment customers have many paths forward. For some, the same streamlined experience within Business One for their team that they’re getting with iPayment is what ultimately matters most. Third Wave CreditCard is going to offer the best native experience and custom support to give you more payments control:
- Control over your gateway
- Control over your costs
- Control over if, how, (and when) you migrate
Native, Embedded SAP B1 Experience
Just like iPayment, CreditCard is a native SAP Business One add-on and doesn’t rely on a workaround, bolt-on, or external portal. It’s purpose-built to live inside of SAP and bring your gateway data and processing into the software. When we first designed CreditCard, we designed it as a point-solution extension of our Business One Bizweaver toolkit. Bizweaver builds native workflow functionality specifically for B1, and even when CreditCard expanded into its own standalone product, the native-to-B1 philosophy remained. Just like with all of Third Wave’s products, your users stay in the same screens they already know—no pop-ups, no external dashboards, no context switching.
CreditCard vs. iPayment
Folks looking at how CreditCard stacks up to iPayment are going to see many of the same functionalities they rely on today, and a few more that improve upon the current experience:
- PCI Compliance: CreditCard is a Certified SAP Add-On, designed with PCI DSS compliance at its core—using tokenization and encryption to protect sensitive data while helping you avoid costly compliance headaches.
- Rate negotiation: Level-II and level-III transaction data means lower merchant rates with your current gateway provider. Some new CreditCard customers also use the opportunity to further renegotiate merchant rates with a gateway switch.
- Gateway Flexibility: Unlike solutions that require you to move to a specific processor, we give you gateway choice between leading gateways today. If you decide that another makes more sense for your business, you can migrate whenever—tomorrow, next month, or in a few years.
- Web Client Compatibility: Just like Container Management (another Third Wave B1 add-on), CreditCard is being taken to web client in 2026, preparing it for the future of B1.
Your Transition Strategy
Current iPayment customers don’t need to migrate tomorrow, but they do need a plan.
Third Wave has helped SAP Business One customers navigate change for decades, and CreditCard was built around the B1 native experience, just like iPayment. Going to CreditCard brings continuity—not disruption—when your payment systems inevitably need to evolve. If you’re currently using iPayment and want a true 1:1 replacement that keeps payments native, flexible, and cost-effective, let’s talk.