| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| B2B BNPL and net terms | Receivables and billing | 0% | 17 of 90 | 17% | 6 | under 10 labels · led by Resolve Pay at 56% |
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 0 | 1 | 0 | 1 |
| GPT-5.4 mini | 0 | 0 | 0 | 0 | 0 |
| Gemini 3.5 Flash | 0 | 0 | 0 | 0 | 0 |
| Perplexity Sonar | 0 | 0 | 0 | 0 | 0 |
| Grok 4.1 Fast | 0 | 1 | 0 | 0 | 1 |
| Mistral Small | 0 | 0 | 0 | 0 | 0 |
| DeepSeek V4 Flash | 0 | 0 | 0 | 0 | 0 |
| Llama 4 Maverick | 0 | 0 | 0 | 0 | 0 |
| Qwen 3.7 Flash | 0 | 0 | 0 | 0 | 0 |
| Kimi K2 | 0 | 1 | 0 | 0 | 1 |
| GLM 4.7 FlashX | 0 | 1 | 0 | 1 | 2 |
| MiniMax M2.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-6 Luna | 0 | 0 | 0 | 0 | 0 |
| Muse Glimmer 30B | 0 | 0 | 1 | 0 | 1 |
Verbatim evidence the judge attached to positive labels.
“Capchase | SaaS/software | Multi-year contracts; revenue-based | Flexible for subscriptions” Grok 4.1 Fast · B2B BNPL and terms · paraphrase prompt · alternative
“For SaaS businesses, Capchase Pay is purpose-built for your model.” Kimi K2 · B2B BNPL and terms · paraphrase prompt · alternative
“Built for recurring‑revenue SaaS models” GLM 4.7 FlashX · B2B BNPL and terms · comparative prompt · alternative
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
“user reviews (found on G2) highlight specific operational friction points that suggest caution” GLM 4.7 FlashX · B2B BNPL and terms · negative prompt · soft negative
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 22 of the 22 answers that named Capchase Pay and are not a share of its labels.
Eighty-six of the eighty-six domain citations in answers naming Capchase Pay came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read October 5, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
| Kind | Pages | Last 90 days | 2025-11 to 2026-10 | Latest | Categories named |
|---|---|---|---|---|---|
| Blog | 261 | 1 | 2026-07-22 | Cash flow forecasting, Revenue recognition | |
| Glossary or explainer | 112 | 0 | 2025-09-03 | ||
| Comparison | 40 | 0 | 2025-09-03 | ||
| Webinar or virtual event | 25 | undated | |||
| Case study | 11 | undated | |||
| Template or tool | 5 | 0 | 2025-02-11 | ||
| Report or ebook | 2 | undated | |||
| News or press | 2 | undated | |||
| Podcast or video | 1 | 0 | 2025-02-11 |
Every page capchase.com exposes, subdomains included. Kind is read from the address and title. The last 90 days, the latest date and the twelve months count pages by when they were published, from the site's feeds, a date in the address, or the page's own publication date, read from up to a hundred of its most recently changed pages; a page that says only when it last changed is counted in its kind but not in when, so the recent counts are a floor, and a kind none of whose pages gives a publication date reads undated. An event counts as online when its address or title says so (webinar, on demand, virtual or online summit); a conference, summit, trade show, expo or roadshow that does not say so is counted as a conference or event, which on a vendor's site is mostly in person. Read October 5, 2026.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
What Capchase Pay's own pages state, read October 5, 2026: capchase.com, capchase.com/platform, capchase.com/customers, capchase.com/integrations. A claimed page can correct any of them.
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Capchase Pay's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Capchase Pay, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for Capchase Pay by email, built from the raw record of the edition. It shows: