Why Prophet 21 distributors add Payment Hub, and what changes when they do
Prophet 21 is very good at the distribution problem: pricing contracts, branch inventory, blanket orders, will-call and delivered lines on the same order. Payment acceptance was never its center of gravity, and the gap shows up in AR every month.
Most P21 distributors we work with run a familiar setup. Counter staff key card numbers into a terminal that has no idea which P21 invoice is being paid. The AR clerk gets a settlement report from the processor and re-keys cash receipts by hand, matching amounts to invoices as best they can. Customers who want to pay online email a card number or call it in. None of this is wrong, exactly. It is just slow, and it puts card data in places it should not be.
Payment Hub replaces that with one flow. A payment starts in P21, or in a portal that reads live P21 data, and the result posts back to P21 as a cash receipt applied to the correct invoice, in the correct branch, against the correct GL cash account. The AR clerk stops re-keying. The counter terminal becomes an extension of order entry. The customer pays from a link on the invoice you already send.
Payment Hub vs native P21 payment, honest side-by-side
Prophet 21 includes credit card processing through Epicor's own payment services and a short list of partnered processors. It handles a card on an order. Payment Hub is the gateway-agnostic option for distributors who need more than that, and it is worth being clear about where the two differ.
| Capability | Native P21 Payment | Payment Hub on P21 |
|---|---|---|
| Gateway / processor choice | ✗ Epicor Payment Exchange or a small set of partnered processors | ✓ 19+ gateways: Worldpay, Adyen, Cybersource, Fortis, PayTrace, Stripe, Braintree, Authorize.Net and more, on your merchant account |
| Customer self-service portal | ✗ Not included. Customers call, email or pay through a separate tool | ✓ Branded portal reading live P21 open items, with pay-many, pay-on-account and saved methods |
| Click-to-pay links on invoices | ✗ Requires a third-party add-on | ✓ Payment link on every P21 invoice format, tokenized, no card data in email |
| Level III line-item data | ✗ Not sent, so B2B card volume settles at higher interchange | ✓ Level III built from oe_line detail on every eligible card transaction |
| Multi-branch merchant routing | ✓ Per-location processing supported | ✓ Routing by branch, merchant ID and GL cash account with one configuration |
| Blanket order and release captures | ✗ Manual re-authorization per release | ✓ Automatic reauthorization and capture as releases ship |
| ACH / eCheck | ✓ Available through select partners | ✓ ACH, eCheck and card on the same portal and the same cash receipt posting |
| Surcharging | ✗ Not available in most configurations | ✓ Compliant surcharging where state law and card brand rules allow, with disclosure handled |
Native processing is the right answer for a single-branch distributor with modest card volume and no interest in a portal. It is included and it works. Distributors move to Payment Hub when they cross into multi-branch operations, want to stop re-keying cash receipts, or start looking at what Level III would save on their B2B card mix. Those three reasons account for most of the P21 conversations we have.
Epicor Prophet 21 payment processing, for industrial distributors
Prophet 21 runs industrial distributors in fasteners, fluid power, HVAC, safety, welding and medical supply, where counter sales, consignment restocks and rush repair-part shipments all land on the same receivables. Integrating Payment Hub with P21 keeps what its built-in processing handles on an order, and adds the invoice side:
- AR automation. Reminders, statement runs and dunning on past-due open items run by branch and by customer, so the credit team works the exceptions instead of every account.
- Cash application and payment reconciliation. Payments post as P21 cash receipts applied to the invoices they settle, and pay-on-account payments land on the customer for credit to apply. Settlements route by branch, merchant ID and GL cash account.
- B2B payments for distribution. Pay-many across open invoices, and automatic reauthorization and capture as each blanket-order release ships, instead of re-keying a card for every release.
- Credit card processing fees and surcharging. P21's native processing doesn't offer surcharging in most configurations. Payment Hub applies a disclosed surcharge where state law and card-brand rules allow it, and never to a debit card.
- Customer payment portal. A branded portal reading live P21 open items, with saved payment methods, so a plant buyer or contractor pays what they owe without calling the branch.
- ACH payments. P21's own ACH runs through a short list of partners. With Payment Hub, ACH and eCheck sit next to cards in the portal and post as ordinary P21 cash receipts.
- Level 2 and Level 3 interchange. Maintenance and plant buyers pay for MRO and safety orders on purchasing cards, so Level III data is built from oe_line detail on every eligible payment.
- Visa CEDP. Visa's CEDP decides whether that Level III data counts. Its April 18, 2026 schedule prices a payment with failed data at the same non-qualified rate as one with none, and the validation rules aren't public, so Payment Hub uses P21's own order lines rather than a one-line summary.
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 Prophet 21 + Payment Hub FAQ
The questions P21 administrators, AR managers, IT teams and Epicor partners ask before adding Payment Hub to a Prophet 21 deployment.
Does Clarity Payment Hub integrate with Epicor Prophet 21?
Yes. Payment Hub integrates with Prophet 21 through the P21 REST API on Epicor's middleware layer, using standard endpoints and token authentication. Invoice payments, order deposits, counter payments, refunds and on-account payments all post to P21 in real time as cash receipts.
How is this different from the payment processing built into P21?
Native P21 processing takes a card on an order through Epicor's payment services. It does not include a customer portal, click-to-pay invoice links, Level III enrichment or gateway choice. Payment Hub adds all four on top of whichever gateway and merchant account you prefer, and it applies every payment to the right invoice and branch automatically.
Which P21 versions and deployments does Payment Hub support?
P21 2019 and later with the middleware (API Server) installed, on-premise or in Epicor's cloud. If you are on an older release without the REST layer, we assess a supported connector path before quoting. Most customers we see are already on a version with the API.
Do we have to install Business Rules or DynaChange changes?
No. The integration lives outside your P21 database and uses only the REST API. Your existing Business Rules, DynaChange rules and customizations stay as they are. That also keeps your P21 upgrade path unchanged.
What is the implementation timeline for P21?
Forty-eight hours from API access is the standard go-live for the core integration: connection, branch mapping, invoice link on your formats, testing in your P21 test company and cutover. Portal branding, gateway migration and recurring-payment setup are added on top when you want them, and none of them delay the core.