The ocmod package for OpenCart 3.0. Upload it through the Extension Installer, no core files touched.
Install the OCMOD package, point it at your approved production Coriunder URL, and take payments on the hosted page. The extension deliberately rejects HTTP and common sandbox, staging and demo endpoints, so a misconfigured store fails loudly instead of quietly.
After confirming, you will be taken to the Coriunder secure payment page.
A single OCMOD upload, then everything else happens in the OpenCart admin.
The shopper pays on Coriunder’s page and returns to your store. Card data never reaches your OpenCart installation.
HTTP is rejected, and so are common test, sandbox, staging, demo and development endpoints. The approved production URL must sit under coriunder.cloud.
coriunder.cloud
Payment notifications carry a signature that is verified before any order status changes, so a forged POST cannot mark an order paid.
Map pending/3DS, successful/paid and failed/declined replies onto the OpenCart order statuses your team already uses.
Use a live merchant ID and personal hash, or a live portal token and production portal endpoint for dynamic configuration.
Ships as coriunder_oc3.ocmod.zip, installed through the OpenCart extension installer — no core file edits.
coriunder_oc3.ocmod.zip
A redirect flow with a signed webhook backing it up.
The payment method appears at checkout once the extension is enabled and credentials are saved.
OpenCart hands the signed request to the Coriunder payment page over HTTPS. 3-D Secure runs here when enabled.
The shopper lands back on your confirmation page while the order awaits its verified result.
Coriunder POSTs the result to your store. The signature is verified, then the order moves to your mapped status.
This extension takes a deliberately strict line on configuration. A store pointed at an unapproved or non-HTTPS endpoint will not process payments, which is the correct outcome for a payment integration.
Before general enablement, take a current file and database backup and complete a controlled low-value live transaction.
Current extension version: 3.1.1.
Back up first, then install like any other OCMOD extension.
Take a current file and database backup before installing anything on a live store.
Upload coriunder_oc3.ocmod.zip through Extensions → Installer, then refresh the modification cache.
Open Extensions → Payments → Coriunder, enter your live credentials and production URL, and map your order statuses.
Complete a controlled low-value live transaction before enabling the method for all shoppers.
No. The extension intentionally rejects HTTP and common test, sandbox, staging, demo and development endpoints. Verification is done with a controlled low-value live transaction instead.
3.0.4.0, 3.0.4.1 and 3.0.5.0. Version 3.0.3.9 is expected to work but must be verified on your own store.
It must be reachable over publicly trusted HTTPS without a login, maintenance-mode block or CDN challenge in front of it.
Only if you prefer dynamic configuration. Either a live merchant ID plus personal hash, or a live portal token plus production portal endpoint, will work.
They sit in your configured pending/3DS status until the verified result arrives, then move to the paid or failed status you mapped.
No. The extension ships as an OCMOD package and installs through the standard OpenCart extension installer.
Download the OCMOD package and connect your OpenCart 3 store to Coriunder.