Description
Saga Payments for WooCommerce is a full-featured payment gateway built for Nordic merchants. Accept secure payments through multiple payment methods with enterprise-grade features:
Payment Methods
- Card Payments – Visa, Mastercard, American Express, Discover
- Vipps – Norway’s most popular mobile payment app
- Klarna – Buy now, pay later
- Apple Pay – Fast checkout for Apple users
- Google Pay – Fast checkout for Android users
- Swish – Sweden’s most popular mobile payment app
- MobilePay – Denmark and Finland’s popular mobile payment app
Features
- Easy Setup – Just enter your Merchant ID, Terminal ID, and Public Key
- Saved Payment Methods – Customers can save cards for faster checkout
- WooCommerce Subscriptions – Full support for recurring payments with automatic renewals
- WooCommerce Pre-Orders – Charge customers when pre-ordered products become available
- Authorize & Capture – Authorize payments and capture later, or capture immediately
- Auto-Capture – Automatically capture when order status changes to Processing/Completed
- Auto-Void – Automatically void authorizations when orders are cancelled
- Express Checkout – Apple Pay/Google Pay buttons on product pages and cart
- WooCommerce Blocks – Full support for Blocks Checkout including saved cards
- HPOS Compatible – Full support for High-Performance Order Storage
- Refunds – Full and partial refunds directly from WooCommerce admin
- Professional Design – Clean, responsive payment widget
Plugin Integrations
- WooCommerce Subscriptions – Automatic recurring payments
- WooCommerce Pre-Orders – Charge on release
- WooCommerce Blocks – Full Blocks checkout support
- WooCommerce HPOS – High-Performance Order Storage
- Saga Product Sync – Bidirectional product catalogue synchronisation
- Compatible with all major WordPress themes
Product Sync (Saga)
Automatic bidirectional synchronisation between your WooCommerce store and Saga:
- Saga is master – pull products, prices, images, VAT rates and stock from Saga into WooCommerce
- Push changes back – WooCommerce product edits are automatically pushed to Saga in real-time
- Inventory sync – relative stock deltas (STOCK_DOWN / STOCK_UP) on order completion, refund and cancellation
- Auto-retry – failed inventory adjustments are queued and retried every 5 minutes (up to 20 attempts)
- Full field mapping – prices (øre <-> kroner), VAT rates (25 / 15 / 12 / 0 %), units, barcodes, cost price, images
- Admin panel – WooCommerce -> Saga Product Sync with connection test, manual sync, and status dashboard
- Configure via WooCommerce -> Saga Product Sync
Requirements
- WordPress 5.8 or later
- WooCommerce 7.0 or later
- PHP 7.4 or later
- SSL certificate (HTTPS)
- Saga Payments merchant account
External services
This plugin relies on the following external services. A Saga Payments merchant account is required. Each entry says when the service is called and what is sent to it.
Saga Payments API
All payment operations (order creation, payment verification, refunds, captures, voids, and subscription management) are handled through the Saga Payments API proxy server. When a customer initiates a checkout, order data including amount, currency, line items, and customer billing/shipping information is sent to this service via server-side HTTP requests.
The same service is also called server-side:
- To confirm that your server belongs to your Saga store, when the store is set up or its server changes: the merchant ID, the store ID and a random installation secret generated by this plugin are sent, and the service e-mails a confirmation code to the address registered for the store. The code the administrator enters is sent back to it.
- For the shop’s own access credential for this service: requested with the merchant ID, the store ID and the installation secret, and revoked when the administrator disconnects the shop.
-
When a guest customer pays with a previously saved card: the customer’s e-mail address, a generated one-time code, the store name and the cart total are sent, and the service e-mails the code to the customer through the Resend e-mail service. No card data is sent.
-
Service URL: https://sagapay-api-v3.kristoffer-afc.workers.dev/api
- Provider: Saga Payments (Cloudflare Worker proxy to Surfboard Payments)
- Website: https://sagapay.no
- Terms of Service: https://www.sagapay.no/terms-of-service
- Privacy Policy: https://www.sagapay.no/personvernserklaering
Saga Account Connection
Used only when an administrator connects the shop to Saga, or disconnects it, from the Saga Payments settings. “Connect” sends the administrator’s browser to Saga’s sign-in page with the address of this site’s settings page to return to, a one-time state value, a PKCE code challenge and, when the shop already has one, its store ID. After the administrator approves, the plugin exchanges the one-time code for the store’s credentials in a server-side request (the code, the same return address and the PKCE code verifier are sent). “Disconnect” sends a server-side request that revokes the store’s API key, signed with the shop’s connection secret. Nothing is sent to this service during checkout.
- Service URL: https://auth.sagapay.no (authorize, token and revoke)
- Provider: Saga Payments
- Website: https://sagapay.no
- Terms of Service: https://www.sagapay.no/terms-of-service
- Privacy Policy: https://www.sagapay.no/personvernserklaering
Saga Checkout
Used only when Saga Checkout is chosen as the checkout in the Saga Payments settings. Shops that use the standard payment form do not call these addresses.
- Checkout sessions (server-side): when a customer opens the checkout, the plugin creates a checkout session with Saga. It sends the store and terminal IDs, the order number, the order lines with their prices and tax, the shop’s shipping options, the addresses to return to after payment, the shop’s name, web address, support e-mail address, terms and privacy page addresses and accent colour, and, when the customer has already entered them in the shop, the customer’s e-mail address, name and shipping address. The plugin then reads the session’s payment status, and the order’s contact and delivery details, back from the same API. Test API keys (sg_test_) use the sandbox address.
- Checkout script and stylesheet (in the customer’s browser): Saga’s checkout script and its stylesheet are loaded from Saga’s CDN on the checkout page and display Saga’s checkout form. What the customer enters in that form goes directly to Saga. In Redirect mode the customer is sent to the checkout page address Saga returns for the session.
-
Settings screen: the “live test” in the Saga Checkout settings creates a test session with the same API and asks Saga which payment methods it would offer for it (the session ID is sent).
-
Service URL: https://carbon.sagapay.no/v1 (sandbox: https://sandbox-carbon.sagapay.no/v1)
- Script URL: https://cdn.sagapay.no/sdk/v2/sagapay.min.js
- Stylesheet URL: https://cdn.sagapay.no/checkout/v2/sagapay-checkout.css
- Payment methods URL: https://checkout.sagapay.no/v1/payment/methods/
- Provider: Saga Payments
- Website: https://sagapay.no
- Terms of Service: https://www.sagapay.no/terms-of-service
- Privacy Policy: https://www.sagapay.no/personvernserklaering
Saga Store Details
Saga’s checkout and payment pages show the terms and privacy links registered for your store. The Saga Payments settings screen reads them from Saga when an administrator opens it, at most every 12 hours (every 10 minutes while Saga has not answered), so it can tell you when one of them leads nowhere. The merchant ID and the store ID are sent server-side. Nothing is sent from the storefront.
- Service URL: https://checkout.sagapay.no/v1/store/
- Provider: Saga Payments
- Website: https://sagapay.no
- Terms of Service: https://www.sagapay.no/terms-of-service
- Privacy Policy: https://www.sagapay.no/personvernserklaering
Saga Payments Merchant Dashboard and Documentation
The plugin settings screen links store administrators to Saga Payments dashboard and documentation pages for API key, webhook, and product catalogue setup. These links open only when an administrator clicks them. No customer or payment data is sent automatically by these documentation links.
- Dashboard URL: https://dashboard.sagapay.no
- API key documentation URL: https://docs.sagapay.no/guides/getting-started/opprett-api-nokler
- Webhook documentation URL: https://docs.sagapay.no/guides/getting-started/webhooks
- Product catalogue documentation URL: https://docs.sagapay.no/api-reference/api-reference/product-catalogue/
- Provider: Saga Payments
- Terms of Service: https://www.sagapay.no/terms-of-service
- Privacy Policy: https://www.sagapay.no/personvernserklaering
Saga Regnskap (Accounting) Integration
Registration: the plugin sends a registration request to the Saga Regnskap accounting service when the store owner completes merchant OTP verification or clicks the “Koble til regnskap” button in the gateway settings, so the merchant’s bookkeeping can be reconciled against the store. For a store that has a Saga merchant ID and store ID but is not connected to the accounting service (including a store that was told it has no accounting agreement), the registration is also retried once in the background after each plugin update, the next time an administrator opens the WordPress admin. Only store-level facts are sent: the Surfboard merchant ID, the store URL, the activation reference, plugin/WordPress/WooCommerce versions, currency, tax display setting and which gift card system is installed. The accounting service answers by calling this site’s /wp-json/saga-accounting/v1/handshake to confirm the domain. For a store without an agreement the plugin keeps only that answer, and no access is granted.
Seller details: once connected, the plugin asks the accounting service once a day, and when an administrator clicks “Hent selger på nytt”, for the seller’s company details that are printed on sales documents. The merchant ID and the store URL are sent.
What the accounting service reads (connected stores only, that is merchants with a Saga Regnskap agreement): order and refund totals (amounts, tax rates, Saga payment references), from a read-only, token-authenticated REST endpoint served by this plugin at /wp-json/saga-accounting/v1/. These totals contain no customer names, e-mail addresses, phone numbers, addresses or IP addresses. When sales documents are enabled, whether this plugin issues them or an invoice plugin it serves them from, the accounting service also downloads every issued sales document and credit note as a PDF from the same endpoint. A sales document identifies the buyer as the bookkeeping rules require: name, company, billing address, postcode, city, country, e-mail address and, where it applies, VAT number, together with the order lines. No payment credentials are sent.
- Service URL: https://regnskap.sagapay.no (fallback: https://saga-regnskap-api.kristoffer-afc.workers.dev)
- Provider: Saga Payments (Cloudflare Worker)
- Website: https://sagapay.no
- Terms of Service: https://www.sagapay.no/terms-of-service
- Privacy Policy: https://www.sagapay.no/personvernserklaering
Surfboard Online SDK
The payment form displayed on your checkout page is rendered by the Surfboard Online SDK. This JavaScript library is loaded from an external server into the customer’s browser and handles the secure payment UI including card input fields, Vipps/MobilePay popups, Klarna widget, and Apple Pay / Google Pay buttons. Card data is entered directly into Surfboard-hosted iframes and never touches your server.
- SDK URL: https://thorium.surfgw.com/OnlineSDK.js
- Provider: Surfboard Payments
- Website: https://www.surfboardpayments.com
- Terms of Service: https://www.surfboardpayments.com/terms-and-conditions
- Privacy Policy: https://www.surfboardpayments.com/privacy-policy
Surfboard Hosted Payment Page
When the plugin is configured in redirect mode, or for certain subscription flows, the customer’s browser is redirected to a hosted payment page operated by Surfboard Payments. The order amount, currency, and return URLs are passed via the redirect. All payment data is entered on the hosted page.
- Service URL: https://pay.withsurfboard.com
- Base URL used by redirects: https://pay.withsurfboard.com/
- Provider: Surfboard Payments
- Terms of Service: https://www.surfboardpayments.com/terms-and-conditions
- Privacy Policy: https://www.surfboardpayments.com/privacy-policy
Surfboard Vipps/MobilePay Intermediary
For Vipps and MobilePay payment flows, the Surfboard SDK loads an intermediary page in an iframe to handle the mobile payment authorization. This is managed automatically by the Surfboard Online SDK and serves as the bridge between your store and the Vipps/MobilePay apps.
- Service URL: https://vipps.withsurfboard.com
- Provider: Surfboard Payments
- Terms of Service: https://www.surfboardpayments.com/terms-and-conditions
- Privacy Policy: https://www.surfboardpayments.com/privacy-policy
Google Pay API
When Google Pay is enabled as a payment method, the Google Pay JavaScript SDK is loaded in the customer’s browser to render the Google Pay button and handle the payment sheet. Payment token data is returned to your store and forwarded to the Saga Payments API for processing.
- SDK URL: https://pay.google.com/gp/p/js/pay.js
- Provider: Google
- Website: https://pay.google.com
- Terms of Service: https://payments.google.com/payments/apis-secure/get_legal_document?ldo=0&ldt=googlepaytos
- Privacy Policy: https://policies.google.com/privacy
QR Code Generation
For Swish payments, if the payment gateway does not return a pre-rendered QR code image, the plugin generates a QR code locally using the bundled qrcode-generator library (MIT license, by Kazuhiko Arase). No external service is called for QR code generation.
Saga Product Sync API
If the optional product synchronization feature is enabled, the plugin sends product data (name, description, price, VAT rate, SKU, barcode, images, categories and variants) and stock changes from your WooCommerce catalog to the Saga Payments product catalogue, and reads products, prices and stock back from it. Requests are server-side, run on a schedule and when a product is saved or an order changes stock, and use the store’s API key. Test API keys (sg_test_) use the sandbox address. This is an opt-in feature configured in the plugin settings.
- Service URL: https://carbon.sagapay.no (sandbox: https://sandbox-carbon.sagapay.no)
- Provider: Saga Payments
- Terms of Service: https://www.sagapay.no/terms-of-service
- Privacy Policy: https://www.sagapay.no/personvernserklaering
Saga POS Order Sync
If the optional pickup order sync is switched on (it is off by default), an order with local pickup is sent to the shop’s Saga till so staff can prepare and hand it over. The plugin sends:
* the order lines (Saga catalogue product and variant IDs, quantity and price after discount);
* the customer’s name and phone number;
* the customer’s order note;
* whether the order is paid online or will be paid in the store.
It also reads the order’s status back. The till reports accepted, ready, picked up, paid in store or cancelled, and those reports reach the plugin’s webhook through Saga. When switched on, the plugin also adds the till’s order events to the shop’s own Saga webhook subscription. Requests are server-side and use the store’s API key. No e-mail address and no card data is sent.
- Service URL: https://carbon.sagapay.no
- Provider: Saga Payments
- Terms of Service: https://www.sagapay.no/terms-of-service
- Privacy Policy: https://www.sagapay.no/personvernserklaering
Inventory Diagnostics (Administrators Only)
The Saga Payments diagnostics page has an inventory check that an administrator can run for one product. It reads that product’s stock from the Saga catalogue (and, when asked, lists the merchant’s stores and catalogues), and changes the product’s stock there only when an administrator explicitly asks for that. It sends the store’s API key and the merchant, store, catalogue and product IDs, server-side. It never runs by itself and sends no customer data.
- Service URL: https://api.sagapay.no
- Provider: Saga Payments
- Terms of Service: https://www.sagapay.no/terms-of-service
- Privacy Policy: https://www.sagapay.no/personvernserklaering
Payment Method Logos
Payment method logos (Visa, Mastercard, Amex, Vipps, Klarna, Apple Pay, Google Pay, Swish, MobilePay) are bundled locally within the plugin in SVG format. No external CDN is used for logo display.
SVG files and inline SVG markup use the standard SVG namespace URI http://www.w3.org/2000/svg and xlink namespace URI http://www.w3.org/1999/xlink as static XML identifiers; these are not external network requests.
Installation
- Upload the
saga-paymentsfolder to the/wp-content/plugins/directory - Activate the plugin through the ‘Plugins’ menu in WordPress
- Go to WooCommerce > Settings > Payments > Saga Payments
- Enter your Merchant ID and Store ID (from your Saga Payments dashboard at https://dashboard.sagapay.no) and click Save changes
- The plugin will automatically provision your Terminal ID and Public Key on save – no manual key handling required
- Enable the payment method and save
FAQ
How do I get a Saga Payments account?
Contact Saga Payments at support@sagapayments.com to set up your merchant account.
Does this support test mode?
Test mode (the sandbox) works with a Saga TEST account only. When you connect with “Connect to Saga”, the plugin follows the account you connected: a live account takes real payments, and its test mode cannot be switched on, because a live account does not exist in the sandbox and every payment would fail.
To test on a live account before your customers see Saga, turn on “Test on the live account”: Saga is then shown at checkout to administrators only. Pay a small amount with a real card while logged in, then cancel the order. Within 24 hours the amount is released; after that it is captured and refunded in full automatically. Turn the setting off to open Saga to your customers.
Which currencies are supported?
The plugin supports NOK (Norwegian Krone), SEK (Swedish Krona), DKK (Danish Krone), EUR and other currencies supported by Saga Payments.
Can customers save their cards?
Yes! When “Enable Saved Cards” is turned on in settings, logged-in customers can save their cards for faster future checkout.
Does this work with WooCommerce Subscriptions?
Yes! Full integration with WooCommerce Subscriptions for automatic recurring payments, payment method changes, and subscription lifecycle management.
Can I authorize and capture later?
Yes! Set “Capture Mode” to “Authorize only” in settings. Payments are authorized at checkout and captured automatically when the order is marked Processing or Completed — or, with “Capture when: Only when the order is marked Completed”, only at Completed. You can also capture from the order page.
Changelog
4.0.808
- Fix: the «Saga Checkout status» row and its «Test Saga Checkout» button show only when Saga Checkout is the chosen checkout. On WooCommerce’s own checkout (the default) the test reported «refused … Connect to Saga first.», which merchants read as their payments failing.
- Fix: a capture is no longer reported as collected when Saga has only accepted it. Saga processes delayed captures (all Klarna payments, and Authorize only) in batches and can still fail them. The plugin now asks Saga for the result about 30 minutes later. If the capture failed, the order is marked as not collected and the capture is sent again once. If that fails too, a shipped-looking order goes back On hold with «do NOT ship», and the shop is e-mailed.
- New: the plugin watches every payment it has authorised but not yet captured. An order marked Completed, or with a shipping status such as «Shipped», whose capture never happened is captured. The shop is e-mailed 7, 3 and 1 day before the authorisation expires (Klarna 28 days, cards about 7). On the last day the payment is captured so the money is not lost; this can be switched off in the settings.
- New: an order cancelled more than 24 hours after the payment was authorised, when Saga no longer releases an authorisation, is settled by capturing the full amount and refunding it in full as soon as Saga confirms the capture. The customer ends up paying nothing. A void Saga refuses is settled the same way, and so is Refunded set by hand on an authorised order.
- New: after the update, every capture from the last 30 days is checked once at Saga, so a failed capture is found while it can still be collected.
- New: the order list shows each payment’s capture state — days left to capture, sent and waiting for Saga, confirmed, failed, or a cancellation being settled. The order screen shows the deadline and the history, and past 24 hours the Void button says what it will do («Cancel payment (capture + full refund)»).
- New: e-mails go to the shop’s notification address. Deadline warnings come as one e-mail per check, not one per order. Failures are sent at once, and the shop is told when a problem it was warned about is resolved. The dashboard shows how many payments are waiting to be captured and which expire first.
- New: the messages about captures, voids, refunds and deadlines are in Norwegian on a Norwegian site.
- Fix: a capture is sent when a shop marks Processing an order whose authorisation was never recorded (a missed confirmation), instead of nothing.
- Fix: a capture or void that got no answer from Saga is not reported as failed; Saga is asked what happened.
- Fix: a Capture on a cancelled order no longer reopens it.
- Fix: an earlier void on the same order no longer blocks capturing a new payment.
- Fix: a refund Saga has not confirmed after about 24 hours is reported on the order.
- Fix: a subscription renewal that was charged late (after a retry, or a day the scheduled job did not run) no longer pushes the next one a month too far. The next renewal is counted from the billing cycle the charge paid for, not from the day it ran, so no month goes uncharged. A subscription that stood still for months (a failed renewal paid late, “Test Renewal Now” on a lapsed one) continues from the current cycle and is never charged for the months it missed. Subscriptions charged before this version change over at their next renewal.
- Fix (subscriptions): a renewal charge Saga declined (PAYMENT_DECLINED) or cancelled no longer holds the subscription for good or gets charged again every 30 minutes. A charge that stays unconfirmed is noted once and reported to the shop after 24 hours. A daily plan is no longer charged again minutes after sign-up. A subscription whose order a shipping plugin marked «Shipped» keeps renewing. A missing recurring-charge terminal is reported instead of only logged. A failed renewal paid late counts toward a fixed number of payments. On a database without named locks the renewal job and the order-screen buttons now exclude each other. «Cancel subscription» stops renewals even if Saga cannot be reached.
- Fix (refunds): a refund is refused while its capture is not yet confirmed or after Saga reported the capture failed, because Saga can pay out a refund of money it never collected. A refund that got no answer while Saga was creating it is remembered, and another refund on the order is refused for 30 minutes so the same money is not paid out twice. The same amount refunded again within 10 minutes is treated as a double-click and not sent. A refund goes to the Saga order that was actually paid. A PS_0025 answer on Klarna/Vipps/Swish/MobilePay is recorded as pending until Saga’s return order confirms it, instead of as refunded. A refund Saga reports as failed or declined is caught, the refund status is followed for about two days instead of 11 hours, and the shop is e-mailed when a refund did not go through or is not confirmed.
- Fix (subscriptions): an expired stored card no longer ends the subscription on the spot with nobody told. When the renewal falls due, the customer gets the pay link for it and can pay with another card. Once a cycle is paid, any older pay link for it is cancelled, so the customer cannot pay the same cycle twice.
- Fix (payments): the cancelled-order check no longer closes an order for good while Saga still reports its payment as in progress (an open Vipps or Klarna app), so a payment approved a moment later is still found. An unsigned webhook for a second charge that Saga cannot confirm yet is asked for again instead of dropped. Express checkout from the cart refuses an order that needs shipping when no shipping is chosen, instead of charging the goods without freight, and asks Saga before cancelling an order on the browser’s word. A Saga Checkout order held for review is recorded as authorised, so it is captured when the shop moves it on. Two wallet completions at once can no longer both create an order. The daily check for stuck orders is no longer filled by orders that are only waiting to be captured.
- Fix: test mode follows the account the shop connected with. A shop on a live account that ticked “Test mode” sent its live ids to Saga’s sandbox and every payment failed with an API error; the box is now locked to the connected account and says why. New setting “Test on the live account” shows Saga at checkout to administrators only, so a shop can try a small real payment (and cancel it) before customers see Saga.
- Fix: a cancellation is never settled by refunding a capture Saga has not confirmed. An order already refunded «manually» in WooCommerce is not captured at all, so the customer is not charged.
- New: payment problems that need a person (a failed or unconfirmed capture, an authorisation close to or past its deadline, a cancellation that could not be settled) are also reported to Saga, so they can help. Only ids, amounts and the reason are sent, nothing about the customer. Needs Saga proxy 2.0.8.
- Fix: «Void sent» is no longer called «Funds released» while Saga is still processing it (VOID_INITIATED).
- Fix (checkout): reloading the checkout — or a phone reloading it on the way back from the Vipps app — no longer leaves the previous payment open next to a new one. The attempt left behind is cancelled at Saga first; if it has already been paid or is still being approved, no second payment is opened and it is confirmed instead. A payment still being approved is waited for for up to 15 minutes before it is replaced.
- Fix (checkout): the shopper is no longer told «payment failed» after 24 seconds while Saga still has the payment under way. The page waits for about three minutes, and then says the payment is being confirmed and not to pay again. The same message replaces «not confirmed — contact support» on the fallback verification page, which also no longer lets go of the order, so the next «Place order» cannot start a second payment.
- Fix (checkout): a paid Saga payment can no longer be used to complete a new order built from someone’s basket when the order it was made for still exists (in any status, also in the bin). An order is no longer held on-hold by a second amount check that read an old, abandoned Klarna attempt instead of the payment.
- Fix (Saga Checkout): the thank-you page no longer reloads for ever when the payment is still settling. Two confirmations of the same order can no longer run at once (two delivery lines, notes twice). A paid order is no longer put back to draft (and deleted by WooCommerce a day later) on shops without HPOS, nor cancelled by WooCommerce’s unpaid-order clean-up while the payment settles. An order held by the payment checks is left as it is. Drafts between two and twenty hours old are checked too. Saga Checkout no longer takes over an order another payment attempt (or another payment plugin) left pending, and the normal checkout no longer takes over a Saga Checkout order.
- Fix (Express): a new Express attempt no longer opens a second payment while the previous one can still be approved in Vipps or Swish; the previous one is cancelled at Saga first. Cancelling an Express payment cancels it at Saga before the order, so a late approval cannot land on a cancelled order. A double tap is refused at once, and Express works on hosts without named database locks. The goods are reserved for the shopper as WooCommerce’s own checkout does, so two shoppers cannot both pay for the last one.
- Fix (stock): a held order that fails gives its goods back.
- Fix (sales documents): no sales document is issued for money that is only reserved; it is issued when the payment is captured (the status change that captures still gets it on its e-mail). A payment taken in test mode gets no document and is marked as a test for the accounting engine. A refund Saga refused gets no credit note. A refund of an invoice issued by Saga Payments still gets its credit note (and it is still e-mailed) after the shop switched to another invoice plugin, «outside» or «Ingen». Deleting a refund in WooCommerce annuls its credit note with the reason and keeps the document on the order. A refund of less than its lines is credited with the right VAT, not with the difference as «øreavrunding». Two requests can no longer give one sale two numbers. Sales taken on by 4.0.794–4.0.803 before the shop started issuing are not documented (or mailed) at pairing.
- New (accounting): the accounting read API says whether a Saga payment’s money is collected (authorised, capture pending, confirmed, failed, expired) and whether it was a test payment.
- Fix (subscriptions): a renewal charge is recorded before the card is charged — for the plugin’s own subscriptions, WooCommerce Subscriptions and pre-orders — so a server that stops mid-charge cannot lead to a second charge. A paid renewal order now holds only the subscription, not one-off items bought with it (their stock was taken again on every renewal). «Test Renewal Now» no longer charges a subscription whose payments are all made unless forced.
- Needs Saga proxy 2.0.8 (route GET /payments/{id}/capture) to read capture results. Proxy 2.0.9 (code verification hardening) is independent of the plugin.
4.0.807
- Changed: with Saga Regnskap connected, the shop issues its sales documents itself or says what does. The choices are Automatisk (the default), Saga Payments, another invoice plugin (when one is installed) and another system outside WooCommerce (an ERP, accounting program or till) — «Ingen» is not offered. A connected shop that had «Ingen» issues automatically from the update, for orders paid from then on only, and the admin is told from when; the customers get the sales document by e-mail. Without Saga Regnskap the shop’s own choice stands.
- New: «Et annet system utsteder (utenfor WooCommerce)», which tells Saga Regnskap that another system documents the sale, so it is not documented twice.
4.0.806
- Improved: the sales document states the VAT rate on every line and, for each rate, the amount it applies to and the VAT; it also states the place of delivery.
- Fix: a sales document is never issued with the VAT left out. If the seller is registered for VAT but WooCommerce computes no VAT (taxes off, or no rates), no documents are issued and the settings say why. A line with an amount but no VAT rate stops that order’s document — no number is used, and the order gets a note for a person.
- Fix: a credit note never states a VAT rate that is not one of the sale’s rates.
4.0.805
- Improved: who issues sales documents is chosen on the Saga Payments card, where a connected shop sees it, not only under Advanced settings. Nothing is chosen for the shop: the card shows the saved choice, and only Save changes it.
4.0.804
- Changed: who issues sales documents is one choice — Automatisk, Saga Payments, another plugin, or Ingen (none). The separate box «Utsted salgsdokument» is gone: with Automatisk and no invoice plugin, Saga Payments issues and the customers get the sales document by e-mail. Nothing changes at the update: a shop where the box was off is set to Ingen, and issuing only starts when the shop owner saves a choice.
- Changed: Saga Payments documents only orders paid after the choice was saved and the shop was connected to Saga Regnskap, whichever came last — never older orders, and never a late e-mail for them.
4.0.803
- Fix: when the shop switches on «Utsted salgsdokument», orders paid before that are no longer given a sales document. Before, an older order got a numbered document — attached to WooCommerce’s “completed” e-mail to the customer — when the shop later marked it completed. Only sales paid after the plugin became the issuer are documented.
- Fix: reading an order’s payment method no longer saves the order. Some orders got the title “Saga_payments (Saga)” — the plugin’s own id, not a payment method — and every time the title was read (order list, REST, the 5-minute check) the order was saved again, so it looked changed to accounting and order integrations although nothing had changed.
4.0.802
- Improved: Saga Checkout shows the American Express logo when American Express is on for the shop, as the WooCommerce checkout does. The plugin tells Saga Checkout which card brands to show; this changes logos only, never which payment methods can be used.
4.0.801
- Fix: with American Express on, a checkout that sends the customer to the Saga payment page asked Saga to limit the page to “AMEX” among the methods. Saga refuses that, so the page was created a second time with no limit at all, and showed methods the shop had not chosen. American Express is now sent as part of card payments.
- Fix: the American Express logo is also shown in the «Sikker betaling» box under the payment method, not only next to its name. The box left it out in both the block checkout and the classic checkout.
4.0.800
- Fix: the American Express logo is shown when American Express is registered on the Saga merchant account. Before, only an “activated” status counted, so the logo was missing although American Express was enabled.
4.0.799
- Improved: pickup orders sent to the Saga till.
- A cash or split payment rounded to whole kroner at the till is no longer reported as a different amount.
- An order with an item at a 100 % discount is not sent to the till, and the order says what to do instead.
- Refunding such an order in WooCommerce no longer puts stock back, because the return at the till does that.
4.0.798
- New: pickup orders can be sent to your Saga till (off by default). When switched on, an order with local pickup appears in the till, the till reports when it is ready, picked up or paid in the store, and the customer is told when the order is ready. Orders paid in the store are documented by the till’s receipt.
- New: one-click setup from the Saga merchant portal. The portal can install, connect and configure the plugin with WooCommerce’s own checkout and Saga in redirect mode.
- Improved: the Connect button tells Saga which plugin version is connecting.
4.0.797
- Security: on a shop without a webhook secret, a payment notification no longer decides which payment an order captures or refunds. The payment id is only recorded once Saga lists it for that order.
- Security: a Saga Checkout order held for review because the payment does not match it (another country, VAT or shipping zone than the address) is no longer completed automatically by the background payment checks.
- Security: Express checkout from the cart is refused when the cart was priced for another country than the address, and an address given without a country gets the country the cart was priced for. Express now also follows the shop’s payment method rules and maximum order amount.
- Security: a link sent to an administrator can no longer put its own text into the Saga connection card or cancel a connection in progress.
- Fix: when several requests start at the same moment right after an update, the shop no longer risks losing its connection to the payment service.
- Fix: the background registration for Saga Regnskap now runs when an administrator opens the admin, not from the public WordPress scheduler, and the sales document catch-up can no longer run twice at once.
- Fix: Saga Checkout status checks are rate limited, and a customer’s name or address is no longer mistaken for a payment status when old payment attempts are cleaned up.
4.0.796
- Security: the payment id a browser reports when it finishes a payment is now only accepted if Saga confirms it belongs to that order. Before, a crafted request could make a held authorisation capture a different payment.
- Security: a payment notification only captures a held payment automatically once the payment has been confirmed with Saga.
- Security: the daily refresh of your company details for Saga Regnskap now runs when an administrator opens the admin, not from the public WordPress scheduler.
- Security: deleting a guest’s personal data no longer removes a card that a customer account has saved, or that an active subscription still uses.
- Security: messages from payment pages are checked more strictly, so another page cannot interrupt a Klarna payment or change the recorded payment method.
- Fix: stock management is only switched off for products the Saga till does not count when the stock figure was written by the sync itself. A stock count you keep in WooCommerce is never changed.
- Fix: Saga Regnskap and the sales document catch-up now agree on refunds of a sale that is still waiting for its document, never document a sale another invoice plugin already numbered, and never run twice at once.
- Improved: the American Express check no longer switches American Express on or off on an unclear answer from Saga.
4.0.795
- Fix: products from the Saga till that the till does not keep stock for are no longer shown as “Out of stock” on the web. They sell without a stock count, as at the till. Products the till created before this update are corrected automatically on the next sync, unless you have set their stock yourself in WooCommerce.
- Fix: the American Express logo now shows at checkout when American Express is activated for your Saga account, and Apple Pay and Google Pay accept American Express cards there too.
4.0.794
- Fix: when Saga Payments issues your sales documents, a paid order that could not get its document at the time of the sale (for example while the seller details were still being fetched) now gets it automatically within the hour, instead of never, and your customer receives it by e-mail in your shop’s usual order e-mail, with a line saying it was issued after the purchase. Refunds made in the meantime get their credit notes the same way. Each order gets exactly one document.
- Improved: an order whose sales document cannot be produced no longer uses up a document number when it fails.
- Fix: sales documents Saga Payments has already issued stay available to your customers and to Saga Regnskap after you install another invoice plugin.
- Improved: Saga Regnskap can now see, for every order, whether Saga Payments will issue its sales document, whether another invoice plugin does, or whether nobody in the shop does — so a sale is never documented twice.
4.0.793
- New: “Capture when” setting for authorised payments (Authorize only, and Klarna): when the order is marked Processing or Completed (as before), or only when it is marked Completed — for shops that invoice at Processing and ship later.
- Changed: authorised payments are now captured, and released when an order is cancelled, also when the order status is changed from the WooCommerce app, the REST API, a shipping or ERP integration, WP-Cron or WP-CLI — not only in wp-admin. If you set orders to Processing that way and do not want the money taken then, choose “Capture when: Only when the order is marked Completed”.
- Fix: reconnecting to Saga no longer switches “Authorize only” back to immediate capture.
- Fix: when your own system creates the order as Processing and asks Saga to capture later, the authorisation is now recorded on the order, so it is captured when the order is completed.
- Improved: the Saga Regnskap connection now reports when an order was completed, and the VAT rate of every refunded line, including refunded delivery and fees.
- Fix: product and category names reach the Saga till without HTML codes such as “&”.
- Improved: works alongside other payment methods and checkout plugins the standard WooCommerce way. Shipping, taxes and fees are recalculated as usual while you type your address, no Saga payment is prepared for shoppers who choose another payment method, and Saga’s styles only apply to Saga’s own payment windows.
- Improved: reliability of subscriptions and renewals, saved cards, captures, refunds, express checkout and the product sync with the Saga till.
- Improved: the connection between your shop and Saga is now tied to your own server. If Saga asks you to confirm your server, enter the code sent to the merchant e-mail in the Saga Payments settings.
- Fix: no more notices on PHP 8.2+ and WordPress 6.7+.
4.0.792
- Security: hardened several checkout endpoints so order details, status and payment links can only ever be seen or changed by the shopper the order belongs to.
4.0.791
- Fix: Saga Checkout embedded in your checkout page no longer changes the look of the rest of the page — your theme’s fonts, colours, links and spacing stay as they are, on desktop and phone.
4.0.789
- Fix: Saga Checkout embedded in your checkout page now looks the same on every theme. Themes that style form fields could squeeze the fields so the text you typed sat on top of the field’s label.
4.0.788
- Please update: this release strengthens how your shop connects to Saga and is required to keep taking payments — older versions are being phased out. Updating is all that is needed; if Saga Payments asks you to confirm your server after updating, it e-mails a code to the address registered with Saga.
- Improved reliability and hardening across checkout, saved cards, express checkout and product sync.
- Fix: a paid Saga Checkout order is completed as soon as Saga confirms it.
4.0.786
- New: Saga Checkout. Choose it on the Saga Payments card, right under your connection, and Saga’s checkout replaces the checkout form: the customer gives their details, chooses delivery from your own shipping rates and pays in one place, embedded in your checkout page (Inline) or on Saga’s hosted page (Redirect). Your order summary with each line’s options, a coupon field and a note to the shop stay beside it, and customers can still choose your other payment methods. Orders are created by WooCommerce’s own checkout from the cart, so product options, coupons, taxes, stock, e-mails and reports behave as with any order. The settings screen shows whether the shop is ready and can run a live test against Saga.
- New: the Saga Payments card asks where the customer pays — in your checkout page (Inline) or on Saga’s page (Redirect) — and saves with your usual Save changes button.
- Fix: the “terms and conditions” and “privacy policy” links in Saga’s checkout and payment page lead to your own pages. Saga shows the addresses registered for your store (your-shop/terms and your-shop/privacy), which led to “page not found” on shops without pages there; the shop now sends them to the terms page chosen in WooCommerce and the privacy page chosen in WordPress, and the Saga Payments card says when one still leads nowhere.
4.0.770
- Fixed: on shops where WooCommerce stores its visitor-tracking cookies base64-encoded, Saga orders still showed “Origin: Unknown”. The plugin has recorded where customers came from since 4.0.453, but read those cookies in a way that only worked for the default encoding. It now reads them exactly as WooCommerce’s own tracking script writes them, and also records the three newer campaign fields (source platform, creative format, marketing tactic).
- Fixed: “Buy now” on a product page lost what the customer chose in the product form — a customiser’s design, add-on fields and the prices they add, and attributes such as a colour picked from “any”. It now goes through the cart exactly as “Add to cart” does, with the customer’s existing cart set aside and put back untouched, and refuses with WooCommerce’s own message when a required option is missing.
- Fixed: a customer who paid with Vipps and skipped the checkout’s optional phone field left the order with no phone number, so no shipping label could be printed. The phone the payment carries is now added to any paid order that has none, before the new-order e-mail is sent. A number the customer typed is never replaced.
- Setup: connecting now includes the last step it used to leave out. Saga only accepts payments from a server it has confirmed belongs to the shop, and that confirmation was hidden at the bottom of the advanced settings, so a shop could read “ready to take payments” while its payments were refused. The code is now e-mailed as part of connecting and asked for in the connection card itself, and the card says “one step left” until it is done.
4.0.768
- Fixed: pressing Disconnect could do nothing at all, for ever. Disconnecting proves who your shop is by signing a request with its Saga secret, and that secret was only ever kept in the product sync settings. Deleting and reinstalling the plugin wipes those, so a shop that came back from a reinstall looked connected, could not prove it, and was refused by Saga every single time with nothing changed and nothing to press. The secret is now kept with the connection and restored alongside it.
- The confirmation screen now says what went wrong instead of leaving you on a dead end. It tells you whether Saga refused your shop’s identity or simply could not be reached, offers to try again, and — if it keeps failing — lets you disconnect the shop here anyway. That last option says plainly that it does not revoke the key at Saga, so you know to revoke it in the Saga portal yourself.
- Also fixed on the way: the link back to that screen was being built with its ampersands written out as HTML, which is right for a link on a page and wrong for a redirect. The browser then looked for a parameter that did not exist and reported that the link had expired.
4.0.766
- Fixed: the Disconnect button on the confirmation screen did nothing. It was being filtered through a function that allows the tags of a blog post, and a form is not one of them, so the button was stripped down to plain text before the page was sent. The question was there; there was simply no way left to answer it. Affects 4.0.765.
4.0.765
- Fixed a critical error when opening the Disconnect confirmation. The screen loaded the WordPress admin header from a context that has no admin screen, which made WordPress fire a hook without a page name and crash the site with a 500. The confirmation is now a standalone page that needs none of that. Affects 4.0.763 and 4.0.764.
- Hardened: the product sync admin no longer fatals if WordPress fires the script hook without a page name. Any plugin or theme reaching that state would have taken the whole site down with it, not just this screen.
4.0.764
- Connecting now sets capture to Immediate, so a payment is taken when the order is placed …