Expenses
Newest First
All expenses
All methods
All
All
Bug bounty claim for https://github.com/jhipster/generator-jhipster/issues/27315
Category
Maintenance and Development
from Sviatoslav Makhynko to JHipster •
zł 766.11 PLN
$200.13 USD
Paid
Invoice #221134
Bug bounty claim for https://github.com/jhipster/generator-jhipster/issues/24469
Category
Maintenance and Development
from Marcelo Boveto Shima to JHipster •
$500.00 USD
Paid
Invoice #220550
Bug bounty claim for https://github.com/jhipster/generator-jhipster/issues/19658
Category
Maintenance and Development
from Marcelo Boveto Shima to JHipster •
$200.00 USD
Paid
Invoice #220549
Bug bounty claim for https://github.com/jhipster/jhipster-kotlin/issues/378
Category
Maintenance and Development
from Marcelo Boveto Shima to JHipster •
$500.00 USD
Paid
Invoice #220546
$100 bug bounty claim for https://github.com/jhipster/jhipster-lite/pull/10835
Category
Maintenance and Development
from Quentin Monmert to JHipster •
$100.00 USD
Paid
Invoice #220117
$500.00 USD
Paid
Invoice #220095
$300 bug bounty claim for https://github.com/jhipster/generator-jhipster/pull/27268
Category
Maintenance and Development
from Quentin Monmert to JHipster •
$300.00 USD
Paid
Invoice #219958
$500.00 USD
Paid
Invoice #219454
$100 bug bounty claim for https://github.com/jhipster/generator-jhipster-quarkus/pull/371
Category
Maintenance and Development
$100.00 USD
Paid
Invoice #219307
$100 bug bounty claim for https://github.com/jhipster/generator-jhipster-quarkus/pull/355
Category
Maintenance and Development
$100.00 USD
Paid
Invoice #219305
Page Total:$3,000.13 USD
Payment processor fees may apply.
Collective balance
Tags
Expense policies
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
INFORMATION REQUIRED ON EXPENSES:
Please refer to the documentation here for payment processing requirements on reimbursements and invoices.
REFUNDS:
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.
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.