Receipt #79267 to JHipster
By Ember Buck
on Expense scheduled for payment
By Ember Buck
on Expense processing
By Ember Buck
on Expense paid
Amount Paid for Expense: $2,520.00
Payment Processor Fee (paid by JHipster): $20.00
Net Amount for JHipster: $2,520.00
Net Amount for Christophe Bornet: $2,520.00
Collective balance
Expense policies
Expense policies
File an invoice only when you are requesting payment for services you personally performed. We can only pay the individual who completed the work -- no third parties or friends. The person who performed the work must be the owner of the account receiving payment.
We have strict requirements for what we can and cannot process. Certain information is required on all invoices, and we cannot process payment if required information is missing.
Please review our full policies before submitting:
https://docs.oscollective.org/for-hosted-member-projects/spending-money-and-getting-paid
https://docs.oscollective.org/for-hosted-member-projects/spending-money-and-getting-paid
If your expense is missing required information or documentation, you will be asked to revise it before processing can begin.
Processing and Payment:
- Expenses are processed twice weekly after approval by a Collective administrator and a secondary OSC review
- Payments are made via PayPal or Wise (bank transfer)
- Payments are limited to countries supported by these providers
- If you use PayPal, you may be required to complete a KYC process
An uploaded invoice is not required -- the information entered in the expense form is sufficient.
If you choose to upload an invoice, address it to:
Collective/Project Name, Open Source Collective
440 N. Barranca Avenue #3939
Covina, CA 91723, USA
- Create a Pull Request that fixes a ticket with the “$$ bug-bounty $$” label.
- In order to close the ticket automatically, you must have one commit message with the Fix keyword. For example, Fix #1234 to close ticket #1234.
- That Pull Request must be merged by someone from the core team. If there are several Pull Requests, the core team member either selects the most recent one or the best one - that’s up to them to decide what is best for the project.
- You can then add an expense for the bounty amount on the JHipster OpenCollective. You must add a link to your Pull Request in the description (for example, a $100 bug bounty claim for https://github.com/jhipster/generator-jhipster/pull/1234). You will also need to provide an invoice, see the Open Collective FAQ for expenses for more details, and to get a Google Docs template that you can use.
- Then, you must add a comment on your Pull Request, telling that you claimed the money, with a link to your OpenCollective expense. This is to be sure it is the same person who fixed the issue and claimed the money.
- That expense will then be validated by @jdubois, @deepu105, or @pascalgrimaud and you will receive your money on your Paypal/bank account.
FAQ
How do I get paid from a Collective?
Submit an expense and provide your payment information.
How are expenses approved?
Collective admins are notified when an expense is submitted, and they can approve or reject it.
Is my private data made public?
No. Only the expense amount and description are public. Attachments, payment info, emails and addresses are only visible to you and the admins.
When will I get paid?
Payments are processed by the Collective's Fiscal Host, the organization that hold funds on their behalf. Many Fiscal Hosts pay expenses weekly, but each one is different.
Why do you need my legal name?
The display name is public and the legal name is private, appearing on receipts, invoices, and other official documentation used for tax and accounting purposes.
Collective balance
$74,259.63 USDFiscal Host:
Open Source Collective