Three regions on one wall
UK, EU and US, each a store view with its own currency and rules, all paying into the same account and the same report.
Multi-store
Three regions, four currencies, one reconciliation.
An accessories brand sells from UK, EU and US storefronts on one Magento. The Payments Suite is installed once, configured per store view, settles each currency correctly and reports across all of it in one place. Finance closes the month from one ledger instead of three spreadsheets.
- Shopped on the EU storefront2 items · 96.00 EUR
- Paid in EUR, settled in EUR
- Order in the group report
Why it matters
What changes for the business.
Configure once, vary where needed
Credentials, fraud rules, 3DS settings and currencies per store view, from one extension and one admin.
Currencies settle correctly
GBP, EUR, USD and AUD on one Opayo account, each storefront in its own currency, no conversion surprises at settlement.
Finance sees the whole group
Reports and payouts cover every store, filterable by store view and currency, and flow to Xero, SAP or NetSuite as one feed.
Compliance without repetition
PCI scope, 3DS2 and tokenisation are handled the same way on every storefront because it is the same suite.
How it works
Step by step, from the first switch-on.
- 1
Install once
One Composer install of the Payments Suite on the Magento instance that runs all the storefronts.
- 2
Configure per store view
Set the Opayo vendor, currency, protocol and fraud rules per website or store view where they differ; inherit where they do not.
- 3
Customers pay in their store's currency
The checkout charges the storefront's currency and settles it on the matching currency of the account.
- 4
Reconcile as a group
Transactions and payouts from every storefront appear in one report, exportable and ERP-ready.
Ways merchants use it
One brand, one month-end.
Groups with regional storefronts, brands selling in several currencies, and finance teams reconciling more than one site.
The new storefront
An Australian store view goes live. It inherits the suite and gets AUD and its own fraud settings in an afternoon, with no second installation.
Month-end
One export, four currencies, every payout with fees and order references. The ERP posts it, and the close is a morning's work.
What you need
Before you switch it on.
- ebizmarts Payments Suite installed once on the Magento instance running all the storefronts
- An Opayo account with the currencies you sell in enabled
- Per-website or per-store-view configuration for credentials, currency and fraud rules
- Optional ERP connector for Xero, SAP or NetSuite
Also in Payments Suite
Opayo by ElavonEvery Opayo protocol, fraud controls per store view, deferred capture and PayPal, on the integration stores have run for a decade.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.All 11 Payments Suite featuresBack to the overview.
Questions
What merchants ask before they turn it on.
Do I need a licence per storefront?
No. One install covers every storefront on the Magento instance.
Can storefronts have different fraud rules?
Yes. 3DS, AVS/CV2 and other rules are configurable per store view.
Which currencies are supported?
GBP, EUR, USD and AUD on one Opayo account, matched to the store view.
Can I report per store and for the group?
Yes. Reports filter by store view and currency, and can be exported for the whole group.
Does this work with Hyvä on some storefronts and Luma on others?
Yes. The Hyvä build of the suite works alongside the standard suite on multi-store setups.
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.