binance-pay

What This Skill Does

The Binance Pay skill enables OpenClaw AI agents to natively interact with the Binance cryptocurrency payment gateway. It allows your agent to programmatically create payment orders, verify the status of transactions, close orders, and manage refunds directly from the command line or an automated workflow. By leveraging the Binance Pay API, the skill provides a secure, low-latency bridge between your application logic and the world's largest cryptocurrency exchange ecosystem, supporting over 200 million users.

Installation

To integrate this skill into your environment, use the following installation command via the OpenClaw CLI:

clawhub install openclaw/skills/skills/0xterrybit/binance-pay

Ensure you have your Binance Merchant API credentials ready, as the skill requires the BINANCE_PAY_API_KEY, BINANCE_PAY_SECRET, and BINANCE_PAY_MERCHANT_ID to be configured as environment variables before usage.

Use Cases

This skill is highly versatile for developers and business owners. It can be used to set up automated crypto checkout pages for e-commerce platforms, handle instant micro-payments in DApps, automate refund workflows for customer service bots, or track incoming order status updates in real-time. It is particularly useful for platforms requiring high-volume transactions with zero-fee internal transfers.

Example Prompts

1. "Create a new Binance Pay order for 50 USDT for the customer's purchase of a premium membership, labeled as Order #1001."
2. "Check the current status of Binance Pay order number 1678904532 to see if the payment has been confirmed."
3. "Process a partial refund of 10 USDT for the Binance Pay payment associated with prepay ID '123456789' due to a stock discrepancy."

Tips & Limitations

When using this skill, always ensure that your server time is synchronized via NTP, as the Binance API relies on precise timestamps for signature generation. Note that the API is intended for merchant-level operations; ensure your account is verified for API access. Because this involves financial transactions, always wrap your agent's calls in error handling logic to account for network timeouts or invalid payload structures. Finally, maintain the secrecy of your API keys at all times, preferably by using a secure secrets manager rather than hardcoding values in your scripts.