The right integration for a sunsetting ERP
Use Clarity Payment Hub for Dynamics GP payment processing and add a customer portal, real-time cash application and a choice of 19+ gateways while you still run GP.
When you migrate, the payment layer stays and only its ERP connector changes.
Payment Hub's multi-integration and upgradeable platform is designed to avoid that trap. It integrates with GP today through the standard integration stack (eConnect, Web Services for Microsoft Dynamics GP, and Integration Manager), and it integrates with every major migration destination too, including Business Central, Finance & Operations, NetSuite, Acumatica, Sage, SAP, Epicor, Infor, and 20+ other ERPs. When you migrate off GP, the Payment Hub layer stays. Your customer portal still works. Your saved tokenized payment methods still work. Your subscription billing runs continue. Your L3 enrichment logic applies to the new ERP's invoice data. Only the Clarity Connect ERP connector changes.
RM cash receipts posted, not keyed
AR automationReminders, statements and dunning on open Receivables Management balances for each GP company, with subscription billing running against GP customers.
Cash application and payment reconciliationPayments post to GP as RM cash receipts through eConnect, applied to the SOP invoices they settle.
One payment, posted to GP
- CUSTOMER PORTALPaid across open RM balances
- RM CASH RECEIPTPosted via eConnect
- APPLYApplied to the SOP invoices it settles
- GP COMPANYPosted per company
Payments on GP that carry over when you migrate
B2B payments on GP and after itCard, ACH and wallet payments on SOP invoices and orders for every GP company, through a payment layer that only swaps its ERP connector when you migrate.
Credit card processing fees and surchargingA disclosed surcharge where state and card-network rules allow it, recorded in GP on its own line. Debit cards are never surcharged.
Today, and after the move
- SOP INVOICEPaid by card, ACH or wallet
- SAVED METHODSKept in Payment Hub
- MIGRATIONOnly the ERP connector changes
- PORTALSame address, same users
A portal that moves with you
Customer payment portalA portal reading live GP data, which keeps its address, branding, users and saved payment methods when you move to your next ERP.
ACH paymentsACH beside cards, so customers paying large invoices by bank use the same portal on GP and after it.
Lower card costs on commercial cards
Level 2 and Level 3 interchangeLine-item data from SOP and invoicing lines goes with each eligible commercial card payment, and the same logic applies to your next ERP's invoices.
Visa CEDPVisa now judges commercial card payments on that line data: under its April 18, 2026 schedule, failed data is priced like none, and Visa doesn't publish its criteria. The data is built from GP's own SOP lines today and from your next ERP's lines after you move.
Card cost controls
- COMMERCIAL CARDLevel III from SOP line items
- VISA CEDPLine-item data validated
- DEBIT CARDNever surcharged
See it running against your own GP environment
A 30-minute walkthrough: Web Services integration, real-time RM Cash Receipt posting via eConnect, and a branded portal reading live RM data.
The GP lifecycle timeline, what Microsoft has actually announced
Four key dates from Microsoft's official lifecycle announcements. Take these at face value when you're planning Payment Hub deployment and eventual ERP migration.
- April 1, 2025New customer sales ceasedNo new GP licenses sold to prospects after this date
- April 1, 2026New subscription licenses stoppedExisting customers can't add subscription seats after this
- Dec 31, 2029Mainstream support endsNo more product updates, tax / regulatory updates, technical support
- April 30, 2031Security updates endAfter this, GP receives no support whatsoever
Practically speaking: if you're running GP in mid-2026, you have roughly 3.5 years of mainstream support remaining (through Dec 2029) and an additional ~16 months of security-only support after that (through April 2031). Microsoft's recommended migration path is Dynamics 365 Business Central. Enterprise GP customers with larger operational complexity sometimes migrate to Finance & Operations instead.
Most GP customers are planning migration somewhere in the 2027–2029 window, which means most have 1–3 years of Payment Hub-on-GP runtime to benefit from before migration, and then many more years of Payment Hub-on-successor-ERP afterward. The case for Level III data, AR automation and a customer portal holds in both phases.
The migration bridge, Payment Hub today, Payment Hub tomorrow
The core value of Payment Hub for GP customers is that it keeps working on whatever ERP you migrate to, not only on GP. Here's what that bridge looks like.
Payment Hub running on Dynamics GP
2026 → 2029 (or whenever you migrate)
- Integrates via eConnect & Web Services
- Reads RM Customer, SOP Documents, Invoicing
- Posts RM Cash Receipts via eConnect
- Customer portal reads live GP data
- L3 enrichment from SOP / Invoicing line items
- 19+ gateways, ACH, wallets, all available
- Subscription billing runs against GP customers
- Multi-company GP deployments supported
Payment Hub running on BC, F&O, or other
Whenever you migrate, 2027 / 2028 / 2029 / later
- Clarity Connect swaps from GP → destination ERP
- Same customer portal (URL, branding, users)
- Same saved tokenized payment methods
- Same subscription enrollments continue
- Same gateway relationships & merchant accounts
- L3 logic applies to new ERP's invoice data
- Same team-facing views & audit trail
- Migration becomes a back-end swap, not a customer disruption
The practical effect: your customers don't notice the ERP migration from a payment standpoint. They log into the same portal, see their saved methods, pay their invoices, and get their receipts, throughout the migration. Internally, your AR team gets a smoother cutover because the payment layer stays stable while the ERP changes underneath. Your operations team doesn't re-train on a new payment tool. Your CFO doesn't re-write the payment-processing portion of the migration business case.
For the years you still run GP
Dynamics GP still runs mid-market businesses of every kind, with Microsoft's mainstream support through December 31, 2029. Integrating Payment Hub with GP adds the receivables side now, through eConnect and Web Services, and keeps it when you move to Business Central or another ERP:
Questions
Does Clarity Payment Hub still integrate with Dynamics GP given its end-of-life?
Yes, and specifically because of GP's end-of-life, Payment Hub is often the right choice rather than a GP-specific payment tool. Dynamics GP has mainstream support through December 31, 2029, with security updates continuing to April 30, 2031. Many GP customers have 3–5 years of useful runtime ahead of them before migration.
Will Payment Hub still support us once we migrate off GP?
Yes. Payment Hub is ERP-agnostic on its own side, it runs against 25+ ERPs including Dynamics 365 Business Central, Dynamics 365 Finance & Operations (Microsoft's primary migration destinations for GP customers), NetSuite, Acumatica, Sage, SAP, and more.
How does Payment Hub integrate with GP technically?
Through GP's documented integration stack. For real-time transactional integration (customer lookup, invoice read, cash receipt posting, Customer Ledger inquiry), Payment Hub uses Web Services for Microsoft Dynamics GP (WCF/SOAP-based, which is built on eConnect). For direct API access where Web Services has gaps, Payment Hub calls eConnect directly via its COM-based or .NET-based API using XML document schemas.
What's the implementation timeline for GP?
A typical Payment Hub + GP integration goes live in 48 hours once Clarity receives GP test-company credentials (SQL Server + eConnect / Web Services access), gateway credentials, and your baseline configuration (which GP companies map to which merchant accounts and cash GL accounts).
Is the migration from GP to BC a good moment to add Payment Hub, or should we wait?
Adding Payment Hub before migration is typically the better path. Three reasons. First, you get Level III data, a customer portal and AR automation while you still run GP. Second, migration timelines are 2–9 months depending on complexity. Waiting means going without them for the length of the migration project.
Related resources
Payment infrastructure that outlives the ERP.
Live in 48 hours. Your GP license, modules, customizations, and ISV products stay intact. And when migration time comes, the Payment Hub layer follows.
Book a Live Demo