cashapp-pay

What This Skill Does

The Cash App Pay integration skill empowers your OpenClaw agent to seamlessly manage and process payments via Cash App, the U.S. leader in personal finance. This skill bridges the gap between your application and Block, Inc.'s robust payment ecosystem. It provides direct support for the Customer Request API, which orchestrates the secure authentication flow between your platform and the user's Cash App account. By integrating this skill, your agent can handle everything from one-time checkout requests and recurring payment storage to complex point-of-sale transaction lifecycles. It also includes capabilities for handling webhooks for real-time status updates and monitoring dispute reports to ensure healthy account status.

Installation

To integrate this capability into your project, run the following command in your terminal:

clawhub install openclaw/skills/skills/codejika/cashapp

Ensure your project environment has access to your production or sandbox API credentials, as these are required to interact with the Cash App Pay network backend.

Use Cases

• E-commerce Checkout: Enable customers to pay instantly using their Cash App balance without manual card entry, increasing conversion rates on mobile devices.
• Subscription Management: Utilize the ON_FILE_PAYMENT action to securely link user accounts for seamless recurring billing.
• Point-of-Sale Integration: Process in-person transactions by generating dynamic QR codes that allow customers to scan and pay at physical terminals.
• Automated Payment Lifecycle: Build workflows that monitor the state of a customer request and automatically trigger a payment via the Network API as soon as the grant_id is generated.

Example Prompts

1. "OpenClaw, please initiate a new one-time payment request for $49.99 and return the QR code URL for my web checkout page."
2. "Can you check the current status of the customer request ID cr_12345 and let me know if it has been approved yet?"
3. "Set up a webhook listener to notify me whenever a customer_request.state.updated event occurs for my active transactions."

Tips & Limitations

• Polling Frequency: Always poll the status of a customer request at a rate of 1x per second to ensure accurate, real-time UI updates.
• Security: Never invoke server-side Network API methods from client-side code; keep your secret keys stored in secure environment variables.
• QR Hygiene: Remember that QR codes rotate every 30 seconds and expire after 60 seconds. Always fetch the latest trigger from your polling response to avoid transaction failures.
• Architecture: Pay Kit SDK handles the UI rendering, so leverage it for frontend interactions to minimize custom development overhead.