Invoice #279119 to WebdriverIO

Project Contribution PR webdriverio/webdriverio#14952

Paid
Invoice #279119
Maintenance and Development
Submitted by MRUNAL DIWAKAR CHAUDHARIApproved by Christian Bromann

Dec 27, 2025

Expense Details

Invoice items
Project Contribution PR webdriverio/webdriverio#14952
Date: December 23, 2025
$25.00 USD

Project Contribution PR webdriverio/webdriverio#14933
Date: December 24, 2025
$35.00 USD

Project Contribution PR webdriverio/webdriverio#14917
Date: December 24, 2025
$35.00 USD

Project Contribution PR webdriverio/webdriverio#14909
Date: December 24, 2025
$35.00 USD

Project Contribution PR webdriverio/webdriverio#14904
Date: December 24, 2025
$35.00 USD

Project Contribution PR webdriverio/webdriverio#14907
Date: December 24, 2025
$35.00 USD

Project Contribution PR webdriverio/webdriverio#14896
Date: December 24, 2025
$35.00 USD

Project Contribution PR webdriverio/webdriverio#14901
Date: December 24, 2025
$25.00 USD

Project Contribution PR webdriverio/webdriverio#14918
Date: December 24, 2025
$25.00 USD

Project Contribution PR webdriverio/webdriverio#14886" and the pull request title ("fix: detect stale elements in BiDi mode for getCSSProperty (#14885)
Date: November 29, 2025
$35.00 USD

Project Contribution PR webdriverio/webdriverio#14880" and the pull request title ("fix(wdio-cli): respect maxInstancesPerCapability for dynamic capabili…
Date: November 29, 2025
$50.00 USD

Project Contribution PR webdriverio/webdriverio#14881" and the pull request title ("fix(wdio-junit-reporter): add property support for Cucumber tests
Date: November 29, 2025
$15.00 USD

Project Contribution PR webdriverio/webdriverio#14900" and the pull request title ("added mocking for fs/promises")
Date: December 2, 2025
$15.00 USD

chore: update GitHub Actions macOS runner from 13 to 15
Date: December 12, 2025
$25.00 USD

Project Contribution PR webdriverio/webdriverio#14944 fix(webdriverio): fix wildcard support in browser.mock
Date: December 22, 2025
$50.00 USD

Project Contribution PR webdriverio/webdriverio#14957
Date: December 25, 2025
$25.00 USD

Total amount
$500.00 USD
Additional Information

Collective

WebdriverIO@webdriverio
Balance:
$5,988.19 USD

payout method

PayPal
Verified
Account details  
Email:
********

on
Expense created
on
Expense updated
on
Expense updated
on
Expense updated
on
Expense updated
on
Expense approved
on
Expense scheduled for payment
on
Expense processing
on
Expense paid

Amount Paid for Expense: $500.00

Payment Processor Fee (paid by WebdriverIO): $10.00

Net Amount for WebdriverIO: $510.00

Net Amount for MRUNAL DIWAKAR CHAUDHARI: $500.00

Collective balance
$5,988.19 USD

Current Fiscal Host
Open Source Collective

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. 
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
The goal with this collective is to sponsor development of the project as well community events. The following expense types may be eligible for reimbursement from this collective::

  • Event Expenses:
    If you host an event that has a speaker talking about using WebdriverIO and its features you can expense up to $100. Reimbursement requirements for event expenses include:
    • You or the event account must share the project on social media (Twitter, Facebook or LinkedIn) at least 3x
    • The event page must have the WebdriverIO logo and a link to the project page in your meetup description
    • You must use the funds for qualified event expenses such as food, beverage, room or equipment rental.
    • You must submit receipts with your reimbursement request.
  • Development Expenses
    If you have done development work on any of the repositories within the GitHub WebdriverIO organisation you may reimburse up to $1000 if the following requirements are met:
    • You must have submitted qualifying pull requests that have closed at least 10 issues that were labeled with “Expensable 💸
    • Every additional issue closed with that label can be expensed with $100
    • You must submit links to all issues you’ve closed due to your pull requests
    • 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.
    • Pull Requests 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 must claim an “Expensable 💸” issue by commenting to the issue thread to ensure that no one else is working on the same issue.
    • Anyone contributing to WebdriverIO is eligible to expense their work if the implemented features or bug fixes are not objectives of a commercial job.
  • Travel Expenses
    If you are a member of the Technical Steering Committee team you are eligible to expense flights and hotel accommodations for travel to conferences or meetups as part of a speaking engagement on WebdriverIO. You may expense up to $500.  Reimbursement requirements for travel expenses include:
    • You must send out a post from your main social media account (e.g. Twitter, LinkedIn or personal blog) thanking all contributors of the collective after the event took place.
    • You must use the funds for qualified travel expenses such as ground or air transportation to the event and hotel accomodations. 
    • You must submit receipts with your reimbursement request.

All expenses that meet the above requirements will be reviewed and processed by the collective administrators within 7 days of receiving the request.

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

$5,988.19 USD