Merit
Sign in
Discover›SaaS›Stripecom
SaaS

GitHub Sponsors Enables Global Open-Source Funding with Stripe

S
GitHub Sponsors
59/100validation score
60000000$
total investments facilitated in open-source software
103countries
countries supported on the platform
5x
increase in global country coverage

GitHub Sponsors used Stripe Connect, Payments, Radar, and Invoicing to launch a global open-source funding platform in two months, expand to 103 countries, and reduce dispute-handling time by 20 hours per month.

“Partnering with Stripe provided a brand that enterprises know, tools to maximise trust and compliance and the capability to scale across the globe.”

— Kevin Crosby, Senior Director of Open-Source Funding

“Given the nature of GitHub Sponsors, we encounter credit card testing. Stripe's new dispute process helps us monitor for fraudulent activity and prevent it at scale.”

— Kevin Crosby, Senior Director of Open-Source Funding

“Large organisations like Microsoft can participate in GitHub Sponsors since customers can request a single invoice, pay and set up sponsorship within minutes.”

— Kevin Crosby, Senior Director of Open-Source Funding

“Like so much of the internet, open source is a fundamental part of what we do at Stripe.”

— Mike Fix, Engineer and Head of Open Source
Hero image

Hero image

1

About the Vendor

Stripe is a global payments infrastructure company offering products including Connect, Payments, Radar, and Invoicing. Stripe enables businesses to accept payments, manage fraud, handle global payouts, and streamline invoicing at scale.

2

About the Brand

GitHub Sponsors is a program by GitHub that enables organisations and businesses to make one-time or recurring payments to developers working on open-source projects, helping maintain, secure, and innovate the software that underpins the global digital supply chain.

3

Challenge

GitHub Sponsors needed a simple, trustworthy, and scalable onboarding experience for developers and funders globally, including in developing nations like India and Brazil. The platform required compliance with local regulations, tools to prevent credit card fraud, and an enterprise-grade invoicing system to replace a slow, manual process that was preventing organisations from participating. Rapid launch and scaling were also priorities.

4

Solution

GitHub Sponsors launched with Stripe Connect in 2019 for international developer payouts in local currencies. Stripe Payments (including the Payments Intelligence Suite with Adaptive Acceptance, network tokens, and card account updater) was implemented to optimise payment performance. Stripe Radar was deployed for AI-powered fraud detection, and Smart Disputes was adopted to automate chargeback responses. Stripe Invoicing replaced the manual invoicing process, enabling enterprises to request, pay, and set up sponsorships within minutes.

5

Execution

GitHub Sponsors integrated Stripe Connect within two months of launch in 2019. The platform progressively adopted additional Stripe products — Payments, Radar, Smart Disputes, and Invoicing — to address fraud, dispute management, and enterprise billing needs as the program scaled globally.

6

Results

GitHub Sponsors launched its Stripe Connect integration in just two months. The platform has since facilitated over $60 million in open-source investments and expanded from 22 to 103 supported countries. Invoicing time was reduced from days to minutes, and the platform saw a 13% year-over-year increase in new organisations requesting invoices. Smart Disputes saved 4–5 hours of work per week, reducing dispute-handling time by approximately 20 hours per month.

Tech Stack

Stripe ConnectStripe PaymentsStripe RadarStripe InvoicingSmart DisputesAdaptive Acceptance

Validation breakdown

Audited against Merit's standard
Evidence quality57/100

How well the outcomes are documented and traceable.

Authority signals62/100

Brand recognition, client relationship, and external references.

M
Merit Validation Team✓ Verified
Independent audit · Merit standard

Data source: declared · none

View original source →