Connect Fortis to 25+ ERPs in 48 hours

Fortis, a gateway, Payment Hub makes it a payment platform

Fortis is an excellent embedded-payments gateway: global card acceptance, ACH, tokenization, 3DS2, vault, commercial-card enhanced-data support, a clean OAS-based API. What it is not is an industry-aware payment platform. A nonprofit does not run payments the way a distributor does. A hospital does not run payments the way a university does. A subscription SaaS does not run payments the way a county treasurer does. None of that industry behavior lives inside any gateway, Fortis included. Payment Hub is the layer that takes Fortis's acquiring capacity and turns it into the payment experience each vertical actually needs.

Headquartered in Plano, Texas and founded in 2009, Fortis processes billions of dollars annually and has public backing from Audax Private Equity and Lovell Minnick Partners (joint recapitalization, March 2025). It's a stable, well-capitalized gateway choice, which makes it a good foundation to build an industry-specific payment stack on top of. Payment methods are complete (Visa, Mastercard, Amex, Discover, JCB, UnionPay, ACH), tokenization and 3DS2 are native, and Fortis is publicly CEDP-ready on Visa's Commercial Enhanced Data Program.

Payment Hub consumes the Fortis gateway through the Fortis Platform API and builds on top: a branded self-service customer portal, 25+ ERP connectors, CEDP-ready Level 3 auto-enrichment from ERP line items, Pay-on-Account, tokenized ACH and card wallets, real-time cash application back to the ERP, and industry-specific workflows tuned to how each of eight verticals actually gets paid. Same Fortis MID. Same settlement. Same statement. One negotiated rate structure.

Industries Clarity Payment Hub unlocks on Fortis

Fortis alone is a gateway, excellent at what that means. What it is not is an industry-specific payment platform. A nonprofit, a distributor, a hospital, a university, and a subscription SaaS all need payments to behave very differently, and none of that behavior lives inside the gateway. Payment Hub is the industry-aware layer that takes Fortis's acquiring capacity and shapes it into a payment experience that fits how each vertical actually runs.

How Payment Hub connects Fortis to your ERP

Clarity Connect, the integration engine under Payment Hub, with 15+ years of active development, reads from and writes to your ERP in real time using each platform's supported API layer. Fortis stays in control of authorization, tokenization, settlement, and the card networks. Clarity stays in control of the ERP-side posting and the customer experience.

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 systems (Dynamics GP/NAV, Sage 100/300, SAP ECC, Oracle EBS, SYSPRO, Epicor Prophet 21/Eclipse/Eagle) we use a lightweight outbound-only secure agent that calls from inside your network, no inbound firewall ports to open, no VPN tunnel required.

ERP reach: Fortis native + Payment Hub extension

The clearest way to see the partnership is to map each ERP against who ships the connector. Fortis covers four ERPs natively with first-party plugins. Payment Hub extends the same Fortis gateway account to 21 additional ERPs using Clarity's integration library.

Same Fortis account underneath both paths. Whether a given subsidiary is on NetSuite (Fortis native) or Dynamics GP (Payment Hub connector), the transaction flows through the same Fortis gateway, settles into the same Fortis merchant account, and reports on the same Fortis statement. Level 3 data is captured the same way, tokenization uses the same Fortis vault, and recurring schedules use the same Fortis token.

The portal and AR layer Fortis doesn't ship

This is where Fortis's product ends and Payment Hub's begins. Fortis's strength is embedded payments inside other software. Payment Hub's strength is the customer-facing portal and the AR team's back office.

What the customer sees

A branded payment portal at your domain, invited from your invoice email, your statement, or a signed single-use Quick Pay link. Customers log in and see their full AR picture: open invoices pulled live from the ERP, statements, credit balances, and tokenized wallets for card and ACH (stored in Fortis's vault). They can pay a single invoice, consolidate multiple invoices into one payment, apply credits, pay on account, or enroll in auto-pay, all posted back to the ERP in real time.

What the AR team sees

A clean ERP-native view of applied cash, Fortis-authorized, tokenized, already posted. No end-of-day reconciliation, no spreadsheet matching, no lookups between the gateway report and the AR subledger. The gap between "Fortis confirmed authorization" and "cash applied in the ERP" shrinks from overnight batch to seconds.

What the finance team sees

Level 3 optimization firing on eligible commercial cards, ACH defaulting above a configurable dollar threshold, surcharging or cash-discount running compliantly where elected, and a single pane of glass across every buyer, every ERP, every payment method, all still processed by Fortis, funded through Fortis's merchant account, and governed by the Fortis merchant agreement.

CEDP and Level 3: Fortis is ready, Payment Hub fires the data

Fortis has publicly documented its stance on Visa's Commercial Enhanced Data Program (CEDP), the April 2025 replacement for the old Level 2 / Level 3 interchange structure. The Fortis gateway accepts the enhanced-data fields. The merchant still has to populate them, transaction by transaction. That's where Payment Hub comes in.

What Fortis has publicly said about CEDP

Fortis's own published material frames CEDP as a data-validation regime that replaces the prior Level 2/3 structure. The economics Fortis itself has cited: a 0.05% participation fee applied to eligible B2B transactions submitted with validated enhanced data, and a 7–10% interchange reduction for merchants who consistently submit accurate Level 3 data. Net effect: merchants whose payment flow reliably passes clean Level 3 data come out meaningfully ahead. Merchants who submit incomplete or unvalidated data pay more than they used to.

Where Payment Hub fits

Fortis's gateway accepts the enhanced-data fields as part of the Platform API transaction payload. Someone still has to send those fields on every transaction, and they have to match the invoice of record, or CEDP validation fails. Payment Hub pulls line-item, tax, PO, freight, and customer-code data directly from your ERP at authorization time, no manual entry, no catalog reconciliation, no gateway-level reconstruction. Validation passes on the first try because the data is the invoice.

Security, PCI scope, and enterprise compliance

Fortis is a Level 1 PCI DSS service provider with a PCI-certified vault and tokenization stack. Clarity Payment Hub is built to push your deployment to the lightest possible compliance scope and leave the cardholder-data environment at Fortis where it belongs.

• Tokenization at Fortis. Every card and ACH account is tokenized directly in Fortis's PCI-certified gateway vault. Raw credentials never touch Payment Hub's infrastructure and never touch your servers.
• SAQ A scope for most merchants. Because cardholder data is captured and stored entirely inside Fortis's environment, your PCI self-assessment drops to SAQ A, the lightest tier, with no cardholder-data environment to audit on your side.
• SOC 2 Type II. Clarity Ventures operates to SOC 2 Type II standards. Security, availability, confidentiality, and data-handling controls are independently audited on an ongoing basis.
• 3DS2 &, fraud controls. Fortis-level 3D Secure 2, AVS, CVV, and velocity checks combine with portal-level controls: invoice-bound authentication, customer-matched billing addresses, signed single-use Quick Pay links. Defense profile tuned to B2B invoice fraud rather than consumer card fraud.
• Outbound-only agent for on-premise ERPs. No inbound firewall ports. No VPN tunnel. No public ERP exposure.
• OAS-based API surface. Payment Hub consumes the same Fortis Platform API exposed to Fortis's ISV partners, with the same authentication, the same audit trail, and the same SDK-generated clients.

Related resources