Svitlana H.

I test the part of your product where mistakes cost money. Fourteen years in QA, with the last several focused on payment flows, checkout, and recurring billing — the places where a bug is not a cosmetic annoyance but a failed charge, a double charge, or a subscription that silently stops renewing. What I do: Checkout and payment journeys end to end: card entry, tokenization, gateway responses, declines, 3DS challenges, retries and failed-payment recovery. Subscription and recurring billing logic: renewal schedules, plan changes, proration, volume and tiered pricing, dunning. Webhook and async flow testing, where the UI says one thing and the backend state says another. I don’t stop at the interface. I verify what actually happened — API responses in Postman, records in the database via SQL, event logs, and network traffic in DevTools. A confirmation screen is not proof that the money moved correctly. How I work: I build structured test documentation rather than ad-hoc checks: test plans, suites, cases and checklists that your team can keep using after the engagement ends. I’ve set up testing processes and defect-reporting standards from scratch on teams that had none. I’m also hands-on with Playwright in Python for UI and API automation, so manual coverage can be converted into a regression suite instead of staying manual forever. Where I’ve worked: E-commerce and subscription platforms (Shopify ecosystem), SaaS payment and transactional workflows, regulated gaming, and analytics platforms serving enterprise clients including 3M, P&G and Mattel. Tools: Postman, Playwright (Python), SQL, Chrome DevTools, Sentry, Kibana, Jira, TestRail, Zephyr, Confluence, GitHub. If you’re launching a checkout, migrating a payment provider, or seeing charges that don’t reconcile — tell me what’s happening and I’ll tell you how I’d find the cause.