Mayar Payment

What This Skill Does

The Mayar Payment skill is a robust integration designed for OpenClaw users to interface directly with the Mayar.id payment gateway. It acts as an MCP-enabled bridge allowing you to automate the lifecycle of financial transactions. Whether you are running an e-commerce store, a subscription-based service, or a consultancy, this skill enables you to programmatically generate payment invoices, create unique payment links, track customer transaction statuses in real-time, and manage recurring billing. It specifically streamlines Indonesian payment methods, including bank transfers, e-wallets (like OVO/Dana/Gopay), and QRIS, making it an essential tool for local businesses looking to automate their checkout flows within the OpenClaw ecosystem.

Installation

To get started, first ensure your system has the Mayar API credentials stored securely at ~/.config/mayar/credentials. Once your credentials are in place, configure your mcporter.json file by adding the 'mayar' server under 'mcpServers', pointing to the Mayar SSE endpoint with your Authorization header. Finally, execute clawhub install openclaw/skills/skills/ahsanatha/mayar-payment to sync the skill with your agent. Test the connectivity by running mcporter list mayar to confirm all 15+ tool definitions are loaded.

Use Cases

This skill is perfect for:

1. Automated Invoicing: Generating payment links the moment a customer agrees to a service.
2. E-commerce Workflows: Creating transactional links for cart checkouts.
3. Subscription Management: Handling recurring memberships.
4. WhatsApp Marketing: Using the generated link inside automated WhatsApp messages to drive conversions.
5. Transaction Monitoring: Auditing successful payments or following up on expired/pending transactions.

Example Prompts

1. "Generate a payment link for a client named Budi for 500,000 IDR for 'Professional Consultation' and send it to his WhatsApp."
2. "Check the status of the latest invoice I sent to see if the transaction has been completed."
3. "List my last 10 transactions and tell me which ones are still pending payment."

Tips & Limitations

Always ensure the 'mobile' number provided in the API arguments is strictly formatted as a quoted string (e.g., ""628123456789"") to avoid syntax errors. Be aware that the 'expiredAt' parameter must follow the ISO 8601 format including the correct UTC offset for Western Indonesian Time (WIB/UTC+7). As this skill involves financial data, ensure your API credentials are kept in a restricted-access file with chmod 600 permissions.