VoguePay
$39.00

Your African Store Deserves a Real Checkout

Nigerian and West African buyers want to pay. VoguePay lets them. Hosted checkout, hardened server-side verification, multi-currency conversion — all wired into your Joomla ecommerce store.

Everything You Need to Accept VoguePay on Joomla

18 features. One plugin. A checkout that African buyers actually complete.

Hosted Checkout — PCI Off Your Plate

Buyers pay on VoguePay's servers. Card data never touches your Joomla install. You are not in scope. Sleep better.

Three-Layer Fraud Verification

Every callback is verified server-side: merchant ID, paid amount, transaction status. Forged notifications get nothing.

Multi-Currency Conversion

Store in USD, buyers pay in naira. The correct converted amount submits to VoguePay automatically. No under-charges. No manual calculators.

Forward-Only Finalization

A confirmed order stays confirmed. Duplicate callbacks, retries, replayed notifications — none of them roll back a paid order. Ever.

Geozone & Order Amount Gating

Restrict VoguePay to Nigeria, West Africa, or any custom zone. Set minimum and maximum order amounts. The right payment method appears for the right buyer, automatically.

Five Checkout Messages, All Configurable

Selection, before-payment, success, error, cancel — every customer touchpoint has a text field in the plugin settings. Your words, your tone, your store.

Sandbox Mode with Dashboard Warning

One toggle for risk-free testing. The J2Commerce admin dashboard shows a yellow warning if you forget to turn sandbox off before going live. You cannot accidentally sell in demo mode without knowing it.

Three Order Status Mappings

Map Approved, Pending, and Failed outcomes to whichever statuses your fulfillment workflow uses. Your pickers, packers, and customer service team see exactly what they need to act.

Bootstrap 5 + UIkit Templates

Two included storefront templates — pick the one that matches your Joomla theme. Both work out of the box. No CSS edits required.

Verification That Does Not Trust the Callback

VoguePay sends a notification when payment completes. Most gateway plugins trust that notification. This one does not. Instead, it goes back to VoguePay directly — server to server — and asks VoguePay what actually happened. Then it checks three things before touching your order status:

  • The merchant ID in the response matches your account
  • The amount paid matches the order total to within one cent
  • The transaction status is genuinely Approved before order confirmation fires

A forged callback — the kind someone crafts with a guessed transaction ID and a "success" status — fails all three checks. Nothing happens. The order does not confirm. Your customer does not walk away with free goods.

A Checkout Your African Buyers Actually Complete

The payment button renders. Your customer clicks. A spinner appears, the button locks — no double-submits, no duplicate orders. The form auto-posts to VoguePay's hosted page, where local payment options are available and familiar. Payment goes through. VoguePay redirects back to your store. Your customer sees the success message you wrote in the plugin settings.

  • Double-submit protection baked into the checkout JavaScript
  • Customer notes saved before redirect so nothing is lost mid-journey
  • Custom thank-you article links on the confirmation page

Admin Order View With Transaction Lookup

Every order paid through VoguePay shows the VoguePay transaction ID right in the J2Commerce order detail view — linked directly to your VoguePay merchant portal. One click and you are looking at the transaction in VoguePay. No tab-switching, no manual lookup, no copying IDs between windows.

  • Transaction ID displayed and linked on every paid order
  • Sandbox indicator visible in the admin view when test mode was active
  • Full transaction details recorded on the order for audit and dispute resolution

Real-World Use Cases

A Lagos-based clothing store sells to buyers across Nigeria, Ghana, and Côte d'Ivoire. International payment options have high failure rates for local debit cards. They add VoguePay, geo-restricted to West African countries. Buyers in those zones see VoguePay at checkout — a familiar, working option. Buyers outside those zones never see it. Cart abandonment on the payment step drops. Orders stop bouncing at the gateway. The store finally has a checkout that matches its market.

A Joomla store selling eBooks, templates, and online courses to Nigerian professionals adds a thank-you Joomla article that contains the download link. Customer pays via VoguePay, lands on the confirmation page, sees the article with their download. No manual fulfillment. The customer note captured at checkout — saved server-side before the buyer ever leaves your store — carries any delivery instructions through to the order record. Clean. Automatic. Works.

A store operating in USD with African buyers using naira or cedis. Each order captures the exchange rate at checkout. When the VoguePay form submits, the converted gateway amount is exactly what VoguePay charges. The verification step confirms VoguePay charged that exact amount — not more, not less. Disputes stay manageable. Bookkeeping stays clean. The admin order view shows the transaction ID linked to the VoguePay portal. Every order is traceable in under a click.

Stop Losing African Sales at Checkout

Nigerian buyers are ready to pay. Your Joomla ecommerce store should let them. Add VoguePay. Watch the abandoned carts stop piling up. That is simple math.

Translated In The Following Languages

Arabic Unitag (ar-AA), Chinese, Traditional (zh-TW), Danish (da-DK), Dutch (nl-NL), English (en-GB), English, USA (en-US), Finnish (fi-FI), French (fr-FR), German (de-DE), Greek (el-GR), Hebrew (he-IL), Italian (it-IT), Japanese (ja-JP), Norwegian Bokmål (nb-NO), Persian Farsi (fa-IR), Polish (pl-PL), Portuguese, Brazil (pt-BR), Portuguese, Portugal (pt-PT), Russian (ru-RU), Spanish (es-ES), Swedish (sv-SE), Turkish (tr-TR)


  • Developer J2Commerce
  • Extension Type Payment
  • J2Commerce Version 4.x, 6.x
  • Joomla Version 4.x, 5.x, 6.x
Language Translations
Arabic UnitagArabic Unitag
Chinese, TraditionalChinese, Traditional
DanishDanish
DutchDutch
EnglishEnglish
English, USAEnglish, USA
FinnishFinnish
FrenchFrench
GermanGerman
GreekGreek
HebrewHebrew
ItalianItalian
JapaneseJapanese
Norwegian BokmålNorwegian Bokmål
Persian FarsiPersian Farsi
PolishPolish
Portuguese, BrazilPortuguese, Brazil
Portuguese, PortugalPortuguese, Portugal
RussianRussian
SpanishSpanish
SwedishSwedish
TurkishTurkish

New Feature Initial J2Commerce 6 release of the VoguePay hosted-redirect payment gateway

New Feature Hardened server-side verification: API poll + merchant-id match + amount match

New Feature Forward-only, idempotent finalization (never downgrades a paid order)

New Feature Multi-currency charge conversion on every path

New Feature Sandbox/test mode (merchant id auto-switches to demo)

New Feature Bootstrap 5 and UIkit storefront template variants

Improvement Migrate from J2Store v4 FOF plugin to native Joomla 6 namespaced MVC

Improvement Convert jQuery checkout to vanilla ES6 with double-submit guard

New Feature Geozone restriction, thanks-article, and customizable checkout messages

New Feature 20-language translations

Deletion Drop legacy J2Store FOF base class, $vars templates, and manual file logging

Update Requires Joomla 6.x + J2Commerce 6.x + a VoguePay merchant account

Update J2Commerce/J2Store v4 and Joomla 4/5 plugin support

Stay Updated

Subscribe for free and be the first to know about the latest features, updates, and new additions.