surfboard_white
Book a demo

Surfboard Payments

Every payment is a journey. We built every inch of it.

Surfboard is the payments platform behind financial institutions, ISVs and enterprises. In-store, online and agentic, one integration, one settlement, multi-clouds.

Start building Book a demo

Point your coding agent at Surfboard

See it in your colours

We read your public site to pick the terminals, capabilities and guides that fit, and to put your brand on the hardware. Nothing is stored on our side.

  • Licensed payment institution
  • Supervised by Finansinspektionen
  • PCI DSS 4.0, multi-cloud
Payment methods One API

Cards · Apple Pay · Google Pay · Swish · Vipps · MobilePay · Klarna · Pay by Bank · Gift cards · Invoice

The same methods, across every channel

  • In-store Countertop, handheld, mounted, outdoors
  • Tap to Pay On iPhone and Android, no terminal
  • Online Hosted pages, SDKs, server-to-server, links
  • Unattended Kiosks, EV charging, vending, transit
  • Agentic Created and paid by software over the API
One settlement. One report. One customer profile.

Trusted by

Customers include SAS, BookSalon, Liveday, CareLabs, Swepearl, AB Karl Hedin, Payer and Hemglass.

I The stitched stack

Most payment stacks aren't built. They're accumulated.

A terminal vendor. A gateway. An acquirer who owns the hardware. A reconciliation spreadsheet only one person in finance fully understands. Each new channel arrives as another integration, another report, and another wait on somebody else's roadmap.

None of it was designed. It just kept being added to.

  • 4–6

    vendors to take payments in a single shop

  • 12–24

    months waiting on a feature you don't control

  • 250+

    questions on a full PCI assessment

  • 0

    of your hardware kept when you change acquirer

II One integration

Integrate once. Get all of it.

Merchant onboarding, terminals, Tap to Pay, online checkout, tips, tokenization, gift cards, settlement and analytics arrive through the same API. Add a channel later and there is nothing new to integrate, only something new to switch on.

One POST /orders creates the order and starts the payment. initiatePaymentsOptions picks the method, card, Swish, Klarna, gift card, invoice, a saved token, and the rest of controlFunctions carries the behaviour: tips, pre-auth, delayed capture, delayed payout, surcharges, split payments, NFC tag reads.

Add an online block and the same call hands back a hosted payment page instead, 3-D Secure, tokenization, link expiry and your own redirect URLs. Nothing else about the request changes, and both land on one settlement report.

The documentation is addressable by machines as well as people, so a coding assistant can do most of the work while you read this.

  • Instant sandbox
  • llms.txt
  • MCP server
  • OpenAPI
Read the developer docs

Create an order and take a payment on a terminal

POST /orders

{
  "terminal$id": "83a3b280c51b280604",
  "referenceId": "order-3312",
  "orderLines": [
    {
      "id": "0000CHI01",
      "name": "Nike Shoes",
      "quantity": 2,
      "amount": {
        "regular": 200, "campaign": 100, "shipping": 50,
        "total": 350, "currency": "752",
        "tax": [{ "amount": 0, "percentage": 0, "type": "VAT" }]
      }
    }
  ],
  "controlFunctions": {
    "orderLineLevelCalculation": true,
    "tipsMode": "ROUNDUP",
    "delayCapture": true,
    "initiatePaymentsOptions": {
      "paymentMethod": "CARD"
    }
  }
}

What comes back

orderId
The order everything else hangs off, payments, refunds, receipts, settlement.
paymentId
One per payment attempt. Store it against the order until the payment completes.
interAppJWT
Optional app-switch token that makes inter-app CARD starts faster.

initiatePaymentsOptions is what turns order creation into a payment. Drop it and you get an order that waits.

III Every channel

In the shop. In the browser. In the agent.

01, In-person payments

In the shop

Terminals on the counter, in the hand, on the wall, and out in the weather. Tap to Pay on iPhone and Android when there is no terminal at all.

  • Countertop
  • Handheld
  • Tap to Pay
  • Unattended
In-person payments

02, Online checkout

In the browser

Hosted pages, SDKs, server-to-server, payment links. Cards, Swish, Klarna, Apple Pay, Google Pay, Pay by Bank, settled on the same report as the shop floor.

  • Hosted pages
  • SDKs
  • Payment links
Online checkout

03, Agentic commerce

In the agent

Autonomous software creates orders, triggers payments and manages the full lifecycle over the same API a human would use. Endpoints documented for LLMs.

  • Agentic
  • MCP
  • llms.txt
Agentic commerce
IV The hardware

Terminals that arrive, pair, and get on with it.

Open the box, enter a pairing code, take a payment. Every device runs the same payment application, so the terminal on the counter and the one on the delivery bike behave identically against the integration you have already written. Fleet configuration is remote, and it is an API call.

SurfTouch Pro

SurfTouch Pro

Handheld, all screen
SurfPrint Pro

SurfPrint Pro

Handheld with printer
SurfMini

SurfMini

Ultra-slim miniPOS
SurfPad Pro

SurfPad Pro

High-performance with physical PIN
SurfAlone

SurfAlone

Unattended and self-service
SurfXpress

SurfXpress

22" self-checkout
Tap to Pay on iPhone

Tap to Pay on iPhone

No terminal at all
Tap to Pay on Android

Tap to Pay on Android

No terminal at all
Every device
V Three clouds

The first multi-cloud platform to pass PCI DSS 4.0.

Active instances run on Google Cloud, AWS and Azure at the same time, three independently certified providers, in sync. If one slows, traffic moves. No manual failover, no maintenance window, no apology email.

  • Google Cloud Active
  • Amazon Web Services Active
  • Microsoft Azure Active

Under certain conditions the architecture satisfies PCI B-IP, taking your assessment from 250-odd questions down to roughly 45, close to P2PE simplicity without the P2PE bill.

What PCI DSS actually requires
VI Five hours

Our record from signing up to a live terminal is five hours.

Not a pilot, and not a sandbox, a real merchant taking real money the same working day. Most platforms measure onboarding in quarters. We had time for lunch.

  1. Minutes

    Sandbox

    Sign up and get a full test environment with every endpoint live.

  2. Hours

    Integrate

    One integration covers every channel you will ever switch on.

  3. Same day

    Onboard

    Merchants, stores and terminals configured over API or portal.

  4. 5 h record

    Go live

    Flip to production and start settling real transactions.

Create a free account
VII Beyond the transaction

The payment is where it starts.

Every authorisation carries context, who paid, on what, in which channel, at which store. The platform hands that back to you as something you can build a business on rather than a CSV you reconcile on Fridays.

VIII Proof

Regulated in Sweden. Running well past it.

Surfboard Payments AB is a licensed payment institution supervised by Finansinspektionen, the Swedish Financial Supervisory Authority. We carry the regulatory weight so the software on top of us doesn't have to.

In the press

Accepted everywhere we operate

  • Visa
  • Mastercard
  • American Express
  • Discover
  • Swish
  • Vipps
  • Klarna
  • Apple Pay
  • Google Pay
  • Samsung Pay
  • Pay by Bank
  • Dankort
Every payment method
IX Dispatches

From the newsroom

All writing

Shipped recently

Changelog
X The first wave

Come and build on it.

Spin up a sandbox this afternoon, or tell us what you are trying to launch and we will show you where Surfboard fits. Either way, the first payment is closer than you think.

Open a sandbox Book a demo

Tell us what you're building

By submitting this form, you consent to allow Surfboard Payments to store and process the personal information above to provide you with the content requested.