mercury-payments
Pay invoices via Mercury Bank API. Use when sending ACH or wire payments through Mercury, creating recipients, querying transactions, or managing payment workflows. Covers recipient lookup/creation, payment execution (ACH and domestic wire), idempotency keys, wire purpose formatting, and transaction querying with date ranges.
Why use this skill?
Integrate OpenClaw with Mercury Bank to automate ACH and domestic wire transfers, manage vendor recipients, and query financial transactions securely.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/nathan-deepmm/mercury-paymentsWhat This Skill Does
The mercury-payments skill serves as an advanced integration layer for the Mercury Bank API, enabling OpenClaw agents to perform treasury management and payment operations programmatically. This skill streamlines the entire financial lifecycle, from discovering available corporate accounts and managing vendor databases to executing complex fund transfers such as ACH and domestic wires. It is designed to bridge the gap between financial administrative tasks and automated workflows, ensuring that payment logic is consistently applied across the organization.
Installation
To integrate this skill, use the ClawHub command-line interface:
clawhub install openclaw/skills/skills/nathan-deepmm/mercury-payments
Ensure your environment variables are configured with a valid Mercury API token that possesses the necessary 'write' scopes. Verify connectivity to https://api.mercury.com/api/v1 before initialization.
Use Cases
This skill is intended for high-velocity financial teams and operations managers. Common use cases include:
- Automated Vendor Payouts: Automatically trigger ACH payments upon invoice reconciliation.
- Routine Payroll & Wire Transfers: Execute domestic wire transfers for payroll, contractors, or significant vendor invoices using categorized wire purpose codes.
- Transaction Monitoring: Querying historical transactions to reconcile bank statements with ERP software or accounting ledgers.
- Recipient Management: Maintaining a clean database of verified vendors, including routing and account numbers, to prevent manual data entry errors.
Example Prompts
- "Check my Mercury account balance and send an ACH payment of $450 to 'CloudOps Solutions' for invoice INV-7892, noting it as 'February Server Hosting'."
- "Find the ID for 'Global Logistics' in my Mercury recipients and initiate a domestic wire transfer of $2500, citing it as a vendor payment for logistics services."
- "List all transactions for my 'Operating Account' from the last 15 days so I can audit our recent outbound wire activity."
Tips & Limitations
- Safety First: The skill is designed to prevent accidental double-payments through the use of unique
idempotencyKeyfields. Always store these keys in your audit logs. - Approval Workflow: Always seek explicit human verification before initiating large wire transfers. This skill should function as an execution engine, not an autonomous authorization agent.
- Categorization: When performing wires, ensure the
purposeobject uses valid category strings (e.g., 'vendor', 'contractor') as strictly defined in the Mercury API documentation to avoid rejection. - Date Ranges: While transaction querying is supported, ensure you are mindful of API rate limits if scraping large volumes of transaction history.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-nathan-deepmm-mercury-payments": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: external-api