Avarda Checkout Adapter

Overview Document: Payment Adapters Overview

Overview and Unique Capabilities

The Avarda Checkout Adapter integrates Avarda Checkout 3.0 with Norce Checkout. This page focuses on the unique technical details and configuration for Avarda.

Supported payment methods and other features: Features Overview

Supported Languages

English, Swedish, Finnish, Norwegian, Estonian, Danish, Czech, Latvian, Slovak, Polish, German, Austrian, Russian

B2B and B2C Support

The adapter supports both B2C (person) and B2B (organization) checkout modes. For B2C, customers are identified by their national identification number (social security number). For B2B, customers are identified by their organization identification number. The mode is determined automatically based on the customer type on the Norce order, or can be overridden via the mode configuration option.

Limitations

• Partial Capture is not supported (full order capture only).
• Partial Refund is not supported (full refund only).
• Preselected payment method is not applicable for Sweden market.

Configuration in Norce Admin

The adapter is configured using the following unique details obtained from Avarda:

API Settings

Checkout Setup Options

Styling Options

Custom CSS styling can be configured via the styles object to override Avarda Checkout's default appearance. The styles are passed through to the Avarda Checkout iframe.

Consent Options

Avarda API Environments

In addition to the generic Norce Adapter URLs (see Payment Adapters Overview), Avarda uses the following external API environments:

Embedding the Checkout

Use the purchaseJwt and javascriptUrl returned from the create payment endpoint:

{
  "paymentId": "pfloMHwnSFxLDtaQYTVSeSKaLBx",
  "purchaseJwt": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
  "javascriptUrl": "https://stage.checkout-cdn.avarda.com/cdn/static/js/main.js",
  "styles": {}
}

The Avarda Checkout is embedded as an iframe using the JavaScript SDK. Load the script from javascriptUrl and initialize the checkout with the purchaseJwt token. The checkout iframe handles the complete payment flow including customer identification, payment method selection, and order confirmation.

Client-Side Event Callbacks

The Avarda Checkout JavaScript SDK provides several callbacks that your storefront should handle:

Validation and Process Flow

Implement a two-step validation flow when the customer clicks "Complete Payment":

Step 1: Validate

POST /api/checkout/v1/callback/orders/{order_id}/payments/{payment_id}/validate
Host: {slug}.api-se.stage.norce.tech
x-merchant: {merchant}
x-channel: {channel}
Authorization: Bearer {token}

Step 2: Process (if validation succeeds)

POST /api/checkout/v1/callback/orders/{order_id}/payments/{payment_id}/process
Host: {slug}.api-se.stage.norce.tech
x-merchant: {merchant}
x-channel: {channel}
Authorization: Bearer {token}

The process endpoint checks that the order has not changed since validation, updates consents, billing and shipping address, and transitions the Norce order and payment state.

Confirmation Page

After successful payment completion, Avarda can display a thank you page within the checkout iframe if showThankYouPage is enabled. Alternatively, redirect the customer to your own confirmation page. The payment details can be retrieved using the GET payment endpoint to display order confirmation information.

Troubleshooting (Avarda Specific)

In addition to the generic troubleshooting steps:

• Review the order status in Avarda's admin portal.
• Check that the Avarda order has been fully processed (ProcessedBackEnd: true).
• Use the refresh endpoint to update available payment actions:

POST /api/order/v1/orders/{order_id}/payments/{payment_id}/refresh
Host: {slug}.api-se.stage.norce.tech
x-merchant: {merchant}
x-channel: {channel}
Authorization: Bearer {token}

Common Errors

• 409 Conflict: A payment already exists for this order.
• avarda-order-expired: Checkout session expired, create new payment.
• Capture Fails: Order must be in reserved state and Completed in Avarda.

Payment States

Links and References

• Avarda Checkout Adapter OpenAPI Specification
• Avarda Checkout 3.0 Documentation (External)