payments

payments is a cursor rule for Cursor from lacymorrow/paperclip-hub. It costs 0 tokens per session (857 once invoked), scanned A, original, MIT.

A set of guidelines for handling online payments, including payment-provider webhooks, payment status changes, sensitive data, and error cases. A webhook is an HTTP message sent by a payment provider when an event occurs.

In plain words
What is it for?
Use it when implementing payment endpoints, verifying webhook signatures, processing retries, updating payment records, handling refunds, and meeting PCI DSS payment-security requirements.
Why use it?
It helps prevent forged or repeated payment events, unsafe storage of payment data, incorrect payment states, and failures during retries or refunds.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when implementing payment endpoints, verifying webhook signatures, processing retries, updating payment records, handling refunds, and meeting PCI DSS payment-security requirements.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/lacymorrow/paperclip-hub/payments
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/lacymorrow/paperclip-hub

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for payments

README.md
[![agentmods](https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/payments/github.svg)](https://agentmods.dev/rules/lacymorrow/paperclip-hub/payments)
Your own site
<a href="https://agentmods.dev/rules/lacymorrow/paperclip-hub/payments"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/payments/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for payments

Your own site · 80×15
<a href="https://agentmods.dev/rules/lacymorrow/paperclip-hub/payments"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/payments.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 857 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00857
Opus 5.5 $0.00000 $0.00343
Sonnet 5.5 $0.00000 $0.00171
Haiku 4.5 $0.00000 $0.00086

Measured yesterday against content hash 389be38cb6a5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

payments scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/payments.mdc · 116 lines

How it starts

The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Payment Processing Best Practices

Payment Security

  • Always use HTTPS for all payment-related endpoints
  • Implement proper webhook signature verification for all payment providers
  • Never store sensitive payment data (use tokens and references)
  • Encrypt payment-related data at rest and in transit
  • Implement proper access controls for payment endpoints
  • Regular security audits for payment processing systems
  • Follow PCI DSS compliance requirements

Webhook Implementation

  • Verify webhook signatures using timing-safe comparison
  • Implement idempotency for all payment webhook events
  • Use database transactions for payment state changes
  • Handle webhook retries from payment providers gracefully
  • Log payment webhook events (excluding sensitive data)
  • Monitor webhook success rates and alert on failures
  • Test webhook endpoints with payment provider sandbox environments

Payment State Management

  • Use database transactions for payment status updates
  • Implement proper state machines for payment flows
  • Handle edge cases like partial payments and refunds
  • Synchronize payment data between local database and payment provider
  • Implement proper rollback mechanisms for failed payments
  • Track payment history and audit trails
  • Handle subscription lifecycle events properly

Error Handling

  • Return appropriate HTTP status codes for webhook responses
  • Implement proper error logging for payment failures
  • Never expose internal payment errors to end users
  • Implement graceful degradation for payment system outages
  • Handle payment provider API rate limits
  • Implement retry logic with exponential backoff
  • Monitor payment error rates and patterns

Lemon Squeezy Integration

  • Always verify X-Signature header using HMAC-SHA256
  • Support critical webhook events: subscription_created, subscription_updated, subscription_cancelled, order_created, order_refunded
  • Handle both test and production webhook environments
  • Implement proper customer and subscription synchronization
  • Use Lemon Squeezy checkout URLs for secure payment processing
  • Handle Lemon Squeezy specific payment methods and currencies
  • Test integration thoroughly in sandbox environment

Read the full file on GitHub · 116 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 116 lines · 0 tokens per session scan A 389be38cb6a5

Subscribe to this mod's changes

payments is a cursor rule published in the GitHub repository lacymorrow/paperclip-hub (15 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 857 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-11-10.

Related

payments compared with cursor rules from other repositories

payments next to 6 cursor rules from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
paymentslacymorrow/paperclip-hubCursor rule15yesterdayMITA0Cursor
stripe-webhooksvibestackdev/vibe-stackCursor rule8yesterdayMITA0Cursor
stripe-paymentsvibestackdev/vibe-stackCursor rule8yesterdayMITA0Cursor
always-push-pritsmemeworks/adhxCursor rule195d agoMITA279Cursor
payment-providersshipkit-io/bonesCursor rule21yesterdaynoneA0Cursor
paymentsshipkit-io/bonesCursor rule21yesterdaynoneA0Cursor
ponytailDietrichGebert/ponytailCursor rule188k13d agoMITA604Cursor