Embedded payments provider map · Edition 1.0

Who powers payments for eight software platforms?

Ten public records answer it. Five document embedded infrastructure, one names its processor, and the other four describe a supported gateway, a legacy integration or an announced expansion. Each row names the product, the provider and the document that establishes the role.

Research cut-off 13 November 2026 · Published 13 November 2026 · How the map is built

10
Scoped records
8
Software platforms
5
Named providers
9
Primary documents
Bar chart of the ten records by relationship type: embedded infrastructure 5, named processor 1, supported gateway 2, legacy integration 1, announced expansion 1.
What a payment provider listing proves. Counts describe the ten selected records only. Download the chart (PNG)

What the sources establish

Read the role before you count the relationship.

  • A listing is narrower than a contract

    Two rows document supported gateways, one covers an integration for existing accounts only, and one records an announced expansion. These support a narrower statement than a verified, live customer contract.

  • Distribution and processing can sit with different companies

    A software company may own merchant distribution while another business provides processing infrastructure. Counting a gateway listing as an active operator relationship can distort a target shortlist.

  • The next diligence request is specific

    The strongest follow-up identifies the product, the legal counterparty, the market and the active merchant base.

Role mix: number of records per relationship type
Relationship typeRecords
Embedded infrastructure5
Named processor1
Supported gateway2
Legacy integration1
Announced expansion1

The records

Every record, with its source.

A processor named in a platform’s terms, a supported gateway and a legacy integration answer different buyer questions. Read the product scope before counting the relationship. Each row links to its primary source and has a stable address you can cite.

All 10 records shown

Full dataset, all 10 records (CSV)
Embedded payments provider records, one row per scoped assertion
PlatformProvider and roleProduct and time scopeWhat the source says
Jobberjobber-stripeStripeNamed processorJobber PaymentsTerms dated 19 Dec 2025Jobber names Stripe, Inc. as the processor and reserves the right to change provider. Jobber Payments terms, section 3 (opens in a new tab)Source checked 2026-11-13 ·
Lightspeedlightspeed-adyenAdyenEmbedded infrastructureLightspeed Payments, hospitalityCollaboration began in 2020Adyen describes a move from referrals to a white-label payments offering for Lightspeed. The start date of the later white-label phase is unspecified. Adyen hospitality case study (opens in a new tab)Source checked 2026-11-13 ·
Lightspeedlightspeed-tyroTyroLegacy integrationRestaurant POS, O-SeriesExisting enabled accounts onlyLightspeed retains instructions for merchants already using the Tyro integration. It restricts availability to existing enabled accounts. Lightspeed Tyro integration guide (opens in a new tab)Source checked 2026-11-13 ·
Cloudbedscloudbeds-windcaveWindcaveSupported gatewayCloudbeds PMS, Australia and New ZealandGateway list checked 13 Nov 2026Cloudbeds lists Windcave as a supported gateway in Australia and New Zealand. The listing establishes compatibility. Cloudbeds supported gateways (opens in a new tab)Source checked 2026-11-13 ·
Cloudbedscloudbeds-authorizenetAuthorize.netSupported gatewayCloudbeds PMS, US, Canada and AustraliaGateway list checked 13 Nov 2026Cloudbeds lists Authorize.net for these three countries. The record covers a configuration option for properties. Cloudbeds supported gateways (opens in a new tab)Source checked 2026-11-13 ·
Mindbodymindbody-stripeStripeEmbedded infrastructureMindbody PaymentsCase study checked 13 Nov 2026Stripe identifies Connect as the infrastructure Mindbody selected for its payments platform, including onboarding and payouts. Stripe Mindbody case study (opens in a new tab)Source checked 2026-11-13 ·
Squarespacesquarespace-stripeStripeEmbedded infrastructureSquarespace PaymentsBranded rollout began in 2023Stripe describes helping Squarespace move from Stripe-branded payments to Squarespace Payments. The branded offering used its Connect implementation. Stripe Squarespace case study (opens in a new tab)Source checked 2026-11-13 ·
ROLLERroller-adyenAdyenEmbedded infrastructureROLLER PaymentsPartner listing checked 13 Nov 2026Adyen identifies itself as a payments infrastructure provider for the venue-management platform. Adyen ROLLER partner record (opens in a new tab)Source checked 2026-11-13 ·
Freshafresha-adyenAdyenEmbedded infrastructureEmbedded platform paymentsProvider disclosure checked 13 Nov 2026Adyen describes an existing embedded payments relationship with Fresha while announcing a separate capital product. This row covers payments. Adyen Fresha announcement (opens in a new tab)Source checked 2026-11-13 ·
Toasttoast-adyenAdyenAnnounced expansionUS expansion of payments partnershipAnnounced 10 Aug 2026Adyen announced that its Toast partnership would expand into the US, building on an earlier relationship in other countries. Merchant rollout remains unspecified. Adyen Toast announcement (opens in a new tab)Source checked 2026-11-13 ·

Source check ledger

Nine sources, ten records.

Each primary document was opened and read on the date shown. Two Cloudbeds records rely on one document for two separate gateway options, so the ten records rest on nine distinct sources. A publisher’s own description is labelled as that publisher’s claim.

  1. 01

    Checked

  2. 02

    Checked

  3. 03
    Lightspeed Tyro integration guide (opens in a new tab)

    o-series-support.lightspeedhq.com · supports lightspeed-tyro

    Checked

  4. 04

    Checked

  5. 05

    Checked

  6. 06

    Checked

  7. 07

    Checked

  8. 08

    Checked

  9. 09

    Checked

Downloads

Take the data with you.

Every file is public and needs no form or login. Each file has a SHA-256 hash, listed in the edition manifest, so you can confirm that what you cite is what we published. Edition 1.0 is kept permanently at its own address.

Reuse: cite this page and the record ID. No open licence has been declared for this edition, and no DOI has been issued.

Cite this edition

How to cite it.

Cite the edition, and the record ID with its primary source when you rely on a single assertion. The edition is dated and permanent, so the figure you cite stays checkable after later corrections.

Plain text

Acquiry Market Maps (2026). Embedded payments provider relationships in software platforms, Edition 1.0 [Data set]. Acquiry. Research cut-off 13 November 2026. https://www.acquiry.com/data/embedded-payments-provider-map/

BibTeX

@misc{acquiry_market_maps_embedded_payments_1_0,
  author       = {{Acquiry Market Maps}},
  title        = {Embedded payments provider relationships in software platforms},
  year         = {2026},
  edition      = {1.0},
  publisher    = {Acquiry},
  type         = {Data set},
  note         = {Research cut-off 13 November 2026},
  url          = {https://www.acquiry.com/data/embedded-payments-provider-map/}
}

Edition 1.0 · research cut-off 13 November 2026 · published 13 November 2026 · permanent edition page

Scope

What these ten records do and do not show.

The sample favours accessible English-language disclosures. A missing supplier remains unknown, and the absence of evidence is not a negative assertion. Two Cloudbeds records use the same document.

The records do not establish merchant adoption, customer counts, exclusivity, revenue, market share or willingness to sell. For acquisition diligence, establish the product line and the legal counterparty before attributing revenue. Read the methods.

Review status: prepared by Acquiry Market Maps as a desk review of public documents. A named second reviewer has not been recorded for this edition.

Corrections

Spot an error? Tell us.

Send the record ID, the fact you believe is wrong and a dated public source. Use “Copy a correction request” on any row to start with the text pre-filled, then send it through our contact form. We verify the source, correct the ledger and publish a dated entry; the original edition is preserved.

Send a correctionCorrections and changes

Edition 1.0 has had no corrections since publication. See our corrections policy.

Acquisition searches

Briefing an acquisition in payments or software?

Acquiry turns a buyer’s criteria into conversations with the right owners, including businesses not for sale. Tell us what you want to acquire and we will come back to you directly.

Start a confidential brief

Keep reading