Explore your payment options, minimize disruption, and plan a smooth transition.

Boyum B1 iPayment Is Being Discontinued: How to Prepare Your SAP Business One Payment Processing Strategy

A practical guide to evaluating payment integration options, maintaining business continuity, and planning a successful transition.

Book a 15-Minute Integration Demo

If your business currently uses Boyum B1 iPayment with SAP Business One, the announcement that the solution is being discontinued raises an important question:

How can you transition to a new payment solution without disrupting your business operations?

Payment processing is closely tied to sales orders, customer accounts, invoicing, and financial reporting. Changing the software that manages these transactions requires more than simply installing a replacement.

Businesses need to consider how a transition could affect existing payment workflows, stored customer payment information, transaction processing, accounting efficiency, and ongoing costs.

Domain Technology Group helps SAP Business One customers evaluate integrated payment processing requirements and identify solutions that support secure, efficient financial operations.

What Is Happening with Boyum B1 iPayment?

Boyum IT Solutions has announced it will discontinue B1 iPayment, its payment processing add-on for SAP Business One.

Under Boyum’s published transition plan, Boyum will continue supporting North American customers through December 31, 2026.

Although existing installations may continue operating during the transition period, the approaching end of support makes it important for affected businesses to evaluate their options.

The end of support does not necessarily mean payment processing will stop immediately. However, businesses should not assume that functionality, compatibility, security updates, or support services will remain available indefinitely.

The priority is to establish a transition plan before existing payment operations are disrupted.

Customers should confirm their support arrangements and deadlines with their current provider.

Why Changing Payment Integrations Requires Careful Planning

For SAP Business One customers, credit card processing is often integrated into core financial and operational processes.

Depending on the configuration, payment processing may include:

  • Authorizing payments for sales orders
  • Capturing payments when orders are fulfilled or invoices are issued
  • Managing stored customer payment methods
  • Processing multiple transactions in batches
  • Maintaining payment and transaction records
  • Reconciling payments with outstanding invoices
  • Protecting sensitive customer payment information

Replacing an integration without reviewing these processes can add manual work, create accounting complications, or delay payments.

Before selecting a replacement, document your current payment workflows and identify which capabilities must be preserved or enhanced.

Five Important Questions to Ask Before Choosing a Replacement.

Will the new solution integrate with our existing SAP Business One processes?

An integrated payment solution should support the daily activities of your accounting, sales, and customer service teams.

Consider whether employees can continue managing payment authorizations, captures, transaction information, and invoice processing in SAP Business One.

The goal should be to improve efficiency without adding unnecessary steps or disconnected applications.

What happens to our existing customer payment information?

Many payment processing systems use tokenization to protect sensitive credit card data.

However, payment tokens don’t automatically transfer across providers.

Before migrating, businesses should determine whether they can securely transfer existing payment credentials, whether customers will need to re-enter payment information, and how recurring or stored-card transactions may be affected.

This is one of the most important technical considerations when evaluating a replacement.

Will we need to change our payment gateway or merchant account?

Not all SAP Business One payment integrations support the same processors or merchant account arrangements.

Businesses should determine whether a replacement requires a different payment provider, merchant account, or processing agreement.

The evaluation should include processing fees, contract terms, supported payment methods, and long-term costs.

Can we maintain or improve our payment automation?

Evaluate a replacement for its ability to reduce manual effort.

Consider whether the new solution supports payment pre-authorization, batch processing, automated invoice closure, and transaction tracking.

For manufacturers, distributors, and other businesses processing high transaction volumes, these capabilities can improve financial operations.

What support will be available during and after implementation?

Payment processing is a business-critical function.

Organizations should evaluate the provider’s SAP Business One experience, implementation requirements, technical support, and ability to resolve payment workflow issues.

A successful transition depends on both the software and the expertise supporting it.

Introducing CerePay: Integrated Payment Processing for SAP Business One

Domain Technology Group offers CerePay, an integrated payment processing solution for SAP Business One that uses PayPal Express (Braintree) Express (Braintree) payment technology.

CerePay helps businesses manage payment activities within SAP Business One, reducing manual processing and improving transaction visibility.

Instead of treating payment processing as a separate administrative activity, CerePay connects payment transactions to the financial and operational workflows already managed in SAP Business One.

Simplify Payment Authorization and Capture

CerePay supports payment pre-authorization for sales orders and invoices, helping businesses manage payment activities within existing workflows.

Manual and batch capture capabilities give businesses flexibility in processing authorized transactions.

Business benefit: Reduce repetitive payment-processing steps and handle transactions more efficiently.

Reduce Manual Accounting Work

When payment processing and accounting operate separately, employees may spend extra time updating records, reconciling transactions, and closing invoices.

CerePay supports automated invoice closure and synchronizes payment information with SAP Business One.

Business benefit: Help accounting teams reduce manual updates and maintain more consistent financial records.

Protect Customer Payment Information

Securely managing customer payment information is essential for businesses accepting credit card payments.

CerePay uses tokenization to protect sensitive payment information without storing actual card details directly in SAP Business One.

Business benefit: Support safer payment handling while keeping processing convenient.

Improve Payment Visibility

Finance and accounting teams need reliable access to transaction information.

CerePay provides a transaction register that helps businesses review payment activity and maintain records for payment processing operations.

Business benefit: Improve transaction visibility and make payment activity easier to review.

Support Customer Payment Flexibility

CerePay supports multiple payment methods for business partners, enabling organizations to manage customer payment preferences across supported workflows.

Business benefit: Streamline payment administration for customers with different payment requirements.

Book a 15-Minute SAP Demo

Is CerePay the Right Alternative to Boyum B1 iPayment?

CerePay may be worth evaluating for SAP Business One customers seeking an integrated payment solution that supports payment authorization, capture, secure tokenization, and accounting automation.

However, every SAP Business One environment is different.

Before selecting a replacement, organizations should confirm:

  • Compatibility with their SAP Business One version and deployment environment
  • Supported payment gateways and merchant account requirements
  • Whether existing customer payment tokens can be transferred
  • Required payment authorization and capture workflows
  • Refund, recurring payment, and other transaction requirements
  • Implementation effort, licensing, and ongoing processing costs
  • Available technical support and maintenance arrangements

The right replacement should meet your existing business requirements while improving payment efficiency and financial visibility.

Domain Technology Group can help organizations evaluate whether CerePay fits their SAP Business One environment.

Four Steps to Prepare for Your Payment Integration Transition

Step 1: Review Your Current Payment Environment

Identify the payment gateway, merchant account, stored payment methods, transaction volumes, and SAP Business One workflows currently supported by your payment integration.

Document any recurring issues, manual processes, or limitations that could be addressed during the transition.

Step 2: Identify Your Essential Requirements

Determine which payment capabilities you must retain.

Consider how employees authorize transactions, capture payments, manage customer information, reconcile invoices, and review payment activity.

This is also an opportunity to identify processes you can simplify or automate.

Step 3: Evaluate Integrated Payment Processing Options

Compare potential solutions based on SAP Business One compatibility, functionality, security, payment processing requirements, implementation costs, and ongoing support.

Focus on how each solution meets your organization’s operational requirements.

Step 4: Develop and Test Your Transition Plan

Before changing payment systems, establish how you will handle existing customer payment information, outstanding authorizations, transaction records, and accounting workflows.

Thoroughly test the new integration before moving live payment processing to the replacement solution.

A well-planned transition can minimize disruption and maintain continuity across financial operations.

Frequently Asked Questions

When is Boyum B1 iPayment support ending?

According to Boyum’s published transition information, support for North American customers is scheduled to continue through December 31, 2026. Customers should confirm their support arrangements and any updated deadlines with their current provider.

Will B1 iPayment stop processing payments immediately after support ends?

The end of support does not necessarily mean every installation will stop operating immediately. However, you should not assume continued functionality, compatibility, security updates, or access to supporting services.

Businesses should confirm their specific situation and develop a transition plan.

What alternatives are available for Boyum B1 iPayment?

SAP Business One customers have options when evaluating a replacement for Boyum B1 iPayment.

The right solution depends on existing payment workflows, gateway requirements, security needs, integration capabilities, and long-term costs.

Domain Technology Group offers CerePay, an integrated payment processing solution for SAP Business One that supports payment pre-authorization, batch capture, secure tokenization, automated invoice closure, and transaction tracking.

Businesses considering a transition can work with Domain to assess whether CerePay meets their operational and technical requirements.

Can CerePay process payments through SAP Business One?

Yes. CerePay integrates payment processing with SAP Business One and supports payment pre-authorization, manual and batch capture, tokenization, transaction tracking, and automated invoice closing.

Can existing B1 iPayment tokens be transferred to CerePay?

Token portability depends on the existing payment provider, tokenization method, and the receiving platform.

Domain would need to evaluate the customer’s current environment to determine whether we can migrate existing payment credentials or must collect them again.

Will we need to change our payment processor?

That depends on the replacement integration and the payment infrastructure it supports.

Customers considering CerePay should confirm the applicable PayPal Express (Braintree) Express (Braintree) processing and merchant account requirements with Domain.

How long does a payment integration transition take?

Implementation requirements vary based on the existing environment, payment workflows, customer payment information, testing requirements, and integration complexity.

A technical assessment is the best starting point for establishing a realistic transition schedule.

Plan Your Next Step with Domain Technology Group

If your organization currently uses Boyum B1 iPayment, the approaching end of support is an opportunity to review your payment processing in SAP Business One.

The right solution should do more than continue processing transactions. It should support efficient financial workflows, protect customer payment information, and meet your organization’s operational requirements.

Domain Technology Group offers CerePay to help businesses integrate payment processing into SAP Business One and streamline key financial processes.

Schedule a CerePay Payment Integration Consultation

Book a 15-Minute Integration Demo

Connect with Domain Technology Group to discuss your current payment environment, integration requirements, and whether CerePay is the right solution for your business.

Domain Technology Group — SAP Business One Solutions & Integrated Payment Processing

Source: Boyum IT Solutions, B1 iPayment Detailed Transition FAQ. Verify the latest support arrangements and deadlines before publication.

Publication review: CerePay functionality is based on Domain’s existing product rack card. Domain’s technical team should confirm supported payment processors, token migration capabilities, SAP Business One compatibility, and implementation requirements before publication.

Schedule a CerePay Integration Consultation. 610-374-7644

 

Contact us today

Fill out the form below, or give us a call at (610) 374-7644.