CloudPayments payments and declines report

CloudPayments payments report for your client

CloudPayments is a payment service used by online schools, subscription products, charities and online stores to accept cards, SBP and e-wallets. For a marketer it is the most reliable point in the funnel: it shows how many visitors did not just press Pay but actually paid.

Reportkey exports transactions through the CloudPayments API and builds blocks of a recurring report from them, placed next to ad spend and website analytics and delivered on schedule as a link or PDF.

CloudPayments analytics: successful payments

A CloudPayments transaction moves through several states. Authorized means the amount is held on the card but not charged. Completed means the money was charged. Cancelled means the authorisation was voided, and Declined means the bank or fraud screening rejected the operation. The receipts block uses completed transactions only:

• Successful payments — count per day, week or month.
• Payment amount — turnover from completed transactions.
• Average payment — amount per payment.
• Previous-period comparison for each line.

Test transactions are dropped automatically, so checking the payment form before a launch does not spoil the statistics.

CloudPayments declines and their reasons

What sets this block apart from a regular sales summary is declined payments. Every Declined transaction carries a reason: insufficient funds, limit exceeded, expired card, issuer decline or failed 3-D Secure authentication. The block shows the count and amount of declined payments, the decline share of all attempts and a split by reason and card type.

For an online school during a launch, this table literally shows lost money. A rise in 3-D Secure failures points to terminal settings; a rise in insufficient funds suggests offering instalments.

Refunds and net receipts

A transaction with a refund is flagged in the export. The refunds block shows refunded payments, their amount and net receipts, meaning successful payments minus returned money, the number worth discussing with clients who offer money-back guarantees or trials.

CloudPayments transaction export: cards and currencies

Each transaction stores card type and currency. The card type table shows which card networks buyers use and how turnover splits. Multi-currency terminals are shown per currency rather than summed.

Time zone matters too. CloudPayments returns times in UTC by default, so in a manual export late-night Moscow payments fall into the previous day. Reportkey requests transactions in the project time zone, keeping day boundaries familiar to the client.

CloudPayments data caveats

• A payment is a money result, not an ad conversion; linking it to a campaign requires the invoice or payer ID in a CRM or end-to-end analytics.
• Authorised but unconfirmed payments are not receipts.
• The API password grants full terminal access and should be stored as a high-level secret.

CloudPayments next to ads and analytics

Add Yandex Direct campaigns, VK Ads and payment goals in Yandex Metrica or Google Analytics 4. To link payments to ads, use Roistat; if some payments go through a second provider, add the YooKassa payments block. Report branding, scheduled sending and AI insights are not on every plan. A finished document is shown in the demo report, other payment providers and stores are on the ecommerce and online payments integrations page, and the free 14 days are described on pricing.