Segments
Services
Supported
Use Cases
Timeline
Why Eagle dealers add Payment Hub, and what changes when they do
Epicor Eagle is a point-of-sale system first and an accounting system second, and for the retail counter that is exactly right. The part of an Eagle business that struggles is the other half: the contractor and commercial customers who buy on account and pay by statement.
Walk into the office of a three-store lumber and hardware dealer on Eagle and the pattern is the same. Statements go out at month end. Contractors mail checks, drop them at the counter, or call in a card that someone keys into a virtual terminal or an EPX register as an ROA. The bookkeeper matches what came in against the statement, applies it to invoices in Eagle, and chases the ones that do not add up. Autopay does not exist. Online payment means an email with a card number in it.
Payment Hub gives the house-account side the same convenience the retail counter already has. The contractor gets a statement with a payment link, or logs into a portal that shows every open invoice across the stores they buy from, and pays by card or ACH. The payment posts to Eagle as an ROA applied to the invoices they chose, at the store that owns them. The bookkeeper reviews a list instead of building one.
This is worth more to an Eagle dealer than it sounds because house accounts are where the margin and the risk both sit. A contractor account carrying $40,000 sixty days out is a real problem for a business that size. Making it easy to pay, and easy to pay on time by schedule, is the most direct thing a dealer can do about days sales outstanding.
What stays in Eagle
Eagle remains the system of record for customers, house accounts, invoices, statements, inventory and the general ledger. Payment Hub reads what it needs through Epicor's Eagle integration services and writes ROA transactions in the same shape your office would key by hand. Aging reports and statements look the same, with fewer open items.
Nothing at the register changes. Your POS, EPX terminals, loyalty, signature capture and end-of-day close all run as they do today. Payment Hub is for the account side, and it sits beside Eagle rather than inside it.
The independent retail segments Eagle serves, all covered by Payment Hub
Epicor Eagle is built for independent retailers in a specific set of segments, most of them with a strong contractor or commercial account business alongside walk-in retail. Payment Hub works across all of them, and which features matter most shifts with the segment.
& Home Center
Building Materials
Decorating
& Farm
& Auto Parts
& Specialty
Co-op Members
Lumber and building materials dealers get the most from statement payment and autopay, because their contractor accounts are large and slow. Hardware and home centers with smaller commercial accounts use the portal and invoice links to stop chasing small balances. Pharmacies use the recurring side for institutional and long-term-care accounts. Members of co-ops such as Ace, True Value and Do it Best usually run Eagle across several stores and need the multi-store routing from day one.
Because a dealer often spans two of these, the full feature set is installed and you enable what your office uses.
Payment Hub vs Epicor Payment Exchange, honest side-by-side
Epicor Payment Exchange is Epicor's own processing, integrated with Eagle at the register, and for the retail counter it is a good fit. Payment Hub is about the account side of the business, and many dealers run both. Here is where they differ.
| Capability | Epicor Payment Exchange on Eagle | Payment Hub on Eagle |
|---|---|---|
| Gateway / processor choice | ✗ Epicor is the processor | ✓ 19+ gateways on your merchant account: Worldpay, Adyen, Cybersource, Fortis, PayTrace, Stripe, Braintree, Authorize.Net and more |
| Point-of-sale card present | ✓ Strong: integrated at the register with signature and receipt | ✓ Supported, and most dealers keep EPX at the register and use Payment Hub for accounts |
| Customer self-service portal | ✗ Not included | ✓ Branded portal showing open invoices and statement balances from Eagle, across stores |
| Statement and invoice payment links | ✗ Not included | ✓ Payment link on statements and invoices, tokenized, with the ROA posted on payment |
| Statement autopay and scheduled payments | ✗ Not included | ✓ Autopay on statement date, installment plans, dunning on failed attempts |
| ACH / eCheck for house accounts | ✗ Card-focused | ✓ ACH, eCheck and card on one portal, all posting as ROA |
| Level III line-item data | ✗ Not sent | ✓ Invoice line detail attached to eligible commercial card transactions |
| Multi-store account routing | ✓ Per-store processing | ✓ One configuration mapping each store to its merchant account, bank and GL |
The honest summary: EPX is the better register solution and Payment Hub is the better account solution. A single-store dealer with a small house-account book can live on EPX alone. Dealers move to Payment Hub for the account side when statement collections become a weekly chore, when contractors ask to pay online, or when a second store makes the manual process twice as hard.
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 Eagle
The integration runs on Epicor's Eagle integration API and web services, the same services Epicor uses for its own Eagle Mobile and ecommerce products. Eight capabilities make up the integration, and none of them touch your registers or your end-of-day process.
Eagle integration API
Payment Hub reads and writes through Epicor's supported Eagle integration services: customers and house accounts, open invoices, statement balances and ROA transactions. Access is through a dedicated Eagle integration user and logged on both sides.
Real-time ROA posting
A payment taken in the portal, on a statement link or by phone posts to Eagle as a Received On Account applied to the invoices the customer chose, at the store that owns the account. The office sees it in Eagle the moment it lands.
Statement-aware collections
Payment Hub understands Eagle statements: a customer can pay the statement balance, pick individual invoices, or pay on account and let Eagle apply by age. Statement autopay runs on the statement date and posts the ROA the same way.
Level III auto-enrichment
Invoice line detail, including SKU, quantity, unit price and tax, is attached to eligible commercial card transactions so contractor and purchasing cards settle at Level III interchange. Nobody types it in.
Multi-store routing
Each transaction routes to the merchant account, bank account and GL cash account for the store that owns the account or invoice. A contractor with accounts at two of your stores sees both in one portal, and each payment lands in the right store.
Tokenized method vault
Cards and bank accounts are tokenized at the gateway and stored against the Eagle customer, so autopay, portal payments and phone payments never expose card data to Eagle, your store network or your staff.
Autopay and scheduled payments
Contractor accounts on statement autopay, institutional pharmacy accounts on a monthly draw, and installment arrangements on past-due balances all run on the scheduler, with dunning on failed attempts and every run posting as a normal ROA.
Compatible with EPX, Eagle Mobile and your ecommerce
The integration sits beside Epicor Payment Exchange at the register and beside Eagle Mobile and your ecommerce storefront. It does not replace any of them. It adds account-side payment where Eagle leaves it to the office.
The integration workflow, contractor statement to posted ROA
A concrete walk-through. A three-store lumber and hardware dealer on Epicor Eagle, a co-op member, carries a house account for a framing contractor who buys at two of the stores. Month-end statement is $6,214 across three invoices. Payment Hub handles the statement payment, a mid-month special order deposit and the cash application, all posting to Eagle as ROA.
Contractor buys on account at two stores
During August, Ridgeline Framing picks up lumber and hardware on their house account at the North store and a special-order window package at the Main store. Eagle invoices each sale to the account at the store where it happened: two invoices at North, one at Main. Nothing changes here.
Eagle POSHouse AccountStores 01 + 02Deposit on the special-order window package
The Main store requires a 50 percent deposit on special orders. The counter sends a click-to-pay link for $2,150 from the order. The contractor's office pays it on a company card. Payment Hub tokenizes the card and captures on the Main store merchant account.
Click-to-PaySpecial OrderTokenizedEagle records the deposit as ROA
Payment Hub writes an ROA to Eagle through the integration API, applied as a deposit on the special-order invoice at the Main store, posted to the Main store cash GL. The office sees it on the account immediately.
Eagle APIROAStore 02Month-end statement goes out with a payment link
On August 31 Eagle generates statements. Ridgeline's statement shows three open invoices totaling $6,214 net of the deposit, and it carries a Payment Hub link. The contractor gets a statement they can pay from their phone.
StatementPayment LinkContractor pays the statement in the portal
Ridgeline's office manager opens the portal, sees all three invoices across both stores, and pays the full statement on the saved card. Level III detail from the invoice lines is attached. The portal marks the invoices paid.
Customer PortalSaved MethodLevel IIIROA posts to each store
Payment Hub posts two ROA transactions to Eagle: one at North applied to the two North invoices, one at Main applied to the window invoice. Each hits the right store's cash GL. The account balance goes to zero in Eagle.
Auto-AppliedBalance 0Contractor turns on statement autopay
While in the portal, the office manager enables autopay on the statement date. From September on, the statement balance is drawn on the saved card automatically and posts as ROA, with an email confirmation each time. The dealer stops chasing this account.
AutopayScheduledMonth-end is a review, not a reconstruction
Every payment exists in Eagle as an ROA against the right invoices at the right store. The processor statements match each store's cash GL. The bookkeeper reviews exceptions and the aging report is accurate without a reconciliation pass.
Month-EndReconciledThe detail worth noticing is the two-store payment. In most Eagle offices a contractor who buys at two stores gets two statements and sends one check, and someone has to split it. Here the customer paid once, and Eagle received two correctly applied ROAs.
Payment Hub use cases on Epicor Eagle
All 11 Payment Hub use cases run on Eagle. The ones independent retailers deploy first are highlighted here, and each links to the full use-case page.
Statement payment links, autopay on statement date, and dunning on past-due balances, all posting as ROA.
Contractor-facingSelf-Service Payment PortalA branded portal showing open invoices and statement balances across every store the customer buys from.
StatementsConsolidated Invoice PaymentPay the statement, pick invoices, or pay on account and let Eagle apply by age.
At the registerCounter SalesCard-present payment on special orders and layaways tied to the Eagle transaction.
Multi-storeMulti-Location PaymentsRouting by store, merchant account and GL cash account across every Eagle location.
Contractor cardsLevel III Interchange OptimizationInvoice line detail on commercial and purchasing cards, so contractor payments settle at Level III rates.
Technical details, for Eagle administrators and Epicor partners
The engineering reality of the integration, for the owner or office manager who administers Eagle, the IT provider who supports the store network, and Epicor partners evaluating Payment Hub for an Eagle dealer.
- API layer. Epicor's Eagle integration API and web services, the supported path Epicor provides for third-party applications on Eagle and uses for its own Eagle Mobile and ecommerce products. Entities used: customers and house accounts, invoices, statements and ROA transactions. Requires a current Eagle release with the integration services enabled, and Epicor or your partner enables them.
- Authentication. A dedicated Eagle integration user with access limited to the entities above. Credentials are stored encrypted on Payment Hub's side and rotated on your schedule.
- Data direction. Reads: customers, house accounts, contacts, open invoices, statement balances and store configuration. Writes: ROA transactions and payment-method tokens stored as customer attributes. Payment Hub never writes items, prices, invoices or GL entries directly.
- Card data. No cardholder data reaches Eagle, your store server, your network or Payment Hub's application tier. Entry happens on a PCI DSS Level 1 hosted surface at the gateway, and Eagle receives a token and a reference. Your PCI scope for the account side shrinks.
- Multi-store routing. A configuration map from Eagle store to merchant account, bank account and GL cash account. Adding a store is a configuration change.
- Registers and EPX. Nothing at the point of sale changes. Epicor Payment Exchange, signature capture, receipts and end-of-day close continue as they are. Payment Hub can also drive card-present terminals for special orders and layaways if you want it to.
- Deployment. Works with Eagle on a store server and with Epicor-hosted Eagle. The Payment Hub service reaches the Eagle integration services over TLS through your firewall or Epicor's hosted endpoint.
- Timeline. Standard go-live is 48 hours from API access: connect, map stores, add the payment link to your statement and invoice formats, test against your Eagle test environment, cut over. Portal branding, gateway migration and autopay enrollment campaigns are added when you want them.
- Support. Clarity supports the integration and the payment side. Your Epicor partner and your co-op's Eagle resources keep supporting Eagle exactly as they do today.
Epicor Eagle + Payment Hub FAQ
The questions Eagle dealers, office managers, IT providers and Epicor partners ask before adding Payment Hub to an Eagle store or a multi-store group.
Does Clarity Payment Hub integrate with Epicor Eagle?
Yes. Payment Hub integrates with Epicor Eagle through Epicor's Eagle integration API and web services. Statement payments, invoice payments, special-order deposits, portal payments and refunds all post to Eagle in real time as ROA transactions applied to the right invoices at the right store.
Customers, house accounts, invoices, statements and the general ledger stay in Eagle as the single source of truth.
We use Epicor Payment Exchange at the registers. Do we have to replace it?
No. Most dealers keep EPX at the point of sale and add Payment Hub for the house-account side: portal, statement links, autopay and ACH. The two coexist. If you would rather consolidate onto one processor later, Payment Hub can drive card-present terminals too.
How does Payment Hub handle statements?
Statements carry a payment link, and the portal shows the statement balance and every open invoice behind it. The customer can pay the statement, pick specific invoices, or pay on account. Statement autopay draws the balance on the statement date. Every option posts to Eagle as an ROA applied the way the customer chose.
We have three stores and contractors who buy at more than one. Does that work?
Yes, and it is one of the main reasons multi-store dealers choose Payment Hub. A customer sees all their invoices across stores in one portal login and pays once. Payment Hub posts a separate ROA to each store, applied to that store's invoices and hitting that store's cash GL.
Does Payment Hub post ROA transactions or something else?
ROA. Payments post to Eagle as Received On Account applied to specific invoices, or unapplied on the account when the customer pays on account, which is exactly what your office would key by hand. Aging and statements reflect the payment the same way.
Can we keep our current merchant account for the account side?
Almost always. Payment Hub connects to Worldpay, Adyen, Cybersource, Fortis, PayTrace, Stripe, Braintree, Authorize.Net and more. If your processor is on the list you keep your rates. If you want to change processors later, the integration does not change.
Will Level III savings apply to a hardware or lumber dealer?
It applies to the share of your card volume that comes from commercial and purchasing cards, which for a dealer with a real contractor book is meaningful. Payment Hub attaches invoice line detail to those transactions so they settle at Level III rates, typically 0.5 to 1.0 percent lower. Walk-in consumer cards are unaffected.
Does this change anything about end-of-day at the registers?
No. Register close, EPX settlement and your end-of-day process run exactly as they do now. Payment Hub payments are account-side ROA transactions, and they reconcile against the gateway settlement for the account-side merchant account, separate from register batches.
What about ACH for contractor accounts?
ACH and eCheck run on the same portal and statement links as cards, and post to Eagle as ROA with the bank payment method. Many dealers encourage ACH for larger contractor balances and let the customer choose at payment time.
Does it work with Epicor-hosted Eagle?
Yes. Eagle on a store server and Epicor-hosted Eagle both work. The integration reaches Eagle's integration services over TLS through your firewall or Epicor's hosted endpoint, and Epicor or your partner enables the services on your system.
What is the implementation timeline for Eagle?
Forty-eight hours from API access is the standard go-live for the core integration: connection, store mapping, payment link on your statement and invoice formats, testing in your Eagle test environment and cutover. Portal branding, gateway migration and an autopay enrollment push for your contractor accounts are added on top.
Who supports the integration, Clarity or our Epicor partner?
Clarity supports the integration and the payment side. Your Epicor partner, and your co-op's Eagle support if you are a member, keep supporting Eagle as they do today. We work with them during rollout so nobody is guessing about where a question belongs.