
Integrations
Over a hundred external APIs connected so far: payments, invoicing, CRMs, portals, messaging, deposit protection, e-invoicing. I make them boringly reliable.
What it covers
- Payments and direct debit, with webhooks that reconcile on their own.
- Invoicing and accounting: invoices, receipts and credit notes created automatically for every payment and refund.
- CRMs and lead portals, with automated lead qualification.
- National e-invoicing and VAT-number checks for e-commerce.
- SMS and WhatsApp gateways and bots.
- ERP and internal systems: one clean link between the website and the back office.
- Browser automation and Android emulation where a system has no API, hidden behind one stable interface.
- Airline booking validation at checkout: one service in front of airline APIs, browser automation and boarding-pass OCR, answering in seconds (Obsentum).
- Image delivery: a custom Go + S3 service behind Cloudflare's edge that cut an online shop's image bill by more than 99% (Obsentum).
What a check looks like
PASSWebhook signature verified
PASSDuplicate delivery ignored (idempotent)
PASSFailed call retried with back-off
FAILReconciliation: one payment without invoice
UNKNOWNProvider sandbox: could not verify
Checks only read; nothing is changed automatically.
How it runs
Map the flow
What triggers what, who owns each system, what happens on failure.
Build with retries and idempotency
A repeated event must never create a second invoice.
Test against sandboxes and replayed events
Before real money or real customers are involved.
Monitor and reconcile
Alerts for what failed, a report for what did not match.
What you receive
- Working integrations with tests and monitoring.
- A one-page map of every flow and its failure handling.
- A reconciliation report finance can read.
A good fit when
Your systems exist but do not talk to each other, or they talk and nobody trusts the numbers.
Need integrations that stay reliable?
Send a short message: what you run, what worries you, any deadline.
Get in touch