moneyclaw_skill

This skill helps you issue virtual cards, manage balances, and perform payments securely using MoneyClaw's API and built-in fraud safeguards.
  • Python

2.6k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill moneyclaw

  • _meta.json274 B
  • SKILL.md27.6 KB

Overview

This skill provides virtual Visa/Mastercard issuance, funding, and payment orchestration backed by USDT plus integrated financial intelligence. It issues prepaid cards, manages wallet vs card balances, handles 3DS OTPs via a persistent inbox, and applies phishing/fraud checks and payment optimization guidance. The goal is safe, reliable online purchases and merchant interactions using programmatic API calls.

How this skill works

It uses Bearer token authentication to call MoneyClaw endpoints for account status, issuing cards, fetching sensitive card credentials, topping up, and viewing transactions. Each account includes a permanent agent email inbox that auto-extracts OTPs for 3DS flows. The skill enforces pre-flight checks (card active, sufficient wallet balance, minimum topup) and follows retry and error-handling rules to avoid double-deductions or unnecessary declines. Built-in heuristics inspect URLs, page behavior, and payment forms to detect phishing and recommend safe payment flows.

When to use it

  • Issue a virtual prepaid card funded by USDT for online purchases.
  • Complete merchant checkouts that may trigger 3DS OTP verification.
  • Top up card from wallet before a planned purchase.
  • Accept crypto payments and route funds into card/wallet.
  • Validate merchant legitimacy and run the mandatory payment safety checklist.

Best practices

  • Always call GET /api/me to show both wallet and card balances before actions.
  • Use card.cardId (not card.id) for card endpoints and cache credentials during a purchase session (limit 10/min).
  • Follow the pre-payment checklist: URL, HTTPS, form fields, amount, processor, balance +5% buffer, VPN and clean browser.
  • Wait 10–30s for OTP emails and use GET /api/inbox/latest-otp to extract codes; do not construct mailbox addresses manually.
  • Follow retry rules: wait 30s before checking transactions, max 2 retries per merchant, verify provider responses before repeating topups or purchases.

Example use cases

  • Programmatically issue a prepaid card and auto-load wallet funds for a one-off merchant purchase.
  • Perform a 3DS-protected subscription checkout by extracting OTP from the inbox and submitting it automatically.
  • Top up a card from wallet with validation and handling of 202 processing states to avoid duplicate deductions.
  • Audit recent deposits, topups, fees and card spending using transactions endpoints for reconciliation.
  • Run automated phishing checks on checkout URLs and block risky payment attempts.

FAQ

Always show wallet balance from GET /api/me and card balance if card.cardBalance is present; if missing, report "Card balance: unavailable."

How do I get OTP codes for 3DS?

Use GET /api/inbox/latest-otp after waiting ~10–30 seconds; use extractedCodes[0] as the OTP. Do not guess or construct the mailbox address.

What are common topup failure reasons?

Insufficient wallet balance, card not active, amount below minimum ($10), provider errors (VALUT_ERROR) or validation errors. Follow the pre-flight checks and error-handling table before retrying.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational