內容簡介
Saga Payments for WooCommerce 是一個專為北歐商家設計的全功能支付閘道，提供多種安全支付方式，並具備企業級功能，讓商家輕鬆接受付款。
【主要功能】
• 支援多種支付方式，包括信用卡、Vipps、Klarna 等
• 簡易設置，只需輸入商戶 ID 和終端 ID
• 支援 WooCommerce 訂閱和預購功能
• 自動捕獲和自動作廢授權
• 提供專業設計的支付小工具
• 支援 WooCommerce 區塊和高效能訂單儲存
外掛標籤
開發者團隊
② 後台搜尋「Saga Payments for WooCommerce」→ 直接安裝（推薦）
📦 歷史版本下載
原文外掛簡介
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.
