Google Pay

What This Skill Does

The Google Pay skill provides a robust, standardized framework for integrating Google Pay into web and Android environments. It acts as an expert architect for payment workflows, ensuring that implementations adhere to strict security standards, tokenization requirements, and gateway alignment. By managing the complexities of the Google Pay API, the skill handles everything from initial prerequisite checklists and environment setup to production-ready checkout operations and post-launch troubleshooting. It maintains a dedicated local state via ~/google-pay/, tracking implementation paths, validation results, and incident logs to ensure consistency across the development lifecycle.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/ivangdavila/google-pay

Use Cases

• Checkout Optimization: Implementing frictionless, one-tap payment flows for high-conversion e-commerce web applications.
• Subscription Management: Enabling secure, recurring payment tokens for SaaS products, reducing churn by providing a seamless user experience.
• Android Integration: Adding native Google Pay support to mobile apps, ensuring compatibility with the Google Pay API for Android.
• Gateway Migrations: Managing the transition between payment service providers (PSPs) while maintaining Google Pay availability.
• Failure Mitigation: Using the incidents.md tracking system to analyze and resolve recurring payment failures or tokenization errors during the production rollout phase.

Example Prompts

1. "Initialize the Google Pay setup process for our web-based retail platform. We are using Stripe as our PSP; please generate the initial memory.md file and confirm the required merchant configuration steps."
2. "I'm experiencing payment failures on Android. Please check ~/google-pay/incidents.md and help me debug the tokenization response from the gateway."
3. "Create a validation checklist for our upcoming production release of Google Pay on the checkout page, covering environment verification and currency matching rules."

Tips & Limitations

• Server Truth: Always define amounts and currencies on your backend. Never rely on the client-side payload for final charge amounts to prevent tampering.
• Security: Never share your private keys, full token payloads, or PSP secrets in the chat. The skill is designed to guide you through secure handling practices without exposing sensitive data.
• Prerequisites: This skill enforces a 'prerequisites-first' policy. If your Google Pay merchant profile is not configured for the target environment, the agent will pause implementation to prevent invalid deployments.
• Scope: The skill handles architecture, integration, and diagnostics but requires you to manage your own sensitive credentials.