Verticals
Integration
Supported
Use Cases
Timeline
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.
What makes this bigger for an Eclipse house than for most businesses is generations. A single contractor order can produce three or four invoices as lines ship and get picked up on different days. Applying one check across them correctly is the daily tax of running Eclipse AR. Removing it is where the time comes back.
What stays in Eclipse
Eclipse remains the system of record for customers, job accounts, orders, generations, invoices, pricing and cash. Payment Hub does not keep a parallel ledger. It reads through the Eclipse API, takes the payment on a PCI-compliant surface, and writes a cash receipt in the same shape your credit department creates by hand.
Your Eclipse configuration does not change. Branch structure, matrix pricing, job account terms, ship-via rules, Eterm and Solar all stay exactly as they are. Payment Hub adds a payment link to the invoice form you already send and a portal beside Eclipse, not inside it.
The distribution verticals Eclipse serves, all covered by Payment Hub
Epicor positions Eclipse for a tight set of wholesale distribution verticals with contractor-heavy customer bases. Payment Hub works across all of them, and the payment pattern that matters most shifts with the vertical.
& PVF
& MRO
& Utility
Electrical distributors have the most branches and the largest job-account books, so multi-branch routing and statement autopay matter most. Plumbing and PVF houses live at the counter and on will-call, so card-present terminals tied to generations are the feature they notice first. HVAC distributors see strong seasonal spikes and use the portal to keep collections moving when the phones are busy. Waterworks and utility distributors carry very large project invoices and lean on ACH and Level III.
Most Eclipse distributors span two of these, which is why the full feature set is installed and you turn on what your branches use.
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.
| Capability | Epicor Payment Exchange on Eclipse | Payment 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.
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 ArchitectHow Clarity Connect integrates Payment Hub with Epicor Eclipse
The integration runs on Eclipse's API and web services layer, the supported path Epicor provides for third-party applications and uses for Eclipse Web and Eclipse Mobile. Eight capabilities make up the integration, and none of them require Eterm customization or changes to your Eclipse business rules.
Eclipse API integration
Payment Hub reads and writes through Eclipse's supported API: customers and job accounts, sales orders and their generations, invoices and cash receipts. Access is through a dedicated Eclipse integration user, and every call is logged on both sides.
Real-time cash receipts per generation
A payment taken in the portal, on an invoice link or at the counter posts to Eclipse as a cash receipt applied to the generation invoice it settles, at the branch that owns it. Unapplied and on-account payments post with the customer and branch set so credit can apply them without guesswork.
Job-account and generation-aware order-to-cash
Deposits on special-order lines, counter capture on the will-call generation, and portal payment on the delivered generation, each applied to its own invoice. The pattern follows how the Eclipse order is actually fulfilled.
Level III auto-enrichment
Order line detail, including product, quantity, unit price, tax and ship-to, is attached to eligible commercial card transactions so contractor and purchasing cards settle at Level III interchange. Nobody types it in.
Multi-branch routing
Each transaction routes to the merchant account, bank account and GL cash account for the Eclipse branch on the order or invoice. A contractor with jobs served from three branches sees every invoice in one portal, and each payment lands at the right branch.
Tokenized method vault
Cards and bank accounts are tokenized at the gateway and stored against the Eclipse customer, so the counter, the portal and the credit department can reuse a method without card data ever touching Eclipse or your network.
Statement autopay and scheduled payments
Job accounts on statement autopay, installment arrangements on past-due balances and fixed monthly draws for service contracts all run on the scheduler, with dunning on failed attempts and every run posting as a normal cash receipt.
Compatible with EPX, Eclipse Web and your storefront
The integration sits beside Epicor Payment Exchange at the counter, beside Eclipse Web and Eclipse Mobile, and beside your ecommerce storefront. It does not replace any of them. It adds AR-side payment where Eclipse leaves it to the credit department.
The integration workflow, split-generation order to closed job account
A concrete walk-through. A regional electrical distributor with eleven branches on Epicor Eclipse takes a $23,800 order for an electrical contractor's school renovation job: switchgear on a special order with a deposit, wire and conduit for will-call, and fixtures delivered to the site. Payment Hub handles the deposit, the counter payment and the delivered-generation invoice, all posting to Eclipse as cash receipts.
Inside sales enters the job order in Eclipse
The branch rep creates sales order S1042377 in Solar Eclipse for Keystone Electric on their Lincoln High job account: switchgear on a special order requiring a 30 percent deposit, wire and conduit flagged will-call at the Harrisburg branch, and fixtures on a delivered generation to the site.
Eclipse Order EntryJob AccountBranch 07Deposit captured on the special-order switchgear
The rep sends a click-to-pay link for the $3,900 deposit from Eclipse. Keystone's office pays it on a purchasing card. Payment Hub tokenizes the card, attaches Level III detail from the switchgear line, and captures on the Harrisburg branch merchant account.
Click-to-PayLevel IIITokenizedEclipse records the deposit against the order
Payment Hub writes a cash receipt to Eclipse through the API, applied as a deposit on S1042377 at branch 07 and posted to that branch's cash GL. The credit department sees the deposit on the order the moment it lands.
Eclipse APICash ReceiptContractor picks up the will-call generation
Two days later Keystone's foreman picks up the wire and conduit. The counter rep pulls the order, confirms generation 1 is being picked up, and takes $6,100 on the card-present terminal tied to that generation. Generation 1 invoices and the payment applies to it.
Counter SaleGeneration 1Will-CallFixtures deliver to the site
A week later the branch truck delivers the fixtures. Generation 2 invoices for $9,900. The invoice form carries a payment link, so Keystone gets a payment-ready invoice for exactly the fixtures that arrived.
DeliveryGeneration 2Invoice LinkSwitchgear arrives and ships
Three weeks on, the switchgear arrives from the manufacturer and delivers. Generation 3 invoices for $3,900 net of the deposit. Same payment link, same portal, no extra steps for the branch.
Special OrderGeneration 3Contractor pays both open invoices in the portal
Keystone's office manager logs into the portal, sees generations 2 and 3 open under the Lincoln High job with the deposit already applied, and pays both on the saved purchasing card in one transaction. Payment Hub posts two cash receipts, one per generation, at branch 07.
Customer PortalPay-ManyAuto-AppliedJob account is clean, month-end is routine
Every payment on S1042377 exists in Eclipse as a cash receipt against the generation it settled, at the right branch, on the right GL account. The job account shows zero, the processor statement matches branch 07's cash GL, and nobody applied a check by hand.
Month-EndReconciledThe detail worth noticing is the generations. Four invoices came out of one order, three different payment surfaces were used, and Eclipse received four correctly applied cash receipts. That is the specific problem Eclipse distributors have with payments, and it is the one this solves.
Payment Hub use cases on Epicor Eclipse
All 11 Payment Hub use cases run on Eclipse. The ones electrical, plumbing and HVAC distributors deploy first are highlighted here, and each links to the full use-case page.
A payment link on every generation invoice, tokenized, with the cash receipt applied on payment.
At the counterCounter SalesCard-present terminals tied to the generation being picked up, with the receipt posting to the branch.
Contractor-facingSelf-Service Payment PortalA branded portal showing open invoices by job and branch, read live from Eclipse.
Credit departmentAR Collections AutomationStatement autopay, installment plans and dunning on job accounts, all posting as cash receipts.
Multi-branchMulti-Location PaymentsRouting by branch, merchant account and GL cash account across every Eclipse location.
Contractor cardsLevel III Interchange OptimizationOrder line detail on commercial and purchasing cards, so contractor payments settle at Level III rates.
Technical details, for Eclipse administrators and Epicor partners
The engineering reality of the integration, for IT teams, Eclipse system administrators, the people who maintain your Eterm and Solar environments, and Epicor partners evaluating Payment Hub for an Eclipse distributor.
- API layer. Eclipse's API and web services layer, the supported path Epicor provides for third-party applications on Eclipse and uses for Eclipse Web and Eclipse Mobile. Entities used: customers, job accounts, sales orders and generations, invoices and cash receipts. Requires a current Eclipse release with the web services enabled, and Epicor or your partner enables them.
- Authentication. A dedicated Eclipse integration user with access limited to the entities above. Credentials are stored encrypted on Payment Hub's side and rotated on your schedule. Payment Hub never holds an Eterm login.
- Data direction. Reads: customers, job accounts, contacts, open orders and generations, open invoices, branch and company configuration. Writes: cash receipts, deposit applications and payment-method tokens stored as customer attributes. Payment Hub never writes pricing, inventory, order lines or GL entries directly.
- Card data. No cardholder data reaches Eclipse, your network or Payment Hub's application tier. Entry happens on a PCI DSS Level 1 hosted surface at the gateway, and Eclipse receives a token and a reference. Your PCI scope shrinks.
- Branch routing. A configuration map from Eclipse branch to merchant account, bank account and GL cash account. Adding a branch is a configuration change, not a project.
- Customizations. No Eterm macros, Solar customizations, business rule changes or schema changes are installed in your Eclipse environment. Existing customizations, EPX at the counter and third-party integrations continue to operate unchanged.
- Deployment. Works with Eclipse on-premise and with Epicor-hosted Eclipse. The Payment Hub service reaches the Eclipse web services over TLS through your firewall or Epicor's hosted endpoint.
- Timeline. Standard go-live is 48 hours from API access: connect, map branches, add the payment link to your invoice forms, test against your Eclipse test environment, cut over. Portal branding, gateway migration and statement-autopay enrollment are added when you want them.
- Support. Clarity supports the integration and the payment side end to end. Your Epicor partner keeps supporting Eclipse exactly as they do today.
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.
Customers, job accounts, orders, invoices and cash stay in Eclipse as the single source of truth. Works with Eclipse on-premise and Epicor-hosted.
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.
Does it handle job accounts and multiple branches?
Yes. Job accounts, sub-accounts and the branch on each order are read from Eclipse. A contractor with jobs served from several branches sees every open invoice in one portal login, and each payment routes to the merchant account, bank and GL cash account for the branch that owns the invoice.
Will Level III interchange savings apply to our contractor card volume?
Almost certainly. Contractors pay electrical and plumbing distributors on commercial and purchasing cards more than most industries. Payment Hub attaches order line detail to each eligible transaction so it qualifies for Level III rates. The saving is generally 0.5 to 1.0 percent on that volume, applied automatically once enabled.
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.
Can we keep our current gateway and merchant account?
Almost always. Payment Hub connects to 19+ gateways including Worldpay, Adyen, Cybersource, Fortis, PayTrace, Stripe, Braintree and Authorize.Net. If your processor is on the list you keep your rates and your relationship.
What happens at the counter for will-call generations?
The counter terminal is tied to the Eclipse order, so the rep confirms which generation is being picked up and takes payment against it. The generation invoices and the cash receipt applies to it automatically, posting to the branch. No separate terminal batch to match later.
Does the portal read live Eclipse data?
Yes. The portal reads open invoices, credits, deposits and job-account structure directly from Eclipse through the API, so the contractor sees exactly what your credit department sees. Payments post back the same way, and the portal reflects them at once.
How does statement autopay work for job accounts?
A contractor enables autopay in the portal, or your credit team does it for them. On the statement date the open balance is drawn on the saved method and posts to Eclipse as cash receipts against the open invoices. Failed attempts go into dunning with email notice. It is the single most effective thing an Eclipse distributor can do for DSO.
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.
Who supports the integration, Clarity or our Epicor partner?
Clarity supports the integration and the payment side. Your Epicor partner keeps supporting Eclipse exactly as they do today. We work directly with partners during rollout so nobody is guessing about where a question belongs.