First off, yes, Stripe uses Stripe to bill our own customers. In fact, for our larger customers who have negotiated complex pricing plans, we're currently migrating much of our manual billing to a system that's inspired by Stripe Billing.
Second, this article seems to miss the point of Stripe. It seems to want to build a platform, which is what Stripe Connect is designed for.
For example, charging a percentage fee is just one line (https://stripe.com/docs/api/application_fees):
` $application_fee_percent = 5`
Slack, Atlassian, and Notion have all built their B2B billing on top of Stripe. But we don't target just B2B or B2C ecommerce in case a business has multiple revenue streams (which many businesses are increasingly adding). In fact, we designed Billing so it can flex across any business model—per-seat, usage-based, tiered, or even graduated.
This is the point of Stripe. A single stack that flexes with your business as it grows and pricing that's public.
Second, this article seems to miss the point of Stripe. It seems to want to build a platform, which is what Stripe Connect is designed for.
For example, charging a percentage fee is just one line (https://stripe.com/docs/api/application_fees):
` $application_fee_percent = 5`
Slack, Atlassian, and Notion have all built their B2B billing on top of Stripe. But we don't target just B2B or B2C ecommerce in case a business has multiple revenue streams (which many businesses are increasingly adding). In fact, we designed Billing so it can flex across any business model—per-seat, usage-based, tiered, or even graduated.
This is the point of Stripe. A single stack that flexes with your business as it grows and pricing that's public.