Skip to content
Works

Payments & integrations

Checkout, subscriptions, and system integrations built by people who run a payments company.

Book a call

What we do

Stripe, Square, Authorize.net and PayPal setup

Subscriptions and recurring billing

Marketplace and split payments

ERP, accounting and CRM integrations

Custom APIs and webhooks

Developer experience for your own API: OpenAPI specs, SDKs and sandboxes

MCP servers, so AI coding agents integrate against your API correctly

What you get

A checkout tested against real cards and real failure cases
Webhooks that survive retries and duplicate events
Reconciliation your accountant can actually follow
Dunning and retry logic for failed subscription charges
PCI-conscious architecture: card data never touches your servers
Runbook for refunds, chargebacks, and disputes

Related work

Financial services

Payments API — MCP server and a verified integration corpus

A payments API whose official documentation disagreed with its real behaviour. We built the corpus that tells the truth, and an MCP server so AI coding agents can integrate against it correctly.

What we did

  • MCP server
  • OpenAPI 3.1
  • Contract testing
  • Developer experience
Financial services

Payments API — developer portal and integration sandbox

The place developers go to integrate card payments from a website, a system or an ERP: documentation, a sandbox merchant and a webhook receiver they can test against.

What we did

  • Developer portal
  • Webhooks
  • HMAC verification
  • Sandbox
Financial services

Payment platform — merchant portal & payouts

For a licensed payment facilitator we built the merchant portal, the transaction ledger, and the supplier-payout module used daily by hundreds of businesses.

What we did

  • Laravel
  • MySQL
  • Bank rails
  • Merchant portal
Financial services

Core ERP built for a fintech, not adapted to one

Generic ERPs assume you sell things and collect invoices. This one was built around money in motion: settlement cycles, commissions and a reconciliation that has to close daily.

What we did

  • Core ledger
  • Settlement
  • Reconciliation
  • Commissions
Hospitality

Small-hotel network — booking and payments

A hotel association needed one place for its members to take reservations and card payments without a big-chain budget.

What we did

  • Booking engine
  • Payments
  • Multi-tenant

Frequently asked questions

  • Yes, and we'll be blunt about rates. We run a licensed payment facilitator, so we read the fee schedules the same way your processor does.

Let's build something that works.

Tell us what you're trying to accomplish. We'll reply within one business day with a clear next step.

Book a call

or email hello@mdvworks.com