Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Accept crypto payments (NEAR, USDC, USDT) via a beautiful payment page with PingPay or HOT PAY integration.
Accept crypto payments (NEAR, USDC, USDT) via a beautiful payment page with PingPay or HOT PAY integration.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Accept crypto payments (NEAR, USDC, USDT) via a beautiful payment page with PingPay or HOT PAY integration.
Creates a hosted payment page where people can pay you in crypto with just a few clicks: Beautiful UI - Mobile-friendly payment page with preset amounts Multi-token - Accept NEAR, USDC, or USDT Dual provider - Works with PingPay or HOT PAY (or both) Public URL - Exposes via localhost.run tunnel First-time friendly - Setup wizard guides new users Smart token selection - Once a token is selected, others are hidden to avoid confusion (great for HOT PAY where each token has a unique checkout link)
User selects token (NEAR, USDC, or USDT) User enters amount or picks preset Clicks "Pay Now" Redirects to PingPay checkout with pre-filled amount
User selects token (only configured tokens shown) Other tokens are hidden to avoid confusion User enters amount or picks preset Clicks "Pay Now" Redirects to HOT PAY checkout link for that specific token and amount
cd ~/.openclaw/skills # Clone or extract the skill npm install
You need either PingPay or HOT PAY (or both): Option A: PingPay (recommended for beginners) Sign up at https://pingpay.io Set your NEAR wallet in Dashboard โ Settings Get API key from Dashboard โ Settings โ API Keys Add to .env: PINGPAY_API_KEY=your_key_here Option B: HOT PAY (for advanced users) Visit https://pay.hot-labs.org/admin/overview Create payment links for each token (NEAR, USDC, USDT) Set your NEAR wallet as recipient when creating each link Copy each item_id and add to .env
Copy .env.example to .env: cp .env.example .env Edit .env: # Display name (actual recipient is set in PingPay/HOT PAY dashboard!) RECIPIENT_ADDRESS=your-account.near # Choose provider PAYMENT_PROVIDER=pingpay # or 'hotpay' # PingPay config (if using PingPay) PINGPAY_API_KEY=your_api_key_here # HOT PAY config (if using HOT PAY) HOTPAY_NEAR_ITEM_ID=your_near_item_id HOTPAY_USDC_ITEM_ID=your_usdc_item_id HOTPAY_USDT_ITEM_ID=your_usdt_item_id
./start.sh Or manually: npx ts-node start-tunnel.ts This will: Start Express server on port 3000 Create public URL via localhost.run Display the shareable payment link
Share the generated https://xxxxx.lhr.life URL to accept payments!
The recipient address (where payments go) is configured at the provider level, NOT in the .env file: PingPay: Set in your PingPay Dashboard โ Settings โ Wallet Address HOT PAY: Set when creating each payment link The RECIPIENT_ADDRESS in .env is only for display on the payment page. To change where payments actually go, update your provider's dashboard settings.
localhost.run generates random URLs that change each restart. For a permanent domain: Sign up at https://admin.localhost.run/ Configure your custom domain Update the tunnel command in start-tunnel.ts Or use your own reverse proxy (Cloudflare Tunnel, ngrok paid, etc.)
When a user asks to accept payments: User: "Create a payment page to accept USDT donations" Agent: 1. Check if near-getpay skill is installed 2. Ask which provider they want (PingPay or HOT PAY) 3. Guide them through setup if not configured 4. Run: cd ~/.openclaw/skills/near-getpay && ./start.sh 5. Share the generated public URL
User: I need to accept crypto payments Agent: I'll set up a payment page for you using the GetPay skill. First, do you have a PingPay or HOT PAY account? User: No, what's easier? Agent: PingPay is simpler. Here's what to do: 1. Sign up at https://pingpay.io 2. Add your NEAR wallet address in settings 3. Get an API key from Dashboard โ API Keys 4. Share it with me (or add to .env yourself) Let me know when you have the API key! User: Got it: sk_test_abc123... Agent: Perfect! Starting your payment server... [runs start.sh] โ Your payment page is live: https://abc123xyz.lhr.life Share this link to accept NEAR, USDC, or USDT payments!
near-getpay/ โโโ SKILL.md โ You are here โโโ package.json โโโ tsconfig.json โโโ .env.example โ Config template โโโ .env โ Your config (gitignored) โโโ start.sh โ Quick start script โโโ start-tunnel.ts โ Server + tunnel launcher โโโ server-simple.ts โ Main payment server โโโ scripts/ โโโ pingpay-client.ts โโโ payment-orchestrator.ts
Edit .env: PORT=8080
Replace localhost.run in start-tunnel.ts: // Option 1: ngrok const tunnel = spawn('ngrok', ['http', PORT.toString()]); // Option 2: Cloudflare Tunnel const tunnel = spawn('cloudflared', ['tunnel', '--url', `http://localhost:${PORT}`]); // Option 3: localtunnel (less reliable) const tunnel = spawn('npx', ['localtunnel', '--port', PORT.toString()]);
HOT PAY sends webhooks to /webhook/hotpay. To use: Expose your server publicly (not localhost.run - needs stable URL) Configure webhook URL in HOT PAY dashboard Server logs payment confirmations automatically
Edit preset amounts in server-simple.ts: tokens: [ { symbol: 'NEAR', chain: 'NEAR', decimals: 24, presets: [0.5, 1, 5, 10] // โ Change these }, // ... ]
Update colors, fonts, text in the HTML template sections of server-simple.ts.
Add to the tokens array (requires provider support): { symbol: 'ETH', chain: 'NEAR', decimals: 18, presets: [0.01, 0.05, 0.1, 0.5] }
Visit http://localhost:3000/setup to see setup instructions.
Run: ssh-keygen -t rsa -b 2048 -f ~/.ssh/id_rsa -N ""
localhost.run tunnels timeout after inactivity. Restart the server.
You need to create a payment link for each token. Missing tokens won't appear on the payment page.
PingPay: Check API key is valid and account is active HOT PAY: Verify item_ids match your created links
โ API keys stored in .env (gitignored) โ No private keys needed (payments go directly to provider) โ HTTPS via tunnel โ Webhook signature verification (HOT PAY) Never commit .env to git!
# From the skill directory openclaw skill pack # Share the .skill file # Users install with: openclaw skill install near-getpay.skill
git init git add . git commit -m "Initial commit: NEAR GetPay skill" git remote add origin https://github.com/yourusername/near-getpay.git git push -u origin main Users install with: cd ~/.openclaw/skills git clone https://github.com/yourusername/near-getpay.git cd near-getpay npm install
Visit https://clawhub.com Upload the .skill package Add description and tags Publish!
Issues: GitHub Issues (if published) PingPay: https://pingpay.io/docs HOT PAY: https://pay.hot-labs.org/admin OpenClaw: https://docs.openclaw.ai
MIT Made for OpenClaw ๐พ
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.