payment_id works with Verify Payment, and it appears in Transaction History with the same subscription_id and billing_reason.
Path Parameters
string
required
The subscription whose charges to list.
Query Parameters
integer
default:"1"
Page number.
integer
default:"10"
Items per page, maximum
100.Charge fields
string
required
Identifier of the payment. Use it with Verify Payment.
string
required
Same vocabulary as Verify Payment:
PENDING, SUCCESS, FAILURE or EXPIRED.string
required
Payment method used:
flouci (wallet), card, or NA while pending.string
required
Why the charge exists:
subscription_create (the first, on-session payment), subscription_cycle (a scheduled renewal) or subscription_retry (a dunning retry after a failed renewal).integer
required
0 for the first attempt of a period, then 1, 2, 3 for the retries.date | null
First day of the period this charge pays for. For the first charge it is the creation day.
date | null
Last day (exclusive) of the period this charge pays for.
null on the first charge.integer
required
Amount in millimes.
integer
Your fee in millimes; empty string
"" until computed.integer
VAT on the fee in millimes; empty string
"" until computed.timestamp
When the charge was created.
timestamp | null
When the wallet was debited (or the debit failed).
Several charges can share the same
period_start: a failed renewal (attempt: 0) followed by its retries (attempt: 1, 2, 3). At most one of them is SUCCESS.