One payment setup across platforms
Whether you build on Norce, Shopware, Shopify, or Magento/Hyvä, your Nets payment configuration carries over. You avoid rebuilding payment logic for each channel.
Your checkout runs on Nets. Build ecommerce around it.
Nets handles payments well. The question is how to connect it to an ecommerce platform that fits your business. Nordic Web Team helps you make that decision and deliver the full project, from platform choice to live checkout.
Fits with
Nets is a Nordic payment infrastructure provider, now part of the Nexi Group — one of Europe's largest PayTech companies. In ecommerce, Nets operates through Nexi Checkout (formerly Nets Easy), an embedded checkout that handles card payments, invoice, Swish, MobilePay, Vipps, Apple Pay, Google Pay, and other local methods across the Nordics and parts of Europe. Over 140,000 merchants use Nexi Group's payment infrastructure.
For Nordic ecommerce merchants, Nets occupies a different position than pure payment gateways or checkout specialists. It combines acquiring (processing the actual card transactions) with a checkout frontend, giving merchants one agreement for both. That simplifies contracts but also means the checkout model shapes how the integration works with the ecommerce platform.
Where Nets sits in the stack
Nexi Checkout works as an embedded checkout — similar to Kustom. The merchant's ecommerce platform sends cart data to the Nets iframe, which handles payment method selection, address entry (via pre-fill from the Nets network), and transaction authorisation. The result flows back to the platform for order creation.
This means Nets replaces or supplements the platform's native checkout at the payment step. The pre-fill feature is powered by the Nets merchant network: if a customer has previously purchased from any Nets merchant, their details can be auto-populated, reducing friction for returning shoppers across the network.
Everything outside the checkout — product catalogue, pricing, cart logic, shipping, order management, fulfilment — stays with the ecommerce platform and the ERP. The integration complexity lives in how accurately cart data reaches the iframe and how payment events (capture, cancel, refund) flow back into order management.
Nets across platforms
On Shopware, Nets has an official plugin maintained through the Nexi Group's ecommerce team. It handles the embedded checkout flow, payment method presentation, and order state mapping. For multi-market Shopware setups, different payment methods can be shown per market based on Nets' coverage.
On Magento/Hyvä, Nets provides a Magento 2 extension for Nexi Checkout. The module handles the iframe embedding, order synchronisation, and payment lifecycle. Hyvä's frontend sits alongside the Nets checkout without conflict, but the backend order flow still needs careful configuration.
On Norce, Nets integrates through the payment layer. Norce's commerce engine passes cart and buyer data to Nets and receives payment confirmations back. For B2B setups, the integration needs to handle how buyer identification and payment method eligibility work together.
On Shopify, Nets can be connected as a payment provider, though the integration depth depends on Shopify's payment partner framework. For Nordic merchants on Shopify, Nets adds familiar local methods that Shopify Payments may not cover fully.
Nets as acquirer and checkout combined
Unlike providers that only handle the checkout frontend (and route to third-party acquirers), Nets/Nexi also processes card transactions directly. This means one contract, one settlement, and one dashboard for both the checkout experience and the card acquiring. For merchants who value operational simplicity and consolidated reporting, this is a practical advantage.
The trade-off: the checkout UI is tied to the Nets/Nexi ecosystem. If you want to combine Nets acquiring with a completely custom checkout frontend, or use Nets alongside other checkout providers in a payment orchestration setup, the architecture gets more complex.
Multi-currency and cross-border
Nets supports SEK, NOK, DKK, EUR, USD, GBP, PLN, and CHF. For Nordic merchants selling across the region — Sweden, Norway, Denmark, and Finland — this covers the core currencies. The checkout adapts language and payment methods based on the customer's location.
For expansion beyond the Nordics into continental Europe, Nets' coverage extends through the broader Nexi Group infrastructure. However, local European methods like iDEAL (Netherlands), Bancontact (Belgium), or Sofort (Germany) may require additional configuration or complementary providers like Mollie or Adyen.
Nets and the ERP connection
Payment events from Nets — authorisation, capture, refund, settlement — need to reach the merchant's ERP. For Nordic businesses on Fortnox, Visma, or Business Central, Junipeer handles the middleware layer, mapping Nets transaction data to the ERP's expected format. Settlement reconciliation is particularly important since Nets consolidates multiple payment methods into unified payouts.
When Nets fits — and when to complement it
Nets is a natural choice for Nordic merchants who want a single provider for checkout and card acquiring, with strong local payment method coverage across Sweden, Norway, Denmark, and Finland. The network-wide pre-fill feature and brand-customisable checkout work well for conversion in the Nordic market.
For merchants expanding beyond the Nordics, complementary providers often make sense. Adyen covers global markets. Mollie adds depth in Benelux and DACH. For B2B payment orchestration, Briqpay handles the complexity that a single checkout provider typically does not.
Beyond the integration
Connecting Nets is one part of the delivery. The surrounding work includes platform selection, checkout UX decisions (embedded vs. redirect flow), multi-currency configuration, ERP data flow mapping, QA across payment methods and edge cases, and rollout planning. A Nets checkout that performs in one market needs to be tested and configured separately for each additional market.
Strengths
Nordic payment expertiseMulti-market checkout supportEstablished merchant coverageStrong acquirer network
Business benefits
Faster checkout, fewer drop-offs
A well-integrated Nets checkout reduces friction at the point of purchase. Properly mapped payment methods, stored cards, and local options keep conversion rates healthy.
Clear financial reconciliation
When order data and payment events sync correctly between your ecommerce platform and Nets, your finance team spends less time matching transactions manually.
Multi-market readiness from day one
Nets supports multiple currencies and local payment methods across the Nordics and Europe. A properly designed integration lets you add markets without reworking the payment flow.
Confident refund and capture handling
Partial captures, split shipments, and refunds are common in ecommerce. Getting these flows right between your platform and Nets avoids support overhead and accounting errors.
Platform choice that fits your operations
Norce suits complex product and pricing models. Shopware gives flexibility for mid-market B2B and B2C. Shopify offers speed for teams that want low operational overhead. Magento/Hyvä works when you need deep customisation with modern frontend performance. We help you match the platform to your actual business, not the other way around.
Delivery approach
Junipeer serves as the integration layer between Nets and your chosen ecommerce platform, handling payment event mapping, order status sync, and data consistency. But the integration is only one part of the work. A successful project also involves platform selection, data quality review, checkout UX design, content preparation, QA across payment scenarios, and rollout planning. Nordic Web Team delivers the full scope, not just the connector.
Beyond the integration
The integration is only one part of the work. Platform choice, data quality, content, UX, QA, and the launch itself also need to be planned and delivered for the solution to work in practice.
1
Discovery and platform selection
We review your current Nets setup, checkout requirements, and operational needs. Together we evaluate which platform — Norce, Shopware, Shopify, or Magento/Hyvä — fits your product catalogue, team, and market plans.
2
Architecture and integration design
We map how payment data flows between Nets and your chosen platform. This covers transaction events, capture logic, refund handling, and multi-currency rules. Junipeer provides the integration layer, and we design the surrounding data model.
3
Build and QA
We build the storefront, connect Nets through the integration layer, and test every payment scenario — successful purchases, failed transactions, partial captures, refunds, and edge cases across markets and payment methods.
4
Launch and optimisation
We plan the rollout to minimise risk, monitor payment performance after go-live, and help you optimise checkout conversion and operational workflows once real traffic flows through the system.
FAQ
Do we keep Nets as our payment provider?⌄
Yes. The entire point is to keep Nets running and build ecommerce around it. We connect your chosen platform to Nets so payment processing, settlement, and reporting continue as they do today.
How do Norce, Shopware, Shopify, and Magento/Hyvä differ for a Nets-based setup?⌄
All four platforms support Nets integration. Norce is strong when you have complex pricing, large catalogues, or multi-brand structures. Shopware offers flexibility for mid-market B2B and B2C with a modern tech stack. Shopify is the fastest to launch and easiest to operate, though it gives you less control over backend logic. Magento/Hyvä gives deep customisation and strong frontend performance but requires more development effort. The right choice depends on your team, catalogue complexity, and growth plans.
What data syncs between Nets and the ecommerce platform?⌄
Typically: payment authorisation events, capture confirmations, refund status, settlement references, and transaction metadata. The exact scope depends on your platform, Nets product (Easy, Checkout, or inline), and how your finance and fulfilment processes work.
What does a project like this cost?⌄
Pricing ranges from a focused payment review to a staged rollout across markets. The scope depends on platform choice, number of payment methods, market count, and how much surrounding work is needed on UX, content, and data quality. We scope transparently after discovery.
What work is needed beyond the Nets integration itself?⌄
The integration is one piece. A full project typically includes platform selection, information architecture, checkout and UX design, content migration or creation, data quality checks, QA across payment scenarios and devices, and a structured rollout plan. Nordic Web Team covers all of this.