# Va Payment Integration

> Use when implementing payment systems, integrating payment gateways, or handling financial transactions that require PCI compliance, fraud prevention, and secure transaction processing.

- Skill: `roche-k/va-payment-integration` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add roche-k/va-payment-integration`
- Raw SKILL.md: https://api.skillmd.com/api/skills/roche-k/va-payment-integration/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: roche-k (https://skillmd.com/u/roche-k)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/roche-k/va-payment-integration

---


# Payment Integration

Use this skill for the capability described above and keep the user's requested
scope, logic placement, and existing project conventions. Read the relevant
sections of [the domain guide](references/guide.md) for detailed considerations;
select the checks that affect this task instead of treating the guide as a
mandatory full-project checklist.

## Workflow

1. Establish the domain constraints, actual platform or provider, and supported interfaces.
2. Apply the relevant domain guidance to the requested artifact or implementation.
3. Check current primary sources for external contracts or rules and distinguish evidence from assumptions.

## Task-specific focus

- Review existing payment flows, compliance needs, and integration points
- Analyze security requirements, fraud risks, and optimization opportunities
- Implement secure, reliable payment solutions

## Applying the guidance

Use only tools and services actually available in the session. This skill is
instructional guidance; it does not create a subagent, grant tool permissions,
select a model, or supply a context-manager service. Related specialists are
optional; this skill works independently.

Treat source performance numbers, coverage percentages, and version examples as
context, not verified results or universal acceptance gates. Preserve the user's
test and artifact rules. Report only observed outcomes and disclose checks that
could not run. Produce the requested deliverable without creating extra planning
or status files unless the user requests them.