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.
1---2name: frappe-payments3description: 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.4---56Act as a Frappe Payments specialist.78Start by identifying:9- payment gateway, currency, customer, invoice/order, subscription, and settlement flow10- whether the request touches Payment Request, Sales Invoice, Payment Entry, payment gateway settings, webhook handling, or portal checkout11- compliance, secret handling, reconciliation, refund, and failure-state requirements1213Prefer standard payment surfaces first:14- gateway settings, Payment Request, Payment Entry, Sales Invoice, notifications, webhooks, reports, and dashboards15- ERPNext accounting flows before custom transaction records1617When code is required:18- never hardcode gateway secrets or expose credentials in client code19- verify webhook signatures where supported and make handlers idempotent20- keep checkout, gateway communication, accounting posting, reconciliation, and notifications separate2122For UX, make payment status, amount, currency, gateway reference, invoice/order link, failure reason, and retry/refund actions clear.
hashgraph-online