Worldpay MCP. Manage payments, refunds, and settlements from chat.

You're running a global payment operation. You don't wanna be staring at dashboards; you want this stuff handled in natural conversation. This server connects Worldpay directly to your agent, letting you manage payments, handle refunds, and audit settlements without leaving the chat window.

Processing Payments & Managing Tokens

You can initiate a brand new payment order instantly using create_payment_order. You just gotta supply four things: a secure reusable token, the total amount in money, what currency you're paying in, and a description for the order. The tool spits out real-time confirmation right away, giving you an order code to track everything else.

Need to handle customer payment data? Don't store raw card numbers; that’s risky business. You use create_reusable_token to generate a secure, reusable token from sensitive card details. This process lets you keep processing payments for the same customer later on without ever having to deal with their actual credit card number again.

When you need payment history or specific transaction info, you've got options. To check what happened with any paid order, use get_order_details and give it that specific payment order code. If you're tracking a token—maybe you wanna see its status or metadata—you run get_token_details, providing just the specified token ID.

Refunds and Auditing Settlements

If an order needs money coming back, use refund_payment_order. Just give it the original order code and the exact amount of money you need refunded. This handles both partial and full refunds against a payment that's already cleared.

To audit your books, you list all settled funds using list_payment_settlements. That gives you a high-level overview of every batch of money deposited into your Worldpay account. For the deep dive—the granular details on one specific settlement period—you run get_settlement_details, supplying only that single settlement batch ID. You'll see exactly what transactions make up those funds.

System Checks and Configuration

You gotta know if the connection is solid before you start transacting. Run get_api_health to check the live operational status of the Worldpay API connection. This confirms whether your gateway is reachable right now, so you can troubleshoot immediately if something's up.

If you use webhooks for real-time updates—which you should—you need to verify that setup. You run list_webhook_endpoints to list every registered notification endpoint, letting you confirm the configuration settings are rock solid and ready to receive payment updates. If your system uses tokens for payments, you can also get a list of all those endpoints using list_webhook_endpoints, verifying they're set up correctly.

Every piece of data—from creating an order via create_payment_order with the token, amount, currency, and description; to generating reusable payment identifiers through create_reusable_token; to confirming a transaction's status using get_order_details by code; to processing a partial reimbursement using refund_payment_order against an order code; or pulling deep accounting info via get_settlement_details with a batch ID—you manage the entire lifecycle right here.

You can confirm connectivity anytime with get_api_health, and you'll always know which endpoints are live by checking list_webhook_endpoints. These tools give you total control over payments, refunds, and settlement reporting.