Thank you for contributing to the Web Monetization specification. Your contributions help shape emerging web standards.
- Have you read the Code of Conduct?
- Check out the existing issues and see if we accept contributions for your type of issue
- (Optional) Join the Community Group and agree to the W3C Community Contributor License Agreement (CLA)
You can contribute to the Web Monetization specification in several ways.
Discussions are where we have conversations about the specification and the broader ecosystem.
If you have questions, new ideas, or want to explore something before opening an issue — join the discussion.
If you have an idea for improving the specification or introducing new functionality, open an issue describing your proposal. Please search existing issues first to avoid duplicates, and be clear about the problem you're solving and why it matters.
Early feedback is encouraged before jumping into implementation.
We use GitHub issues to track bugs, inconsistencies, or gaps in the specification. If you've found something that needs fixing, search open issues to see if someone else has reported the same thing. If it's new, open an issue — we'll use it to discuss the problem before any work begins.
When reporting an issue, please include:
- A clear and descriptive title
- A detailed description of the problem
- Links to relevant sections of the specification
- Context or examples where possible
Feel free to fork the repository and create a pull request for changes you think you can contribute — whether small fixes or larger spec changes.
The team will review your pull request as soon as possible.
The main specification source lives at specification/index.html. This file uses ReSpec, the standard tool for authoring W3C specifications.
You don't need a full development setup to contribute to the spec.
Preview changes with npx serve ./specification/ (or any other static HTTP file server) and opening http://localhost:3000/index.html.
This repository also includes:
- Web Monetization flows →
specification/flows/ - Browser extension API →
specification/extensions-api/
Prettier is disabled for files under specification/*. W3C specifications follow a formatting style that conflicts with Prettier (for example, void elements without trailing slashes), and there is currently no clean way to align the two.
This is a Community Group Draft, so iteration is expected. We only snapshot major versions of the specification — for example, the 2021-03-17 draft currently lives in specification/versions/.
For website development, see here
- Fork the repository
- Create a new branch from
main - Make your changes and commit them
- Open a pull request to
mainwith a clear title and description- Consider using conventional commit format (e.g.,
feat: add new API endpoint,fix: resolve validation error)
- Consider using conventional commit format (e.g.,
- If your PR addresses an existing issue, reference it using
Closes #123 - Be prepared to address feedback and make changes if needed
Contributor attribution (W3C requirement)
To add a contributor (other than yourself, that's automatic), mark them one per line as follows:
+@github_username
If you added a contributor by mistake, you can remove them in a comment with:
-@github_username
If you are submitting on behalf of someone else and didn't contribute directly, you can remove yourself using the same syntax.
- Maintainers will review your PR for clarity, correctness, and alignment with the specification
- Please respond to feedback promptly and make any necessary changes
- Once approved, your changes will be merged into the main branch
Thank you for contributing to Web Monetization! Join the conversation on Slack to connect with other contributors and stay up to date on developments.