google-payImplement Google Pay for web and Android with tokenization safety, gateway alignment, and production-ready checkout operations.
Install via ClawdBot CLI:
clawdbot install ivangdavila/google-payRequires:
Grade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://clawic.com/skills/google-payAudited Apr 17, 2026 · audit v1.0
Generated Mar 21, 2026
An online retailer wants to add Google Pay to their web checkout to reduce friction for mobile users. The agent will implement tokenization via a payment gateway, ensure idempotent authorization calls, and validate fallback options before production launch.
A SaaS company needs Google Pay for recurring billing on Android apps to improve conversion. The agent will set up recurring payments with secure token handling, enforce server-side amount validation, and implement failure recovery logs for subscription renewals.
A travel booking app aims to boost Android user conversions by integrating Google Pay directly into the app. The agent will choose the Android API path, configure merchant prerequisites, and ensure capability checks to prevent broken wallet buttons.
A gaming platform seeks to streamline in-app purchases with Google Pay for faster transactions. The agent will implement PAYMENT_GATEWAY tokenization, validate test and production environments separately, and set up incident tracking for failed payments.
A business service provider wants to offer Google Pay for one-time and subscription invoices to reduce payment friction. The agent will ensure gateway alignment, enforce idempotency on retries, and maintain validation logs for audit compliance.
Businesses earn revenue by charging a percentage or fixed fee per transaction processed through Google Pay. This model requires high-volume checkout flows and reliable tokenization to minimize failures and maximize fee income.
Companies use Google Pay for automated recurring payments, generating steady monthly or annual revenue. This model depends on secure token handling and idempotent operations to prevent duplicate charges and ensure customer retention.
Businesses integrate Google Pay primarily to increase conversion rates on mobile and web, leading to higher overall sales revenue. Success relies on minimizing friction, providing fallback options, and validating rollout readiness to avoid lost sales.
💬 Integration Tip
Always validate environment prerequisites like merchant IDs and gateway support before coding, and enforce server-side amount matching to prevent payment mismatches.
Scored Jun 19, 2026
Manages free AI models from OpenRouter for OpenClaw. Automatically ranks models by quality, configures fallbacks for rate-limit handling, and updates openclaw.json. Use when the user mentions free AI, OpenRouter, model switching, rate limits, or wants to reduce AI costs.
Use CodexBar CLI local cost usage to summarize per-model usage for Codex or Claude, including the current (most recent) model or a full model breakdown. Trigger when asked for model-level usage/cost data from codexbar, or when you need a scriptable per-model summary from codexbar cost JSON.
Reduce OpenClaw AI costs by 97%. Haiku model routing, free Ollama heartbeats, prompt caching, and budget controls. Go from $1,500/month to $50/month in 5 min...
Generate and edit images with Gemini API using pure Python stdlib. Zero dependencies - works on locked-down environments where pip/uv aren't available.
Manage and use local Ollama models. Use for model management (list/pull/remove), chat/completions, embeddings, and tool-use with local LLMs. Covers OpenClaw sub-agent integration and model selection guidance.
Auto-route tasks to the cheapest Claude model that works correctly. Three-tier progression: Haiku → Sonnet → Opus. Classify before responding. HAIKU (default): factual Q&A, greetings, reminders, status checks, lookups, simple file ops, heartbeats, casual chat, 1-2 sentence tasks. ESCALATE TO SONNET: code >10 lines, analysis, comparisons, planning, reports, multi-step reasoning, tables, long writing >3 paragraphs, summarization, research synthesis, most user conversations. ESCALATE TO OPUS: architecture decisions, complex debugging, multi-file refactoring, strategic planning, nuanced judgment, deep research, critical production decisions. Rule: If a human needs >30 seconds of focused thinking, escalate. If Sonnet struggles with complexity, go to Opus. Save 50-90% on API costs by starting cheap and escalating only when needed.