Adobe Commerce and Magento payment gateway integration
Payment providers hire us to build their Magento modules, and merchants hire us to get a gateway live in checkout. Either way, the work is the same: a checkout that takes the money, a store that knows what happened to it, and a module that still works after the next upgrade.
Ask AI about our Magento payments work
Which Magento payment gateways have we worked with?
Three of these are Magento modules we built, and one is a provider's module we maintain and extend. The others we integrated into a merchant's checkout. Each one is on this list because the work shipped.
-
Float
Module we built
Buy now, pay later for Magento 2, since 2021, and still shipping.
Read the build story -
LayUp
Module we built
The first Magento 2 module for LayUp's lay-by plans, since 2020.
-
Ecentric
Module we built
A hosted payment page, webhooks and saved cards. The code is public.
Read the code -
Peach Payments
Module we maintain
Their Magento module, maintained and extended since 2021.
-
Stripe
Integrated into a store
Stripe's own module, installed and configured, with checkout tested in Stripe's sandbox.
-
Authorize.Net
Integrated into a store
The official Authorize.Net module, with ParadoxLabs' CIM module for saved cards.
-
Braintree
Integrated into a store
Set up in a merchant's checkout.
-
PayPal Payflow
Integrated into a store
Set up in a merchant's checkout.
Over the years we've also worked with Chase Paymentech and a number of other gateways.
What does a Magento payment integration have to get right?
Taking a test payment is the easy part. These are the parts that decide whether the checkout holds up with real customers, real refunds and a real auditor.
- PCI scope: SAQ A, A-EP or D
- We keep your PCI scope as small as the gateway allows, and tell you which questionnaire you are building for before we build it. A hosted payment page or gateway-hosted card fields usually means SAQ A. A checkout page your store serves that sends card data straight to the gateway means SAQ A-EP. Card data touching your servers means SAQ D.
- 3-D Secure 2 and SCA
- Frictionless and challenge flows, exemptions where the gateway supports them, and the order states Magento needs while a shopper is in a challenge, so an abandoned challenge does not leave an order stuck in pending payment.
- Webhooks and reconciliation
- Signed webhooks checked before anything changes, handling that is safe to repeat so a retry never invoices twice, and a way to match what the gateway settled against what Magento invoiced.
- Refunds and partial captures
- Online refunds from the credit memo, partial and multiple captures for orders that ship in parts, and voids for authorisations that never ship.
- Multi-currency
- Base, display and charge currencies kept straight, rounding that agrees with the gateway, and the right merchant account for each store view or currency.
- Sandbox testing
- Every flow runs against the gateway's sandbox, with its test cards and 3-D Secure scenarios, on a staging copy of your store before a live key is touched.
- Upgrades without breaking checkout
- New Magento and Adobe Commerce releases, PHP versions and gateway API changes are tested against the module before they reach your customers. That is the part of payments work most teams quote for once and then leave.
How does an engagement run?
-
1
We talk about the gateway and the store.
Which gateway, which edition and version, which payment methods and currencies, and which PCI questionnaire you want to end up on. If a module already exists, we read it first.
-
2
You approve a written scope.
The work is priced in points, with our reasoning and how confident we are in the estimate. Nothing starts until you approve it.
-
3
We build and test against the sandbox.
On a staging copy of your store, every flow above, including the failures: declined cards, abandoned challenges, refunds after a partial capture.
-
4
We go live, and we stay.
Live keys, a watched first week, and a rollback plan. Then the module is kept working through every Magento release and API change after it.
What does keeping a payment module working look like?
One example, with every figure read from the module's own repository.
Float Payments
Magento Open Source, Adobe Commerce, Mage-OS
Buy now, pay later for Magento 2, built from scratch and still shipping.
- First shipped
- September 2021
- Releases
- 9
- Latest
- 1.1.0, July 2026
- Commits
- 134
Tested against Magento 2.4.6 and 2.4.7. Read the build story
Building a gateway module for Shopify, WooCommerce, BigCommerce or OpenCart as well? That is the same work on other platforms, and it is on our payment gateway module development page.
Common questions
Do you build payment modules for gateways, or integrate gateways for stores?
Both. Payment providers hire us to build and maintain the Magento module their merchants install. Merchants hire us to get a specific gateway live in their checkout, or to fix one that is misbehaving. The engineering is the same; who owns the module afterwards is what differs.
Which PCI questionnaire will my store be on?
It depends on where card data travels, and we decide that with you before building. A hosted payment page or gateway-hosted card fields usually means SAQ A. A checkout page your store serves that posts card data straight to the gateway means SAQ A-EP. Card data on your own servers means SAQ D. Your acquirer has the final word on which applies.
Does this work on Magento Open Source and Mage-OS as well as Adobe Commerce?
Yes. The payment layer is the same across the three, so a module we build runs on Adobe Commerce, Magento Open Source and Mage-OS. Where an edition differs, such as Adobe Commerce B2B features like payment on account, we say so in the scope.
What happens to the payment module at the next Magento upgrade?
We test it against the new release on staging before your store moves, and fix what the release breaks. That is part of keeping a module working, not a separate surprise project.
Our checkout has orders stuck in pending payment. Can you help?
Usually, yes. Stuck orders tend to come from a webhook that never arrived or was not trusted, a 3-D Secure challenge the shopper abandoned, or a cron job that cancels pending orders too early. We find which one it is before changing anything.
Talk to us
Tell us which gateway, and which store.
Whether you are a payment provider that needs a Magento module or a merchant that needs a gateway working, we will tell you honestly what it involves, including when the answer is that you do not need us.
0%