Payments in Omnium

Omnium integrates with a wide range of external payment providers to handle both online and in-store transactions.
When a customer completes a purchase, the selected provider (e.g. Vipps, Klarna, Stripe) authorizes the payment.

Omnium then stores the payment details on the cart and, once the cart is placed, on the order.
This allows Omnium to manage post-order operations such as capture, refund, and cancellation through the configured provider integration.

Supported Payment Providers

Omnium currently supports the following providers:

• Adyen
• Aera
• Aera Invoice
• Authorize.Net
• Avarda
• AwardIt
• Bonus Points
• Dintero
• Klarna
• Klarna v3
• N-Genius
• Netaxept
• Nets
• NetsEasy
• PayEx
• PayPal
• Qliro
• ResursBank
• Shopify
• Stripe
• Svea
• Swish
• Toss
• Vipps
• Vipps E-Payment
• Walley
• Webhook Payment
• Zaver
• Atome

Getting Started with Payments

Key Concepts

• Omnium does not provide a checkout widget.
  Your frontend application is responsible for integrating directly with the payment provider (using their SDK, redirect, or widget).

• Omnium stores and manages payment records.
  Once the provider has authorized the transaction, you must attach the payment details to the cart in Omnium.

• Omnium executes post-order operations.
  After the order is created, Omnium can capture, refund, or void the payment through the configured provider integration.

Checkout Flow

The checkout flow typically looks like this:

1. Customer completes checkout in your storefront.
2. Frontend initiates payment with the chosen provider.
3. Provider returns transaction details such as transaction ID, amount, and status.
4. Frontend calls Omnium APIs to build the cart:
   • AddPaymentToCart
   • AddShipmentToCart
   • AddCustomer
   • AddStore
5. Cart is placed as an order in Omnium.
6. Omnium can later capture, refund, or void the payment.

Adding a Payment to a Cart

Once the provider confirms the payment, you must register it in Omnium.

Endpoint

POST /api/Carts/{cartId}/AddPayment

Example payload

{
  "amount": 2070,
  "paymentMethodName": "Dintero",
  "paymentType": "Dintero",
  "status": "Processed",
  "transactionId": "T13456746.5zfEvTWmkBBjw6fTYSEE",
  "transactionType": "Authorization"
}

Field notes

• amount → total paid or authorized amount
• paymentMethodName → must match the provider name configured in Omnium
• paymentType → identifier of the provider (e.g., Dintero, Klarna)
• status → payment status from the provider (e.g., Processed, Authorized)
• transactionId → unique ID returned by the provider
• transactionType → type of transaction (e.g., Authorization, Capture, Refund)

Key Notes

• The frontend is responsible for integrating the provider in checkout.
• Omnium does not return a payment widget.
• The paymentMethodName in your API request must match the provider configuration in Omnium.
• Always attach the payment before creating the order.

In-Store Payments and Paylinks

Many Omnium payment integrations also support in-store payments. This is typically done by generating a paylink, which is sent to the customer so they can complete the payment on their own device.

Paylinks are most commonly used for:

• Payments over the phone
• Offsite payments where the customer is not physically present

For web checkouts, the approach is different:

• Your website must implement the full checkout flow with the provider.
• You must also handle the provider’s authorization callback before registering the payment in Omnium.

Next Steps

• Configure your payment provider in Omnium (Configuration → Settings → Orders → Payment Providers)
• Implement checkout flow with the provider of your choice (see provider SDK/API docs)
• Use Omnium’s APIs to attach the payment and create the order
• Manage post-order payment operations (capture, refund, void) via Omnium