You run Briqpay. Now build ecommerce around it.

Briqpay is a Swedish payment orchestration platform built for B2B ecommerce. It combines invoice, credit assessment, and multiple payment methods in a single checkout layer, giving merchants control over how business buyers pay. For ecommerce teams with B2B flows — particularly those dealing with credit lines, company identification, and mixed buyer segments — Briqpay is relevant when standard consumer-focused checkout providers fall short.

But connecting Briqpay to an ecommerce platform is only part of the picture. How checkout performs in production depends on the platform, the ERP, and the delivery work that ties everything together.

What Briqpay does in the stack

Briqpay sits between the ecommerce platform and the payment providers. Rather than connecting directly to a single payment provider, Briqpay orchestrates multiple providers behind one checkout interface. The merchant defines rules for which payment methods, credit limits, and fraud checks apply to which buyer segments — and Briqpay routes accordingly.

This orchestration layer is valuable for B2B, where the same store might serve a credit-approved wholesale customer paying by 30-day invoice and a new buyer who needs real-time credit assessment before checkout completes. Consumer payment methods like card and Swish can sit alongside business invoicing in the same flow.

Everything outside that checkout moment — product catalogue, pricing rules, cart logic, order management, fulfilment, returns — belongs to the ecommerce platform and the ERP. The integration between Briqpay and those systems is where most project complexity lives.

Briqpay across platforms

On Norce, Briqpay is a natural fit for B2B-heavy commerce setups. Norce handles complex pricing, customer-specific catalogues, and multi-market logic. The integration requires mapping buyer data from Norce to Briqpay's credit and payment rules, and ensuring order status flows cleanly back through the pipeline.

On Shopware, Briqpay integrates through the payment plugin layer. Shopware's open architecture gives flexibility in how payment states, buyer segments, and checkout flows are configured — but that flexibility requires careful testing to ensure every combination works.

On Shopify, Briqpay can be connected as a payment provider, but Shopify's standardised checkout limits how much B2B-specific logic can be applied. For simpler B2B setups or merchants using Shopify Plus, it works. For complex credit flows, the constraints surface quickly.

On Magento/Hyvä, Briqpay benefits from Magento's mature B2B capabilities — company accounts, purchase orders, credit limits. Hyvä improves frontend performance while the payment orchestration runs through Briqpay's layer.

Across all platforms: Briqpay's orchestration works, but the surrounding platform context — how buyer data, pricing, and order management connect — determines whether checkout actually performs under real conditions.

Payment orchestration for mixed segments

Many Nordic merchants sell to both businesses and consumers from the same store. Briqpay's rule engine lets merchants define different payment flows per buyer type. A consumer might see card and Swish. A known business buyer might see invoice with pre-approved credit. A new business buyer might trigger a real-time credit check before any payment method is offered.

This kind of routing requires clean buyer data from the platform. Company numbers, registration details, and customer group assignments need to flow into Briqpay at the right point in the checkout. If the platform cannot reliably distinguish between buyer types, the orchestration breaks down regardless of how well Briqpay is configured.

Briqpay and the ERP connection

For merchants running a Nordic ERP — Fortnox, Visma, Business Central, or similar — payment data from Briqpay needs to reach the business system accurately. Invoice references, credit decisions, capture events, and settlement data all need to land in the right accounts.

Junipeer handles this middleware layer. When Briqpay connects through a platform that also runs Junipeer, payment events and order data flow through to the ERP without manual reconciliation. This is especially important for B2B, where invoice matching and credit tracking create operational overhead if not automated.

When Briqpay fits — and when to complement it

Briqpay is strongest when B2B payment logic drives checkout complexity: credit assessment, multiple payment providers, buyer-segment routing, and invoice management. For merchants who sell primarily to businesses in the Nordics, or who need to orchestrate several payment providers behind one checkout, Briqpay addresses a real gap.

For pure B2C, Klarna or Svea may be simpler starting points. For international expansion beyond the Nordics, Adyen adds broad method and market coverage. And for merchants who already run Briqpay alongside other providers, the orchestration model itself can evolve as the payment stack grows.

Beyond the integration

Connecting Briqpay to the platform is one deliverable inside a larger project. Checkout UX for B2B buyers, data quality in the product catalogue, company account structures, credit workflow design, QA across payment scenarios, and rollout planning all surround the integration. A B2B checkout that handles edge cases — partial deliveries, amended invoices, credit limit changes mid-order — requires testing and design work that goes well beyond the API connection.

The delivery scope reflects that reality. Payment is important, but it is one component inside a broader ecommerce build.