Ready-made module

Payment Hub PRO Adapter for OpenCart / ocStore

PAYMENT-HUB-PRO-OPENCART

OpenCart / ocStore Ready to install

Payment Hub PRO Adapter for OpenCart / ocStore

Payment Hub PRO Adapter connects the OpenCart / ocStore checkout to a separate Payment Hub Core: the store creates an intent, presents eligible PSPs and accepts signed results only.

OpenCart / ocStore 3.x

Platform version* Licensed domain* Payment Hub Core status*

Promotional installation

Installation and basic check by our team — free with promotion

2,990.00 грн. Ex Tax: 2,990.00 грн.

Updated14/09/2026

Files available after payment

No core file overwritesExtension Installer / OCMOD

12 months of updatesUpdated 14/09/2026

Developer supportReady to install

Clean codeDocumented structure

PRODUCT OVERVIEW

What this module does

Payment Hub PRO Adapter connects the OpenCart / ocStore checkout to a separate Payment Hub Core: the store creates an intent, presents eligible PSPs and accepts signed results only.

Payment logic is centralized while the store adapter stays thinProvider credentials, routing and integration logic live in Core; the store keeps native checkout, redirect and HMAC status verification.

PAY

Payment Hub ArchitectureSTORE ADAPTER · CORE SERVICE · HOSTED PSP

SIGNED FLOW

OpenCart / ocStore adapterCart, order, redirect and application of the paid status.

Payment Hub CoreMerchant shops, PSP accounts, intents, routing and callbacks.

LiqPay · MonobankHosted payment page; card data never passes through the store.

One Core for multiple stores and platforms

Every store receives its own Shop ID, API token and webhook secret. Core decides which PSPs are eligible for an order, while adapters avoid duplicating every provider integration.

2ready PSPsLiqPay and Monobank verified in real checkout.

HMACcallback verifyNo order status changes without a valid signature.

HTTPSbetween componentsCore must be publicly reachable for redirect and notify.

1 domainadapter licenceCore deployment is quoted separately.

How a payment moves

Cart contextSend amount, currency, order and merchant context to Core.

Payment intentCore returns eligible PSPs and selection data.

Hosted checkoutRedirect the buyer to LiqPay or Monobank securely.

Signed statusCore sends an HMAC callback and the adapter updates the order.

What the adapter does

Store configuration

Core URL, Shop ID, API token, webhook secret and paid status.

Native payment options

OpenCart / ocStore presents only methods eligible for the cart.

Webhook verification

Signature validation happens before any order change.

Order recovery

The PrestaShop adapter resolves the real order through cart ID.

Geo / status mapping

The OpenCart adapter respects geo zone and chosen paid status.

Readable source

A thin PHP adapter with no ionCube or encrypted files.

IMPORTANT INFRASTRUCTURE

Core service is required before adapter setup

The archive does not contain the Laravel Core and cannot talk to PSPs by itself. A deployed Core, merchant-shop record and at least one active PSP account are required.

Core URLPublic HTTPS endpoint.

CredentialsShop ID, API token and webhook secret.

PSP accountActive LiqPay or Monobank in Core.

Current version 1.0.0 scope

LiqPay and Monobank are implemented and verified. Other providers, bank-statement reconciliation, pay-link messaging and unified analytics are not included in this release.

Included with the purchase

Adapter for one platform and domain, readable source, guide, 12 months of updates and help connecting to an existing Core. Core deployment is a separate service.

Need a standalone iPay.ua checkout?iPay.ua Checkout PRO works without Payment Hub Core and may be simpler for a store using one provider.

Compare solutions

BUILT FOR COMMERCE

Module features

Thoughtful functionality for a real store, without unnecessary complexity.

One adapter, shared core

The store sends order context to Payment Hub Core while providers and credentials are managed centrally.

LiqPay and Monobank

The current version has been live-tested with both providers and their hosted payment flows.

HMAC-verified callbacks

Every incoming confirmation is checked against a dedicated webhook secret before changing an order.

Native checkout flow

OpenCart presents eligible options and redirects the buyer safely to the selected PSP.

Order status sync

After confirmation, Core notifies the store and the adapter applies the configured paid status.

Thin architecture

PSP secrets and complex provider logic stay out of the store adapter and are maintained in Core.

QUICK START

Launch together with Payment Hub Core

The purchase includes the store adapter. Deployment and operation of the separate Payment Hub Core are quoted separately, unless the client already has one.

Prepare Core

Deploy Payment Hub Core over HTTPS, create the merchant shop, enable a PSP and obtain Shop ID, API token and webhook secret.

Install the adapter

Upload the OCMOD, install the payment method and enter the Core URL and issued credentials.

Run a test payment

Verify intent creation, hosted-checkout redirect, callback signature and paid-status change on a real test order.

TECH DETAILS

Technical specifications

Payment Hub PRO Adapter connects the OpenCart / ocStore checkout to a separate Payment Hub Core: the store creates an intent, presents eligible PSPs and accepts signed results only.

Ready to installIn Stock

PlatformOpenCart / ocStore

Compatible versions3.x

InstallationExtension Installer / OCMOD

PHP versionPHP 7.4+

Licence1 domain

LocalisationУкраїнська, English, Русский

{ }

Need help or a custom change?

We can check compatibility, help with installation or adapt the module to your workflow.

Discuss the task

FAQ

Frequently asked questions

Developer support

Is Payment Hub Core included in the archive and price?

No. This is a store-adapter licence. Core is a separate Laravel application that must already be deployed and configured; its implementation is quoted separately.

Which payment providers work today?

Version 1.0.0 implements and live-tests LiqPay and Monobank. Other PSPs are not advertised as ready in this release.

Does the store receive card details?

No. Buyers enter payment details on the provider hosted checkout. The adapter handles an intent, redirect URL and signed status only.

Can several stores use one Core?

Yes. Core supports separate merchant-shop records and PSP accounts. Every store receives its own Shop ID, API token and webhook secret.

Shopping cart

Your cart is empty

Payment Hub PRO Adapter for OpenCart / ocStore

What this module does

One Core for multiple stores and platforms

How a payment moves