If you run a B2B store on Magento 2, adding net terms affects more than checkout. It changes how buyers pay, how credit gets reviewed, how invoices are collected, and how your team manages receivables after the sale. The Resolve Magento 2 integration is built to support that broader workflow. It adds Resolve as a payment option within Magento 2 so eligible business buyers can apply for net terms during checkout, while merchants manage orders in Magento and connect the checkout flow to Resolve’s wider platform for B2B Net Terms, Accounts Receivable, B2B Payments, and integrations.
For Magento merchants, that means this is not just another payment extension. It is part of a larger embedded B2B payments and receivables workflow that can support buyer credit decisions, collections, payment handling, and accounting connections across your finance stack. Resolve’s official Magento 2 technical guide confirms the main implementation path: install the extension, retrieve your API credentials, configure Resolve as a payment method, review order-management functions, test the flow, and then move to production. The Adobe Commerce Marketplace listing also confirms that Resolve is available as a Magento integration for Adobe Commerce merchants.
This guide walks through the setup process, the buyer experience, how Magento order actions sync with Resolve, and what to review before launch.
Before starting the integration, make sure you have the following:
Resolve’s setup docs also recommend reviewing your current checkout process in advance so you understand how the Resolve payment option will affect customer experience and internal operations.
If you are planning the full receivables side of the rollout, it also helps to review Resolve’s net terms for ecommerce, Resolve for sellers, and better than factoring pages so your checkout flow lines up with your broader finance process.
Resolve documents Composer as one supported installation method.
From your Magento 2 root directory, run:
composer require resolve/magento2
composer update
php bin/magento setup:upgrade
php bin/magento setup:di:compile
After installation, clear Magento cache so the default Resolve configuration becomes available.
You can also verify module availability from the command line:
php bin/magento module:status
Composer is generally the cleaner path for teams that already manage Magento extensions through standard deployment workflows.
If you are not using Composer, Resolve also documents a manual command-line installation flow.
1. Download the extension package.
2. Create the module directory if it does not already exist:
mkdir -p app/code/Resolve/Resolve
3. Unzip the extension files into app/code/Resolve/Resolve/.
4. Verify that Resolve_Resolve appears in Magento’s module list.
5. Run the Magento setup commands:
php bin/magento module:enable Resolve_Resolve php bin/magento setup:upgrade
Depending on your environment, you may also need to compile dependencies and clear cache before testing the payment method.
Resolve’s Magento 2 guide says your Merchant ID and Secret API Key are available in the merchant dashboard under:
Settings > Integrations > Direct API
Use sandbox credentials while you are testing the sandbox integration. When you are ready for production, use the production dashboard to retrieve the live credentials.
This separation matters. Using the wrong key in the wrong environment is one of the easiest ways to create avoidable setup errors.
After installing the extension, configure Resolve in Magento by going to:
Stores > Configuration > Sales > Payment Methods > Resolve
Then update the key settings:
If Magento does not reflect the changes immediately:
That refresh step is part of Resolve’s documented setup flow and is worth doing before any deeper troubleshooting.
Once configured, Resolve appears as a payment option during checkout.
According to Resolve’s official Magento 2 guide, the integration allows your site to:
From the buyer’s perspective, the flow is straightforward:
One important correction here: the experience should not be described as guaranteed fully in-page with no redirect. Resolve’s docs explicitly say that merchants should test the flow and confirm that the buyer is redirected back to the confirmation page after completing the Resolve checkout process.
This is one of the most important operational parts of the integration.
Resolve’s Magento 2 guide says that processing these actions in Magento updates order status in the Resolve dashboard:
Resolve notes that you can process orders in the dashboard, but strongly recommends using Magento 2 so order status stays synced with Resolve.
That recommendation is important for internal consistency. If your team already uses Magento as the source of truth for order handling, keeping these actions inside Magento helps reduce status mismatches and manual cleanup.
|
Magento 2 action |
Effect in the Resolve workflow |
|---|---|
|
Authorize |
The order amount is authorized in the Resolve payment flow |
|
Capture |
The payment flow is captured through Magento and updated in Resolve |
|
Cancel |
The order cancellation is reflected in Resolve |
|
Refund |
The refund updates the transaction state in Resolve |
|
Partial refund |
The partial refund updates the remaining transaction balance in Resolve |
Resolve recommends testing your configuration before going live.
The documented test flow includes:
Resolve specifically notes that fake address or phone information can prevent proper testing. It also says the sandbox URL indicates you are in the testing environment.
Before launch, Resolve asks merchants to email their test site so Resolve can verify the configuration and provide production credentials.
After sandbox validation, Resolve’s Customer Success team provides the production key.
The best go-live approach is simple:
Once that is done, the Magento 2 integration becomes part of a larger Resolve operating workflow instead of a standalone payment add-on.
Resolve explicitly recommends installing and testing the extension in a sandbox or staging environment before pushing it live. Skipping that step makes production your test environment.
Sandbox and production credentials are different. Pull the keys from the correct dashboard before saving them in Magento.
If Resolve does not appear at checkout after configuration, flush Magento cache and reauthenticate in the admin before assuming the extension failed.
Resolve recommends reviewing your current checkout flow before implementation. That matters because payment methods change customer experience, approval steps, and support workflows.
Resolve says Magento should remain the main place where authorize, capture, cancel, and refund actions are handled if you want status syncing to stay clean.
The original article overstated compliance language. A safer and more accurate description is this:
Resolve’s Magento 2 integration is designed so the checkout process works through Resolve’s payment flow rather than requiring merchants to manually manage that process outside the platform. Resolve’s documentation focuses on the transaction flow, key setup, and order handling, but the reviewed source materials do not explicitly state named certifications such as PCI, SOC 2, or ISO for this Magento extension.
That means merchants should:
This keeps the article aligned with verified claims instead of unsupported certification language.
Here are the main features that matter most for Magento merchants evaluating Resolve:
These features make the Magento extension more useful when it is treated as part of a larger B2B payments workflow rather than a standalone plugin.
Resolve is a strong fit for Magento merchants that want to offer B2B payment terms inside checkout while keeping the rest of the receivables process more structured.
It is especially relevant for:
If your team wants to move beyond manual terms management, the integration is most valuable when it is paired with Resolve’s larger credit, receivables, and payments workflow.
The Resolve Magento 2 integration is best understood as a Magento checkout extension connected to a broader B2B credit-to-cash workflow. It gives merchants a documented way to install Resolve in Magento 2, configure the payment method, retrieve credentials, test in sandbox, and manage order actions in a way that stays aligned with Resolve.
That makes it useful for merchants who want more than a basic payment add-on. If your team wants to offer net terms within checkout while keeping order handling in Magento and tying that experience to a broader receivables process, Resolve provides a practical path to do that.
Before rollout, review the official docs, validate the buyer journey in sandbox, and make sure the extension fits the rest of your stack through Resolve’s integrations, accounts receivable tools, and B2B payments platform.
Install the Resolve Magento 2 extension through Composer or manual setup, enable it under Stores > Configuration > Sales > Payment Methods, enter your Merchant ID and Secret API Key, and test the flow in sandbox before going live.
Yes. Resolve’s Magento 2 extension is listed on the Adobe Commerce Marketplace.
The buyer continues through Resolve’s payment flow, completes the required steps, and is redirected back to your store’s confirmation page.
Yes. Resolve’s Magento 2 guide says that authorize, capture, cancel, refund, and partial refund actions processed in Magento update order status in Resolve.
Yes. Resolve recommends testing the integration in a sandbox or staging environment before production and verifying that the transaction appears in both Magento and the Resolve sandbox dashboard.
This post is to be used for informational purposes only and does not constitute formal legal, business, or tax advice. Each person should consult his or her own attorney, business advisor, or tax advisor with respect to matters referenced in this post. Resolve assumes no liability for actions taken in reliance upon the information contained herein.