You are a developer with a deadline. Your team has decided to charge customers on a recurring basis, and you have been asked to put together a shortlist of billing vendors by Friday. You open the Subscription Billing & Invoicing use case on apis.io, because a catalog with scored providers seems like a sensible place to start.
The page says it scopes 35 providers. That sounds thorough. Then you start reading the names.
The top of the list looks respectable. Airwallex leads at 83.8, followed by WSO2 at 83.0, Didomi at 80.0, Token.io at 71.6, Adyen at 71.1 and Avalara at 69.9. All six are in the exemplar band. Amberflo sits lower, at 46.5 in the developing band. But as you go through them, you notice that most are not what you would call a billing engine. WSO2 is an API management platform with monetization features. Didomi is consent management. Token.io is open-banking payments. Only Amberflo, which does usage metering and pricing, is a billing engine in the sense a builder means.
Further down, it gets stranger. Ace Hardware is on the list at 28.8. So are Urban Outfitters at 26.0, Agilent Technologies at 29.4 and Crystal Reports at 24.5. Two other members, management and monetization, are not companies at all. They are topic-collection records the catalog created itself, and they score 9.6 and 8.6.
Now you look for the names you expected. Stripe is not there. Neither are Chargebee, Recurly, Zuora, Lago or Metronome. All of them have records in the catalog. They are simply not in this use case. By their Kin Scores, Stripe is at 81.1, Chargebee at 48.5, Lago at 38.4, Metronome at 37.4, Recurly at 35.7 and Zuora at 35.5. If Stripe Billing were admitted, it would rank third. Chargebee, the company most people would name first for subscription management, would land in the developing tier.
The post that reports all this does not shrug it off. It says plainly that this is the finding and that it is the catalog's to fix. The page counted 35 providers and 822 APIs in August, led by Avalara at 75.7. The provider count is the same today, but the API count is 228. The band mix has moved toward the middle, with 6 exemplar, 6 strong, 11 developing, 3 thin, 7 emerging and 2 minimal. Airwallex now holds the top spot. Same headline number, a different set of facts underneath.
The explanation is mechanical. The use case matches on 26 raw terms, from "API Monetization" to "Customer Invoicing". A word like "monetization" catches retailers with affiliate programs and analytics vendors with billing features, while the dedicated billing vendors evidently carry tags the matcher does not read. Membership by keyword rewards the vocabulary a record happens to use, not the job the company does.
That changes how you use the page. You were about to treat 35 as a measure of the market. It is really a measure of which records happen to use certain words. A count that looks authoritative can be wrong about the very thing you came to learn, and here the catalog says so about itself.
So you do not shortlist from the list as shown. You take the post's own answer instead: for the engine, Stripe, Chargebee, Lago, Metronome, Recurly, Zuora and Amberflo, plus Avalara for tax, which the post notes is still the part that goes wrong. Those eight names go to your team on Friday.
The post also says what would fix the page, and all of it is on the catalog's side: admit the billing vendors by what they sell, drop the topic-collection records, and stop matching retailers on the word monetization. Until that happens, you know to read membership and ranking separately, and to check who is absent as carefully as who is present.
Read the original: https://apis.io/2026/10/22/subscription-billing-lists-ace-hardware-and-misses-stripe/