# How Acquiry maps payment providers

**Edition 1. Research cut-off 13 November 2026.** This public-sources desk review covers ten selected platform, product and provider records. Each records a particular role, evidence statement, source and time scope. The scope is selective. It does not estimate provider market share, merchant counts or target availability.

## What qualifies

Start from an operator’s published terms, product documentation, a dated announcement, or a named supplier case study. Inspect the actual text and identify the product, entity or brand, supplier role, geography where stated, effective-date information and source publisher. Label a provider’s own description as such. An icon, a copied press release or a checkout screenshot is insufficient to establish a named processor. A missing supplier remains unknown. Lack of public evidence does not justify a negative assertion.

| Classification | Meaning for this edition |
|---|---|
| Named processor | The platform’s terms name the processor for the specified product. |
| Embedded infrastructure | A participant documents infrastructure used in a named offering. |
| Supported gateway | Platform documentation lists a compatible option. Merchant adoption is unresolved. |
| Legacy integration | Documentation limits an integration to a pre-existing population. |
| Announced expansion | A participant announced a geographic or product expansion. Actual rollout may differ. |

Each row has one primary classification for the specific assertion. A platform or provider may appear more than once. Counts are descriptive of the selected rows. Selective coverage reflects the availability of identifiable English-language sources. A single publisher can document different roles. Reprints or attributed quotes in one release do not supply independent corroboration. Two Cloudbeds records use one source for two separate gateway options. No customer contracts, fees, exclusivity, revenues or transaction intent have been independently audited.

## Updating the record

Keep the record ID stable when correcting its text. Record the old interpretation, new interpretation, affected edition, source, reviewer and date in a public amendment entry. If a relationship is replaced by a different one, retire its original identifier and give the new relationship a new identifier. Update the website and issue a new archive edition when underlying data changes. Preserve the earlier citable snapshot. Link both editions and explain whether a figure changed. A refreshed retrieval date alone is insufficient to change the research cut-off.