Skip to content

WePay is gone: what Adobe Commerce and Magento stores should move to

Home / Blog / WePay is gone: what Adobe Commerce and Magento stores should move to


WePay is gone. Chase bought it in 2017, J.P. Morgan has since folded it into J.P. Morgan Payments, and WePay's own help center says transactions on the WePay platform have stopped. Every WePay account was either closed or moved to one of two Chase products:

  • Chase Payment Solutions, which takes card payments online through an Authorize.Net gateway running on Chase processing.
  • J.P. Morgan Payments, with its Online Payments API and Checkout.

So if you came here looking for a WePay payment gateway module for Magento 2 or Adobe Commerce, the honest answer is that none can work anymore, and nobody can build you a new one. What you can do is move your store to whichever of those two your account landed on, or to another gateway. Both moves are very doable. We build and maintain payment modules for Adobe Commerce, Magento Open Source and Mage-OS, so this is the practical version: what happened, what to move to, what it means for orders you already took, and what the new integration has to get right.

What happened to WePay?

Is WePay still in business? Not as a payment platform. By the time Chase bought it, WePay was a payments company for software platforms: marketplaces, invoicing tools and fundraising sites that needed to pay their own users. The deal closed in December 2017. In May 2024, J.P. Morgan said it had decided to fully integrate the WePay platform into its own commerce platform, and that it had ended some of WePay's software-partner agreements along the way.

When What happened Source
December 2017 WePay officially becomes a Chase company Chase press release
May 2024 J.P. Morgan says it will fully integrate the WePay platform, and that it has ended certain software-partner agreements J.P. Morgan article, archived copy
By July 2026 WePay's help center: transactions have stopped, refunds can't be issued through WePay, and each account was either moved to Chase Payment Solutions or J.P. Morgan Payments, or closed WePay Help Center, archived copy
November 2026 wepay.com and WePay's API address no longer resolve Our own check, November 2026

Both of those pages have since come down, which is why the links above point to archived copies.

What replaced WePay for Adobe Commerce and Magento stores?

It depends on where your account went, so find that out first. The answer decides how big the move is.

Where your WePay account went What Chase offers for online payments What that means in Adobe Commerce
Chase Payment Solutions An Authorize.Net gateway powered by Chase processing The short path: an existing Authorize.Net extension. Authorize.Net has lived in extensions since 2.4.0, when Adobe removed it from core
J.P. Morgan Payments The Online Payments API and Checkout No ready-made extension that we could find, so a module has to be built
Closed Nothing to migrate Choose a new gateway on its own merits

If you moved to Chase Payment Solutions, this is the easy one. Authorize.Net already has mature Adobe Commerce modules, so the work is setup, testing and a careful switch-over rather than new code. We've run Authorize.Net on Adobe Commerce and Magento stores since 2020, through Authorize.Net's own extension and through ParadoxLabs' CIM module, which saves cards for repeat buyers. Chase isn't new ground for us either. Chase's own company history says Paymentech is now Chase Payment Solutions, and Oleg, who runs X2Y, has worked with Chase Paymentech and numerous other gateways over the years.

If you moved to J.P. Morgan Payments, someone has to build the module. When we looked in November 2026, neither the Adobe Commerce Marketplace nor Packagist had an extension for J.P. Morgan's Online Payments API, from J.P. Morgan or anyone else. The only Chase-related code we turned up connects to Chase's older Orbital gateway, which is a different system. So this is a build, and building payment modules is what we do. We built Float's Magento module from its first commit in 2021 and still ship its releases, and we built Ecentric's, which you can read on GitHub. A J.P. Morgan module gets built the same way, on Adobe Commerce's own payment framework, and the sections below are the parts it has to get right.

Maybe you picked WePay because it paid out to many sellers, like a marketplace or a fundraising site. Then you're really asking a different question: who holds the money, and how does it get split? That deserves its own conversation before anyone writes a line of checkout code.

Is there still a WePay payment gateway module for Magento 2?

No working one. Any Magento 2 WePay payment gateway module, whoever wrote it, has to talk to WePay's API, and that API is gone. When we checked in November 2026, wepay.com, its API address and its developer site didn't resolve at all. There is nothing at the other end of the call.

If a WePay module is still installed on your store, it's safe to switch it off and remove it. Adobe Commerce saves the payment method's title on every order. When a method's code is missing, it shows those orders through a built-in stand-in method, so your order history stays readable. The payment details stay in Adobe Commerce's own tables. If the module kept anything in a table of its own, export it before you uninstall.

What happens to orders your store took through WePay?

They still need looking after, and WePay can't do it for you.

  • Refunds. WePay's help center is blunt: refunds can no longer be issued through WePay. If your account was closed, you refund the customer another way, such as a check. If it moved to Chase Payment Solutions or J.P. Morgan Payments, Chase's support team can help you refund from the transferred account. Either way, record it in Adobe Commerce as a credit memo with Refund Offline, so the order, the stock and your reports match what really happened.
  • Disputes. Chargebacks on old payments can still show up, and the help center still lists them as a support topic. Match them to orders by the WePay ID your old module saved on each order, if it saved one.
  • Tax forms. Some merchants got two 1099-K forms for 2025, according to WePay's help center. One came from WePay, Inc. and one from Paymentech, LLC, the J.P. Morgan company behind Chase Payment Solutions and J.P. Morgan Payments. If your store's 2025 card sales don't match one form, look for the second.

What shape should the new checkout take?

J.P. Morgan's Checkout comes in three shapes, and most gateways offer something close to each:

  • Hosted Payment Page. The shopper leaves your store, pays on J.P. Morgan's page and comes back. Our Float and Ecentric modules work this way too: the shopper pays on the provider's own page.
  • Drop-in UI. A JavaScript form from the provider runs on your checkout page and collects the card there. The shopper never leaves your store. Which PCI questionnaire that puts you on depends on how the form is built, so ask (more on that below).
  • Pay by Link. You send a payment link by email or text. Useful for phone orders and for business accounts paying an invoice, rather than for the storefront checkout.

Behind all three sits the Online Payments API itself, the direct route, where your own code sends every payment request. It gives you the most control. If card numbers ever pass through your servers, it also gives you the most PCI work.

For most stores, the hosted page or the drop-in form is the right call. The real difference between them is PCI scope.

How much PCI work does each option leave with you?

The PCI Security Standards Council sorts online stores into self-assessment questionnaires, or SAQs, by how the payment page is built. The short version:

How the payment page works Usual questionnaire Why
Full redirect to the provider's hosted page SAQ A Everything on the payment page comes from the provider (PCI SSC FAQ 1291)
The provider's form in an iframe on your checkout SAQ A, plus one extra condition You confirm your page isn't open to script attacks, either with your own controls (PCI DSS requirements 6.4.3 and 11.6.1) or with written confirmation from the provider (PCI SSC FAQ 1588)
Your page builds the form and posts the card to the provider SAQ A-EP Your site produces part of the payment page (PCI SSC FAQ 1291)
Card numbers reach your server SAQ D The questionnaire for stores that accept card data on their own website (SAQ D for Merchants)

Two things catch people out. The script condition in the second row covers the scripts on your checkout page, including the ones other extensions add, and an Adobe Commerce checkout usually has a few. And your acquirer, not your developer, decides which questionnaire you file, so confirm it with them.

What does 3-D Secure 2 add to the checkout?

3-D Secure is the step where the card's bank checks that the shopper really is the cardholder. J.P. Morgan's 3-D Secure documentation gives the two main reasons to use it. When authentication succeeds, the cost of fraud chargebacks can shift to the card's issuer. And it helps meet Strong Customer Authentication rules under PSD2 in the EU and the UK. The same page says places such as the EU, the UK, India and Australia may require it.

Most of the time the bank approves quietly from the data it was sent. That's the frictionless flow. Sometimes it asks the shopper to prove who they are, which is the challenge. The challenge is where an Adobe Commerce checkout needs care, because the shopper is off on the bank's screen while the order waits.

  • The first answer isn't the whole answer. After authentication, J.P. Morgan POSTs a short result to your return URL, and your module then asks the API for the full details. Treat that first message as a signal.
  • A missing return URL skips 3-D Secure. J.P. Morgan's docs say that without one, it won't run the 3-D Secure step and goes straight to authorization. That's an easy bug to ship and a hard one to notice.
  • The order needs a waiting state. Usually that's pending payment, while the bank decides. When to create the order is a real choice with costs either way. We wrote up both designs and why we switched.
  • Plan for the messy endings. The shopper closes the window, the challenge times out, the result arrives twice. Each one needs its own outcome, and "leave the order pending forever" isn't one of them.

How should the module trust webhooks and reconcile payouts?

J.P. Morgan lets you pick which events send a webhook, and each notification carries IDs you use to look up the details (Online Payments overview). So the pattern is the same as the 3-D Secure return: the webhook tells you something changed, and the API tells you what.

On the store's side, three habits keep the books straight:

  • Guard on order state. A webhook that arrives twice must not create two invoices. Our Float module only acts on a payment notification while the order is still new or pending payment, and it sends the order email only after the invoice exists.
  • Send a unique ID with every request. J.P. Morgan's API takes a request ID you generate, so it can spot duplicates and let you retry safely. That's what keeps a double click on Place Order from turning into two charges.
  • Keep the gateway's IDs on the order. The payment, each capture and each refund get their own ID. Save them on the payment record, the invoice and the credit memo, and carry them into whatever your accounting or ERP system imports. Then matching a payout line to an order is a lookup, not an afternoon. If an ERP is part of the picture, our ERP integration readiness checklist covers what else has to travel with the order.

Can the module capture per shipment and refund part of an order?

With J.P. Morgan, yes. One authorization can have several captures, which is what split shipments need, and one payment can have several refunds.

Adobe Commerce only offers that in the admin if the module says it can. Each payment method declares whether it supports partial capture and partial refunds per invoice. If it doesn't, your team either invoices the full amount up front or does refunds by hand in the gateway's portal.

This matters most for B2B. A distributor ships what's in stock today and the backorder in three weeks. The clean way is to authorize when the order is placed, then capture each shipment as it leaves. Authorizations expire, though, so the module also needs a plan for the backorder that ships after the first authorization has lapsed. J.P. Morgan's API allows more than one authorization on a payment for exactly that case.

Some gateways simply can't refund through their API, and an honest module says so. Our Ecentric module tells the admin to refund in Ecentric's merchant portal and writes that note on the order, so nobody assumes the money went back when it didn't.

How do you test it before real money moves?

J.P. Morgan hands out test credentials during onboarding, and its test environment returns results based on the request and the card details you send. Ask for access early. How good the sandbox is decides how fast the rest of the build goes.

What we'd want covered before a payment module goes near a live store:

  • an approved card and a declined one, for a guest and for a logged-in customer
  • a 3-D Secure challenge that passes, one that fails, and one abandoned halfway
  • a webhook that arrives late, one that arrives early, and one that arrives twice
  • a double click on Place Order over a slow connection
  • a partial capture, a partial refund and a full refund
  • a second website with its own credentials

Automate the ones that touch money. This fall we added Stripe's own module to an Adobe Commerce store we look after, and wrote Playwright checkout tests for it. They cover a guest and a registered customer, and run against Stripe's test mode.

What have we built and maintained for payment gateways?

Integration Platform What it does Since
Float Payments Adobe Commerce / Magento 2 Float's card-linked instalments in South Africa: redirect checkout, an instalment preview on product pages, the order created before the redirect, per-website settings Since 2021
Ecentric Adobe Commerce / Magento 2 Ecentric's hosted payment page, webhook confirmation, saved cards in the customer account, and refunds pointed to Ecentric's portal. The code is on GitHub Since 2023
Peach Payments Adobe Commerce / Magento 2 Peach Payments' Magento module, maintained and extended Since 2021
LayUp Magento 2 The first Magento 2 module for LayUp's lay-by plans Since 2020

We also look after stores that run Stripe, Authorize.Net, Braintree and PayPal Payflow.

A module built on the platform's own payment framework works across Adobe Commerce, Magento Open Source and Mage-OS. Version support still needs saying plainly. Float's module documents Adobe Commerce and Magento Open Source 2.4.6 through 2.4.7 on PHP 8.3. Mage-OS moves on its own release schedule, so we test there before we promise it.

The longer stories: building and maintaining the Float module and what building a payment module from scratch involves, which is written for payment providers. How we take on this work is on our payment gateway module development page.

Where did your WePay account land?

That's the question to answer first, and it's usually one call to Chase. If it went to Chase Payment Solutions, an Authorize.Net extension may be all you need, and we'll happily tell you so. If it went to J.P. Morgan Payments, that's a module to build, and we'd love to build it. Starting over with another gateway works too. Tell us which one and which Adobe Commerce version you're on, and we'll come back with what the build really involves, including the parts that never make it into an API reference.


Written by X2Y.DEV
WePay J.P. Morgan Payments Payments Adobe Commerce Magento Mage-OS
Back to Blog

0%