Frequently Asked Questions

Payment Hub is a technology solution designed to help businesses get paid faster. It integrates with your ERP and payment provider of choice, providing a fully automated, self-service invoicing portal for your customers. The platform delivers invoice visibility, online payment processing, automated notifications, monthly statement generation, and a digital wallet — all connected directly to your existing ERP data.

Payment Hub combines an integration platform with a B2B customer portal to deliver invoicing, payment processing, notifications, and statement functionality. The integration layer pulls invoice and account data from your ERP in real-time, while the portal gives your customers 24/7 self-service access. Both the integration platform and portal offer scalable, customizable APIs for growing businesses.

A standalone payment gateway only processes transactions. Payment Hub is a complete B2B accounts receivable portal that integrates with your ERP to provide real-time invoice visibility, aging analysis, self-service payment, digital wallet management, automated notifications (20+ types), monthly statement generation, and Quick Pay links — all tied to your existing invoice and customer data. It also supports payment gateway flexibility, meaning you can use your existing processor or switch to one that offers better rates.

Yes. The ERP integration replicates invoices in the Payment Portal in real-time. Customers can view their full invoice history, filter by status or date range, see aging balances with color-coded visualization, export invoice lists, download individual invoice PDFs, and process payments — all without calling your AR team.

Tier I integrations are for the most commonly deployed ERPs. These are pre-built, off-the-shelf connectors that can be configured and deployed in approximately 2 weeks. Examples include Epicor Eagle, Epicor Eclipse, Epicor P21, Dynamics GP, SAP Business One, Infor SyteLine, and NetSuite.

Tier II integrations involve custom connector development for less common or highly customized ERP environments. These typically require closer to 8 weeks for development and testing. Any ERP with an accessible API, SDK, or database connection can be integrated — consult your representative for a budget and timeline estimate.

Payment Hub supports the top 25 ERPs as Tier I pre-built integrations, including:

• Microsoft Dynamics: D365 F&O, D365 Business Central, Dynamics AX, Dynamics GP, Dynamics NAV, Dynamics CRM/CE
• Epicor: Eagle, Eclipse, P21, Kinetic, E10, E9
• SAP: SAP Business One
• Oracle: NetSuite, Oracle EBS
• Infor: SyteLine, Cloud Suite Industrial (CSI)
• Sage: Sage 50, 100, 300, X3
• Other: Acumatica, QuickBooks Enterprise, Syspro

Yes. Any ERP that exposes an accessible API, SDK, or database connection can be integrated with Payment Hub as a Tier II custom integration. Contact your sales representative for a project scoping, budget estimate, and timeline for your specific ERP environment.

For common ERPs and payment processors (Tier I), setup typically takes one to four weeks depending on client readiness and credential availability. Tier II custom integrations may require 6–10 weeks. Timeline can also be affected by the scope of customizations, data migration, and client-side testing requirements.

Payment Hub supports credit card and ACH (eCheck) payments as standard. Additional development enables mobile payments and point-of-sale functionality. The digital wallet tokenizes both bank accounts and credit cards securely through PCI-compliant providers, allowing customers and sales representatives to store and reuse payment methods.

No. Payment Hub integrates with most U.S.-based payment processors. If you're locked in with your current processor due to your ERP, Payment Hub can often unlock flexibility to work with additional processors. You can also submit your current merchant statement for a competitive pricing comparison.

Yes. Payment Hub supports all five major processors to guarantee the required data fields for Level II and Level III interchange qualification. This can significantly reduce processing fees for B2B card transactions — typically saving 0.5%–1.5% per transaction when qualifying fields are submitted correctly.

Yes. Surcharging is supported through many payment gateways and processors and is permitted in 45 U.S. states. Payment Hub automatically calculates the surcharge amount and displays it transparently to the customer before payment confirmation — ensuring compliance and informed consent. This allows businesses to fully offset credit card processing costs.

Yes. Payment Hub integrates with PCI-compliant payment providers for credit card tokenization. The platform does not store card numbers directly — all sensitive payment data is tokenized at the processor level. The digital wallet stores tokens (not card numbers), enabling secure future use for both customers and sales reps.

Quick Pay generates a secure, tokenized payment link that can be included directly in invoice emails. When a customer clicks the link, they are taken directly to a pre-populated payment page for that specific invoice — no portal login required. This dramatically reduces friction for one-time payers and significantly improves collection speed.

Payment Hub includes 20+ automated email notification types covering: new invoice generated, invoice due date reminders, payment received confirmations, payment method added/removed, monthly statement available, failed payment alerts, Quick Pay link sent, account registration, password reset, and more. Each notification is configurable per implementation.

Pay-on-Account allows customers to make a general account payment without selecting specific invoices. The payment is automatically distributed across their oldest unpaid invoices first (FIFO — first in, first out), reducing the AR team's work of manually applying unallocated payments. This is particularly useful for customers who pay a fixed monthly amount.

Yes. Payment Hub automatically generates monthly account statements and makes them available for customer download as PDF. Customers receive an email notification when their statement is ready. All historical statements are archived and accessible through the portal, eliminating the need to mail paper statements.

No. Payment Hub offers flexible hosting options: self-hosting on your own infrastructure, managed hosting, or third-party cloud providers such as AWS, Azure, or Rackspace. The platform is multi-tenant capable and can be deployed in shared or dedicated environments depending on your security and compliance requirements.

The platform supports a true multi-tenant architecture where multiple client instances can run on shared infrastructure while maintaining complete data isolation. Each tenant gets its own database schema, subdomain, and branding configuration. This makes it cost-effective for partners to host multiple clients from a single infrastructure footprint.

The platform uses a plugin-based architecture built on Phoenix.Core. ERP connectors, payment providers, and feature modules are all implemented as plugins that extend the core platform without modifying it. This means new ERP connectors can be added without rebuilding the base platform, and updates to one plugin don't impact others. Plugins hook into a shared pipeline system for consistent data flow.

ERP connectors use a combination of scheduled sync jobs and real-time event-driven hooks depending on the ERP's capabilities. Data is normalized through a shared data model (EkDB) that maps ERP-specific field formats to a standard schema. Invoice records, customer accounts, and payment postings are all managed through this normalized layer, which then feeds the portal's front-end and the payment processor.

Payment Hub supports a wide range of payment gateways and processors including Stripe, Nuvei, and many others. The payment provider is implemented as a plugin, meaning new gateways can be added without core platform changes. The platform is processor-agnostic by design, giving partners and clients flexibility to select or switch processors based on rates and relationships.

Adding a new payment gateway requires implementing the gateway's API in a new payment plugin. Typical effort ranges from 2–6 weeks depending on the gateway's API quality, documentation, and sandbox testing environment availability. Once a gateway is added as a plugin, it becomes immediately available to all tenants.