Zip Payment MCP. Manage the entire order lifecycle, from checkout to refund.

Listen up. This isn't some boilerplate API wrapper that sits there doing nothing until you write three hundred lines of middleware. The Zip MCP Server connects your merchant account—your actual payment processing setup—directly to your agent. It lets your AI client handle the entire Buy Now, Pay Later (BNPL) lifecycle without you having to write any clunky integration code yourself.

You're gonna manage everything from initial checkout intent right through to final financial cleanup using simple natural language commands.

When you use this server, your agent handles complex payment state logic—the stuff that always trips up developers who think they can just call a single endpoint and be done with it. It manages the whole process for both US and global payments, letting you stop switching between different merchant portals to get something simple done.

Managing Checkout Sessions

Need to start a payment? You use create_zip_checkout. This tool kicks off a new checkout session, requiring specific inputs like an amount, a currency code, and the necessary redirect URLs. It doesn't process anything yet; it just spins up the initial transaction container and gives you the URL your customer needs to click through to finish paying.

Processing Funds Reservation (Authorization)

Once they hit checkout, you need to reserve the money before anything else happens. You use authorize_zip_order to hold those funds against an order; this is critical for US gateway integrations and ensures the payment amount is earmarked but not actually moved. If that's a global transaction, or if you need to confirm the reservation, you can call confirm_zip_order.

These tools make sure the cash is set aside correctly, ready for whatever comes next.

Finalizing Payments (Capture)

Authorization just means 'we expect this money.' It doesn't mean it's yours. When your goods ship and you need to finalize the sale, you use capture_zip_payment. This moves the reserved funds—the authorized hold—and pulls them into your account, officially completing the transaction for the customer.

Auditing Order Status

You gotta know where your money is at all times. You check the real-time status of any Zip order ID using get_zip_order_status. This tool reports exactly what state that payment is in—whether it's still 'Authorized,' if it's been fully 'Captured,' or if it got 'Cancelled.' It gives you a clear, immediate look at where the money sits.

Handling Financial Reversals and Cleanups

Things go wrong. Payments get returned, or sometimes you authorize an order but never actually ship anything. For returns, you use refund_zip_payment to process refunds; it handles both full amounts and partial payouts for orders that already captured funds. If you authorized the money but decided not to proceed—the payment was never fulfilled—you release those reserved funds by calling void_zip_payment.

This cleans up the financial hold, making sure neither party gets charged for nothing.

Account Configuration Review

If you're setting things up or just wanna double-check your limits, you run get_zip_merchant_config. That tool grabs and reports all the current details about your merchant account settings—things like API access parameters and currency limits. It keeps you in the loop on what's available to process.

Bottom line: Your agent handles the messy state machine logic for these payments, so you just tell it what you need done. You don't worry about the payment flow; your AI client does.