CNBS Software Ties Payments and Commerce to SAP Without Middleware

CNBS Software builds its business around connecting customers, vendors, and employees to SAP without the delays that typically come from batch processing or third-party middleware. The company organizes that mission around two named products: ChronarPay, a payment portal, and WECO eCommerce, a storefront platform. Both connect directly to SAP, and CNBS also has a sister company, Smart Data, which delivers IT services and digital solutions that extend the value of ERP systems more broadly.

Direct SAP and Oracle Payment Connectivity

ChronarPay is a PCI-compliant payment portal built for enterprise-grade transactions. It connects directly to SAP and Oracle, which CNBS says allows transactions to post in real time without a middleware layer. PCI DSS compliance is a standard requirement for any system handling card data, and the direct ERP connection enables that real-time posting.

That direct connection is designed to eliminate reconciliation work between the payment system and the ledger. Transactions post to SAP or Oracle as they occur, and CNBS says this speeds up cash flow. Eliminating middleware between customer-facing payment systems and the ERP is a general efficiency consideration for SAP-run finance organizations.

ChronarPay processes credit cards, ACH transfers, and recurring payments, plus other electronic payment methods, giving finance teams a single connected path for the formats their buyers use most. Built-in compliance tools support transactions across currencies and geographies.

On the customer-facing side, the portal lets buyers view invoices, make payments, and track balances online, so they can manage those tasks without contacting the vendor for each one.

Extending SAP Beyond the Four Walls

WECO eCommerce applies a similar direct-connection model to online storefronts. Orders, pricing, and availability pull from SAP in real time, again without middleware, meaning the product data shown to a buyer reflects current SAP records. WECO supports both traditional and headless architectures, giving implementation teams flexibility in front-end design while the backend connection to SAP stays constant. Headless commerce, where the presentation layer is decoupled from backend systems, is an established pattern across B2B and B2C platforms, and WECO’s support for it fits within that trend.

The platform is built to handle large-scale B2B catalogs while offering B2C-style convenience, multi-language support, and capacity for high transaction volume.

Smart Data, CNBS’s sister company, addresses a related problem from a different angle: unifying multiple backend systems into a single customer-facing portal. In a documented project for Davey Tree, Smart Data built a responsive portal that integrated SAP, Dynamics CRM, and CMS data.

The team built OData services in SAP to expose real-time service and account information, then used custom APIs to bring in CRM and CMS content. OData is a widely used SAP-native protocol for real-time data exposure across many SAP integration projects. Smart Data also implemented SAP Customer Data Cloud for identity management and single sign-on, addressing the access-control complexity of combining several systems into one login experience. The resulting platform is described as scalable, reducing operational strain on support teams while giving Davey Tree’s customers more direct tools to manage their own service and account needs.

What This Means for SAPinsiders

Direct SAP connectivity removes reconciliation delays. Finance teams using SAP-integrated payment portals like ChronarPay may see less manual matching between payment platforms and the ERP ledger. The shift changes the shape of month-end close work without adding new reporting requirements.

Sister-company portfolio spans payments and portals. SAP customers evaluating vendors for payment automation and customer-facing portal builds may find it relevant that CNBS Software and Smart Data operate as sister companies. Buyers weighing a single relationship against separate vendors for these two needs now have that structure to consider.

Multi-system portals require identity and access planning. IT and security teams supporting a unified customer portal spanning SAP, CRM, and CMS need governance for identity management across systems, as Smart Data does with SAP Customer Data Cloud for single sign-on. Planning for that becomes a necessary step once multiple backend systems feed one front end.