Provides MCP-compatible payment and refund tools using Antom APIs for AI-assisted transactions.
Configuration
View docs{
"mcpServers": {
"alipay-global-antom-mcp": {
"command": "uvx",
"args": [
"ant-intl-antom-mcp"
],
"env": {
"CLIENT_ID": "your_client_id_here",
"GATEWAY_URL": "https://open-sea-global.alipay.com",
"ALIPAY_PUBLIC_KEY": "your_alipay_public_key_here",
"PAYMENT_NOTIFY_URL": "https://your-domain.com/payment/notify",
"MERCHANT_PRIVATE_KEY": "your_merchant_private_key_here",
"PAYMENT_REDIRECT_URL": "/"
}
}
}
}You can deploy and use the Antom MCP Server to handle payment and refund operations through AI assistants. It wraps Ant International's Antom payment APIs into MCP-ready tools, enabling secure, conversational payment flows between users and your backend.
You use the Antom MCP Server by running it as an MCP tool in your AI agent setup. The server exposes a set of payment and refund endpoints you can invoke from your assistant’s workflow. You’ll configure the MCP client to load the Antom MCP server as a tool, supply required credentials, and then call the available actions (such as creating a payment session or initiating a refund) during a conversation.
Prerequisites: ensure you have Python 3.11 or higher and a working package manager (uvx is recommended; you can also use pip). You must operate with a valid Antom Merchant Account and have these credentials ready: CLIENT_ID, MERCHANT_PRIVATE_KEY, ALIPAY_PUBLIC_KEY, PAYMENT_REDIRECT_URL, and PAYMENT_NOTIFY_URL.
Configuration and runtime details are shown below so you can start the MCP server and wire it into your AI agent. Use the provided environment variables exactly as shown or with your own values substituted for the placeholders.
Security: protect the merchant credentials and RSA keys. Do not expose MERCHANT_PRIVATE_KEY or ALIPAY_PUBLIC_KEY in client-side code or logs. Use secure secret management for keys and URLs.
Examples demonstrate how to integrate with a typical AI agent. The server supports creating payment sessions, querying payments, cancelling payments, and handling refunds.
Troubleshooting: verify that all required environment variables are provided, the gateway URL is reachable, and the webhook/redirect URLs are correctly configured in your Antom Merchant Account. If you encounter a timeout, check your payment flow state handling in the agent and consider increasing timeout thresholds for long-running operations.
Create a payment session for client-side SDK integration so a user can complete a payment in a guided flow.
Query the status and details of a previously submitted payment request.
Cancel an active payment when results are not returned within the expected timeframe.
Initiate a refund, supporting full or partial refund against a successful payment.
Check the status and details of a previously submitted refund request.