The ebizmarts Payments Suite for Magento 1 / OpenMage — the Opayo by Elavon (formerly Sage Pay) integration — is still provided and maintained. It’s a legacy product — new features land in the Magento 2 extension — but it continues to receive compatibility and security fixes: the current release is 10.0.5 (May 2025, SHA-256 support), and the line includes OpenMage compatibility (verified against 19.5.3).
It supports the SERVER, FORM, DIRECT and PayPal integrations, plus REPEAT payments for backend orders. Some integrations are backend-only, and PCI DSS obligations vary by integration — SERVER inFrame is the most common choice.
How to get it
The Magento 1 extension isn’t distributed through a public repository. Contact ebizmarts support and we’ll supply the latest release package.
Requirements
Standard Magento 1 system requirements, plus PHP’s mbstring extension.
Installing
- On a live store, enable maintenance mode (
maintenance.flag), and editindex.phpto allow your own IP so you can keep working:
if (file_exists($maintenanceFile) && $_SERVER['REMOTE_ADDR'] != 'MY_IP')- If you use Magento Compilation, disable it before installing and recompile afterwards.
- Uncompress the package and copy all folders into the root of your Magento store.
- Refresh the cache at System → Cache Management — don’t skip this step.
- Enter valid MyOpayo panel credentials under System → Configuration → Sales → ebizmarts Payments Suite (Reporting & Admin API Integration).
- Configure the module under System → Configuration → Sales → Opayo. Log out of the admin and back in if the section doesn’t appear the first time.
Configuring
Licence key. Enter your licence key and activate it with the button next to the field. Licence keys are unique per domain — if a developer needs a test licence for a staging domain, contact support.
Test mode. Test-mode credentials must come from the MyOpayo test environment — sign in at sandbox.opayo.eu.elavon.com/mysagepay/login.msp (live accounts use live.sagepay.com/mysagepay/login.msp). Live credentials won’t work against the test servers.
Transaction currency. Choose whether transactions use Magento’s base currency, the store-view currency, or the currency selected in the currency switcher.
Integration requirements — as with Magento 2, register your site’s IP address in MyOpayo → Settings → Valid IP’s for every integration:
| Integration | Additional requirement |
|---|---|
| SERVER (inFrame or redirect) | IP registration only |
| FORM | Encryption key, from MyOpayo → Settings → Admin (main admin user) |
| DIRECT / PI | API credentials — in MyOpayo open the Administrator tab and choose Create API credentials |
| PayPal | PayPal enabled on your Opayo account |
The Reporting & Third Man API credentials (set during installation, step 5) power fraud information and transaction reporting in the admin.
Common errors
| Problem | Fix |
|---|---|
| SameSite cookie error — Chrome blocks the payment callback cookies | System → Configuration → General → Web: enable HTTP Only and append /;Secure;SameSite=None to the cookie path, or set the equivalent header in Apache/Nginx |
| Error 4006 — TxType not supported | Contact Opayo support with your vendor name and the attempted txtype (in the logs); for PayPal, ask them to enable the “Complete” option |
| Error 4020 — invalid IP address | Register your server’s IP in MyOpayo under Settings → Valid IP’s; a simulator account helps identify the exact IP |
| Error 5006 — redirection URL failure | Check firewall rules, disable maintenance-mode/site restrictions and basic auth on POST callbacks, disable SSL 3.0, and remove the MageCom_ReCaptcha module if present |
| Payment fails and the checkout reloads | Remove minified jQuery from the checkout layout XML; check OneStepCheckout compatibility; re-enable symlinks if SUPEE-9767v2 disabled them. Also set Use SID in frontend to Yes (System → Configuration → General → Web) and, for SERVER, Validate HTTP_USER_AGENT to No |
| Place order throws a 500 error | Reveal the real error: uncomment ini_set('display_errors', 1); in index.php and add Mage::setIsDeveloperMode(true); |
| Module can’t create its database tables | Back up, then run the module’s queries.sql manually — adding your table prefix to the CREATE TABLE statements if you use one |
| Error 4028 — related transaction not found | You’re repeating against a cancelled transaction; only active, successful transactions can be repeated |
| “Page not found” behind the SERVER iframe in IE10 | Known IE10 HTTPS-iframe bug — no module-side fix |
| SERVER iframe not displaying | Twitter Bootstrap’s modal CSS overrides the iframe — remove those rules from bootstrap.css |
| Google Analytics shows Opayo referrals | Add the Opayo domains to your GA referral-exclusion list |
| Clearing TEST orders | When deleting test orders, also back up and clear the module tables: sagepaysuite_action, sagepaysuite_paypaltransaction, sagepayreporting_fraud, sagepaysuite_tokencard, sagepaysuite_transaction |
Fatal error on Authorise & Capture — Call to a member function getMethod() on boolean |
The session’s order id was lost during invoicing — set both Server and Save Order Before to Yes in configuration |
Changelog
10.0.5 · 2025-05-23
Fixed
- SHA-256 support, per Opayo’s XML API changes
10.0.4 · 2025-05-21
Fixed
- Occasional crashes when viewing cart or order details
10.0.3 · 2024-10-08
Fixed
- Fraud check could override other orders’ fraud data
10.0.2 · 2024-09-04
Added
- Compatibility with OpenMage 19.5.3
10.0.1 · 2024-01-22
Fixed
- Bug in the phone validation for UK phone numbers
10.0.0 · 2024-01-18
Added
- URL update compatibility: ready for the new Elavon and Opayo URL changes
Fixed
- cURL version issues
Removed
- MyAccount token creation
Earlier history
The Magento 1 line goes back to 2011. In compressed form: 4.2.x (2017–2022) brought 3-D Secure v2 and SCA support, Drop-In card entry, MOTO improvements, token management, fraud scoring and PHP 7.2 compatibility; 3.0.x (2013–2015) added the dashboard, basket XML, orphan-transaction recovery and multi-currency support; 1.x (2011–2012) established the core integrations, PayPal Express, token cards and 3-D Secure. Contact support if you need the detailed release notes for an older version.