Integrations
Integrations and API
MetroPay connects to the services a workspace needs to bill and get paid, under your own accounts. This page says what those are, and what does not exist yet.
Plainly
No REST API — an MCP server for AI assistants
MetroPay has no REST API, no outbound webhooks, and no Zapier or similar connection. It does have a Model Context Protocol server: an AI assistant such as Claude, ChatGPT, Cursor or Claude Code can work inside a workspace as the member who connects it, at the access level that member grants. How that works, and what it can and cannot do. If you would build something against a REST API, the message you send from the contact page is read by the people who would make it.
In place today
Four services, each doing one job
These are the providers the sub-processors page names. None of them is something you install: each works under your own account, or on our side of the line, as described.
Stripe
Card payments, in your own Stripe account
Connect a Stripe account from Settings, Payment gateways. Customers pay by card on the invoice page and the money settles with Stripe under your own agreement with them; MetroPay never holds it.
SSLCommerz
Cards and mobile payments in Bangladeshi taka
Enter your own SSLCommerz store credentials in Settings, Payment gateways. Cards, bKash, Nagad and mobile banking, settled in your own account. The credentials are stored encrypted and never returned to the browser.
Postmark
Delivers every invoice, reminder and receipt email
Mail goes out from the MetroPay sending address by default, or from your own domain once you verify it with the DNS records shown in Settings, Email. Every message is logged with its delivery status.
Cloudflare
Serves the site and issues certificates for your own domain
When you run invoice and payment pages on a subdomain you own, Cloudflare issues and renews the certificate at its edge once the DNS records you publish are verified. Until then, pages keep being served from MetroPay.
Next best action
Need something that is not here?
There is no REST API, no outbound webhook and no Zapier connection today — AI assistants connect through the MCP server instead. What people ask for shapes what gets built next, so a message that says what you would connect, and why, is the most useful thing you can send.