Fraud Blocker Epicor Eclipse Payment Processing | Clarity Payment Hub
Clarity Payment Hub™/Integration

Epicor Eclipse payment processing, branch-level payment automation for electrical, plumbing and HVAC distributors

Use Clarity Payment Hub for Epicor Eclipse payment processing and post job-account invoices, counter will-calls and portal payments to Eclipse as cash receipts against the right generation, at the right branch, on the gateway you choose.

Why Eclipse distributors add Payment Hub, and what changes when they do

Eclipse is exceptionally good at the electrical and plumbing distribution problem: branch inventory, job accounts, order generations, will-call and delivered lines on the same ticket. Payment acceptance was bolted on later, and it shows at the counter and in the AR office.

The Eclipse distributors we work with tend to run the same way. Contractors buy on job accounts and pay by statement, which means checks, a lot of them, matched by hand. Counter sales on a card go through an EPX terminal that knows the order but not much else. Anyone who wants to pay online calls the branch or emails a card number to the credit department. The AR team spends the first week of every month applying cash and the rest of it chasing the balance.

Payment Hub connects those pieces. A contractor pays a job invoice from a link, or logs into a portal that shows every open invoice across the branches they buy from, or pays at the counter on a terminal tied to the generation being picked up. Each payment posts to Eclipse as a cash receipt applied to the right generation invoice, at the right branch, on the right GL account. The credit department reviews instead of keys.

Payment Hub vs Epicor Payment Exchange on Eclipse, honest side-by-side

Epicor Payment Exchange integrates with Eclipse at the counter and on orders, and for card-present sales it does the job. Payment Hub is about everything after the counter: invoices, statements, portals and the cash application behind them. Many distributors run both.

CapabilityEpicor Payment Exchange on EclipsePayment Hub on Eclipse
Gateway / processor choice✗ Epicor is the processor✓ 19+ gateways on your merchant account: Worldpay, Adyen, Cybersource, Fortis, PayTrace, Stripe, Braintree, Authorize.Net and more
Counter card present✓ Strong: integrated at the counter with receipt✓ Supported, and most distributors keep EPX at the counter and use Payment Hub for AR
Customer self-service portal✗ Not included✓ Branded portal showing open invoices by job and branch, read live from Eclipse
Click-to-pay links on invoices✗ Not included✓ Payment link on every Eclipse invoice form, tokenized, with the cash receipt applied on payment
Per-generation cash application✗ Manual in cash receipts✓ Each payment applies to the generation invoice it settles automatically
Statement autopay and ACH✗ Card-focused, no autopay✓ Statement autopay, installments, ACH and eCheck on one portal, all posting as cash receipts
Level III line-item data✗ Not sent✓ Order line detail attached to eligible commercial card transactions
Multi-branch routing✓ Per-branch processing✓ One configuration mapping each branch to merchant account, bank and GL

The fair summary is that EPX is a counter solution and Payment Hub is an AR solution. A distributor with two branches and a small job-account book can live on EPX alone. Distributors add Payment Hub when cash application across generations eats the credit department's month, when contractors ask to pay online, or when someone finally looks at what Level III would save on the contractor card mix.

Epicor Eclipse payment processing, built around job accounts, generations and branches

Electrical, plumbing, HVAC and PVF distributors on Eclipse sell to contractors on job accounts, from several branches, on orders that ship in generations. Integrating Payment Hub with Epicor Eclipse keeps everything Eclipse and Epicor Payment Exchange already do at the counter, and adds the receivables side of that business:

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 Architect

Epicor Eclipse + Payment Hub FAQ

The questions Eclipse administrators, credit managers, IT teams and Epicor partners ask before adding Payment Hub to an Eclipse deployment.

Does Clarity Payment Hub integrate with Epicor Eclipse?

Yes. Payment Hub integrates with Epicor Eclipse through Eclipse's API and web services layer. Invoice payments, deposits, counter payments, portal payments and refunds all post to Eclipse in real time as cash receipts applied to the generation invoice they settle, at the branch that owns it.

We use Epicor Payment Exchange at the counter. Do we have to replace it?

No. Most Eclipse distributors keep EPX at the counter and add Payment Hub for AR: the portal, invoice links, statement autopay and ACH. The two coexist. If you want one processor everywhere later, Payment Hub can drive counter terminals too.

How does Payment Hub handle order generations?

Each generation invoices on its own in Eclipse, and Payment Hub applies each payment to the specific generation invoice it settles. A contractor who pays two open generations in the portal produces two cash receipts, one per invoice. This is the part that removes the most manual work from an Eclipse credit department.

Do we need Eterm macros or Solar customizations?

No. The integration lives outside Eclipse and uses only the supported API. Your Eterm environment, Solar customizations and business rules stay exactly as they are, and your Eclipse upgrade path is unchanged.

What is the implementation timeline for Eclipse?

Forty-eight hours from API access is the standard go-live for the core integration: connection, branch mapping, invoice link on your forms, testing in your Eclipse test environment and cutover. Portal branding, gateway migration and autopay enrollment are added on top without delaying the core.

Related resources

Branch-level payment automation on Epicor Eclipse.

Book a 30-minute walkthrough and see Payment Hub running against your own Eclipse test environment: API integration, a deposit on a special-order line, a counter payment tied to a will-call generation, a portal payment across two delivered generations, cash receipts posting per generation and per branch in real time, and Level III enrichment from order lines. Live in 48 hours. Your Eclipse license, Eterm, Solar, EPX counter terminals and customizations stay intact.

EPICOR ECLIPSE + PAYMENT HUB · AT A GLANCE Distribution verticals 5 Integration method Eclipse API Eterm / Solar changes None required Deployment models On-prem + Epicor-hosted Gateways supported 19+ BRANCH-LEVEL · GATEWAY AGNOSTIC
5Dist. Verticals
19+Gateways
48hrGo-Live