List an off session charge's attempts
Every presentment made for one charge, newest first. The charge alone says failed; only this says what the processor answered and when each attempt happened, which is the question behind “why has this customer not paid”. THE ROWS ARE APPEND-ONLY at the database grant, so a published attempt is never rewritten or removed. That is what makes this usable as evidence in a dispute. error is the processor’s own decline text and is a DIAGNOSTIC STRING, not a stable machine value: branch on status and show this to a person. It is null on a succeeded attempt, as is next_retry_at. An unknown charge id is a 404 rather than an empty page, so a typo can never be read as “this charge was never attempted”.
Authorizations
A secret API key. Publishable keys cannot reach this API. A key may carry an expiry, and an expired key is refused exactly like an unknown one, with a 401 that names no reason; check the key's expires_at in the dashboard rather than inferring it from a response. When a merchant rolls a key's secret they choose a grace window of up to 3 days, and for its duration BOTH the new secret and the one it replaced authenticate, so an integration moves over on its own deploy schedule instead of at the instant the button is pressed. Move before the window closes: after it, the old secret is refused. Nothing else about this contract moves with a roll. The key keeps its id and its scopes, so the only thing an integration updates is the credential itself.
Path Parameters
Query Parameters
Rows per page. Out of range is a 400 rather than a silent clamp, so a client asking for more than 100 learns it did not get it.
1 <= x <= 100The next_cursor from the previous page. Opaque: decode nothing from it and construct nothing by hand, since its encoding is not part of this contract. Omit it to read the first page.