First Data Payments
$39.00

One Plugin. Two Gateways. Zero Card Data on Your Server.

Your First Data account works hard. Your Joomla ecommerce store should work with it — US Global Gateway e4, UK IPG Connect, and a hosted checkout that keeps card data off your hands entirely.

2
Gateway protocols in one install
SAQ-A
Lightest PCI compliance tier
3
IPG checkout collection modes
Auto
Confirmation emails on approval

Everything Your First Data Account Needs

Two gateways, one checkout, zero card data on your server. Here's what's packed inside.

Dual Gateway in One Plugin

US Global Gateway e4 and UK IPG Connect coexist in one install. Switch between them with a single toggle. No second plugin, no duplicate settings, no second support contract.

Hosted Payment Page (SAQ-A)

Card data never touches your Joomla server. First Data collects, validates, and processes — you get a signed result. PCI scope drops to SAQ-A, the shortest and simplest self-assessment questionnaire.

Response Signature Verification

Every gateway response is hash-verified before your store confirms an order. Forged approvals and replayed transactions fail the check. Response validation ships on by default — the setting that protects you is already set.

Pre-Authorization Mode

Hold the card without charging it. Capture when you're ready to ship, the item is confirmed available, or the custom order is complete. No refund-and-recharge. No awkward customer conversations about pending charges.

Three IPG Checkout Modes

Pay Only, Pay Plus, and Full Pay control what the hosted page asks your customers to fill in. Digital goods need less. Physical shipments need more. You decide — customers don't answer questions they don't need to.

Order Status Mapping + Auto Emails

Map First Data outcomes to the J2Commerce order statuses your workflow uses. Confirmed order triggers the notification engine — email sent, status updated, fulfillment kicked off. No manual checking required.

Payment Surcharge

Add a named surcharge as a percentage, a flat fee, or both. Apply a tax profile to it if your jurisdiction requires. The surcharge appears as a transparent line item — no hidden cost, no awkward fine print.

Geozone Restriction

Show this payment method only to customers in regions where your First Data account is active. Global Gateway e4 for North America, IPG Connect for Europe — with the right geozone, customers only see what applies to them.

Level-3 Processing (US)

Pass line-item data to First Data GGe4 for B2B interchange optimization. Corporate and purchasing cards qualify for lower interchange rates when line-item detail is present. The savings on high-volume B2B orders are real and recurring.

The Forgery Problem — Solved Before You Even Had to Ask

A lot of payment plugins accept whatever the gateway sends back and confirm the order. That's a forged-approval waiting to happen. This plugin verifies the gateway's response with a cryptographic hash before it trusts a single thing. If the numbers don't check out, the order stays unconfirmed and your admin group gets an email. The whole thing happens in the background, invisibly, every time.

  • SHA-256 hash verification for UK IPG Connect responses
  • MD5 relay-response hash check for US Global Gateway e4
  • Response validation on by default — the secure setting is already set
  • Double-charge protection catches duplicate gateway posts before they confirm

Two Gateways, One Admin Screen, Zero Configuration Theater

US Global Gateway e4 uses a completely different signing scheme, field names, and endpoint from UK IPG Connect. Most merchants running both regions either paid for two separate integrations or gave up and routed everything through a third processor they didn't want. This plugin brings both gateways under one configuration screen. One toggle, two protocols, separate credential sets that never get confused.

  • US mode shows only US fields — UK fields stay out of the way
  • UK mode shows IPG Connect fields — Sale or Pre-Auth, three checkout modes
  • Full sandbox credential sets for both modes — test without touching live
  • Level-3 line-item data toggle in US mode for B2B interchange savings

Real-World Use Cases

A wholesale distributor has run First Data Global Gateway e4 for six years — negotiated rates, established bank relationship, zero appetite to change processors. They enable US mode, enter their credentials, flip Level-3 processing on, and map the confirmed status to their existing "Processing" order state. Corporate card orders route through at commercial interchange rates. Savings compound every month. Nobody filled out a new merchant application.

A UK fashion retailer migrates their Joomla store to J2Commerce and needs a checkout their European customers recognize. They enable UK/EU mode, enter their IPG Connect store name and shared secret, set transaction type to Sale, and leave checkout mode on Pay Only since shipping is collected separately on the store side. Response validation is already on. One week of sandbox testing later — hash verification confirmed, test orders processing correctly — they go live. European customers see a PSD2-compliant hosted checkout. The abandoned cart rate falls.

A custom furniture studio takes orders online with a six-to-eight week build lead time. They can't capture payment at checkout — materials cost and availability aren't confirmed at that point. Pre-Authorization mode holds the card at checkout for the quoted amount; capture happens when the piece is complete and ready to ship. The admin notification group gets an email if anything fails at the gateway — before the customer's "what happened to my order?" call arrives. Orders don't fall through the cracks. Customers don't get surprised.

Your First Data Account Has Been Waiting Long Enough

One plugin, two gateway protocols, a hosted checkout that keeps card data off your hands, and a response verifier that doesn't take the gateway's word for it. Install it. Configure it. Go live. That's it. That's the extension.

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

Fix Reject a gateway transaction already applied to a different order (cross-order replay)

Fix Defer persisting gateway transaction id/status until signature + amount pass

Improvement Serialize order finalization with a row lock to prevent concurrent double-finalize

Improvement Key the double-charge guard on the paid order state, not a present transaction id

New Feature Localize the AMOUNT_MISMATCH and DUPLICATE_TRANSACTION rejections in all 21 languages

Update Order confirmation email and history still fire once for the genuine payment callback

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.