One API for Every Gateway You Connect
NMI, Authorize.Net, Stripe, and PayPal each have their own API. Midcove gives you one payment gateway API instead — the same request and response shape no matter which gateway the merchant's MID is boarded with.
Integrate once, regardless of gateway
A merchant's MID might sit on NMI today and Stripe tomorrow. Instead of writing and maintaining separate integrations for each, you build against Midcove once and let us handle the routing underneath.
- Integrate once regardless of which gateway your MID is boarded with.
- Every sale, void, and refund call follows one consistent request and response shape.
- Switch or add a gateway later without touching your integration code.
- Webhooks fire in the same format across every gateway, so one handler covers them all.
POST /v1/transactions/sale
Content-Type: application/json
Authorization: Bearer sk_live_51Nx...
{
"mid": "mid_8k2p91",
"amount": 4200,
"currency": "USD",
"card": {
"number": "4111111111111111",
"exp_month": "09",
"exp_year": "2027",
"cvv": "123"
},
"order_id": "ORD-10493"
}From your app to any gateway in three steps
Call the Midcove API
Send a sale, void, refund, or lookup request to one endpoint using your MID.
Midcove routes it
We match the MID to its boarded gateway — NMI, Authorize.Net, Stripe, or PayPal — and send the request there.
Get one response format back
The result comes back in the same shape every time, along with a webhook if the status changes later.
Unified API questions
Do I need a different integration for each gateway?
No. Midcove's unified API gives you one payment gateway API to integrate against. It works the same whether the MID behind it is boarded with NMI, Authorize.Net, Stripe, or PayPal.
What happens if I switch or add a gateway later?
Your integration code doesn't change. Because every request and response follows the same shape, adding or switching a boarded MID to a different gateway doesn't require rewriting your sale, void, or refund calls.
Do webhooks work the same way across gateways?
Yes. Webhook events use the same payload structure regardless of which gateway processed the underlying transaction, so your webhook handler doesn't need gateway-specific logic.
Is the unified API a wrapper around each gateway's own API?
Yes. Midcove sits between your application and the gateway. You call Midcove's API once, and Midcove routes the request to the correct boarded MID and gateway behind the scenes.
Build on one API, not four
See full request examples and get API access for your boarded MID.