What changed, and when.
A changelog is a sign of a platform that is actually maintained. This section records meaningful improvements across routing, reporting, risk operations, and the developer platform.
Entries are dated and written plainly, so operators and developers can see what changed and whether it affects them. Illustrative entries below indicate the format; live entries publish as the platform evolves.
Why the changelog matters
Transparency
See how the platform improves over time.
Developer clarity
Know when API-relevant changes land.
Operational awareness
Understand new capabilities as they ship.
Plainly written
No jargon-for-its-own-sake.
Recent (illustrative) entries
Configured with your acquiring, routing, and reporting during onboarding — and supported by a team that knows the account.
Book a call→Routing — issuer-aware retries
Refined retry timing for recurring transactions.
Reporting — scheduled delivery
Saved reports can be emailed on a cadence.
Risk — review queue workflow
Improved handling of flagged activity.
API — signed webhook events
Expanded event coverage with signatures.
What we log
Routing & risk
Improvements to orchestration and scoring.
Reporting
New reports, filters, and exports.
Developer platform
API, webhook, and SDK changes.
Changelog FAQs
Answers to the questions merchants ask most about this part of the platform.
How often is the changelog updated?
Meaningful improvements are logged as they ship. The entries shown here are illustrative of the format; live entries publish continuously as the platform evolves.
Will I be told about breaking changes?
API-relevant and breaking changes are highlighted so developers can prepare; versioning keeps stable integrations working.
Where do I see API-specific changes?
API and webhook changes are noted in the changelog and detailed in the API Docs.
Are these entries real?
The examples shown are illustrative placeholders of the format. Vertlo does not publish invented metrics or claims.