The account that never changed
The vendor name from the Sage Pay days still works. The retailer moved to PI for 3DS2 without touching the account or the extension.
Opayo by Elavon · formerly Sage Pay
The Opayo integration that has followed the gateway through every name.
Sage Pay became Opayo in 2020, and Opayo is now part of Elavon. The Payments Suite has run on this gateway for over a decade with existing accounts unchanged. PI for a fully embedded checkout, Form and Server for a hosted page, PayPal and local European methods alongside cards, and the fraud controls you set, per store view.
- Paid by card in the embedded checkoutOpayo PI · 3DS2
- Passed the store's AVS/CV2 rules
- Captured when the order shipped
Why it matters
What changes for the business.
The protocol that fits your checkout
PI for an embedded, on-site checkout; Form and Server for a hosted page that keeps PCI scope minimal. Switch protocols without switching extensions.
Fraud rules you control
3D Secure, AVS and CV2 checks, IP allow-lists and the rules you want enforced, set per store view in the Magento admin.
Authorise, then capture when ready
Deferred and authenticate-only transactions, with automated release when the order is ready to ship.
More than cards
PayPal and local European payment methods through the same account, and GBP, EUR, USD and AUD without a second gateway.
How it works
Step by step, from the first switch-on.
- 1
Connect your Opayo account
Enter the vendor name and keys from your existing Sage Pay or Opayo account. Nothing about the account changes.
- 2
Choose the protocol
PI for the embedded checkout with 3DS2, Form or Server for hosted pages. Each is configured per store view.
- 3
Set the rules
3DS, AVS/CV2 and IP rules, deferred or immediate capture, and the payment methods to offer, per store view.
- 4
Run it for years
Twelve months of updates and support with every licence, across Adobe Commerce and Magento Open Source from 2.2 to the latest 2.4.
Ways merchants use it
One retailer, one gateway, ten years.
UK and European merchants on Opayo, stores migrating from the old Sage Pay extension, and anyone who wants fraud rules that differ by storefront.
The rule for the trade store
The trade store view gets stricter AVS/CV2 and deferred capture on despatch. The consumer store keeps immediate capture. Same suite, two rule sets.
The PayPal buyer
A customer who only pays with PayPal checks out through the same integration, and the order in Magento looks like any other.
What you need
Before you switch it on.
- An Opayo by Elavon account (existing Sage Pay accounts work unchanged)
- ebizmarts Payments Suite on Adobe Commerce or Magento Open Source 2.2 or later
- The protocol, fraud rules and payment methods chosen per store view
- PayPal linked to the Opayo account if you want to offer it
Also in Payments Suite
Payments Suite for Hyvä CheckoutThe same suite, rebuilt for Hyvä Checkout: wallets, tokenised cards, 3DS2 and Recover Checkout, native to Hyvä.Apple Pay and Google PayOne-tap wallets in the checkout, on by default once enabled.Recover CheckoutStalled checkouts get a one-click resume link by email or SMS.Saved cards and 3DS2Cards vaulted as tokens; repeat orders in one tap, PCI scope kept small.Phone orders and payment linksMOTO from the admin with a secure prompt, or a pay-by-link by email or SMS.In-store and Tap to Pay on iPhoneTerminals at the counter and Tap to Pay on any recent iPhone, one ledger.All 11 Payments Suite featuresBack to the overview.
Questions
What merchants ask before they turn it on.
Is Opayo the same as Sage Pay?
Yes. Sage Pay was renamed Opayo in 2020, and Opayo is now part of Elavon, which keeps the Opayo name for the gateway.
Which protocols does the suite support?
PI, Form and Server, plus PayPal and local European payment methods alongside cards.
Can I defer capture until despatch?
Yes. Deferred and authenticate-only transactions with automated release of deferred orders.
Are fraud rules per store view?
Yes. 3DS, AVS/CV2 and IP allow-lists are configured per store view.
Does it work on Magento 1?
The Magento 1 extension remains in the store for existing merchants. New development is on Magento 2 and Adobe Commerce.
Turn it on, or ask us first.
The payments team will tell you plainly what switching this on involves for your store, and what it costs.