Snaplii A2M Payment

Snaplii A2M Payment — MCP Plugin

Install

openclaw plugins install clawhub:snaplii-a2m-payment

Snaplii A2M Payment — MCP Plugin

Agent-to-Merchant (A2M) payments — where AI agents complete transactions without checkout. Snaplii uses pre-funded gift cards as a payment rail, enabling instant, merchant-ready execution across 500+ brands.

Prerequisites

  1. Download the Snaplii App (iOS / Android)
  2. Create an API Key in the app: More → Payment Methods → AI Payment Management → + New API Key
  3. Install the MCP server: pip install snaplii-cli "mcp[cli]"PyPI package | Source code

Tools

ToolDescription
snaplii_initAuthenticate with API key (not stored)
snaplii_config_showShow auth status
snaplii_browse_tagsBrowse gift card categories (CA/US)
snaplii_browse_brandBrand details and denominations
snaplii_giftcard_listList owned gift cards
snaplii_giftcard_detailCard redemption code (sensitive)
snaplii_purchaseBuy a gift card (requires explicit user confirmation)
snaplii_apikey_listList API keys
snaplii_apikey_createCreate API key
snaplii_apikey_deleteDelete API key
snaplii_cashback_calcCalculate cashback savings
snaplii_dashboardOwned card inventory summary

Security

  • API key handling: API keys are used only to obtain a short-lived token and are never stored on disk. Keys are passed via hidden stdin input (CLI) or MCP tool parameters (plugin) — never as command-line arguments.
  • Sensitive data: Card redemption codes, PINs, and barcode URLs are treated as confidential. They are never displayed unless the user explicitly requests them.
  • Purchase authorization: All purchase, API key creation, and API key deletion operations require explicit user confirmation before execution. The agent must not execute these autonomously.
  • Spending limits: API keys are scoped with hard spending limits set in the Snaplii app. Agents can only spend from prepaid Snaplii Cash balance.