cloudpayments

Implement CloudPayments payment flows with HMAC-verified webhooks and 54-ФЗ receipts.

15|2|Updated May 23, 2026
One-click install
npx skills add https://github.com/VKirill/antigravity-for-claude-code --skill cloudpayments
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cloudpayments
Source: https://github.com/VKirill/antigravity-for-claude-code/tree/main/skills/cloudpayments
Command: npx skills add https://github.com/VKirill/antigravity-for-claude-code --skill cloudpayments

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

CloudPayments integration work is hard to get right: you must implement multiple webhook gates, verify HMAC signatures on raw bodies, handle idempotency, and correctly support payments, refunds, subscriptions, and 54-ФЗ receipts.

Core Features & Use Cases

  • Widget + REST payment flows: implement one-step charges, two-step auth/capture, and server-side charges by cryptograms or saved tokens.
  • Secure webhook handling (Check/Pay/Fail/Refund/Recurrent): verify Content-HMAC/X-Content-HMAC over the raw request body, return correct {code: ...} semantics, and make processing idempotent using TransactionId.
  • Recurring billing + tokenization: store CloudPayments tokens, set up /subscriptions/create, and update your state on Recurrent webhooks.
  • 54-ФЗ fiscal receipt integration: build and attach CustomerReceipt with correct enums (taxationSystem, Vat, method, object) for charges and refunds.
  • High-stakes reliability defaults: recommended timeout budgets, retry expectations, HMAC pitfalls avoidance, and troubleshooting playbooks for common production failures.

Quick Start

Use the cloudpayments skill to implement secure CloudPayments payment handling with webhooks by verifying Content-HMAC, adding idempotent TransactionId processing, and wiring Check/Pay/Refund/Recurrent logic plus a 54-ФЗ CustomerReceipt.

Frequently Asked Questions about cloudpayments

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify CloudPayments webhooks using HMAC-SHA256 in Node.js?

To verify CloudPayments webhooks, compute an HMAC-SHA256 hash using your secret key over the raw request body and compare it against the Content-HMAC or X-Content-HMAC header before parsing the payload. This ensures webhook gate handling remains secure and prevents unauthorized processing.

What is the correct way to handle idempotency for CloudPayments payment lifecycle events?

Idempotency for CloudPayments payment lifecycle events is handled by consistently tracking the TransactionId. When processing Check, Pay, Fail, or Refund webhooks, you must use this TransactionId to ensure duplicate notifications do not cause double processing or state corruption.

How do I generate 54-ФЗ fiscal receipts for CloudPayments charges and refunds?

Generating 54-ФЗ fiscal receipts requires constructing a CustomerReceipt object with correct enums for taxationSystem, Vat, method, and object. You must attach this receipt data to both charge and refund operations to comply with Russian fiscalization requirements.

Can I implement recurring billing and subscriptions with CloudPayments tokens?

Yes, recurring billing is supported by storing CloudPayment tokens and utilizing the /subscriptions/create endpoint. You can manage recurring charges and update your internal state by listening for Recurrent webhook events to track subscription lifecycle changes.

What response code should my CloudPayments webhook endpoint return for successful processing?

CloudPayments webhook endpoints must return a JSON response containing `{code: 0}` to indicate successful processing. If processing fails or you wish to reject the notification, you must use appropriate reject semantics so CloudPayments can retry the webhook as needed.

Does CloudPayments integration support both widget and REST API payment flows?

CloudPayments integration supports widget-based payments, server-side REST API charges by cryptograms, and charges using saved tokens. It covers one-step charges, two-step auth and capture flows, as well as refunds, voids, and СБП transactions.