PrestaShop · coriunder module

One module, every PrestaShop from 1.7.8 to 9.1.

Upload the ZIP in the Module Manager, enter your Merchant ID and Personal Hash, and the Coriunder payment option appears at checkout. Shoppers pay on the hosted page and a signed webhook moves the order to the right state.

1.7.8–9.1
PrestaShop
3-D Secure
Supported
Signed
Webhooks
What you get

Built for PrestaShop, not ported to it

A standard PrestaShop module — no overrides, no theme surgery.

Hosted payment page

Shoppers pay on Coriunder’s page and return to your order confirmation. Card data never reaches your PrestaShop installation.

Order state mapping

Reply 000 becomes Payment accepted, 553 becomes 3-D Secure pending, and anything else becomes Canceled.

Signed webhooks

The dedicated webhook controller verifies the signature before the order state changes.

Portal or static credentials

Provide Merchant ID plus Personal Hash, or a Portal Token plus Portal Endpoint for dynamic merchant configuration.

Optional gateway logo

Upload an image to show beside the payment option, or leave it empty for a text-only method. A Remove Logo switch clears it.

Hosted page language

Choose the display language of the Coriunder payment page, defaulting to en-US.

How it works

From cart to confirmed order

A redirect flow with a dedicated webhook controller settling the result.

Shopper picks Coriunder

The payment option appears at the payment step once the module is enabled and credentials are saved.

They pay on the hosted page

The redirect controller sends the signed request to the Coriunder payment page. 3-D Secure runs here when enabled.

They return to your store

The shopper lands back on the order confirmation page.

The webhook sets the state

Coriunder POSTs to /module/coriunder/webhook; the verified reply code maps to the final order state.

Built for trust

Verified before anything changes state

The module keeps its redirect and webhook controllers separate, and no order state changes until a signed webhook has been verified against your Personal Hash.

Debug Logging writes payment events to PrestaShop’s own log system, so you can trace an order under Advanced Parameters → Logs without bolting on extra tooling.

See the technical documentation
  • Signed requests. Payment requests are signed with your Personal Hash before leaving PrestaShop.
  • Verified webhooks. The webhook controller validates the signature before touching order state.
  • Explicit state mapping. Reply codes map to PS_OS_PAYMENT, PS_OS_PREPARATION and PS_OS_CANCELED — nothing is inferred.
  • HTTPS gateway URL. The hosted payment page is reached over HTTPS.
  • Native logging. Debug events go to PrestaShop’s log system rather than ad-hoc files.
  • Credential separation. Either static credentials or portal configuration is used — never a silent mix.
Requirements

Check your store in ten seconds

Current release: 1.3.1.

RequirementSupported
PrestaShop1.7.8 through 9.1.x (runtime verification recommended per shop/PHP combination)
PHPA version supported by the selected PrestaShop release
AccountCoriunder Merchant ID + Personal Hash
Webhookhttps://your-store.com/module/coriunder/webhook
Gateway URLDefault https://uiservices.coriunder.cloud/hosted/default.aspx
Transaction Typesale or authorization
Installation

Live in four steps

The ZIP must contain the module folder at its root before you upload it.

Prepare the ZIP

Confirm the archive contains coriunder/ at its root, with coriunder.php inside.

Upload

Go to Back Office → Modules → Module Manager → Upload a module.

Configure

Set Enable to Yes and enter your Merchant ID and Personal Hash, or your Portal Token and Endpoint.

Go live

Confirm the Gateway URL, pick a display language and transaction type, and save.

Questions

Frequently asked

The payment option is not showing at checkout.

Confirm the module is enabled and that valid credentials — or a complete portal configuration — have been saved.

Orders are stuck in Preparation.

Verify the webhook URL is publicly accessible and that no firewall or security module blocks POST requests from Coriunder.

I am seeing signature errors.

The Personal Hash must match the value in the merchant portal exactly, with no extra whitespace.

How do reply codes map to order states?

000 is Payment accepted, 553 is 3-D Secure pending, and any other code cancels the order.

Do I have to use a gateway logo?

No. Leave the Gateway Logo field empty for a text-only payment option, and use Remove Logo to clear one you uploaded earlier.

Where do I find the logs?

Enable Debug Logging, then check Advanced Parameters → Logs for detailed event traces.

Ready to accept payments?

Download the module and connect your PrestaShop store to Coriunder.