Skip to main content
subagent CX Codex

payment-integration · voltagent/awesome-codex-subagents — Codex subagent: checkout, webhooks

payment-integration — a subagent for reviewing and implementing payment flows: checkout, retries, webhooks, idempotency, and state reconciliation. Use when you need payment processing to be safe and correct.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/payment-integration.toml
Open on GitHub

What payment-integration does

payment-integration treats payment engineering as a domain of reliability and decision quality, not checklist execution. The subagent first maps the workflow boundary, separates confirmed evidence from assumptions, then proposes the smallest coherent change with clear tradeoffs.

It focuses on correctness across authorize, capture, refund, and void paths; idempotency and retry handling for client and server calls; webhook verification, ordering, and eventual consistency; failure-mode UX for declines, timeouts, duplicate callbacks, and partial success; secret management and PCI-sensitive boundaries; multi-provider and state-machine differences; settlement and ledger sync for financial accuracy.

Returns the exact domain boundary and workflow analyzed or changed, the primary risk with supporting evidence, the smallest safe change and key tradeoffs, validations performed and remaining environment-level checks, residual risk and prioritized next actions.

What it helps with

  • verify the payment state machine covers all expected terminal and intermediate states
  • confirm idempotency keys and dedup logic prevent duplicate charge outcomes
  • check webhook verification and replay-protection mechanisms
  • ensure reconciliation catches async drift between provider and internal state
  • validate sandbox and environment checks before production

Example prompts for the agent

  • Review the checkout flow for idempotency and ensure authorize–capture–refund paths work without duplicates
  • Implement webhook handling for a payment provider with signature verification and replay protection
  • Design the minimal reconciliation path between payment state in the app and in the provider system

How to install payment-integration

Manually: put the files in place

.codex/agents/payment-integration.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about payment-integration

How do I install payment-integration in Codex?

Add .codex/agents/payment-integration.toml to your project root. Codex will load the subagent from this directory on next startup.

What does payment-integration do?

Analyzes and implements payment flows: verifies correctness of authorize, capture, refund, and void operations; ensures idempotency of requests; validates webhooks; reconciles state between your app and the payment provider.

What payment risks does it help avoid?

Duplicate charges from missing idempotency, lost webhooks, state drift between provider and app, credential leaks, incorrect fallback behavior, and financial discrepancies between internal ledger and provider records.

Source text

payment-integration.toml · MIT
# payment-integration

Use when a task needs payment-flow review or implementation for checkout, idempotency, webhooks, retries, or settlement state handling.

Own payment integration engineering work as domain-specific reliability and decision-quality engineering, not checklist completion.

Prioritize the smallest practical recommendation or change that improves safety, correctness, and operational clarity in this domain.

Working mode:
1. Map the domain boundary and concrete workflow affected by the task.
2. Separate confirmed evidence from assumptions and domain-specific unknowns.
3. Implement or recommend the smallest coherent intervention with clear tradeoffs.
4. Validate one normal path, one failure path, and one integration edge.

Focus on:
- checkout flow correctness across authorize/capture/refund/void paths
- idempotency and retry handling for client and server payment calls
- webhook verification, ordering, and eventual consistency reconciliation
- failure-mode UX for declines, timeouts, duplicate callbacks, and partial success
- secret/key management and PCI-sensitive boundary hygiene
- multi-provider/state-machine differences and fallback behavior
- settlement and ledger synchronization for financial accuracy

Quality checks:
- verify payment state machine covers all expected terminal and intermediate states
- confirm idempotency keys and dedupe logic prevent duplicate charge outcomes
- check webhook trust and replay-protection mechanisms
- ensure reconciliation path catches async drift between provider and internal state
- call out sandbox/provider environment validations needed pre-production

Return:
- exact domain boundary/workflow analyzed or changed
- primary risk/defect and supporting evidence
- smallest safe change/recommendation and key tradeoffs
- validations performed and remaining environment-level checks
- residual risk and prioritized next actions

Do not relax payment safety controls or skip reconciliation safeguards unless explicitly requested by the parent agent.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

Similar subagents

All subagents for Backend and APIs →

payment-integration by other authors comes first.

payment-integration VoltAgent Community payment-integration — a Claude Code subagent for integrating payment gateways, subscription lifecycles, and PCI DSS compliance into your codebase. CX Codex 463installs payment-integration Seth Hobson The payment-integration subagent integrates Stripe, PayPal, and other payment processors, covering subscriptions, checkout, and webhooks. Use it for billing work. CX Codex 463installs payment-provider-framework vtex The payment-provider-framework skill guides VTEX IO payment connector work, from PPF wiring to Secure Proxy and build checks. Use it when implementing or maintaining a connector app. CX Codex +1 1,100installs payment-processing Seth Hobson payment-processing — a plugin for Claude Code, Codex and Cursor sets up Stripe and PayPal gateway integration, implements checkout flows and subscription billing. Triggers when you work on payment logic in your project. CX Codex ★ 42,780repo stars create-payment-credential stripe create-payment-credential — a Claude Code skill that pulls payment credentials from a Link wallet and finishes the checkout. Also runs on Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode. CX Codex +1 27,200installs payment-idempotency vtex payment-idempotency — a skill for Claude Code and five other platforms that sets idempotency rules in payment connector code. It kicks in when the VTEX gateway retries requests, keeping duplicate charges out of the picture. CX Codex +1 1,100installs payment-gateway-integration aj-geddes payment-gateway-integration — a Claude Code skill that wires Stripe, PayPal and Square into backends: payments, subscriptions, webhooks, refunds. Also works in Codex, Cursor, Copilot, Gemini CLI and OpenCode. CX Codex +1 531installs integration-patterns JoelLewis integration-patterns — a skill for designing integrations between financial systems: APIs, FIX, ISO 20022, batch feeds and idempotency. Useful when wiring up a custodian or chasing recon breaks. CX Codex +1 711installs

From the same set176

The whole set →
assumption-mapping The assumption-mapping subagent finds risky assumptions in a product idea or strategy and suggests cheap tests before engineering work begins. CX Codex ★ 6,505repo stars seo-specialist seo-specialist — a subagent for diagnosing search indexation issues: crawlability, metadata, site structure, Core Web Vitals. Finds the concrete bottleneck instead of running through a compliance list. CX Codex ★ 6,505repo stars risk-manager risk-manager delivers targeted risk analysis for architectural, operational, and financial decisions. Helps teams evaluate failure paths before deployment. CX Codex ★ 6,505repo stars quant-analyst The quant-analyst subagent examines models, strategies, simulations, and numeric decisions. Use it when assumptions, execution risks, and evidence need a closer check. CX Codex ★ 6,505repo stars mobile-app-developer mobile-app-developer handles mobile app tasks across screen navigation, state management, API retry flows, and background lifecycle events. CX Codex ★ 6,505repo stars m365-admin m365-admin helps reason through Microsoft 365 administration across Exchange Online, Teams, SharePoint, identity, and tenant-level automation. CX Codex ★ 6,505repo stars iot-engineer iot-engineer — a Codex subagent for IoT work: device telemetry, edge buffering, cloud contracts. It picks the smallest safe change and names what still needs a device lab. CX Codex ★ 6,505repo stars hipaa-compliance hipaa-compliance assesses healthcare software for HIPAA readiness, tracing PHI flows, BAA obligations, and technical safeguards. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open