Restore confidence in the figures.

Merchants, partners and support flagged discrepancies across payments reporting, payouts reporting and statements. Calculations and data transformations had not kept pace with improvements to the incoming data feed. I prioritised reporting consistency and clearer workflows.

My contribution

I defined requirements, redesigned the core payments and payouts screens, set acceptance criteria and approved the release before August 2026. Engineering and QA owned technical corrections and validation, including sample transaction tracing, processor-record comparisons, exception testing and finance/support involvement.

Choose what to postpone

Second-chargeback/pre-arbitration support was another possible use of engineering capacity. I weighed low incidence, recoverable amounts, fees, implementation effort and support workload, and recommended postponing it. The recommendation was accepted, keeping reconciliation and usability ahead of that capability.

Scope and decision-making

From April 2025 to August 2026, I held the sole product leadership remit across ValPay’s core product, related offerings and internal systems. I shaped strategy and quarterly priorities for CEO and CTO approval, leading primarily through influence across sales, support and engineering.

What changed after release

I observed fewer support inquiries and improved merchant satisfaction/NPS after the release. These are qualitative observations without retained figures or a comparison window.

Visual evidence

The opening map explains the prioritisation decision. Original captures of the shipped payments interface are unavailable; the Partner Portal is a separate product and is not presented as a substitute.