Labs · Research note
What a payments integration tells an acquisition buyer
A corrected row in the embedded payments provider map shows how much a public disclosure can support. It names the infrastructure and the launch date, and leaves revenue, exclusivity and contracting parties for further evidence.
- Credit
- Acquiry
- Version
- 1.0
- Date
- Built on
- Provider map, edition 1.1
One row changed in edition 1.1
In the record squarespace-stripe, the evidence field has new wording. It is the only cell that differs between edition 1.0 and edition 1.1. All ten records are still present, and the dataset still holds 10 records, 8 platforms, 5 providers and 9 source URLs.
Edition 1.0 · Published 13 November 2026
Stripe describes helping Squarespace move from Stripe-branded payments to Squarespace Payments. The branded offering used its Connect implementation.
Edition 1.1 · Evidence checked 13 November 2026
Stripe says its Connect and Payments products provide payments infrastructure for Squarespace merchants. Squarespace launched its branded payments offering in 2023.
Record squarespace-stripe. Source for both: Stripe Squarespace case study (opens in a new tab). The role (Embedded infrastructure), the provider (Stripe) and the time scope (Branded rollout began in 2023) did not change.
Which statement changed
The earlier wording told a migration story. It said Stripe describes helping Squarespace move from Stripe-branded payments to Squarespace Payments, and it said the branded offering used its Connect implementation. The revised wording makes two plain statements instead: Stripe says its Connect and Payments products provide payments infrastructure for Squarespace merchants, and Squarespace launched its branded payments offering in 2023.
Why a buyer would care
A shortlist often starts from a sentence such as “this platform runs on that provider”. The two wordings support different sentences. The revised one supports a statement about which products provide infrastructure for the platform's merchants and when the branded offering launched. It makes no claim about migration history or about which implementation sits under the branded offering, so a buyer who relied on the earlier sentence should read the new one before repeating it.
What this disclosure does not establish
The public disclosure identifies infrastructure and the launch date. Revenue attributable to a supplier, exclusivity, and the identity of every contracting party would each need further evidence. Read the source (opens in a new tab).
See the same idea at work in Who actually supplies this brand? It starts from this Squarespace row, then lets you correct a fictional ten-shop count and rerun the numbers.
The ten rows are a selective sample
The edition holds 10 records for 8 software platforms and 5 providers, each tied to one of 9 source URLs. The rows were chosen to show how different documents support different roles. They are not a census, and no share of any market can be read from them. Counts below come from the released CSV.
| Role | What it means | Records |
|---|---|---|
| Embedded infrastructure | A participant documents infrastructure used in a named offering. | 5 |
| Named processor | The platform’s terms name the processor for the specified product. | 1 |
| Supported gateway | Platform documentation lists a compatible option. Merchant adoption is unresolved. | 2 |
| Legacy integration | Documentation limits an integration to a pre-existing population. | 1 |
| Announced expansion | A participant announced a geographic or product expansion. Actual rollout may differ. | 1 |
| All records | 10 | |
Exercise: read one role against its source
Choose one of the five roles. You will see every published row with that role and the single document behind it. Open the source and check whether it supports the wording on the row, and no more.
- Inputs
- records.csv, edition 1.1. SHA-256
a1b27cdd18cde3ff98a72d49115b44681107064a53bb43814054709cd5351e81 - Run
- Filter the relationship_type column to one role, count the rows, then open each source_url and compare it with the evidence cell.
- Expected
- Embedded infrastructure: 5 · Named processor: 1 · Supported gateway: 2 · Legacy integration: 1 · Announced expansion: 1 · Total: 10
Pick a role to see the rows it covers and the document behind each one.
The 10 published records
| Record | Platform and product | Provider | Role | Source |
|---|---|---|---|---|
| jobber-stripe | JobberJobber Payments | Stripe | Named processor | Jobber Payments terms, section 3 (opens in a new tab) |
| lightspeed-adyen | LightspeedLightspeed Payments, hospitality | Adyen | Embedded infrastructure | Adyen hospitality case study (opens in a new tab) |
| lightspeed-tyro | LightspeedRestaurant POS, O-Series | Tyro | Legacy integration | Lightspeed Tyro integration guide (opens in a new tab) |
| cloudbeds-windcave | CloudbedsCloudbeds PMS, Australia and New Zealand | Windcave | Supported gateway | Cloudbeds supported gateways (opens in a new tab) |
| cloudbeds-authorizenet | CloudbedsCloudbeds PMS, US, Canada and Australia | Authorize.net | Supported gateway | Cloudbeds supported gateways (opens in a new tab) |
| mindbody-stripe | MindbodyMindbody Payments | Stripe | Embedded infrastructure | Stripe Mindbody case study (opens in a new tab) |
| squarespace-stripe | SquarespaceSquarespace Payments | Stripe | Embedded infrastructure | Stripe Squarespace case study (opens in a new tab) |
| roller-adyen | ROLLERROLLER Payments | Adyen | Embedded infrastructure | Adyen ROLLER partner record (opens in a new tab) |
| fresha-adyen | FreshaEmbedded platform payments | Adyen | Embedded infrastructure | Adyen Fresha announcement (opens in a new tab) |
| toast-adyen | ToastUS expansion of payments partnership | Adyen | Announced expansion | Adyen Toast announcement (opens in a new tab) |
About this work
- Material type
- Research note and public-data exercise
- Credit
- Acquiry (organisational)
- Version
- 1.0, 13 November 2026
- Canonical URL
- https://www.acquiry.com/labs/reading-a-provider-map/
- Data
- Embedded Payments Provider Map for Software Platforms, edition 1.1, evidence checked 13 November 2026
- Scope
- 10 published rows covering 8 software platforms and 5 providers. A selective sample, not a census of any market.
- Method
- Read each published row and the one document that establishes it. See the map’s methods page for how rows are selected and worded.
- Limitations
- Counts describe these ten rows only. A public document supports the statement it makes and nothing wider.
Sources used in this note: the Stripe Squarespace case study (opens in a new tab) and the 9 source URLs listed in the table above.
Cite this work
The dataset carries a canonical URL citation. A DOI will be added only after it resolves publicly and matches this edition.
The data, edition 1.1
Acquiry (2026). Embedded Payments Provider Map for Software Platforms, edition 1.1 [dataset]. 10 records, 8 platforms, 5 providers, 9 sources. Evidence checked 13 November 2026. https://www.acquiry.com/data/embedded-payments-provider-map/editions/1.1/
This note
Acquiry (2026). What a payments integration tells an acquisition buyer [research note], version 1.0, 13 November 2026. https://www.acquiry.com/labs/reading-a-provider-map/
Download the CSV (edition 1.1)MethodsEdition 1.1What changed between editions
Spot an error?
Send the work ID labs-reading-a-provider-map, the edition, the row anchor and the source through the corrections channel.