Skip to main content
Paymend makes processing and settlement detail available across four different reports, which collectively describe the full lifecycle of a payment, from the moment it is created through to the money settling in your account.

Payments created

Every payment record opened, whether or not it was later processed.

Transactions succeeded

Sales captured and refunds returned.

Payments disputed

Alerts, RDRs, chargebacks and fraud reports raised against your payments.

Settlement paid out

Every event that contributed to a payout, with associated fees.

​
Reports are period-based and immutable

Each report covers one closed period. It is generated after the period ends and never changes afterwards.
Regenerating a report for a period you already hold returns byte-identical content. If a report you already downloaded differs from a later copy, treat that as a defect and contact support rather than reconciling against it.
This has two consequences worth designing around:
  • A report is a safe primary key source. Once you have ingested a period, you never need to re-read it to pick up amendments.
  • Late-arriving data lands in a later period, not a restated one. A dispute raised in September against a payment created in July appears in the September dispute report. It does not cause July’s report to change.
Every row in every report carries an event_id that is unique to that event. This is the event-level join key between processing and settlement reports. Non-payment events also have a payment_id - the same paymentId value returned in responses from the payments API - which allows reconciliation between an event and the payment that it relates to.

​
File naming

Dates are YYYYMMDD, and both bounds are inclusive.
Settlement reports carry a single date, not a range. That date is the payout date, not the period the report covers. The events inside it fall in the settlement period that closed before the payout ran — which depends on your payout schedule.
merchant_name is your merchant identifier as configured on your Paymend account. It is stable and safe to parse.

​
Which timestamp defines the period

Each report is bounded on its own event timestamp, so the same payment can appear in reports covering different periods. A payment created in June, captured in July and charged back in August appears in three different processing reports, each in the period matching that stage.

​
Amounts and currency

All amounts are decimal strings in major units — 97.00, not 9700. Negative values are debits against your payout. Each report states its own currency column; see the individual pages.

​
Next steps

Reconciliation guide

How to join the four reports and prove that every processed event was paid out.