Medipay for developers

Payments in your product, three lines at a time

A clean REST API over everything the portal does: create pay links, list payments, push an amount to a card machine, and hear about every event on signed webhooks.

Read the docs Get your API keys
Endpoints

Small surface, real coverage

Everything is scoped to your workspace by your API key. Full request and response shapes, with copy-paste examples, live in the docs.

POST /api/v1/paylinks Create and send a pay link
GET /api/v1/payments List and filter payments
GET /api/v1/summary Takings summary
GET /api/v1/terminals Your card machines
POST /api/v1/terminal-jobs Push an amount to a card machine
GET /api/v1/terminal-jobs/{id} Approved, declined or waiting
The public Medipay API documentation: authentication, endpoints, stored cards, webhooks and MCP, with a curl example.
The docs are public at portal.medipayuk.co.uk/docs. No account needed to read them.
🔑 API keys, per workspace

Issue and revoke keys from the portal's developer area. Every call is scoped to your practice's data and nothing else.

🪝 Signed webhooks

payment.paid and friends, delivered with an HMAC signature so you can verify every event came from us.

🤖 MCP for AI assistants

A Model Context Protocol server so Claude or ChatGPT can answer questions about your takings and create pay links with your permission.

🖥️ Card machines over REST

The same integration our portal uses: create a terminal job, the machine wakes and takes the card, you poll the outcome.

The Medipay terminal integration guide: creating a terminal job from your software, the machine taking the card, polling the outcome.
The terminal integration guide, for software that wants to drive a card machine.

Start building today

Docs are public. Keys take a minute to issue from the portal.

Read the docs Talk to engineering