The Coriunder_Hosted module for Magento 2.4. Redirect checkout, signed callbacks and admin configuration under Stores → Configuration → Sales → Payment Methods.
The Coriunder_Hosted module hands checkout over to the Coriunder hosted payment page and returns the shopper to your store. Credentials are stored with Magento’s encrypted configuration backend, and card data never reaches your Magento instance.
Coriunder_Hosted
You will be redirected to the Coriunder secure payment page after placing the order.
Installed as a standard Composer module, configured entirely from the Magento admin.
Shoppers pay on Coriunder’s page over HTTPS and come back to your success page. Your Magento servers never see or store card details.
The personal hash and portal token are stored with Magento’s encrypted configuration backend rather than as plain configuration values.
Strong customer authentication runs on the hosted page. Contact Coriunder to have it enabled on your merchant account.
Map pending, success and failure replies to the Magento order statuses your operations team already works with.
Supply a portal token and endpoint instead of static credentials to have merchant configuration resolved dynamically. HTTPS is required.
Upload a gateway logo into pub/media/coriunder/logo. Leave it empty and no image is rendered — nothing is bundled as a fallback.
pub/media/coriunder/logo
A standard redirect flow, deployed with the commands your team already runs.
Run setup:upgrade, deploy static content and flush the cache. No core files are touched.
The method appears on the payment step with your uploaded logo, when configured for the store view.
Magento hands the signed request to the Coriunder payment page. 3-D Secure runs here when enabled.
The reply is verified and the order moves to the pending, success or failure status you configured.
The module leans on Magento’s own primitives rather than rolling its own: the encrypted configuration backend for secrets, and the standard payment method interface for checkout.
Debug logging is opt-in and routed through Helper\Data::log(), so it is off unless you deliberately turn it on.
Helper\Data::log()
Current install-ready archive: 1.4.2.
coriunder/module-hosted
Deploy it the way you deploy every other Magento module.
Add the module under app/code/Coriunder/Hosted/, or use the install-ready archive.
app/code/Coriunder/Hosted/
Execute bin/magento setup:upgrade, then setup:static-content:deploy and cache:flush.
bin/magento setup:upgrade
setup:static-content:deploy
cache:flush
Open Stores → Configuration → Sales → Payment Methods → Coriunder (Hosted).
Enter the Merchant ID, base URL and personal hash, map your order statuses, and enable the method.
Deploy the module to app/code/Coriunder/Hosted/ or use the install-ready archive, then run bin/magento setup:upgrade, setup:static-content:deploy and cache:flush.
The personal hash and portal token are stored using Magento’s encrypted configuration backend, not as plain configuration values.
Yes. Supply a portal token and portal endpoint for dynamic merchant configuration instead of static credentials. The endpoint must be HTTPS.
Both. The Transaction Type setting selects whether funds are captured immediately or reserved for a later capture.
The one you upload into pub/media/coriunder/logo. If it is empty, no image is rendered — no logo ships with the module.
Yes. Authentication runs on the Coriunder hosted page; contact Coriunder to have it enabled for your merchant account.
Download the install-ready archive and connect your Magento 2 storefront to Coriunder.