Loading...
Loading...
Public changelog
This is the public release log for Payvra feedback work. Read it when you need to verify whether a roadmap item shipped, what changed in the product, and whether rollout details affect your team.
Use the navigation below to move between incoming requests, public sequencing, and shipped release notes without leaving the public acquisition layer.
What gets logged
Release notes should cover changes that alter merchant behavior, developer workflows, or operator posture in production.
How to read it
Start with the summary, then follow the linked docs or feedback path if you need the implementation and rollout context.
Why it matters
Shipping should leave public evidence. The changelog exists to close the loop between a request, the work, and the live product state.
Feedback is part of the product proof system. A request, a roadmap state, and a changelog entry should line up cleanly enough that a new team can follow the trail.
The changelog should be specific enough that a team can judge whether a release changes implementation work, rollout timing, or operator behavior without opening a support ticket.
Release-note rule
Avoid vague phrases like "general improvements." If a change is worth shipping, it is worth describing plainly.
Filter the public release log
Narrow the changelog by search term, change type, or date window if you need to confirm when a request landed.
Check back once the first shipped update lands. The changelog will explain what changed and why the release matters.