Svea Checkout Adapter

Overview

The Svea Checkout Adapter integrates Svea Checkout with Norce Checkout, enabling merchants to offer Svea's comprehensive payment solution within the Norce Commerce platform. Svea Checkout provides an embedded checkout experience with multiple payment methods including invoice, card payments, Trustly, Swish, Vipps, MobilePay, and part payment options.

This adapter is part of Norce Checkout (NCO) and handles the complete payment flow from checkout initialization through order completion, including post-purchase operations like capture, cancel, and refund.

Capabilities and Supported Flows

Payment Operations

Supported Payment Methods

Advanced Features

Limitations:

• Partial capture is not supported
• Partial refund is not supported
• Refund is only available for orders with a single capture
• Recurring payments cannot be used when nShift shipping is enabled
• Recurring token usage is limited to three orders per day in production
• Age verification (minAge) is not supported for B2B orders

Checkout Flow

The Svea Checkout flow follows these steps:

1. Create Payment Session: The storefront calls the adapter to create a Svea checkout session. The adapter returns an HTML snippet containing the Svea iframe.

2. Display Checkout: The storefront embeds the HTML snippet in the checkout page. The customer interacts with the Svea iframe to enter payment details.

3. Validation Callback: When the customer clicks "Complete Purchase", Svea calls the adapter's validation endpoint. The adapter validates stock availability and discount eligibility.

4. Push Callback: After successful payment, Svea calls the adapter's push endpoint. The adapter updates the Norce order state to completed.

5. Confirmation Page: The customer is redirected to the confirmation URL. The storefront should display the Svea iframe again to show the "thank you" page.

Pending Payment Handling

Svea payments may enter a pending state when they require additional processing before Svea can make a final decision. This occurs in scenarios such as:

• Manual fraud review by Svea's risk team
• Waiting for an external provider or bank to respond (e.g., direct bank transfers)
• Missing delivery address information

When a payment is pending, the Norce order transitions to the Accepted state but the payment remains in Pending status rather than Reserved. The order does not advance to Completed until Svea resolves the pending status.

Svea resolves pending payments asynchronously by firing event notifications. The adapter listens for two events:

• CheckoutOrder.PendingStatusReleased — the payment was approved. The adapter updates the payment state to Reserved and transitions the order to Completed.
• CheckoutOrder.Closed — the payment was declined or expired. The adapter updates the payment state to Declined and transitions the order to Declined.

Event Subscription Setup (Onboarding Requirement)

To receive these event notifications, a Svea event subscription must be registered for each merchant/channel combination during merchant onboarding. The partner or integration team calls the Svea adapter's Add Subscription endpoint:

POST /api/checkout/v1/admin/subscription

This registers a callback with the Svea Payment Admin API and verifies the subscription. Without this subscription, Svea cannot notify the adapter when pending payments are resolved, and orders will remain stuck in the Accepted state.

For implementation details, see the Svea Checkout Adapter Developer Guide.

Links and References

Norce Checkout API References

• NCO Order API
• NCO Configuration API
• NCO Notification API

Svea Checkout Adapter API

• Svea Checkout Adapter OpenAPI Specification

Norce Checkout Overview

• Norce Checkout Introduction
• Working with Norce Checkout
• Payment Adapters Overview
• Svea Checkout Adapter Developer Guide

External Documentation

• Getting Started with Svea Checkout