browser-payment-mcp

Automate payment portal interactions with Playwright and human approval.

11|2|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/NaveedTechLab/skills-library --skill browser-payment-mcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-payment-mcp
Source: https://github.com/NaveedTechLab/skills-library/tree/main/skills/browser-payment-mcp
Command: npx skills add https://github.com/NaveedTechLab/skills-library --skill browser-payment-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, fastmcp, and includes scripts (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines payment portal automation with robust Human-In-The-Loop (HITL) controls, ensuring every transaction requires human oversight for accuracy and security.

Core Features & Use Cases

  • HITL Controls: Strict approval workflow for every payment, enforcing manual review before execution.
  • Payment Automation: Automates payment form filling, drafting, and submission via Playwright browser automation.
  • Use Case: Deploy this Skill in your business for secure payment automation without the risk of automatic or fraudulent transactions.

Quick Start

To automate payment portal interactions, install the skill and execute the command /browser-payment-mcp draft_payment recipient=123456 amount=100.00.

Frequently Asked Questions about browser-payment-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate browser payment portals while requiring manual approval for every transaction?

You can automate browser payment portals with human-in-the-loop (HITL) controls by using Playwright to fill and draft payment forms, enforcing strict manual review and approval before any payment submission executes.

Can I use Playwright to fill out payment forms and hold them for human verification?

Yes, Playwright can automate the browser-based form filling and drafting process for payments, while strict HITL controls pause the workflow to require human verification before final submission.

What's the best way to prevent fraudulent transactions during payment automation?

The best way to prevent fraudulent transactions during payment automation is to enforce strict human-in-the-loop approval workflows, ensuring manual review and verification are required before executing any payment.

Do I need FastMCP to handle human-in-the-loop controls for payment processing?

Yes, this payment automation approach requires both Playwright for browser automation and FastMCP for MCP client communication to successfully implement the strict human-in-the-loop approval controls.

How do I draft a payment for manual review using browser automation?

You can draft a payment for manual review by executing a draft command with the recipient and amount parameters, which uses Playwright to populate the portal form and pause for human approval.