E-commerce & Customer Portals

Shops, checkouts, subscriptions and customer accounts, built on the payment code we already run in our own products.

Most of the commerce code we have written does not sit in a classic retail shop: it takes money inside our own software. bkg.dk collects deposits for salons through Stripe Connect, jasms.dk sells SMS credit through Stripe Checkout and invoices business customers afterwards, and danadresse.dk bills API usage through a Stripe meter. That is the machinery a webshop needs too: products and prices, checkout, webhooks, refunds, receipts and an account page.

We will not show you a portfolio of fashion shops, because we do not have one. Where a shop needs a catalogue that staff edit, we build on WooCommerce and add our own plugins. Where the logic is unusual, such as usage-based prices, deposits or business accounts with credit, we write it ourselves in FastAPI and keep the payment provider's hosted pages for the card details.

What we build for online sales

Online stores

A shop with a product catalogue, variants, shipping and VAT. When your staff will add products themselves, we use WooCommerce with a lean theme and as few third-party plugins as possible; when the catalogue comes from a supplier feed, we sync it by SKU so product URLs never change. On msdf.dk we used WooCommerce as a price catalogue: 7,510 pages with a fixed assembly price, updated in server-side batches at about 0.04 seconds per product, because the REST API with all its hooks was more than twenty times slower. There, the add-to-cart button became a prefilled request form.

Checkout built for your flow

A standard checkout asks for too much and checks too little. We remove fields you do not need, fill in Danish addresses as the customer types and validate CVR numbers for business buyers. Our free plugin Lynbro Danadresse, published on wordpress.org, fills street, postcode and city in WooCommerce checkout, including the newer block checkout, from a DAWA-compatible address API. In bkg.dk the chosen time is held for ten minutes while the customer pays, so two people cannot buy the same slot.

Stripe and MobilePay integration

We integrate payments as code you can read: Stripe Checkout or Payment Element, signed webhooks, and a stored record of every processed event, so a webhook that Stripe retries never charges or books twice. In bkg.dk each salon is its own Stripe connected account and can switch on MobilePay through Stripe. A direct Vipps MobilePay ePayment integration with the merchant's own keys has completed a full payment cycle, signed webhooks included, in the Vipps MobilePay test environment. Which provider is cheapest for you is for you and your bank to compare; we make the one you choose work.

Stock and catalogue sync

Stock figures go wrong when they live in two places. We connect the shop to the one system that owns the number, whether that is a supplier feed, an ERP or the accounting system, and sync on a schedule with a log of every change. We have not built a warehouse system. What we have built is catalogue sync: for msdf.dk, 12,827 IKEA and 780 JYSK products collected from public product data, priced by rule and upserted by SKU. A variation-swatch plugin of ours keeps an availability index for 1,200 variations in 3.1 KB.

Customer portals

A portal lets customers see orders, invoices and usage without writing to you. We have built several. The danadresse.dk dashboard shows API keys, usage, bulk jobs and billing. The LynBro PBX account page has a subscription-and-invoices tab with six months of usage and invoices as PDF. For a Danish construction company we built a quote link the customer opens on a phone to accept or reject the offer without creating an account. Sign-in can be a plain e-mail and password or our single sign-on, LynBro ID.

Subscriptions and usage billing

Recurring revenue needs more than a monthly price: trials, plan changes, failed cards, and usage that is counted and billed afterwards. danadresse.dk reports every address lookup to a Stripe billing meter, so customers pay for what they used. LynBro PBX and bkg.dk sell monthly plans as Stripe subscriptions, and new salons on bkg.dk start with a 30-day trial of the Pro plan. One Stripe rule we learned the hard way: the customer portal refuses two prices with the same interval on one product, so each plan has to be its own product.

B2B sales and invoicing

Business customers want an invoice, not a card form. For jasms.dk we run postpaid accounts with a credit limit and a billing cycle next to prepaid top-ups, and per-customer prices calculated from the real cost of each route plus a fixed margin. Company data fills itself in: CVR lookup on sign-up, and check digits for CVR, EAN and IBAN validated before an order is saved. The bookkeeping side can be connected to e-conomic, Dinero or Billy through jakonto.dk, our own API across Danish accounting systems.

Abandoned-cart recovery

A reminder an hour after a customer leaves the basket can win back a sale, as long as it is lawful and not annoying. We build it as an automation: the shop records the basket, a workflow in n8n or in the shop sends one or two messages, and every e-mail carries a one-click unsubscribe. We have not yet run cart recovery for a client shop. What we bring is sending discipline from our own systems: nothing reaches real customers before you have approved the template and seen it arrive on your own address, and the consent behind each message is stored.

Payment and commerce code we run today

bkg.dk

Our booking software for salons, live since 14 September 2026. Payments: deposits as a fixed amount or a percentage, a saved card for no-show fees, a Stripe connected account per salon with charges made directly on the salon's account, and MobilePay through Stripe. Webhook events are de-duplicated in the database in the same transaction that applies them.

jasms.dk

Our SMS gateway with the sender's own name. Prepaid customers top up through Stripe hosted Checkout with verified webhook signatures; business customers run postpaid with a credit limit. Before the top-up went live we ran 24 payment scenarios against the Stripe API and added 11 unit tests for signature checks.

danadresse.dk

A DAWA-compatible Danish address API that we run since DAWA closed. A free plan and paid plans sold through Stripe Checkout, usage counted by a Stripe billing meter, and a dashboard with keys, usage, bulk cleansing jobs and billing. Its 56 endpoints include validation of CVR, EAN and IBAN numbers.

Lynbro Danadresse for WordPress

Free plugin on wordpress.org that fills in Danish addresses in WooCommerce checkout, block checkout included, and in form plugins such as WPForms, Gravity Forms, Fluent Forms and Formidable. It was approved after 18 days and two review rounds, and both changes the reviewers asked for concerned security.

Tools for e-commerce

Stripe (Checkout, Billing, Connect, meters, webhooks), MobilePay through Stripe and Vipps MobilePay ePayment, WooCommerce for catalogue shops, FastAPI with MySQL or PostgreSQL for custom commerce logic, Celery and Redis for queued work such as payment reconciliation, and n8n for order and e-mail workflows. We prefer the provider's hosted payment pages, so card numbers never pass through your server.

Prices

E-commerce solution
from 10,000 DKK
One integration (payment, accounting, shipping)
from 1,000 DKK
E-mail automation (order or cart e-mails)
from 2,000 DKK
Hourly rate
500 DKK/hour
Project support
600 DKK/month

All prices are ex. VAT, and card or MobilePay fees are set by the payment provider, not by us. The price depends on the number of products and variants, payment methods, subscriptions or business accounts and the systems orders must reach; a fixed quote follows a free scoping talk requested through the contact form.

How a commerce project runs

1

Map the money flow

Who pays, when, with what, and where the money ends up: card, MobilePay, invoice, deposit or subscription. We draw this before choosing a platform, because a deposit or a usage price rules some shop systems out from the start.

2

Everything in test mode first

Successful payment, declined card, refund, dispute, a webhook retried several times: each scenario runs in Stripe test mode with a script you can rerun. The first live payment is made with your own card, never a customer's.

3

Go live behind one switch

Live keys go in as one complete set behind a single switch; if one key is missing, the shop stays in test mode and says which. Going back is the same switch, so a bad launch costs minutes, not a day.

4

Reconcile the first weeks

We compare orders, provider payouts and the accounting export every day for the first weeks and fix mismatches while they are small. After that you can keep us on project support for updates and changes.

Frequently Asked Questions

WooCommerce, Shopify or custom code?

WooCommerce when you want to own the shop and edit products in WordPress. A hosted platform such as Shopify when you want the least upkeep and standard flows are enough; we can add integrations or a booking widget to it. Custom code in FastAPI when the money flow does not fit a shop system, for example usage billing, deposits or credit accounts for businesses.

Can you add MobilePay to our existing shop?

Usually yes. If you already use Stripe, MobilePay can often be switched on as a payment method there, with Stripe handling the payout. Otherwise we integrate Vipps MobilePay ePayment directly with your own merchant keys. Either way we test the full cycle, including refunds and the webhook that confirms the payment, before it goes live.

Do you store our customers' card numbers?

No. Card details are entered on the payment provider's hosted page or field, and our code only receives a token and the result. That keeps card data off your server and reduces the security requirements you have to meet. Saved cards for later charges, such as no-show fees, are also stored at the provider.

Can business customers pay by invoice instead of card?

Yes. We build accounts with a credit limit and a billing cycle, so orders are collected and invoiced monthly, with CVR and EAN checked at sign-up. Overdue invoices can be followed up automatically; for Danish payment reminders under the Interest Act we would connect our product jaryk.dk rather than build that part again.

What do you need from us to start?

A product or price list in any format, the payment methods you want, access to your payment provider account in your company's name, and a short description of how orders are handled today, from order to shipped and booked. With that we can map the flow and give you a fixed price.

⚡

Get an Instant Price Estimate

Use our interactive calculator to get an approximate price for your project in 2 minutes.

⚡ Calculate Price

Ready to Cross the Bridge?

Let's build your lightning bridge to digital transformation. From first consultation to live deployment — we move fast.

Get Started Today