This document is a guide to connecting Github Sponsors for Organizations to your Collective. This option is currently only available for Collectives fiscally hosted by the Open Source Collective (not Open Collective Europe or other fiscal hosts), which will hold the funds on behalf of your project.
Note: Transaction data about the funds you receive through GitHub Sponsors will be shared with Open Source Collective in order to credit your budget.
Open Source Collective projects can use Open Collective to receive GitHub Sponsors funds by following these steps:
Confirm that you have a GitHub organization (not an individual user account). You can create a GitHub organization by following this guide.
Create a Collective for your open source project if you don't already have one. You will need to use Open Source Collective as your fiscal host. Note: Open Collective also has a thing called "Organizations" but this is unrelated. You need an Organization on the GitHub side and a Collective on the Open Collective side. Sorry for the confusing terms!
Visit github.com/sponsors and sign your Github organization up for the Sponsors waitlist. ✔️ Select: "This organization is using a fiscal host" and select Open Source Collective from the menu. ✔️ For non-profit status, answer: “Yes, this organization has nonprofit status but cannot receive tax-deductible donations from individuals (e.g., 501c6)”
Click Join Waitlist. GitHub staff will review your application, and you'll be notified when you can proceed to the next step.
Once your application has been approved by GitHub, you need to connect Open Source Collective's Stripe account by following the below steps.
When you first click on the Stripe Connect account link, you will be taken to a Stripe sign up page.
You will be asked to select the country where you legally operate from, or receive payouts in.
As Open Source Collective is a US entity, select United States.
Enter your own phone number and email, which will be used to verify the account and to send updates.
Next, you will be asked to verify the phone number you gave:
Once the phone number is verified, you will start filling out details about the fiscal host, Open Source Collective.
This next section is asking questions about the business. As a Collective fiscally hosted by Open Source Collective, you need to enter OSC’s details here.
Legal business name:
Open Source Collective
Doing business as:
Name of your Collective
If you are asked for an EIN or "commercial registry number", put in OSC's EIN: 82-2037583.
Next, you will be filling out details as the acting executive for the Collective. Use your personal information on this page.
Finally, you will input bank account information. Funds you receive through GitHub go to Open Source Collective’s bank account, so they can credit the money to your Collective’s budget on Open Collective.
After that, you should be all set! ✌️😎
The standard Open Collective and Open Source Collective fees apply to funds raised via GitHub Sponsors: 10%. GitHub does not charge a fee.
Confusingly, GitHub and Open Collective use the word "organization" to mean two different things.
On GitHub, you need to create an Organization to use Sponsors for your project.
On Open Collective, you need to create a Collective for your project (Organizations on Open Collective are a different profile type, for companies who sponsors open source projects, i.e. for paying money out not accepting money).
Sometimes Stripe will ask for extra info as part of their normal security protocols. If this happens, you can provide Open Source Collective's organizational info as described above.
The address for KYC purposes is the same: 340 S LEMON AVE #3717, Walnut CA 91789 USA. If they ask for anything you don't know the answer to, please contact [email protected]