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
| Feature | Full | Partial | |
|---|---|---|---|
| Capture | ✅ | ❌ | Full order capture only |
| Refund | ✅ | ❌ | Supported for single-capture orders only |
| Cancel / Void | ✅ | — | Supported in reserved state |
Supported Payment Methods
| Method | ||
|---|---|---|
| One-time Payment | ✅ | Standard checkout flow |
| Recurring Payment | ✅ | Subscription/tokenized |
| Invoice (B2C & B2B) | ✅ | Includes Admin Invoice options |
| Card Payments | ✅ | via Svea Card Pay |
| Direct Bank | ✅ | Trustly |
| Digital Wallets | ✅ | Swish, Vipps, MobilePay |
Advanced Features
| Feature | ||
|---|---|---|
| B2B Support | ✅ | PEPPOL invoicing supported |
| Integrated Shipping | ✅ | via Svea Delivery Module (nShift) |
| Pending Payments | ✅ | Handles manual fraud review states |
| Part Payment | ✅ | Campaign and promotion support |
| Age Verification | ✅ | Shop-wide or per-item minAge (B2C only) |
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:
Create Payment Session: The storefront calls the adapter to create a Svea checkout session. The adapter returns an HTML snippet containing the Svea iframe.
Display Checkout: The storefront embeds the HTML snippet in the checkout page. The customer interacts with the Svea iframe to enter payment details.
Validation Callback: When the customer clicks "Complete Purchase", Svea calls the adapter's validation endpoint. The adapter validates stock availability and discount eligibility.
Push Callback: After successful payment, Svea calls the adapter's push endpoint. The adapter updates the Norce order state to completed.
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
Payments may enter a pending state when awaiting external provider responses, missing delivery addresses, or requiring manual fraud review by Svea. In these cases, the Norce order remains in the accepted state until Svea sends an event notification to update the final payment status.
Links and References
Norce Checkout API References
Svea Checkout Adapter API
Norce Checkout Overview
- Norce Checkout Introduction
- Working with Norce Checkout
- Payment Adapters Overview
- Svea Checkout Adapter Developer Guide