Payment Gateway Optimizer

PassAudited by VirusTotal on May 13, 2026.

Overview

Type: OpenClaw Skill Name: payment-gateway-optimizer Version: 1.1.0 The 'Payment Gateway Optimizer' skill bundle is a well-structured set of analytical instructions and reference materials designed to help an AI agent compare payment processors. The bundle consists entirely of Markdown documentation (SKILL.md, quality-checklist.md) and reference data (fee-calculation-reference.md, regional-payment-methods.md). There are no executable code files, shell commands, network requests, or instructions that attempt to exfiltrate sensitive data or manipulate the agent's core behavior. The content is strictly aligned with its stated business purpose.

Findings (0)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

Sharing detailed payment volume, revenue mix, and gateway information could expose confidential business data if copied into an untrusted or shared environment.

Why it was flagged

These inputs are commercially sensitive payment and business details that would be placed into the agent's working context to produce the comparison.

Skill content
Collect the core metrics that drive gateway selection: - Monthly transaction volume (count and GMV) - Average order value and value distribution - Target markets ... - Current gateway and pain points - Technical stack
Recommendation

Provide only the minimum data needed, anonymize exact figures when possible, and review any generated report before sharing it.

What this means

If real gateway keys are later pasted into the agent or a generated document, they could grant access to payment infrastructure.

Why it was flagged

The roadmap anticipates payment-gateway API keys during implementation; API keys are privileged credentials, although the artifacts do not instruct the agent to collect, store, or use them.

Skill content
| Phase 1: Setup | Weeks 1-2 | [Sandbox, API keys, testing] | [All test transactions pass] |
Recommendation

Use sandbox or restricted keys for planning and testing, avoid pasting production secrets into chat, and rotate any key that is accidentally shared.