Skill registry
Business operationsPublic skills

Payment Processing

Governed payment operations for AI agents — intent-based payments with approval gates, evidence collection, reconciliation, and full audit trails. Agents propose, policy decides, humans approve, system executes.

What this skill teaches

A reusable playbook for a specific kind of work.

An MCP server tells an agent which actions are available. A skill adds the judgment around those actions: how to recognize the job, which sequence to follow, what to avoid, and how to decide that the result is complete.

Orchestrate governed payment operations — create payment intents, manage approval gates, execute approved payments, reconcile against invoices, and maintain audit evidence. Use when processing payments, issuing refunds, creating payouts, checking payment status, reconciling transactions, or generating payment reports.…

Architecture

How Payment Processing guides an ADK-Rust agent.

The skill stays readable and portable because it contains instructions rather than service credentials or business data. ADK-Rust supplies it to the agent, the agent chooses from its reviewed tool boundary, and the connected MCP server performs the authenticated operation.

01

User request

The agent receives a goal expressed in ordinary language.

02

Payment Processing skill

Matches intent, supplies the decision guide, and narrows the tool boundary.

03

ADK-Rust agent

Plans the workflow and streams each meaningful step through the runtime.

04

mcp-payments

Executes authenticated operations against the system that owns the capability.

05

Verified result

The skill's completion rules shape the evidence returned to the user.

Portable instructions: SKILL.md · Capability boundary: mcp-payments · Allowed tools: 10

Decision guide

How the agent turns a request into the right action.

These routes come directly from the skill instructions. They help the model recognize intent and select a focused tool or workflow instead of improvising across the entire capability surface.

01

"charge", "collect", "checkout", "invoice payment"?

WORKFLOW 1: Checkout Payment

02

"refund", "return", "credit back"?

WORKFLOW 2: Refund

03

"payout", "pay vendor", "transfer out"?

WORKFLOW 3: Payout

04

"status", "where's my payment", "check payment"?

WORKFLOW 4: Payment Status

05

"reconcile", "match", "verify payment"?

WORKFLOW 5: Reconciliation

06

Unclear?

Ask: "Would you like to collect a payment, issue a refund, or check a payment status?"

Proven workflows

Repeatable sequences for useful outcomes.

A workflow joins several tool calls into a task the user actually recognizes. The skill explains the sequence and the intended result while ADK-Rust streams the agent's progress through the shared runtime.

013-4 calls

Checkout (collect money)

Intent + evidence + approval gate

024-5 calls

Refund

Verify original + intent + evidence + approval

033 calls

Payout (pay vendor)

Intent + evidence + mandatory approval

041 calls

Status Check

Current state with reconciliation info

052-3 calls

Reconciliation

Match payments to invoices/orders

Tool boundary

The skill may use 10 documented tools.

This allowlist is declared by the skill. It keeps the agent focused on the actions needed for this job while mcp-payments retains responsibility for authentication, validation, and the connected system.

lookup_payment
list_customer_payments
get_payment_status
create_checkout_intent
create_refund_intent
create_payout_intent
request_payment_approval
execute_approved_intent
reconcile_payment
attach_payment_evidence

Working rules

What the agent should do.

  • Follow the decision guide, use the declared tool boundary, and verify the result before responding.

Operating boundaries

What the agent should avoid.

  • Review the complete SKILL.md before enabling this skill for production work.

Install and connect

Add the skill beside the capability it expects.

Install the repository where your ADK-Rust skill loader can discover it, connect mcp-payments, and confirm the declared tools are available before asking the agent to use the workflow.

Install the skill
# Claude Code
git clone https://github.com/zavora-ai/skill-payment-processing.git \
  ~/.skills/skills/payment-processing

# ADK-Rust
cp -r payment-processing /path/to/project/.skills/skills/
ADK-Rust loading shape
let skills = SkillLoader::from_dir("~/.skills/skills").await?;
let skill = skills.load("payment-processing").await?;

let agent = LlmAgentBuilder::new("agent")
    .instruction(skill.instructions())
    .tools(skill.allowed_tools(toolset)?)
    .build()?;

The repository's compatibility statement: Requires mcp-payments server connected. Optional: mcp-finance for invoice matching, mcp-notifications for approval alerts, mcp-slack for payment confirmations.

Official documentation

Read the complete skill package.

The repository remains authoritative for its exact instructions, examples, helper scripts, assets, MCP requirements, license, and later updates.

Source record

Repository metadata for this skill entry.

View public repository ↗
License
Apache-2.0
Allowed tools
10
References
3
Revision
b4cd3f2b3464
Updated
May 31, 2026