Open Collective
Open Collective

Invoice #117514 to JHipster

$300 bug bounty claim for

Invoice #117514

Submitted by Renan FrancaApproved by Pascal Grimaud

Jan 7, 2023

Invoice items
$300 bug bounty claim for
Date: January 7, 2023
$300.00 USD

Total amount $300.00 USD

Additional Information


$61,719.46 USD

payout method

Email address  

By Renan Francaon
Expense created
By Pascal Grimaudon
Expense approved
By Ember Buckon
Expense scheduled for payment
By Ember Buckon
Expense processing
By Ember Buckon
Expense paid
Expense Amount: $300.00
Payment Processor Fee (paid by JHipster): $0.25
Net Amount for JHipster: $300.25

Collective balance
$61,719.46 USD

Fiscal Host
Open Source Collective

Expense policies

We process expenses twice a week after an admin of the Collective has approved them. We make payments via PayPal and Bank Transfer (using Wise) and can only make payouts to countries served by these payment processors. You are not required to upload an invoice document (the data you submit in the expense form is sufficient), but if you would like to include an uploaded invoice, please make it out to:
Collective Name, Open Source Collective, 440 N. Barranca Avenue #3939, Covina, CA 91723, USA

Please refer to the documentation here for payment processing requirements on reimbursements and invoices.

If you would like a refund, please email [email protected] with the transaction #, the collective you donated to, the date, and the amount of the transaction.

  • 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 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.


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

$61,719.46 USD