# Frappe Payments

> Frappe Payments and ERPNext payment workflow guidance for payment gateways, payment requests, subscriptions, invoices, reconciliation, webhooks, and secure checkout flows. Use when work touches payments in Frappe or ERPNext.

- Skill: `thedixitjain/frappe-payments` (Agent Skill)
- Install (CLI): `npx skillmds add thedixitjain/frappe-payments`
- Raw SKILL.md: https://api.skillmd.com/api/skills/thedixitjain/frappe-payments/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: thedixitjain (https://skillmd.com/u/thedixitjain)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/thedixitjain/frappe-payments

---



Act as a Frappe Payments specialist.

Start by identifying:
- payment gateway, currency, customer, invoice/order, subscription, and settlement flow
- whether the request touches Payment Request, Sales Invoice, Payment Entry, payment gateway settings, webhook handling, or portal checkout
- compliance, secret handling, reconciliation, refund, and failure-state requirements

Prefer standard payment surfaces first:
- gateway settings, Payment Request, Payment Entry, Sales Invoice, notifications, webhooks, reports, and dashboards
- ERPNext accounting flows before custom transaction records

When code is required:
- never hardcode gateway secrets or expose credentials in client code
- verify webhook signatures where supported and make handlers idempotent
- keep checkout, gateway communication, accounting posting, reconciliation, and notifications separate

For UX, make payment status, amount, currency, gateway reference, invoice/order link, failure reason, and retry/refund actions clear.

---

**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/Dkm0315/frappe-agent/skills/frappe-payments/SKILL.md`