Why manufacturers on ERP 9 and ERP 10 add Payment Hub, and why now rather than after the upgrade
The most common objection we hear from an E10 shop is reasonable: we are moving to Kinetic in eighteen months, so why touch payments now? The answer is that the integration does not change when you upgrade, and the eighteen months of manual cash application do not come back.
Manufacturers on ERP 9 or ERP 10 run a familiar process. Sales orders with deposits get a card number keyed into a virtual terminal. Invoices go out with remit-to instructions. Customers mail checks or set up their own ACH, and a few call in cards. The AR team gets a processor report and creates cash receipts by hand, matching amounts to ARInvoice records. When an order ships in releases, the deposit and the balance captures rarely line up without someone reconciling them.
Payment Hub replaces that with one flow that posts to your Epicor AR. A customer pays a deposit from a link, pays an invoice from the portal, or the AR team takes a card by phone, and the result lands in Epicor as a CashHead and CashDtl applied to the invoice, in the right company and site. On E10 that happens through Epicor's REST services. On E9 it happens through Service Connect. Either way the AR clerk reviews rather than keys.
Payment Hub vs native Epicor payment on E9/E10, honest side-by-side
ERP 9 and ERP 10 include credit card processing through a small set of partnered gateways, and it handles a card on an order. Payment Hub is the gateway-agnostic option for manufacturers who need more than that, and the differences are worth being clear about.
| Capability | Native E9/E10 Payment | Payment Hub on E9/E10 |
|---|---|---|
| Gateway / processor choice | ✗ Limited to Epicor's partnered gateways for that release | ✓ 19+ gateways: Worldpay, Adyen, Cybersource, Fortis, PayTrace, Stripe, Braintree, Authorize.Net and more, on your merchant account |
| Customer self-service portal | ✗ Not included | ✓ Branded portal reading live ARInvoice data, with pay-many, pay-on-account and saved methods |
| Click-to-pay links on invoices | ✗ Requires customization | ✓ Payment link on every invoice form, tokenized, no card data in email |
| Deposits and per-release captures | ✗ Manual reauthorization per release | ✓ Deposit at order entry, automatic reauthorization and capture as each OrderRel ships |
| Level III line-item data | ✗ Not sent | ✓ Level III built from OrderDtl on every eligible card transaction |
| Multi-company / multi-site routing | ✓ Per-company processing supported | ✓ Routing by company, site, merchant account and GL cash account from one configuration |
| Carry-over to Kinetic | ✗ Native processing must be re-implemented against Kinetic's supported gateways | ✓ The E10 integration moves to Kinetic as part of the upgrade, with tokens and configuration intact |
| ACH / eCheck | ✓ Available through select partners | ✓ ACH, eCheck and card on the same portal and the same cash receipt posting |
Native processing is a reasonable answer for a single-company shop with modest card volume and no portal ambitions. Manufacturers move to Payment Hub when they want to stop re-keying cash receipts, when customers ask to pay online, when release-based captures become a monthly reconciliation problem, or when they realize the Kinetic upgrade will otherwise mean rebuilding payments. The last one is the reason this page exists.
Epicor E10 payment processing, and a clean path to Kinetic
Plenty of machinery builders, fabricators and electronics makers still run Epicor ERP 9 or ERP 10 while they plan a move to Kinetic, which Epicor is steering toward its cloud. Integrating Payment Hub with E9 or E10 keeps the card processing your release already has, adds the receivables side, and comes with you when you upgrade:
- AR automation. Reminders, statement runs and dunning on overdue ARInvoice balances run on a schedule for each company and site. Every payment posts as a CashHead receipt, so AR keeps working from the screens it uses today.
- Cash application and payment reconciliation. A payment applies to the ARInvoice it settles, so a make-to-order job billed across several releases closes release by release. Settlements route to the GL cash account for the company and site that owns the invoice.
- B2B payments for make-to-order work. A deposit taken at order entry, then automatic reauthorization and capture as each OrderRel ships, so a long-lead job isn't riding on a card authorization that expired weeks ago.
- Credit card processing fees and surcharging. Where state law and card-network rules allow it, Payment Hub applies a disclosed surcharge to credit card payments and posts it to Epicor as its own line. Debit cards are never surcharged.
- Customer payment portal. A branded portal reading live ARInvoice data, with pay-many, pay-on-account and saved payment methods, so a customer's AP team settles what it owes without calling yours.
- ACH payments. Out of the box, E9 and E10 offer ACH only through select partners. Customers paying big invoices by bank get ACH and eCheck on the Payment Hub portal, and each one lands as a CashHead receipt, same as a card.
- Level 2 and Level 3 interchange. OEM and maintenance buyers often pay on purchasing and commercial cards, so Payment Hub builds Level III line-item data from OrderDtl for every eligible card payment.
- Visa CEDP. Since April 18, 2026, Visa's commercial card schedule has charged a payment whose enhanced data fails validation exactly what it charges one with no data at all, and the network keeps its validation rules private. Epicor unit prices run to four or more decimals, so the lines are taken from OrderDtl as they stand, on ERP 9, ERP 10 and later on Kinetic.
The Missing LinkBetween Paymentsand Your ERP
Clarity Payment Hub closes that gap, connecting your orders, invoices, and payment channels into one flow.
Speak to a Platform ArchitectEpicor ERP 9 / ERP 10 + Payment Hub FAQ
The questions Epicor administrators, AR managers, IT teams and Epicor partners ask before adding Payment Hub to an ERP 9 or ERP 10 deployment.
Does Clarity Payment Hub integrate with Epicor ERP 9 and ERP 10?
Yes, both. On ERP 10 the integration uses Epicor's REST services and OData. On ERP 9 it uses Epicor Service Connect and the business-object services. Deposits, invoice payments, portal payments, refunds and on-account payments all post to Epicor in real time as CashHead / CashDtl records applied to the right invoice.
We are upgrading to Kinetic next year. Should we wait?
No, and this is the most common question we get on E10. Kinetic is the continuation of ERP 10 with the same tables and the same REST services. The integration you build on E10 today is the integration you run on Kinetic, and your configuration, portal and stored tokens carry over as part of the upgrade cutover. Waiting only postpones the benefit and adds payments to the upgrade's scope.
How is this different from the payment processing built into Epicor?
Native processing on E9 and E10 takes a card on an order through a small set of partnered gateways. It does not include a customer portal, click-to-pay invoice links, automatic per-release captures or Level III enrichment, and it does not carry over to Kinetic. Payment Hub adds all of that on whichever gateway you prefer.
Do we have to install BPM directives or customizations?
No. The integration lives outside your Epicor database and uses only the REST services or Service Connect. Your existing BPMs, customizations and workflows stay as they are, and nothing about the integration complicates your Kinetic upgrade.
What is the implementation timeline?
Forty-eight hours from REST or Service Connect access is the standard go-live for the core integration: connection, company and site mapping, invoice link on your forms, testing in your Epicor test company and cutover. Portal branding, gateway migration and recurring setup are added on top. The Kinetic carry-over happens inside your upgrade cutover rather than as a separate project.