Reports
The Reports API allows you to export your payment data as CSV files for accounting, reconciliation, and analysis.
Available Endpoints
| Method | Path | Description |
|---|---|---|
| GET | /reports/payments/export | Export payments as CSV |
| GET | /reports/subscriptions/export | Export subscriptions as CSV |
| GET | /reports/subscription-charges/export | Export subscription charges as CSV |
Fiat columns on the subscription-charges export
/reports/subscription-charges/export carries fiat_amount, fiat_currency and
settlement_status as its last three columns. Unlike the API response, fiat_amount is written
here as a decimal string already scaled to the currency, not in minor units.
Trailing zeros are stripped, so the decimal part is variable width — parse it as a decimal, not as an integer or a fixed two-place string:
API fiat_amount (ARS) | CSV fiat_amount |
|---|---|
1250000 | 12500 |
1250050 | 12500.5 |
1250005 | 12500.05 |
The same caveats as the API field apply. fiat_amount is the plan’s fixed per-cycle price, not a
per-charge rate and not a confirmed payout: on a crypto-settling business it is a pricing figure
only, with settlement_status empty. All three cells are also empty on failed and reverted charges,
and on recurring charges the indexer wrote after winning the race with the API write path — so an
empty cell does not imply the plan is crypto-priced. A subscription’s first charge is the exception
on a fiat-settling business: the subscribe endpoint fills the three fields in even when the indexer
wrote the row. Reconcile against money received only where settlement_status is completed. See
Subscription Charges for the full
field semantics.
