Introduction
Ecommerce checkout payment on Clarity Payment Hub is a real shopping cart checkout, not a payment form. It inherits cart, product catalog, shipping and tax, sales orders, invoice payment, returns, and RMAs from the Clarity eCommerce platform, Clarity's own 15-plus-year ecommerce codebase, and it posts a proper sales order to your ERP at checkout. A tokenized customer wallet and digital wallets make repeat online checkout one click for every purchase, commercial-card Level 2/3 data flows from the cart, and the cash receipt lands in your ERP the moment the gateway authorizes. The result is a faster checkout process, less checkout friction for the shopper, and a clean order for your finance team.
The checkout comes with 15-plus years of ecommerce behind it
Most rival products treat checkout as a form, a few fields for card and address bolted onto a template. Clarity Payment Hub's checkout comes from somewhere different: the Clarity eCommerce platform, Clarity's own 15-plus-year ecommerce codebase. That changes what you get.
Clarity eCommerce is the platform Clarity has been building for more than 15 years to run B2B and B2C ecommerce storefronts. It has a shopping cart, a product catalog, customer-specific pricing, shipping and tax engines, sales order processing, invoice payment, returns and RMAs, customer accounts with order history, and a tokenized wallet, all as built-in capabilities. Clarity Payment Hub is built from and on that platform.
In practice, the platform you get from Payment Hub is not a bolt-on widget. It is a real ecommerce checkout, a full online checkout rather than a payment page. The customer sees a cart they can edit, a line-item-aware total with shipping and tax, a tokenized wallet with saved methods, an order review step, and a post-purchase confirmation. Your ERP sees a proper sales order with line items, customer, tax, and shipping, rather than a lump-sum authorization. If you need a full branded storefront with catalog browse, product pages, and a customer portal, Clarity eCommerce is the sibling product that does the whole thing end to end. If you already have a storefront and need the platform, payment, order, and ERP integration piece, Payment Hub is that layer, running on the same architecture.
How Payment Hub handles ecommerce checkout
Eight capabilities run the Payment Hub experience. Each one is inherited from the Clarity eCommerce codebase and integrated with your ERP through Clarity Connect.
Real cart with editable line items
Shoppers add, remove, adjust quantities, apply promo codes, and see running totals. Tax and shipping recalculate on change. The shopping cart persists across sessions for logged-in customers, and ERP pricing rules apply throughout.
Customer-account-aware pricing and terms
B2B buyers see their negotiated pricing, contract rates, and credit terms, pulled from the ERP in real time. Consumer shoppers see standard pricing. The checkout behaves differently for each, automatically.
Shipping and tax calculation
Real-time shipping rates from carriers, or flat and tiered rules you configure, destination-aware tax calculation through Avalara, TaxJar, or ERP-native tax engines, and multi-ship-to address support for B2B drop-ship or multi-site fulfillment.
Tokenized saved-method wallet
Cards and ACH saved to the account tokenize at the gateway's PCI-scoped vault on first use. Repeat shopper checkouts are one click, and raw PAN never touches your servers. For B2B, saved methods are shared across authorized contacts on the customer account.
Sales order creation in the ERP
On checkout, Payment Hub writes a sales order to your ERP with full line items, customer, ship-to, bill-to, tax, shipping, PO reference, and any discounts. The ERP handles fulfillment, and Payment Hub handles the payment and the order handoff.
Commercial-card Level 2/3 from the cart
Cart line items, tax, customer code, PO reference, and shipping flow to the gateway on qualifying commercial-card transactions, qualifying the card for the lowest-tier interchange. An ecommerce cart is the ideal Level 2/3 data source, and Payment Hub uses it natively.
Returns and RMAs
The buyer initiates a return from the account portal, or customer service initiates it on their behalf. Payment Hub validates the return policy, creates the RMA in the ERP, and, once the return is approved and received, processes the refund back to the original tokenized method. Partial returns pro-rate shipping and tax per your rules.
Real-time order and cash posting to the ERP
The sales order, the cash receipt if paid now or the open invoice if charged to account, inventory allocation, and tax records all post to your ERP through Clarity Connect at checkout completion. There is no nightly batch and no reconciliation mystery.
Sales orders, invoices, and returns: same checkout, different transaction type
The reason the Clarity eCommerce lineage matters is that the ecommerce checkout process covers more than cart, card, and receipt. A real ecommerce codebase handles three distinct transaction types natively, and Payment Hub inherits all three.
Sales orders
The customer browses, adds to the cart, and checks out. Payment Hub creates a sales order in the ERP with full line items, customer, ship-to, tax, shipping, and PO reference. Payment may be immediate by card, ACH, or wallet, or charged to account on Net terms, with SKU-level Level 2/3 for commercial cards and real-time sales-order creation in the ERP.
Invoice payment
The customer signs in, sees open invoices, and pays one or many. It is the same checkout engine with a different entry point: the cart is an invoice selection instead of a product selection. Single or consolidated multi-invoice payment, credit-memo application, short-pay with reason codes, Level 2/3 per invoice on commercial cards, and per-invoice cash application to the ERP all flow through the same codebase.
Returns and RMAs
The buyer initiates a return against a prior order, or customer service does it on their behalf. Payment Hub validates against the return policy, creates the RMA in the ERP, and processes the refund to the original tokenized method when the return is received, including partial returns with pro-rated shipping and tax.
The ecommerce checkout workflow: cart to confirmation
A short checkout process lifts conversion rates and cuts cart abandonment. Payment Hub reduces cart abandonment by keeping the checkout flow short: a saved-method wallet, one click checkout, and guest checkout for first-time shoppers. Each checkout page in the checkout flow shows progress, so the checkout experience stays predictable from cart to order confirmation. A returning shopper completes the purchase in one click checkout, with saved payment details on file, and the next purchase is just as fast. The checkout page never asks for payment details twice, which is the single biggest lever on conversion rates and cart abandonment. Here is what happens when a returning B2B buyer places a new ecommerce order. Each step is Payment Hub doing work that would otherwise fall on a separate ecommerce platform, or on a payment widget plus manual ERP entry.
Customer signs in and browses the catalog. The returning shopper signs in with their account credentials. Payment Hub loads their ERP-sourced account: customer-specific pricing, negotiated rates, saved ship-to addresses, tokenized saved methods, credit limit, and Net terms. The product catalog reflects their pricing tier.
The cart builds with real line items. The buyer adds products to the cart, for example Widget Pro times three at the customer-specific price. Payment Hub calculates subtotal, freight, and tax based on the ship-to jurisdiction, and the cart persists across the session if the customer navigates away.
Checkout review: shipping, PO, notes. The buyer selects a ship-to address, from the saved list or a new one, chooses a shipping method by real-time carrier rates or tiered flat rules, adds a PO reference, and optionally a note for fulfillment. Tax recalculates for the chosen ship-to jurisdiction.
Payment method: saved wallet or new entry. The buyer sees the account's tokenized wallet: a saved commercial card and a saved ACH from prior purchases. They select the commercial card, saved, with no re-keying and no PAN exposure, or enter a new card, ACH, or wallet method that Payment Hub tokenizes on the spot.
Review and authorize. The buyer reviews the full order summary, including line items, shipping, tax, total, ship-to, and payment method, and one click authorizes. For Net-terms customers, there is also a charge-to-account option instead of pay-now.
Gateway authorization with Level 2/3 data. Payment Hub submits the card authorization to the gateway with full Level 2/3 data: line items from the cart, tax, customer code, PO reference, and shipping. The commercial card qualifies for the lowest interchange tier. The gateway returns approval, and Payment Hub records the transaction reference.
Sales order and cash receipt post to the ERP. Payment Hub writes two records through Clarity Connect: a sales order with all line items, ship-to, shipping, tax, PO reference, and customer, and a cash-receipt record applied to that order. Inventory allocation follows the ERP's standard rules, and fulfillment is now the ERP's job.
Confirmation email and order detail in the customer portal. The buyer receives a branded order-confirmation email with the order number, line detail, shipping info, and expected delivery. The order also appears in the buyer's order history in the portal, where they can track it, reorder, or initiate a return from the same platform.
Industries where ecommerce checkout matters
The Clarity eCommerce lineage means Payment Hub's checkout is equally comfortable in B2B-heavy verticals such as distribution, manufacturing, and professional services, and B2C-heavy ones such as nonprofit giving and education merchandise. The vertical-specific patterns, including pricing tiers, tax handling, recurring, and terms, all pull from the ERP rather than being hard-coded into Payment Hub.
B2B Distribution and Wholesale
Ecommerce is increasingly the default channel for B2B parts and distribution reordering. The checkout brings customer-specific pricing tiers, a Net-terms charge-to-account option, multi-ship-to and drop-ship, consolidated invoice payment in the same portal, and SKU-level Level 2/3 on commercial cards.
Manufacturing
Aftermarket parts ecommerce, dealer-portal reordering, service-part catalogs, and configured-product sales orders all run here. PO reference and project codes flow from Payment Hub into the ERP for correct cost allocation.
Healthcare and Life Sciences
Medical supply ecommerce, lab and research supply portals, and practice-to-vendor B2B ecommerce all fit, with customer-specific catalog and contract-price visibility and practice-management or ERP posting for purchase tracking.
Nonprofit and Fundraising
Merchandise storefronts, event-ticket sales, sponsorship packages, and donor-gift catalogs all run on the same checkout, which handles the ticket or merchandise purchase alongside a donation by pay-on-account, with fund-accounting GL posting.
Education
School bookstore ecommerce, continuing-ed course catalogs, alumni-merchandise storefronts, and institutional-vendor B2B ecommerce all apply. The customer-account checkout handles family and student accounts, SIS integration, and institutional AR.
Government and Public Sector
Permit, license, and document-request ecommerce, utility-service ordering, citizen-facing merchandise such as park passes and transit cards, and government-supplier B2B ecommerce all run here, with CEDP Level 3 on commercial-card government purchases.
Professional Services and Agencies
Productized service ecommerce, including packaged consulting, fixed-fee offerings, and templated deliverables sold as catalog items, runs on Payment Hub. Project codes and client-accounting lines flow from Payment Hub into the PSA or ERP system.
Subscription, SaaS, and Membership
Plan-selection checkout for new subscribers, add-on and upgrade purchasing for existing members, and physical-merchandise or event-access sales alongside subscriptions all run here, with subscription recurring sitting on top of the same checkout engine.
ERP integration: Payment Hub writes a real sales order
The difference between a real checkout process and a payment widget is what lands in your ERP. The e-commerce checkout process writes a full record, not a deposit. Payment widgets write a single lump-sum cash receipt. Payment Hub writes a proper sales order with line items, ship-to, tax, shipping, and PO, plus the cash receipt or open invoice alongside it. Your ERP sees an ecommerce order, not a mystery deposit.
Inbound from the ERP
The customer record, customer-specific pricing, contract rates, credit limit, Net terms, saved ship-to addresses, product catalog, tax jurisdictions, PO references, historical orders, and open invoices, all pulled in real time.
Outbound to the ERP
Sales orders with full line items, cash receipts if pay-now, open invoices if charge-to-account, credit applications, RMAs, refund records, and tokenized-method references, all written at the moment of the corresponding customer action.
More than 25 ERP connectors
NetSuite, Acumatica, Dynamics 365 BC and F&O, Dynamics GP and NAV, SAP S/4HANA Cloud and ECC, Sage 100, 300, and Intacct, Oracle EBS, Epicor P21, Kinetic, Eclipse, and Eagle, Infor SX.e and CloudSuite, SYSPRO, Workday, Tyler, and more. For cloud ERPs (NetSuite, Acumatica, Dynamics 365 BC, SAP S/4HANA Cloud), Clarity Connect talks directly to the ERP's cloud APIs. For on-premise ERPs, a lightweight outbound-only secure agent calls from inside your network, with no inbound firewall ports, no VPN tunnel, and no public ERP exposure. Multi-warehouse and multi-entity setups route orders to the correct ERP destination based on ship-to, product, or customer routing rules.
Inventory stays with the ERP
Payment Hub does not duplicate inventory management. Orders post to the ERP, and the ERP's standard inventory-allocation, fulfillment, pick-pack-ship, and shipment-confirmation processes take over. Payment Hub just makes sure the order landed correctly.
Security, PCI scope, and ecommerce-grade fraud controls
The ecommerce checkout process carries a specific risk profile: card-not-present transactions, first-time shoppers, guest checkout, and reshipment fraud patterns. Fraud detection and fraud protection run inside the checkout flow without slowing the checkout experience. Payment Hub's Clarity eCommerce heritage brings matching controls alongside the lightest available PCI scope.
Every card and ACH saved to the customer wallet tokenizes at the gateway's PCI-scoped vault on first use. Raw PAN and raw bank credentials never touch Payment Hub's infrastructure and never touch your servers. Because cardholder data is captured and stored entirely inside the gateway's environment through hosted fields or a tokenization SDK, your PCI self-assessment drops to SAQ A, the lightest self-assessment available.
Where your gateway supports it, and most do, Payment Hub triggers 3-D Secure 2 step-up authentication on risk-flagged checkout attempts, transferring chargeback liability to the issuer and meeting PSD2 SCA requirements for EU customers. Address-verification service and CVV match flow on every card-not-present transaction, and mismatches route to your risk queue per your rules. Configurable daily, weekly, and account-level transaction caps, dollar thresholds per customer, and new-customer velocity rules slow down account-takeover and stolen-card attempts. Non-account guest checkouts carry tighter fraud rules, including first-transaction dollar caps, required 3-D Secure 2, and mismatch handling, since there is no customer history to lean on.
Clarity Ventures operates to SOC 2 Type II standards, with security, availability, confidentiality, and data-handling controls independently audited on an ongoing basis. For on-premise ERPs, the outbound-only agent means no inbound firewall ports, no VPN tunnel, and no public ERP exposure.
Frequently Asked Questions
Is Payment Hub a full ecommerce platform or a payment widget?
Payment Hub is built from and on the Clarity eCommerce platform, with more than 15 years of production ecommerce architecture. That means Payment Hub is a real checkout, not a bolt-on widget tacked onto a template. Cart, product catalog awareness, shipping and tax calculation, multi-currency, sales order creation, invoice payment, returns and RMAs, customer accounts with order history, and saved tokenized payment methods are all inherited directly from the Clarity eCommerce codebase. If you also want a full branded ecommerce storefront with catalog browse and product pages, Clarity eCommerce is the product that does that end to end, and Payment Hub handles Payment Hub, payment, and ERP portion of the same architecture.
Does it handle B2B and B2C ecommerce, or only one?
Both. B2B ecommerce brings customer-specific pricing, Net terms, PO reference tracking, commercial-card Level 2/3 data enrichment, multi-ship-to addresses, and sometimes approval workflows. B2C ecommerce brings guest checkout, one-time payment, consumer digital wallets such as Apple Pay, Google Pay, and PayPal, plus other digital wallets, and simpler tax and shipping models. Clarity Payment Hub's checkout handles both patterns, because the Clarity eCommerce lineage was architected for B2B first, with full B2C support, rather than the other way around. It is the same codebase and the same ERP integration with different defaults per customer segment.
Does the sales order post to our ERP in real time?
Yes. When a customer completes checkout, Payment Hub writes a sales order to your ERP through Clarity Connect with correct line items, customer account, ship-to address, tax, shipping, and any PO reference. The cash receipt, if paid at checkout, or the open invoice, if charged to account on Net terms, is written alongside the order. Inventory allocation follows your ERP's standard logic, because Payment Hub does not duplicate inventory management; it writes the order and lets your ERP handle the fulfillment side.
How does it handle returns and RMAs?
Returns and RMAs are part of the Clarity eCommerce platform and flow through Payment Hub natively. The customer initiates a return from the portal, or customer service initiates it on their behalf, Payment Hub validates the return policy, creates the RMA in your ERP, and, once the return is approved and received, processes the refund back to the original tokenized method. If the original payment was card-present or tokenized card, the refund goes to the same card; if ACH, the refund goes to the same bank account. For partial returns, Payment Hub handles the pro-rated refund including shipping and tax adjustments per your rules.
Does Payment Hub support saved payment methods for repeat customers?
Yes, and this is one of the most-used features of the Clarity eCommerce checkout. Customers save a card or ACH to a tokenized wallet on first purchase, and on subsequent visits the wallet appears at checkout for the returning shopper with one-click re-use on the next purchase. Tokens live at the gateway's PCI vault, not on your servers. For B2B customers, saved methods are shared across authorized contacts on the same account, so any buyer on the account can charge the same saved method, and customers can manage their wallet from the account portal to add, remove, or set a default.
Does commercial-card Level 2/3 data enrichment work in ecommerce checkout?
Yes. When a B2B customer pays with a qualifying commercial card at ecommerce checkout, Payment Hub pulls the SKU-level line items from the cart plus tax, customer code, and PO reference from your ERP, and passes all of it to the gateway on the transaction. This qualifies the card for the lowest Level 2/3 interchange tiers, commonly saving 0.5 to 1.0 percent per transaction. An ecommerce cart is the ideal Level 2/3 data source because the line-item, tax, and shipping fields are already structured at checkout. It works across Worldpay, Cybersource, Fortis, PayTrace, Stripe, Braintree, Authorize.Net, Global Payments, and other supported gateways.
Can we pair ecommerce checkout with invoice payment on the same site?
Yes, and most Clarity deployments do exactly this. A B2B customer signs in to pay an open invoice and places a new ecommerce order in the same session. Payment Hub uses one set of saved methods, one customer record, and one ERP integration. Orders post as new sales orders to the ERP, invoice payments post as cash receipts against open invoices, and both run on the same platform in the same branded storefront, so customers do not switch between a store and a payment portal.