surfboard_white
Book a demo

For enterprise merchants

Two hundred stores, one configuration model.

Dozens of payment methods, multi-channel acceptance, per-store configuration, daily reporting into the ERP, and offline resilience so that one store losing its line does not become chain-wide downtime. Surfboard ships those operational primitives without the integration overhead of a multi-vendor stack.

Book a demo Read the API docs
  • 1 Configuration cascade, chain to terminal
  • 1 Daily settlement file into your ERP
  • Offline Store-level outage resilience
A large retail operation
I Operating at scale

One Platform for Every Channel, Every Store, Every Brand

Most enterprise merchants assemble their payment stack from 5-10 vendors. One for in-store, one for online, one for SoftPOS, one for tokenization, one for reporting, one for terminal logistics. Every vendor adds reconciliation overhead, integration debt, and operational risk.

Surfboard collapses that into a single platform. Unified Commerce as the default. Cascading configuration that scales to thousands of stores. Cross-channel reporting that plugs into your ERP. Offline resilience built into the firmware. Enterprise SLAs and PCI DSS 4.0 multi-cloud certification, operational posture that holds up to the procurement scrutiny enterprise IT applies.

II What enterprises run

Why enterprise merchants choose Surfboard

Six reasons chains and multi-location operators select Surfboard over assembling a vendor stack.

  • One Stack for Every Channel

    Enterprise merchants run in-store, online, in-app, unattended, and SoftPOS payments, usually with separate vendors and disconnected reporting. Surfboard ships Unified Commerce as the default: one API, one ledger, one settlement, one customer profile across every channel.

    • One integration project, not five
    • One reconciliation pipeline
    • One customer view across in-store and online

  • Cascading Configuration at Scale

    Enterprise = thousands of stores, dozens of brands, hundreds of terminal types. Surfboard's cascading configuration model, chain → store → terminal, means you set defaults once and override only where needed. Branding, tipping, payment methods, all configured at the level that fits.

    Roll out a new tipping policy across 500 stores with one PATCH call. Update terminal lock screens for a seasonal campaign in minutes.

  • Reporting Built for Finance Pipelines

    Daily settlement reports per store, per merchant entity. SFTP delivery to your ERP. Cross-channel breakdowns. Adjustments ledger for tip and surcharge audit. Built to plug into NetSuite, SAP, Workday, Visma, Fortnox, or whatever finance system your company already runs.

    No more re-typing CSVs. No more manual export. No more reconciling between processors.

  • Offline-Resilient Operations

    Network failure shouldn't mean lost sales. Surfboard's offline payment modes keep terminals processing when connectivity drops, with configurable risk controls and automatic sync when the network returns.

    Critical for retail, F&B, and hospitality at scale, single-store outages don't propagate into chain-wide downtime.

  • Cross-Channel Customer Recognition

    A customer who buys online and visits the store is the same customer. Surfboard's tokenization unifies them, the same network token represents the card across every channel, enabling loyalty, identification, and personalization across all surfaces.

  • Enterprise-Grade Operational Posture

    PCI DSS 4.0 multi-cloud. 99.99% uptime. 9 active instances across GCP, AWS, and Azure. SLAs that hold up to procurement scrutiny. The compliance posture and resilience track record enterprise procurement teams expect.

    Pair with the Logistics API for programmatic terminal lifecycle management, replacements, returns, and fleet upgrades through the API instead of support tickets.

III Reach for these first

The capabilities enterprise merchants use most

Each one is reachable from the integration you have already written. Nothing below is a separate product to buy.

IV The estate

Multi-brand, multi-store, one configuration model

If your business runs multiple brands under one corporate entity, Surfboard's branding cascade keeps each brand's identity preserved while sharing the underlying infrastructure. Set defaults at the chain level. Override per brand. Override per store. Override per terminal. Same model for tipping, payment methods, and identification policies.

The way enterprise payment configuration should have always worked.
V In code

Talk to our enterprise team

Enterprise deployments come with dedicated solutions architects, custom SLA frameworks, and migration playbooks. Get in touch to walk through your specific stack.

Talk to our enterprise team
// Configure store-level tipping policy across a chain
  PATCH /merchants/:chainMerchantId/tips
  {
    "tipConfig": "ENABLED",
    "tipLevel1": 10,
    "tipLevel2": 15,
    "tipLevel3": 20
  }

  // Override at flagship locations only
  PATCH /stores/:flagshipStoreId/tips
  {
    "tipLevel1": 15,
    "tipLevel2": 20,
    "tipLevel3": 25
  }

Build it yourself

Step-by-step developer guides for everything on this page.

In-store · Guide
Multi-Merchant Terminals

Set up shared payment terminals for multiple merchants using the Multi-Merchant Group API. Ideal for food courts, events, and co-located businesses.

Read guide Online · Guide
Store Management

Create, update, verify, and manage in-store and online stores using the Surfboard Payments Store APIs.

Read guide Online · Guide
Settlements & Reporting

Retrieve settlement reports, view adjustments, manage merchant charges, and register customer profiles for reconciliation and billing.

Read guide In-store · Guide
Device Registration

Register a terminal to a store before it can take payments or receive a partner POS app. Covers rotating codes, QR/registration links, pre-shipped codes, and in-app registration for SoftPOS.

Read guide
Browse all developer guides