near-getpay

What This Skill Does

The near-getpay skill is a robust tool designed to turn your OpenClaw agent into a crypto-payment processing powerhouse. It creates a seamless, mobile-friendly payment landing page that allows you to accept NEAR, USDC, and USDT tokens from your clients or community members. By acting as a bridge between the user and payment providers like PingPay and HOT PAY, it handles the complex routing of transaction data so you don't have to code it yourself. It simplifies the user experience by offering preset payment amounts and a clean, branded interface, while handling the technical redirection needed to initiate the blockchain transaction.

Installation

To get started, navigate to your local OpenClaw skills directory (typically ~/.openclaw/skills) and run the standard installation commands. You will need to clone the repository or use the CLI installer: clawhub install openclaw/skills/skills/cuongdcdev/near-getpay. Once the files are present, install the dependencies using npm install. The skill requires an environment configuration file; copy the .env.example to .env and populate it with your provider-specific credentials (PingPay API keys or HOT PAY item IDs). Finally, launch the service with ./start.sh, which automatically provisions a public URL via localhost.run to expose your payment page to the internet.

Use Cases

This skill is perfect for creators, freelancers, and small business owners operating within the NEAR ecosystem. Use it to collect payments for consulting services, digital product sales, or micro-donations. Because it supports multiple tokens, it is highly versatile for users who prefer different assets. It is also an excellent tool for event ticketing where you need a quick, reliable way to verify payments on-chain without building a full-scale e-commerce backend.

Example Prompts

1. "OpenClaw, start the payment server and give me my unique link so I can receive a 5 NEAR payment for my service."
2. "Update my near-getpay configuration to switch from PingPay to HOT PAY using my latest item IDs."
3. "Show me the status of my current payment tunnel and let me know if my public URL is active for clients."

Tips & Limitations

Always remember that the recipient wallet is defined in your third-party provider's dashboard, not in your local .env file; double-check those settings before sharing your link. For the best user experience, stick to PingPay if you are a beginner, as it offers a smoother, more unified flow compared to the token-specific links of HOT PAY. Note that the skill utilizes a tunnel service to reach the public internet; if you close the terminal process, your payment link will go offline immediately. Keep your .env file secure as it contains sensitive API keys.