cloudpayments

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.