You will get a prioritized audit of your payment flow and what will break
Project details
Payments break in quiet, expensive ways - webhooks that fire twice, double charges, balances that don't reconcile. This is a focused review of your payment flow before it costs you money.
I'm a backend engineer with 5 years in production fintech. I check exactly what quietly breaks in production: webhook idempotency, double-charge and double-fire risk under retries, reconciliation gaps, and float-vs-integer money handling.
You get a written, prioritized report of what will break and what to fix first - clear enough to hand straight to a developer. A low-risk way to see how I work, delivered in 3 days. No production access needed - sandbox/test keys and read access to the code are enough.
I'm a backend engineer with 5 years in production fintech. I check exactly what quietly breaks in production: webhook idempotency, double-charge and double-fire risk under retries, reconciliation gaps, and float-vs-integer money handling.
You get a written, prioritized report of what will break and what to fix first - clear enough to hand straight to a developer. A low-risk way to see how I work, delivered in 3 days. No production access needed - sandbox/test keys and read access to the code are enough.
Programming Languages
PHP, Python, GoCoding Expertise
Performance Optimization, SecurityWhat's included $200
These options are included with the project scope.
$200
- Delivery Time 3 days
- Number of Revisions 1
Frequently asked questions
About Paraxatdin
Fintech & Payments Backend Engineer | Laravel, Go, Stripe & Webhooks
Tashkent, Uzbekistan - 9:30 am local time
I'm a backend engineer with 5 years of production experience, focused on payment and banking systems at a fintech: payment-gateway integrations, idempotent webhook handling, settlement & reconciliation, double-entry ledgers, and subscription billing and KYC flows that have to be correct, not just "done."
What I can do for you:
- Stripe / Laravel Cashier billing, subscriptions & metered usage - with idempotency keys, webhook signature verification, and retry-safe handlers
- Payment-gateway / PSP integrations (Stripe, PayPal, local gateways) reconciled against settlement reports
- Double-entry ledgers, balance integrity & reconciliation routines you can trust
- Subscription billing, dunning, and KYC/AML onboarding flows
- Backend APIs in Laravel (PHP) and Go - clean, tested, documented
- Hardening existing payment code - fixing duplicate-charge / double-fire webhook bugs
Stack: PHP 8 / Laravel (Cashier, Sanctum/Passport, Filament, queues), Go, Python, PostgreSQL/MySQL, Redis, REST APIs, Docker. I use modern AI tooling (Cursor/Claude Code) to ship fixed-scope work faster - but every payment-critical decision (idempotency, concurrency, reconciliation) is reviewed by me, not the model.
How I work: based in Tashkent (UTC+5), available evenings and weekends in a fixed daily window, with a written end-of-session update so you always know where things stand. Strong overlap with EU/UK afternoons and the Gulf; fully async-friendly for US clients.
If you've got a payments or billing problem - a new integration, a reconciliation mess, or a webhook that double-charges - message me with what's breaking and I'll tell you how I'd approach it.
Steps for completing your project
After purchasing the project, send requirements so Paraxatdin can start the project.
Delivery time starts when Paraxatdin receives requirements from you.
Paraxatdin works on your project following the steps below.
Revisions may occur after the delivery date.
Review your payment code
I go through your webhooks, idempotency, retry handling, reconciliation, and money handling, looking for what quietly fails in production.
Prioritize the risks
Every issue I find is ranked by how likely it is to cost you money, so you know exactly what to fix first.