Support Ends
Support Ends
Supported
Migration Path
Timeline
Dynamics GP + Payment Hub, the right integration for a sunsetting ERP
Microsoft Dynamics GP, formerly Great Plains, has been running mid-market businesses since long before "cloud ERP" was a phrase. Microsoft acquired Great Plains in 2001. GP has gone through twenty-plus years of releases, accumulated a massive installed base of SMB and mid-market customers, and earned a reputation as one of the most stable, functional on-prem ERPs in the Microsoft family. It's also end-of-life: Microsoft has announced that mainstream support ends December 31, 2029, with security-only updates continuing through April 30, 2031. New customer sales have stopped. New subscription license sales ended April 1, 2026.
That timeline puts GP customers in an awkward place when evaluating payment integrations. A GP-specific payment tool might work perfectly, until you migrate to Business Central or Finance &. Operations, at which point you have to re-buy, re-implement, and re-train on a new payment layer. That's the trap: the payment tool expires with the ERP, not with the migration.
Payment Hub 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.
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.
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, with the Bridge to Cloud 3 (BTTC3) offer providing a 30% discount on BC user licenses for qualifying GP customers moving to cloud. 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 math on L3 savings, AR automation, and customer portal value works across 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
- 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
only · no
re-implementation
Payment Hub running on BC, F&O, or other
- 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.
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 Dynamics GP
The integration uses GP's documented integration stack, eConnect, Web Services for Microsoft Dynamics GP, and Integration Manager, which Microsoft has supported since the early 2000s and continues to support through the end-of-life timeline. No Dexterity customizations, no direct SQL hacks, no unsupported patterns.
Web Services-based real-time integration
For live customer lookup, invoice read, payment posting, and cash receipt application, Payment Hub uses Web Services for Microsoft Dynamics GP, the WCF/SOAP layer built on eConnect. Preferred approach for real-time portal-initiated and counter-initiated transactions.
eConnect for direct API access
Where Web Services has gaps (certain SOP fields, custom dimensions, specialized document types), Payment Hub calls eConnect directly through its COM-based or .NET-based API, using XML document schemas (RM_TransactionEntry, SOP_Document, etc.) with GP's built-in business-rule enforcement via SQL stored procedures.
Level III from SOP &, Invoicing
Payment Hub pulls line-item data from GP's Sales Order Processing (SOP) documents and Invoicing documents, item description, quantity, UoM, unit price, line total, tax breakdown, customer code, destination ZIP, and packages the Level III envelope for the gateway. 0.3–1.0% savings on qualifying commercial cards.
Tokenized method vault
Customer card and ACH credentials tokenize at the gateway vault, never stored in GP, on Payment Hub servers, or in GP's SQL database. Tokens link to GP Customer records via the eConnect user-defined fields pattern. Raw PAN stays out of your environment.
Multi-company GP deployments
Many GP customers run multiple GP company databases (common legacy pattern for multi-entity organizations that didn't migrate to a single-database multi-company ERP). Payment Hub's routing table maps each GP company database to its own merchant ID, Cash GL, tax setup, and gateway. Per-company payment routing is automatic.
Works with GP ISV products
GP's thriving ISV community (Mekorma for AP, WennSoft for field service / construction, SalesPad for order entry, and many others) works alongside Payment Hub. Payment Hub reads the same GP entities these products write to, so your existing ISV investments stay intact through both runtime and migration.
Migration-ready data layer
All Payment Hub-side data (customer portal accounts, saved tokens, subscription enrollments, transaction history, L3 metadata, AR automation state) lives outside GP, on Payment Hub's infrastructure. When you migrate, this data transfers to the new ERP's connector automatically. You don't lose 3+ years of payment history in the migration.
GP version compatibility
Supports GP 2015 R2, 2016, 2018, 18.2, 18.3, 18.4, 18.5, 18.6, and current (18.7 as of 2026 release). Microsoft has committed to keeping the current version on support through 2029. Clarity supports all actively-supported GP versions and tests against Microsoft's GP monthly update releases.
The integration workflow, from GP SOP invoice to posted RM Cash Receipt
A concrete walk-through: a Dynamics GP 18.6 customer (mid-market industrial distributor with a multi-company GP deployment) receives a $7,280 SOP invoice, pays it through the Payment Hub customer portal using a saved Visa Corporate card, and watches the RM Cash Receipt post to the correct GP company database in real time.
GP generates the SOP invoice
Your AR team posts SOP invoice ORD-50421 in GP (company database DLX), $7,280 across 6 line items, shipping from the Dallas warehouse, Texas tax jurisdiction, Net 30 terms. Invoice becomes available through GP's Web Services via the SOP Document query endpoint. RM Customer balance for ACME Manufacturing updates by $7,280.
GP SOP · RM Web ServicesCustomer sees it in the Payment Hub portal
Acme's AP manager logs into your branded Payment Hub portal. Clarity Connect queries GP's RM Customer and SOP Document entities through Web Services and returns live data, $7,280 new invoice visible, total outstanding $24,160 across 5 open invoices, saved Visa on file, available credit $150 from a prior credit memo. All from the live GP DLX company database.
Live GP data Multi-company awareCustomer selects the invoice and pays
AP manager selects ORD-50421 to pay and applies the $150 credit. Net pay: $7,130 against the saved Visa Corporate card. Payment Hub recognizes the commercial BIN and flags for L3 enrichment before submission.
Credit applied BIN checkClarity Connect pulls L3 data via Web Services
Payment Hub queries GP's SOP Line Item entity for the 6 line items, UoM, unit price, line totals, plus the SOP Header for tax breakdown ($465 TX state + county), freight ($55), customer code (ACME-4021), destination ZIP. All 20+ L3 fields packaged into the gateway envelope in under 500ms.
SOP line fetch 500msGateway authorizes at L3 interchange
Whichever gateway you've configured, Worldpay, Fortis, PayTrace, Authorize.Net, Stripe, or any of the 19+, receives the full L3 envelope. Visa qualifies the transaction at the Level III interchange category, roughly $78 of interchange savings vs. L1 on a $7,130 transaction.
Your gateway ~$78 savedClarity Connect posts RM Cash Receipt via eConnect
Payment Hub calls eConnect's RM_TransactionEntry to post the cash receipt to GP's DLX company database, $7,280 payment (covering $7,130 card + $150 credit memo application), applied to ORD-50421 through GP's native RM apply process. GP's eConnect stored procedures enforce the business rules, SOP invoice closes. Total elapsed time from customer click to GP update: under 3 seconds.
RM_TransactionEntry eConnect postCustomer sees success, GP sees activity
Portal confirms "Payment successful, $7,280 applied to ORD-50421." Receipt emails automatically. Your AR team running the GP Home Page sees the RM Cash Receipt in the day's transaction list. Acme's balance drops to $16,880. SOP invoice shows paid. L3 savings of $78 logged in Payment Hub's reporting.
Portal confirm GP updatedFast-forward: migration year arrives
When you migrate from GP to Business Central (or F&O, NetSuite, Acumatica, whatever), Clarity swaps the ERP connector in Clarity Connect. Customer portal URL unchanged. Acme's AP manager logs in and sees the same interface. Their saved Visa is still there. Their payment history is still there. Their autopay enrollment is still there. Under the hood, Clarity Connect is now writing to the destination ERP, but the customer experience is uninterrupted, and 3+ years of payment history carries forward cleanly.
Connector swap Zero customer disruptionPayment Hub use cases on Dynamics GP
All 11 Payment Hub use cases work on GP. The patterns most common on GP (given GP's distribution / manufacturing skew and on-prem legacy) are highlighted, but all are available.
Pay-link emails, portal, L3-enriched commercial-card acceptance for every GP-generated SOP invoice. The workhorse pattern.
Fills biggest GP gap Self-Service Payment PortalGP doesn't ship a customer portal. Payment Hub adds the modern branded portal your customers expect in 2026.
High ROI on GP Level III InterchangeGP skews toward B2B distribution and manufacturing, exactly the verticals with highest L3 savings. $15K–$50K/year typical.
Cash app ERP Payment ReconciliationReal-time RM Cash Receipt posting via eConnect. End the manual cash-application bottleneck on GP.
Recurring Subscription BillingNative recurring, scheduled, and automated billing against GP customers. Pairs with GP recurring invoice patterns where used.
Multi-invoice Consolidated Invoice PaymentCustomers pay multiple GP SOP invoices in one transaction. Payment Hub splits clean per-invoice to RM apply records.
Aging reduction AR Collections AutomationDunning cadences with direct pay-links. GP's native AR collections reminders get much more effective. DSO reduction 5–12 days typical.
Multi-company GP Multi-Location PaymentsPer-company GP database routing. Common GP pattern of 5–15 company databases for multi-entity operations fully supported.
SOP workflow Order-to-CashPayment embedded in GP's SOP order-entry workflow. Deposits, authorization-capture, partial-shipment handling.
Card-present Counter Sales &, RetailFor GP distribution customers running branch counters and will-call, certified terminals + GP RM customer lookup at counter.
Online orders eCommerce CheckoutClarity eCommerce architecture pairs with GP SOP for B2B storefront checkout with real-time GP inventory and pricing.
Technical details, for GP admins &, Partners
The engineering reality of how Clarity Connect integrates Payment Hub with Dynamics GP, for GP administrators, IT teams, and Microsoft Partners managing GP customers through the sunset window.
- Primary integration layer. Web Services for Microsoft Dynamics GP, WCF-based with SOAP / XML document formats. Preferred for real-time transactional operations. Built on eConnect under the hood.
- Direct API layer. eConnect via COM or .NET, used where Web Services has gaps or for specialized document types. XML document schemas (RM_TransactionEntry, SOP_Document, IV_Item, etc.) with GP's built-in business-rule enforcement through installed SQL stored procedures in each company database.
- Bulk operations. eConnect batch patterns for high-volume loads. Integration Manager available for configurable UI-driven imports if needed for historical backfill or month-end reconciliation exports.
- Authentication. Windows integrated authentication for on-prem GP (domain account with appropriate GP user permissions). For customers running GP on Azure VMs, certificate-based auth and Entra ID conditional-access policies are supported.
- No Dexterity customizations installed. The integration runs from Clarity's infrastructure. No custom Dexterity code installed in your GP environment, no modifications to RM or SOP posting routines, no GP Dexterity dictionary changes. Your GP code base stays vanilla.
- Deployment model. Works with GP on-premises (the dominant deployment pattern), GP on Azure VMs, and GP hosted by partner MSPs. Payment Hub reaches your GP environment through the Web Services / eConnect endpoints via outbound-only firewall rules (inbound firewall ports are not required for most patterns).
- Version compatibility. Supports GP 2015 R2, 2016, 2018, 18.2, 18.3, 18.4, 18.5, 18.6, and current (18.7 as of 2026). Microsoft has committed to supporting the current version through December 31, 2029 with security patches through April 30, 2031, Clarity's compatibility layer covers the full range.
- Multi-company GP databases. Native support for GP's long-standing multi-company database pattern. Each company database is configured in Payment Hub's routing table with its own merchant ID, Cash GL, tax posting setup, and gateway. Per-company routing is automatic based on the originating transaction.
- ISV compatibility. Works alongside common GP ISV products, Mekorma, WennSoft, SalesPad, Binary Stream, Rockton, Greenshades, eOne SmartList Builder, and the broader GP ISV community. Payment Hub reads the same GP entities these products write to. No conflicts with their operation.
- PCI scope. Raw PAN never touches Payment Hub or GP servers, card data tokenizes at the gateway vault via hosted iframe / JS-tokenization. Typical deployment stays in SAQ A / SAQ A-EP scope even on on-prem GP.
- SOC 2 Type II. Clarity Ventures operates to SOC 2 Type II standards with annual independent audits.
- Migration-ready state. All Payment Hub state (portal accounts, saved tokens, subscription enrollments, transaction history, L3 metadata, reports) lives on Payment Hub infrastructure, not in GP's SQL database. When migration arrives, this state transfers with you. No data lost in the ERP swap.
Dynamics GP + Payment Hub FAQ
The questions GP admins, IT teams, Microsoft Partners, and finance leaders ask before adding Payment Hub to their Dynamics GP deployment.
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.
Payment Hub integrates with GP today through eConnect, Web Services, and Integration Manager, and when you migrate to Business Central or Finance &. Operations, the Payment Hub layer carries forward intact. You don't throw away the payment infrastructure when the ERP changes.
What's the Dynamics GP end-of-life timeline exactly?
Four key Microsoft-announced dates. April 1, 2025: new customer sales of Dynamics GP ceased. April 1, 2026: new subscription license sales stopped. December 31, 2029: mainstream support ends (product enhancements, regulatory / tax updates, and technical support all end). April 30, 2031: security updates end, after this, GP receives no support whatsoever.
Existing customers can continue running GP through these dates, but eventually must migrate. Microsoft offers the Bridge to Cloud 3 (BTTC3) promotion providing a 30% discount on Business Central user licenses for qualifying GP customers moving to the cloud.
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.
When you migrate from GP, the Payment Hub side changes minimally: we swap the Clarity Connect ERP connector from eConnect / GP Web Services to whichever ERP you land on (typically BC via REST API v2.0 or F&O via OData + DMF). Your customer portal, saved customer payment methods, subscription enrollments, gateway relationships, L3 enrichment logic, and AR automation all carry forward. The migration is a connector swap, not a Payment Hub re-implementation.
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.
For bulk operations (historical data backfill, monthly reconciliation imports), Payment Hub uses eConnect-based batch patterns. Integration Manager is available for configurable bulk imports but is typically not needed for the operational runtime. No GP Dexterity customizations are installed in your GP environment.
Which GP modules does Payment Hub touch?
Primarily Financials and Sales modules, Receivables Management (RM), General Ledger (GL), Bank Reconciliation, Sales Order Processing (SOP), and Invoicing. For Manufacturing / Project Management / HR shops, Payment Hub integrates with the transactional touchpoints that matter for payment acceptance (manufacturing sales orders, project invoices, service billing).
Customer master data is read from the RM Customer Master (RM00101 table behind the scenes, though Payment Hub uses the eConnect / Web Services API layer rather than direct SQL access). Cash receipts post as RM Cash Receipts (RM_TransactionEntry documents via eConnect). Invoice applications work through the standard RM apply process.
Can we still accept modern payment methods on GP, including mobile wallets and ACH?
Yes. Payment Hub's gateway library (Worldpay, Adyen, Cybersource, Global Payments, Elavon, Fortis, PayTrace, Nuvei, PNC, Stripe, Braintree, Authorize.Net, NMI, USAePay, Square, PayPal, Apple Pay, Google Pay, Amazon Pay, 19+ total plus ACH / eCheck) is all available on the GP integration.
GP customers frequently land on Payment Hub specifically because they want modern mobile wallet support (Apple Pay, Google Pay, Amazon Pay) and a branded customer portal that GP's legacy on-prem architecture doesn't natively provide. Modern payment acceptance doesn't require a modern ERP.
Does Level III interchange optimization work on GP?
Yes. Payment Hub's L3 enrichment pulls line-item data from GP's Sales Order Processing (SOP) documents and Invoicing documents through eConnect / Web Services, item description, quantity, UoM, unit price, line total, tax breakdown, customer code, destination ZIP, and the other 20+ Level III fields, and packages them into the gateway envelope.
Commercial-card transactions qualify for 0.3–1.0% interchange savings per qualifying transaction. A typical GP-running distributor or manufacturer with $5M in annual B2B card volume recovers $15K–$50K in L3 savings annually. That saving continues after you migrate to BC or F&O, the enrichment logic is Payment Hub's, not GP-specific.
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).
For multi-company GP deployments (common among GP customers, given GP's long history), pilot with 1–2 companies in the first 48 hours and add additional companies in subsequent 24–48 hour batches. Your existing GP license, modules, customizations, and ISV products stay intact.
Does it work with our GP ISV products (Mekorma, WennSoft, SalesPad, etc.)?
Yes. The GP ISV community is extensive and Payment Hub is designed to coexist with the common ISV products GP customers run, Mekorma (AP/AR automation), WennSoft (construction / field service), SalesPad (SOP order entry), Binary Stream (multi-entity accounting), Rockton (manager approval / security), Greenshades (payroll / HR), eOne (SmartConnect / SmartList Builder), and many others.
Payment Hub reads and writes through the same eConnect / Web Services layer these products use. No conflicts, no overwriting of records, no broken integrations. Where your ISV product handles specific transaction types (e.g., WennSoft service invoices), Payment Hub accepts payment against those invoices through the standard RM apply process.
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 the L3 savings, customer portal, and AR automation value during the GP runtime, potentially $45K–$250K+ in L3 alone over 3–5 years of remaining GP use. Second, migration timelines are 2–9 months depending on complexity. Delaying Payment Hub means delaying real savings for the duration of the migration project.
Third, when migration arrives, Payment Hub is already a known quantity, your team knows the tooling, your customers know the portal, your gateway relationships are set, so the migration focuses on the ERP transition itself rather than also introducing a new payment layer. The migration becomes less risky. For GP customers planning a BC or F&O migration, we often recommend deploying Payment Hub on GP first, operating it in production for 6–18 months, then using the ERP migration as a connector swap rather than a fresh payment implementation.
What if we never migrate off GP and just run it past 2031?
Some customers are planning exactly that, continuing to run GP past April 30, 2031 without Microsoft support, relying on internal IT for any break-fix and accepting that tax / regulatory updates won't come from Microsoft. It's a valid strategy for certain operational contexts (stable business process, no major upcoming regulatory change, in-house GP expertise, comfortable with the support risk).
Payment Hub continues to work in that scenario as long as your GP environment is running and the Web Services / eConnect APIs respond. There's no dependency on Microsoft-provided GP support for the Payment Hub integration to function. That said, if your operational risk tolerance changes later and you decide to migrate, the connector-swap pattern remains available at that point.
Who supports the integration, Clarity or our GP Partner?
Clarity supports the integration directly. Your Microsoft GP Partner / VAR continues to support the GP platform itself (upgrades, service packs, tax updates, customizations, Dexterity modifications, year-end procedures, training). Payment Hub's support covers the integration layer, payment acceptance, gateway issues, Clarity Connect, L3 enrichment, customer portal, and anything that touches Payment Hub infrastructure.
Most GP Partners are familiar with Clarity Ventures and work collaboratively on deployments. The integration is designed to be partner-friendly, standard integration patterns (eConnect, Web Services), no Dexterity customizations, nothing that disrupts your partner's normal GP delivery model or your customer's GP upgrade practices.