Collection rails

    Collect the way each country actually expects.

    Cross-border billing tends to assume a card. Business buyers in much of Europe do not pay by card — they expect an invoice through the channel their finance system already reads, and collection through the rail their bank already supports. This is the part of the stack that has to be local to work.


    Rails

    Structured per country so a new one is a row rather than a rewrite.

    Cards — everywhere — Supplied as part of the platform rather than assembled from your own acquirer relationship. One onboarding, one release schedule, one statement.

    Invoicing — everywhere — Payment terms, dunning and reconciliation on the invoice rail, priced differently from cards because a bank transfer does not carry card economics.

    Leverandørservice — Denmark — The Danish B2B direct-debit rail. Collections are filed on the bank calendar, and the mandate is established by the debtor with their own bank — we cannot create one on their behalf, and any page that says otherwise is wrong.

    Nordic rails — in progress — Analogues to Leverandørservice in the neighbouring markets. Listed here when they ship, not before.

    Leverandørservice — dansk side


    E-invoicing, built in

    Peppol, NemHandel and OIOUBL are part of the platform rather than a connector you buy separately. A Danish public-sector buyer who requires OIOUBL gets OIOUBL; a Peppol participant gets Peppol under their own participant ID or under one we help register.


    See what it costs

    The invoice rail is priced differently from cards, and both are published for Managed.

    Pricing and the two modes

    Choose for today. Change tomorrow.