Payments MCP server for Claude, Cursor and AI assistants
Model Context Protocol lets an AI assistant use a service directly, instead of you copying things between windows. The eCom Pay MCP server gives Claude, Cursor and other MCP assistants a safe way into your account, so you can ask for a payment link or check whether an order was paid in plain English.
Docs, libraries and the prompt at docs.ecompay.co.uk. Prefer it done for you? Tell us about the app and we set it up with you.
24 hrs
approval, once documents are in
150+
currencies processed
4.5
Trustpilot rating
2010
processing payments since
Frequently asked
What is a payments MCP server?
A connector that lets an AI assistant such as Claude or Cursor work with a payments account directly. The eCom Pay MCP server lets your assistant create payment links and check payments from the chat, under your account and your two step login.
Which assistants work with the eCom Pay MCP server?
Claude, Claude Code, Cursor and any other assistant that supports the Model Context Protocol. Setup instructions are at docs.ecompay.co.uk.
Is it safe to let an AI assistant near my payments?
The assistant acts under your account, with a key you can revoke in the dashboard. Every change made is logged, refunds only happen when you choose, and card numbers are never available to it because the gateway never holds them.
Want to ask your assistant for a payment link instead of opening another dashboard?
Most of what a small business does with payments is repetitive. Send a link, check it was paid, refund the one that went wrong. With the MCP server connected, your assistant does those from the conversation you are already in, and everything still runs under your account and your login.
How the MCP server fits
You connect the eCom Pay MCP server to Claude, Cursor or any assistant that supports MCP, using a key from your dashboard. The assistant then has a set of actions, listed at docs.ecompay.co.uk, that it can perform on your behalf. Refunds are never automatic, and the assistant cannot see card numbers because the gateway never has them.
How to add card payments to your app in three steps
Create a test account
Sign up at the eCom Pay dashboard and you are in test mode straight away, with test cards. Nothing goes live until our team has approved your account, usually within one working day.
Paste the prompt into your AI assistant
Copy the eCom Pay prompt from the docs into your builder. It tells the AI how to add the card form, confirm payments and handle refunds. Test with the test cards until the flow is right.
Swap one key to go live
Once approved, we add your live account details to your dashboard. You swap your test key for the live one. Nothing else in your app changes.
The prompt to paste into your AI assistant
This is the short version. The full prompt for AI coding assistants, with the test card numbers and the signed update format, is on the docs page.
Add eCom Pay card payments to this app. Follow the integration guide at https://docs.ecompay.co.uk/ exactly. Use my test mode key until I say go live, show the embedded card form on the checkout page, confirm the order only when the signed payment update arrives, and never store card numbers.
What your checkout gets
Built and tested on the eCom Pay gateway. The same checkout whichever tool built your app.
Card details encrypted in the browser
Card numbers are encrypted on the customer's device before they leave the page. Your app and your server never see them, which keeps your build simple and your customers safe.
Embedded form or hosted page
Drop the card form into your own page, or send customers to a ready made eCom Pay checkout page when you would rather not build one.
Apple Pay and Google Pay on one switch
Turn wallets on in your dashboard. No Apple or Google developer setup on your side.
3D Secure handled for you
The bank check, including the frictionless flow, runs inside the form. Nothing extra to build.
Payment links and QR codes
One off or reusable links from the dashboard, with a QR code, WhatsApp sharing and up to three reminder emails until it is paid.
Signed order updates
Every payment, refund and dispute update is signed, so your app can prove it came from eCom Pay before it changes an order.
Refunds only when you choose
Full or partial, from the dashboard or from your own system. Nothing is refunded automatically.
Next working day settlement
Money lands the next working day with no rolling reserve, the standard eCom Pay proposes to every merchant, subject to approval.
Businesses eCom Pay approves on AI built apps
Everyday online businesses, and the specialist sectors that need a specialist. Every account is reviewed by a UK team, not an automated model.
MCP server payments, frequently asked
Can the assistant issue refunds?
Only when you ask it to, and only within the limits of your account. Nothing is refunded automatically.
Can I use it before my account is approved?
Yes, in test mode. Live actions start once the account is approved and you switch to your live key.
Does it work for developers building an app too?
Yes. Claude Code and Cursor can use it while building, to create test payment links and check test payments without leaving the editor.
Where is the full list of actions?
At docs.ecompay.co.uk, alongside the API reference and the Node and Python libraries.
Card payments for your AI built app, set up properly
One prompt to build it, test cards to prove it, one key to go live. Approved in 24 hours once your documents are in, settled the next working day with no rolling reserve.