Find the transaction that charged one recurring period
For when a charge landed and its response did not: your retry answers ALREADY_CHARGED, which proves the period was collected and names no transaction. P2Flux stores nothing, so the hash lives only in the contract's log - and without it you cannot attribute the payment to an order, audit it, or refund it, because refunds start from the original settlement.
Give it the subscription and the exact period. There is no 'current period' form on purpose: you are reconciling one specific collection, today or in a year, and the answer must not move under you.
The event is the proof. A settlement is returned only when the contract's own SubscriptionCharged log names this subscription AND this period, and only when its payer, recipient and amount match the signed authorization.
found: false is ordinary. There is no catch-up billing, so a period that was never collected is a normal history: a later period having been charged says nothing about an earlier one. Like the one-time recovery, a miss is a statement about one block height and never a permanent verdict.
A hint is an optimisation and nothing else - it narrows where the search starts, can never turn a miss into a hit, and is safe to omit.
Request
- Base URL: https://api.p2flux.com
- URL: https://api.p2flux.com/v1/charges/recover
- Auth: none required
Request body
Response
Either the located settlement, or a not-found that names the block it was true at.
Example response
{
"subscription_id": "0x2d6bbc112885a6976289e599f71003f7d310e7152ebd662c6221dffd3e0da708",
"tx_hash": "0x2d6bbc112885a6976289e599f71003f7d310e7152ebd662c6221dffd3e0da708",
"payer": "0xb4e43f3fBa5Add75395adAD366627E7d74141Fa9",
"recipient": "0xb4e43f3fBa5Add75395adAD366627E7d74141Fa9",
"net_units": "2500000",
"fee_units": "2500000",
"network_fee_units": "2500000",
"amount_units": "2500000"
}Changes
No recorded changes to this operation across all 1 revision of this API.