Md Mojno M.

I build the accounting and payment integrations that generalist developers get wrong — the ones that reconcile, survive an audit, and don't create duplicate transactions when a webhook fires twice. Most "integration" work on the market is Zapier/Make glue that breaks the moment the data gets complicated. I'm not that. I'm a Python/Django engineer who understands double-entry accounting, so I can explain why a posting is correct — not just that the script ran. WHAT I DO • QuickBooks Online / accounting-system integrations (OAuth 2.0, token refresh, rate-limit handling, bill/invoice/payment sync) • Stripe integrations — subscriptions, Connect/marketplace payouts, dual-level platform + tenant billing • Idempotent sync engines — duplicate-webhook protection, retry/backoff, replayable error queues • Audit-grade logging: every write traced with user, timestamp, payload, and outcome • Reconciliation reporting that ties source-system balances to the accounting system and holds up under review PROOF, NOT CLAIMS I built CashSheets, a multi-tenant double-entry accounting SaaS, solo — including a pluggable integration framework connecting QuickBooks Online, Square POS, and Wave, plus dual-level Stripe billing (platform + tenant). This isn't theoretical accounting knowledge; it's a production system I architected and shipped. I also maintain open-source reference implementations on GitHub (django-saas-kit, wagtail-subscriptions on PyPI) — real, tested code you can read before you hire me. TECH Python, Django, DRF, PostgreSQL, Celery/Redis, Docker, AWS. Integrations: QuickBooks Online, Stripe, Square, Wave, Shopify, PayPal, webhooks, REST APIs, OAuth 2.0. ALSO When a project needs more than backend integration — frontend, infrastructure, deployment — I lead delivery with a vetted team, so you get the whole build coordinated through one point of contact. If you need an accounting or payment integration built by someone who actually understands the accounting, let's talk.