# Zip MCP MCP > Zip manages the full spectrum of Buy Now, Pay Later (BNPL) payments and order processing through your AI agent. Initiate checkouts, authorize funds on US/Global gateways, confirm orders after shipping, capture revenue, or process partial refunds—all without logging into a dashboard. ## Overview - **Category:** money-moves - **Price:** Free - **Tags:** buy-now-pay-later, checkout-automation, order-management, refunds, merchant-services, payment-gateway ## Description Handling e-commerce payments used to mean hopping between multiple merchant portals just to confirm an order's status or run a refund. Now, you can manage the entire financial lifecycle of a sale using natural language commands. Your agent handles creating new checkout sessions and retrieving the necessary payment links for customers. It also manages the money itself: it can hold funds by authorizing orders, finalize them when goods ship via capture, or void payments if something goes wrong. When you use this MCP, your AI client controls every step of the transaction—from initial setup to final settlement. Because financial integrity is non-negotiable, Vinkius enforces a human-in-the-loop approval mechanism that acts as a circuit breaker, ensuring your agent can't overspend and forcing manual sign-off on large or risky transactions before any money moves. This gives you absolute control over the entire payment flow. ## Tools ### authorize_zip_order Holds funds on an order using US gateway protocols. ### capture_zip_payment Transfers held funds for a specific, completed order. ### confirm_zip_order Marks an authorized order as finalized in the system. ### create_zip_checkout Starts a new checkout session and provides the necessary customer redirect URL. ### get_zip_merchant_config Retrieves current details about your merchant account setup. ### get_zip_order_status Checks and reports the real-time status of any existing order ID. ### refund_zip_payment Sends money back to a customer for an issued order. ### void_zip_payment Cancels funds that were authorized but never captured. ## Prompt Examples **Prompt:** ``` Create a Zip checkout for $100.00 USD. ``` **Response:** ``` I've initialized the Zip checkout for $100.00. Here is your checkout ID: 'chk-abc-123' and the redirect URL for the customer to complete payment. ``` **Prompt:** ``` Check the status of Zip order ID '98765'. ``` **Response:** ``` I've retrieved the status for order 98765. It is currently in the 'Authorized' state and is awaiting capture. The total amount is $100.00 USD. ``` **Prompt:** ``` Capture payment for authorized order '98765'. ``` **Response:** ``` Successfully triggered the capture for order 98765. The funds have been processed, and the order state has been updated to 'Captured'. ``` ## Capabilities ### Initiate Checkout Sessions Creates new checkout sessions, giving your agent the redirect URL needed for a customer to complete a purchase. ### Authorize and Confirm Funds Holds funds on an order (authorization) and then finalizes that hold into a confirmed sale using one command sequence. ### Capture Revenue Finalizes the transaction by pulling authorized funds out of the payment network once shipping is complete. ### Reverse Payments Processes full or partial refunds, or voids payments that were held but never captured. ### Track Order Statuses Retrieves the current lifecycle status of any order—authorized, captured, canceled, etc.—in real-time. ### Check Account Details Accesses core merchant account settings like currency limits and general configuration data. ## Use Cases ### A shipment was delayed, requiring a partial refund. The Ops Manager tells their agent: 'Process a $50 partial refund for order 123.' The MCP runs `refund_zip_payment`, immediately updating the records and finalizing the financial correction. ### A customer needs to complete a purchase after leaving the site. The agent uses `create_zip_checkout` to generate a unique link for a high-value order, allowing the customer to pay later without friction. The flow is seamless. ### An order was placed but never shipped; we need to cancel the payment. The agent detects the pre-authorization hold and executes `void_zip_payment`, instantly removing the held funds from the system, preventing revenue leakage. ### A developer needs to test the full flow for a new product line. Instead of manually testing every step, the developer asks the agent to run `authorize_zip_order`, then simulate shipping and call `capture_zip_payment`—all in one command. ## Benefits - You don't have to manually check every portal. Your agent handles everything from generating a new checkout session using `create_zip_checkout` to processing the final capture for revenue realization. - Avoid lost money or manual errors by automating compensation transactions. If an order fails, your agent can issue a full refund with `refund_zip_payment` or void funds with `void_zip_payment` instantly. - Get instant financial oversight without logging in. Use the MCP to check any order's status via `get_zip_order_status`, knowing exactly where the money stands at any time. - The system knows how payments work, so you don't have to code it all yourself. It manages the complex sequence of authorizing funds with `authorize_zip_order` before they can be captured. - Understand your account health instantly. Use tools like `get_zip_merchant_config` to verify currency limits and setup details without navigating settings menus. ## How It Works The bottom line is: you tell your agent what financial action you need, and it handles the specific API calls required to make that money move happen. 1. Subscribe to the MCP and supply your Zip Merchant API Key, Region, and Environment (Sandbox or Production). 2. Connect this MCP from Claude, Cursor, or any compatible client. Your agent now has access to all payment tools. 3. Give your AI client a natural language command like 'Check the status of order 98765'—the system executes the necessary sequence. ## Frequently Asked Questions **How do I start a new order checkout using create_zip_checkout?** You initiate the session by telling your agent to run `create_zip_checkout`, providing the amount and currency. The system responds with a unique redirect URL you must use for the customer to complete payment. **Should I use authorize_zip_order or create_zip_checkout first?** You typically start by using `create_zip_checkout` to generate the session ID and link. Once the customer pays, you use `authorize_zip_order` on that resulting order ID. **What is the difference between capture_zip_payment and confirm_zip_order?** Confirming an order (`confirm_zip_order`) marks it as finalized within Zip's system. Capturing payment (`capture_zip_payment`) is the actual financial step that moves the money from the customer to your bank. **How do I refund a payment using refund_zip_payment?** You must provide the order ID and specify the amount. The MCP ensures this transaction follows all necessary checks before processing the funds back to the original source. **How do I check my current account limits or settings using get_zip_merchant_config?** You retrieve your full merchant configuration details immediately. This call provides access to currency limits, region settings, and other critical account parameters needed before processing any payments. **If I authorized a payment but haven't shipped the goods, how do I use void_zip_payment?** Voiding cancels an authorized amount without affecting your bank balance. This is crucial for reversing funds when you need to cancel or delay shipment before capture. **What should I do if I need a real-time status check on an order using get_zip_order_status?** The function returns the current lifecycle state of any Zip order. It confirms whether the payment is authorized, captured, or has failed, helping you debug workflow issues. **Is there a difference between calling authorize_zip_order and confirm_zip_order?** Authorize reserves funds on the customer's card; it doesn't transfer money. Confirm finalizes the order, signaling that the transaction is complete and ready for shipment. **What is the difference between Authorize and Confirm in Zip?** Authorize initiates the transaction and checks for customer funds. Confirm (used in some regions) finalizes the checkout intent before capture. **Can I process partial captures via the agent?** Yes, the `capture_zip_payment` tool accepts an optional JSON body where you can specify a partial amount to capture if only part of the order is shipping. **How do I handle different regions like US and AU?** Specify your account region ('US' or 'AU') in the configuration settings. The MCP server automatically routes requests to the correct Zip gateway URL.