sohopay

What This Skill Does

The sohopay skill provides a secure, non-custodial interface for initiating payments on the SOHO Pay credit layer. It leverages the EIP-712 standard to facilitate authorized spending through the Creditor smart contract on the Base blockchain. By separating the roles of the Wallet Signer, the SOHO credit infrastructure, and the blockchain settlement layer, the skill ensures that SOHO never takes custody of private keys or manages signing operations. Instead, it coordinates the Just-In-Time (JIT) funding required for transactions, acting as a credit layer that facilitates settlement without ever holding user assets or keys. This architectural choice prioritizes security, keeping signature authority firmly in the hands of the user or their preferred MPC/HSM provider.

Installation

To integrate this skill into your environment, run the following command within your OpenClaw workspace: clawhub install openclaw/skills/skills/max-clinch/soho-pay. Ensure that your environment variables, such as RPC_URL, CHAIN_ID, and appropriate signer configuration, are set correctly according to whether you are operating in a development or production capacity. Refer to the source repository for specific dependency requirements.

Use Cases

• Enterprise Procurement: Streamline B2B vendor payments by automating the issuance of credit-backed transactions to verified merchant addresses.
• E-commerce Checkout: Integrate with front-end platforms to allow users to pay using credit-enabled smart contracts, settling instantly on the Base chain.
• Agentic Commerce: Enable autonomous agents to settle invoices or pay for API usage tokens via the SOHO Pay protocol while maintaining strict human-in-the-loop oversight.

Example Prompts

1. "Please trigger a payment of 50 USDC to the merchant at 0x123... using my configured remote signer."
2. "I need to settle an invoice for 12.5 USDC; please initiate the SOHO Pay flow to the address 0xabc... and confirm the transaction details before signing."
3. "Initiate a payment of 100 USDC to 0x789... using the wallet address 0xdef... on the Base network."

Tips & Limitations

This skill is strictly manual-invocation only. Because it manages financial transactions, it must not be triggered autonomously by an AI agent without explicit user confirmation for every single spend event. Always double-check the merchantAddress as no name resolution is provided—only raw hex addresses are accepted. Ensure your MPC signer service is accessible at the configured WALLET_SIGNER_SERVICE_URL to prevent transaction failure during the broadcast phase.