OpenCart payment gateway extension for high-risk stores: 25 methods, instant payouts, no KYC
This is the WcPay OpenCart payment gateway extension: a native
OpenCart 4 extension, delivered as a single .ocmod.zip archive, that
registers twenty-five independent payment gateways in your admin and settles every order
in stablecoin to a wallet you control. No merchant account, no underwriting file, no
chargebacks, and no company registration.
It exists for one situation. You run an OpenCart store, your product category is one
that acquiring banks label high risk, and either no processor will take you or the one
that did has already closed your account and kept a reserve. This OpenCart payment gateway extension removes the underwriting relationship entirely: there is no account for a risk
department to terminate, because the money never passes through an account in your name at
a bank.
Your customer pays by Visa, Mastercard, Apple Pay, Google Pay, Revolut, Cash
App, Klarna, iDEAL, UPI or Interac, in their own currency, on a hosted form. You receive
the payout minutes later. Most buyers never realise a stablecoin was involved.
What this OpenCart payment gateway extension actually is
A native OpenCart payment gateway extension, not an iframe
The OpenCart payment gateway extension is written against the OpenCart 4 controller, model and event
architecture — the namespaced structure introduced in that release. It is not a generic
redirect button wrapped in an OpenCart skin, and it is not a hosted checkout that takes
your customer off your domain for the whole order. Each gateway appears in
Extensions › Payments exactly like a built-in OpenCart payment
method, with its own edit screen, its own settings row in the database and its own entry
in the checkout list.
That matters for a practical reason. An iframe-based gateway cannot read your geo
zones, cannot set your order status, and cannot be renamed per store. A native OpenCart payment gateway extension can do all three, and this one does.
Twenty-five independent gateways, not one with a dropdown
Installing this OpenCart payment gateway extension puts twenty-five separate payment
gateways in your admin. Each
one is configured on its own, and nothing is shared between them:
| Setting | What it controls |
|---|---|
| Status | Whether this single method appears at checkout. The others are unaffected. |
| Title | The label your customer reads. Write what converts in your market, in your language. |
| Description | The short line under the title at checkout. |
| Wallet Address | Where this method’s payouts land. Each gateway can use a different address. |
| Icon URL | Any image URL, so you can match your own checkout design. |
| Icon Size | A percentage, so a tall logo and a wide one can sit on the same row without looking wrong. |
| Paid Order Status | The OpenCart status applied on confirmation — Complete for digital downloads, Processing for physical goods. |
| Geo Zone | Restrict the method to a region, using OpenCart’s native geo zones. |
| Sort Order | The position of the method in the checkout list. |
Per-gateway wallets are the setting most merchants underestimate. They let you split
revenue by brand, by partner, by country or by accounting stream without running a second
store — something no single-gateway OpenCart payment gateway extension can do.
What is in the OpenCart payment gateway extension download
- The
.ocmod.ziparchive, installable through the standard OpenCart
Extension Installer. No FTP, no file editing, no developer. - An activation key bound to your domain. One key unlocks all twenty-five gateways at
once; you never activate methods one at a time. - A step-by-step installation and configuration guide, with the settings that matter
explained rather than listed. - Setup support by email, included with every plan.
Delivery is by email, normally within minutes of payment confirmation.
Why mainstream processors decline OpenCart stores
OpenCart is one of the most widely deployed open-source carts in the world, and it is
especially popular outside the United States and Western Europe — North Africa, the Middle
East, South Asia, Eastern Europe, Latin America. That geography is exactly where card
acquiring is hardest to obtain, which is why an OpenCart payment gateway extension that
works without underwriting is worth more there than a lower headline rate.
Mainstream processors underwrite a merchant, not a shopping cart. Their risk teams look
at your product category, your country of incorporation, your expected dispute ratio and
your ability to supply audited financials. A one-person digital business selling
subscriptions from Casablanca or Karachi fails that assessment almost every time, however
clean the store is.
When an application is accepted, the terms often make the account barely usable:
rolling reserves of five to ten per cent held for six months, payout delays of seven to
fourteen days, and a dispute threshold above which the account is terminated by email with
the balance held for another ninety days.
The three failures this OpenCart payment gateway extension removes
Account closure. A gateway a third party can switch off is not
infrastructure, it is a loan. Settlement here goes to a wallet you hold the keys to, so
there is nothing to close.
Chargebacks. In digital goods, friendly fraud is structural: the
customer received the product, used it, and disputes the charge anyway. A stablecoin
transfer cannot be clawed back by the sender, so a reversal at card level cannot empty
your wallet.
Settlement delay. Cash flow kills small merchants faster than fees do.
Funds arrive minutes after the card is approved, with no payout cycle and no minimum
threshold.
The payment methods your customer sees
The OpenCart payment gateway extension ships with twenty-five methods, in three
families. You decide which appear; enable two or enable all of them.
| Family | Methods |
|---|---|
| Cards and wallets | Credit card through Stripe, credit card through PayPal, Apple Pay, Google Pay, Revolut Pay, Cash App, Binance Pay |
| Local rails | iDEAL (Netherlands), UPI and IMPS (India), Interac (Canada), Klarna (parts of Europe) |
| On-ramps | Coinbase Pay, Blockchain.com, Ramp Network, MoonPay, Transak, Banxa, Topper, Bitnovo, Robinhood, Simplex, Sardine, UTORG, TransFi, Meld, Particle Network, Alchemy Pay |
Each provider sets its own minimum, from around two dollars for cards up to a hundred
for UPI and Interac, and each has its own country coverage. Running several side by side
is the simplest way to lift approval rates: when one rail pauses a country without notice,
the others keep taking orders. That is a deliberate design choice in this OpenCart payment gateway extension — twenty-five independent gateways fail independently.
How a payment moves through the OpenCart payment gateway extension
Four steps, from the moment your customer presses Confirm Order to the moment the money
is in your wallet and the order is marked paid.
1. Currency conversion
The OpenCart payment gateway extension takes the OpenCart order total in whichever store currency the customer is
browsing — dollar, euro, dirham, rupee, pound — and converts it to its stablecoin
equivalent against a live rate. Nothing is estimated locally, so the figure your customer
pays and the figure you expect to receive come from the same source.
2. A single-use receiving address
A receiving address is generated for that one order and stored against it with a short
confirmation token. Because the address is never reused, two customers paying the same
amount in the same minute can never be confused with one another. This is the single most
common failure in hand-rolled integrations, and the OpenCart payment gateway extension
handles it without you thinking about it.
3. The card payment
Your buyer goes to a clean hosted form: name, card number, expiry, security code, email
for the receipt. No account creation, no wallet app, no crypto knowledge. Card details are typed on the provider’s own PCI-compliant infrastructure and never
reach your server, so the OpenCart payment gateway extension never handles a card
number.
4. Confirmation and payout
When the payment settles, the provider calls your store back on a signed URL. The OpenCart payment gateway extension verifies the amount against what was expected, writes the transaction reference into the
order history, and switches the order to the status you configured. Short payments are
flagged rather than silently approved.
What this OpenCart payment gateway extension protects you from
Four failures cost real money in payment integrations. The OpenCart payment gateway extension handles all four, and each one is worth understanding because you can defeat
the protection by accident.
Underpayment
The expected value is recorded when the payment starts. When the confirmation arrives,
the amount actually received is compared against that figure. Anything meaningfully below
it is written to the order history and marked failed, so a customer cannot pay a fraction
of the total and walk away with the product. Rate movement and provider fees mean the two
figures are rarely identical, so the comparison runs against a tolerance rather than strict
equality — a few cents of drift does not refuse an honest buyer.
A replayed confirmation
Providers sometimes send the same confirmation twice. Without a guard you ship, invoice
and notify twice. The OpenCart payment gateway extension checks whether the order has already been
processed and
acknowledges the duplicate without crediting it again.
A wrong payout address
Saving a payout address in the OpenCart payment gateway extension triggers a real
request to the payment API. If the format is
wrong, if it points at a token contract rather than a wallet, or if your store domain is
not accepted, you see the exact reason on screen while you are still in the admin — not in
a support ticket after a lost sale.
A renamed archive
This is the one mistake that breaks installation, and it is worth knowing before you
start. OpenCart derives the extension folder name from the filename of the archive. Rename
the .ocmod.zip before uploading it and the extension installs into the wrong
place: the gateways appear in the list but their settings pages return Page Not Found.
Upload the file exactly as you received it.
Installing the OpenCart payment gateway extension in six steps
Installing the OpenCart payment gateway extension takes about two minutes, with no FTP
access and no file editing.
- Upload the archive. Extensions › Installer,
upload the file under its original name. - Run the installation. Press the green + beside the uploaded
entry. OpenCart unpacks the files and creates the payment tracking table that matches
confirmations back to orders. - Open the payments list.
Extensions › Extensions, choose the Payments type.
The twenty-five gateways are now listed; install the ones you want to offer. - Activate your licence. Open any installed gateway with the blue
pencil. Paste the key from your email into the activation card at the top and press
Activate — all twenty-five unlock at the same moment and the settings form appears
underneath. - Enter your payout wallet. Paste your address into the Wallet Address
field. It is validated against the API when you save. - Set the title, icon and paid status. Write the checkout label, point
the icon at your logo, pick the order status to apply on confirmation, optionally
restrict the method to a geo zone, set Enabled and save.
Then place one small real order through the OpenCart payment gateway extension and
watch it end to end: the order should flip to your
paid status, the funds should land at the address you entered, and the transaction
reference should be in the order history. Four checks, five minutes, and you find out now
rather than on your first real customer.
Requirements for the OpenCart payment gateway extension
| You need | You do not need |
|---|---|
| An OpenCart 4.x store on HTTPS Outgoing HTTPS requests allowed from your server A wallet address you control A reasonably short store domain |
A company — no LLC, no LTD, no trade register extract A KYC file — no ID, no proof of address, no bank statements A merchant account application Any crypto knowledge |
OpenCart 3 and earlier use a different extension format and are not supported; you
can check your version under Dashboard › System Information, and
the OpenCart
documentation covers upgrading. On the domain length: the payment API enforces a limit
on the confirmation URL it accepts, and an unusually long domain can exceed it. If you are
unsure, send us your domain and we will check it
before you buy.
Which niches this OpenCart payment gateway extension accepts
Card networks maintain internal lists of merchant categories they treat as elevated
risk, because of dispute rates, regulatory exposure or reputational concern. Being on that
list does not make a business illegitimate — it makes it unbankable through conventional
rails. This OpenCart payment gateway extension was built for merchants in exactly that
position.
- IPTV and streaming — subscription reselling, restream panels,
set-top bundles, lifetime access plans. - Digital products — software licences, source code, templates,
ebooks, courses, design assets, account top-ups. - Supplements and nutraceuticals — sports nutrition and wellness
formulas, including trial and recurring offers. - Forex and trading education — signal groups, prop-firm preparation,
indicators, expert advisors, mentoring. - Adult and dating — content subscriptions, memberships, creator
platforms. - Travel, tickets and vouchers — prepaid cards, gift codes, event
access, anything with a long delivery window.
Not every product is eligible, and a small number of categories are excluded outright
for legal reasons. Check the
supported countries and
regions page, or ask before purchasing — we would rather tell you no in advance than
sell you a licence you cannot use.
Licence plans for the OpenCart payment gateway extension
One licence covers all twenty-five payment methods. There is no per-transaction plugin
fee and no revenue share; an API partner fee of roughly 4.5 % applies at the provider
level, and the current breakdown is on the
processing fees page.
| Plan | Price | Sites | Best for |
|---|---|---|---|
| Monthly | $79.99 / month | 1 website | Testing the rails against your real traffic before committing. |
| Annual | $169.99 / year | 1 website | A store that is already selling. Two months of the monthly plan costs more than a year of this one. |
| Lifetime | $399.99 one-time | 3 websites | Several stores, or a store you intend to run for years. Pays for itself in under five months against the monthly plan. |
The plans differ only in duration and in the number of sites. Every plan includes all
twenty-five methods, instant payouts, zero chargebacks, Apple Pay and
Google Pay, Revolut Pay and setup support — no feature is held back for a higher
tier. The payment and refund policy applies
to all three.
If you also run WooCommerce, PrestaShop or WHMCS, those platforms have their own
modules: the WooCommerce edition,
PrestaShop and
WHMCS. Licences are per
platform; write to us for a multi-platform bundle
rather than buying them separately.
Security: what never touches your server
The less your store handles, the less you have to defend. The OpenCart payment gateway extension is built so the sensitive parts never reach you in the first place.
Card details never arrive. The card form is hosted on the payment
provider’s PCI-compliant infrastructure. Numbers, expiry dates and security codes do not
transit your server and are not written to your logs, which keeps your store out of scope
for card data handling and means a compromise of your hosting cannot expose customer cards.
That redirect model is also what keeps a merchant in the lightest self-assessment bracket,
PCI DSS SAQ A — though your acquirer, not
us, decides which questionnaire applies to you.
Confirmations cannot be forged. Every order is issued a single-use
token when its receiving address is created. The callback must present that exact token,
which identifies the order and authenticates the request at the same time. A confirmation
without a valid token is rejected outright.
Failures are visible. Every transaction the OpenCart payment gateway extension rejects writes its exact cause
to OpenCart’s error log, so a configuration problem shows up as a readable line rather than
as a mysterious run of failed orders.
Settlement runs on
Polygon, chosen for
low transfer cost and fast finality, so a payout is not eaten by network fees on a small
order.
What this OpenCart payment gateway extension does not do
A product page that only lists strengths is not worth trusting.
It does not settle into your bank account. The OpenCart payment gateway extension pays out as stablecoin to your wallet. If your business needs fiat directly into an IBAN, a conventional acquirer
is the right tool — assuming one will take you.
It does not refund automatically. A stablecoin payout is final in both
directions. That is what protects you from chargebacks, and it is also what stops you
reversing a payment with one click: to refund, you send funds from your wallet or credit
the customer’s account. Write that into your terms of sale before you open payments, not
after the first request.
It does not support OpenCart 3. The namespaced architecture this
OpenCart payment gateway extension is built on arrived with OpenCart 4.
It does not guarantee provider uptime. Rails occasionally pause a
country or a category without notice. The OpenCart payment gateway extension is built so one rail going quiet never stops the
others, which is the practical reason to keep several enabled — but no uptime
figure is promised, because promising one for someone else’s infrastructure would be a
lie.
It does not handle your tax or your accounting. It takes payments and
tells you they arrived.
Questions asked before purchase
Which OpenCart versions does the payment gateway extension support?
OpenCart 4.x only. Version 3 and earlier use a different extension format.
What exactly do I receive when I buy?
The .ocmod.zip OpenCart payment gateway extension, an activation key bound
to your domain, and the installation guide — by email, usually within minutes.
Does one key activate all twenty-five gateways?
Yes. Paste it into the activation card on any one gateway screen and all twenty-five
unlock at once. The key revalidates itself in the background, so a brief network problem
does not take your checkout offline.
Can my customer pay with an ordinary bank card?
Yes, and that is the normal case. Visa, Mastercard and American Express, in the
customer’s own currency, on a standard card form.
How fast do I receive the money?
Minutes after the payment clears. The OpenCart payment gateway extension has no
settlement cycle, no minimum payout and no rolling reserve.
Do I need a company or a KYC file?
Neither. Individuals and sole traders are accepted on exactly the same terms as
registered companies — that is the reason this OpenCart payment gateway extension
exists.
Can I use a different wallet for each payment method?
Yes. Every gateway stores its own payout address, so you can separate revenue by brand,
partner, country or accounting stream without a second store.
Are there holds, volume limits or bans?
None applied by us: with no merchant account in the conventional sense, there is nothing
to freeze. Individual providers apply their own minimum transaction amounts.
Will the plugin charge me per transaction?
No. The licence fee is the only thing we charge. The API partner fee of roughly
4.5 % is applied by the payment infrastructure itself.
Can I run this alongside my WooCommerce store?
Yes, and they can point at the same payout wallet. The licences are separate; ask us
about a bundle.
What happens if a customer underpays?
The order is marked failed with the transaction reference in its history, so you can
investigate rather than shipping against an incomplete payment.
Can I try it before buying?
There is no trial build, because a licence key is what unlocks the twenty-five gateways of the OpenCart payment gateway extension. What you
can do is read the whole flow on the
OpenCart gateway
page, which includes an interactive copy of the real admin settings screen and the
installation video, then ask us anything that is still unclear.
Support, updates and what happens next
Setup support for the OpenCart payment gateway extension is included on every plan, and
updates are free. The OpenCart payment gateway extension is versioned, so you can see what changed before you upgrade a live store.
If something is broken, we would rather hear about it than have you work around it. Four
questions resolve most of what reaches us, and you can check them yourself first: is the
archive still under its original filename, is the payout address the one you intended, is
the store on HTTPS, and does the OpenCart error log show a rejected transaction with a
reason.
If you are weighing this OpenCart payment gateway extension against a conventional
acquirer, or you are not sure which plan fits,
ask us before you buy — a pre-sales question costs
you nothing and saves a refund request.
Reviews
There are no reviews yet.