| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Payment orchestration platforms | Receivables and billing | 0% | 80 of 81 | 100% | 2 | under 10 labels · led by BlueSnap at 18% | |
| B2B payment acceptance | Receivables and billing | 0% | 42 of 94 | 0% | 1 | under 10 labels · led by Versapay at 19% | newNew since September 2026: not ranked then, 0% now. |
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-5.4 mini | 0 | 0 | 0 | 0 | 0 |
| Gemini 3.5 Flash | 0 | 0 | 0 | 0 | 0 |
| Perplexity Sonar | 0 | 1 | 0 | 0 | 1 |
| Grok 4.1 Fast | 0 | 0 | 0 | 1 | 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 | 0 | 0 | 0 | 0 |
| GLM 4.7 FlashX | 0 | 0 | 0 | 0 | 0 |
| MiniMax M2.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-6 Luna | 0 | 0 | 0 | 0 | 0 |
| Muse Glimmer 30B | 0 | 0 | 0 | 1 | 1 |
Verbatim evidence the judge attached to positive labels.
“Square or PayPal Payments, though their card fees are higher than ACH-focused tools” Perplexity Sonar · B2B payment acceptance · budget 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.
“Users feel that the fees are expensive, particularly affecting small payments and international transactions.” Muse Glimmer 30B · Payment orchestration · negative prompt · soft negative
“High fees (esp. small/international txns), poor support responsiveness, and excessive conversion costs” Grok 4.1 Fast · Payment orchestration · 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 7 of the 7 answers that named PayPal Payments and are not a share of its labels.
Thirty-three of the thirty-three domain citations in answers naming PayPal Payments came from somebody else's page.
Pages are listed as the models cited them.
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 PayPal Payments's own pages state, read October 6, 2026: developer.paypal.com/checkout/refund-payment, developer.paypal.com/payment-methods/uncaptured-payments, developer.paypal.com/sdk/payment/v2, paypal.com/de/digital-wallet/send-receive-money, paypal.com/au/brc/payments/payment-methods. 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 PayPal Payments'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 PayPal Payments, 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 PayPal Payments by email, built from the raw record of the edition. It shows: