All posts by Anatoli Shevtsov
Every declined transaction is lost revenue. Every uncontested chargeback is money left on the table.
I’ve spent 15+ years in payments and over 20 years in technology making sure those losses don’t go unaddressed - solving one of the hardest problems in digital commerce: making payments actually work.
Authorization rates, fraud prevention, network tokenization, cost optimization, and routing strategy - these are the levers I use to recover revenue and reduce risk at scale.
I build and lead payment systems across businesses processing billions in annual volume, turning complex payment challenges into hundreds of millions in revenue.
At PetSmart, I own end-to-end product strategy for payments, fraud, and billing across eCommerce. I delivered a 6% lift in authorization rates through network tokenization and account updater implementation - recovering ~$100M in annual revenue.
Previously, I led a full payments transformation - increasing digital payment adoption by 25%, translating into $X million in incremental revenue, and improving chargeback win rates by 15% through AI-driven dispute automation, reducing manual processes and recovering millions of dollars.
I operate across the full payments stack: card networks, ACH, BNPL, wallets, smart routing, debit optimization, and compliance (PCI DSS, NACHA, GDPR, Durbin). I work across engineering, data, finance, and commercial teams - building and scaling high-performing teams while delivering payment systems that drive revenue, reduce risk, and scale.
Core Focus Areas
- Authorization optimization and conversion uplift
- Fraud prevention, dispute strategy, and chargeback recovery
- Payment orchestration, smart routing, and cost optimization
- End-to-end payment system design across card, ACH, and alternative rails
- Building roadmaps that directly impact revenue, margin, and risk
Technical Skills:
SQL, Jira, Confluence, Aha!, Salesforce, PlantUML, Python, Adyen, Stripe, ACH/NACHA, PA DSS, PCI DSS, GDPR, CCPA, Durbin Amendment, Visa, Mastercard, Amex, Discover, PULSE, STAR, CONEXXUS, IFSF/PCATS Standards
Why Merchants Should Adopt Network Tokenization
Why merchants should adopt network tokenization to improve payment security, reduce lifecycle failures, and support better authorization performance.
Recent Posts
- Payment Processing Costs: Where They Hide and How to Reduce Them
- 3D Secure 2: When to Use It, Exemptions and Liability Shift
- Merchant-Initiated vs Customer-Initiated Transactions Explained
- Card-Present vs Card-Not-Present: What Retail Payments Teams Get Wrong
- Payments KPIs: 10 Metrics Every Payments Product Manager Should Track
Recent Comments
- What Is a Chargeback and How Can Merchants Prevent It? on Supervised vs. Unsupervised Anomaly Detection in Fintech
- Network Tokenization vs. Vendor Tokenization - Anatoli Shevtsov on Why Merchants Should Adopt Network Tokenization
- AI Risk Decisioning Platform Design for Financial Workflows on Fraud Declines vs. No-Fraud Declines
- A2A Payments and the Challenge of Replacing Cards on What Is a Chargeback and How Can Merchants Prevent It?
- Fraud Declines vs. No-Fraud Declines - Anatoli Shevtsov on Why Merchants Should Adopt Network Tokenization