passabsent from every registry#7 by calls of 15 on this host
0.24 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-10-05 14:34 UTC · method
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- — / 100% / 100%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-10-04 08:36 UTC
- First observed by TOLLderived
- 2026-10-04
- Pricederived
- 0.24 USDC
- Networks
- 1
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 4 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.
Among the 15 endpoints on api.zfinia.com, bank statement reconciliation is tied 7th by calls with 9 others.
bank statement reconciliation takes a json body with the fields ledger, statement, closing_balance, opening_balance and date_tolerance_days.
A response from bank statement reconciliation, as declared, includes limits, passed, matches, complete, findings, difference and 2 others.
bank statement reconciliation drew a single call from a single payer in the trailing 30 days.
The last call to bank statement reconciliation came 9 days before the snapshot, 2026-10-04.
Each call is priced at 0.24 USDC, payable on Base.
bank statement reconciliation takes 4% of the calls counted across api.zfinia.com.
TOLL files bank statement reconciliation under identity: a POST endpoint on api.zfinia.com, listed in neither registry at the last pull.
bank statement reconciliation answered the sweep of 2026-10-05 with a valid 402, as at every sweep since 2026-10-04.
Closest in price to bank statement reconciliation within identity: sanctions check at api.strale.io and reviews at www.cultos.dev.
bank statement reconciliation is near the top of prices in identity; 95% of comparable listings are cheaper.
The wallet paid by bank statement reconciliation is the payee of 179 endpoints across 5 hosts.
Seller tags: reconciliation, accounting, exact arithmetic and finance operations.
bank statement reconciliation was missing from the Coinbase registry at the pull of 2026-10-06, confirmed at the pull of 2026-10-06; that is registry presence, not liveness.
Where the sentences above compare this endpoint with others, the comparison is against the index as it stands now, live; the figures above are final.
the payment options, as of 2026-10-05 14:34 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.24 USDC | exact | 0x25e824…6a9608 |
the checks, as of 2026-10-05 06:06 UTC · methodendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-05 06:06 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 12:57 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-04 12:23 UTC | pass | 0 | new-after-daily-2026-10-04 |
Presence in a registry, not liveness of the service (method). Newest first.
- absence from Coinbase confirmed, rule v1
- absent from Coinbase at this pull
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-10-04 08:36 UTC · method
The input and output block
{
"input": {
"body": {
"ledger": [
{
"date": "2026-09-02",
"amount": "-120.51",
"reference": "DD-ENERGY-09"
},
{
"date": "2026-09-13",
"amount": "500.00",
"reference": "INV-2001"
},
{
"date": "2026-09-10",
"amount": "-75.00",
"reference": "EXP-4410"
},
{
"date": "2026-09-09",
"amount": "-14.49"
}
],
"statement": [
{
"date": "2026-09-02",
"amount": "-120.50",
"reference": "DD-ENERGY-09"
},
{
"date": "2026-09-05",
"amount": "500.00",
"reference": "INV-2001"
},
{
"date": "2026-09-09",
"amount": "-14.49"
},
{
"date": "2026-09-20",
"amount": "-100.00",
"reference": "DD-ENERGY-10"
}
],
"closing_balance": "1265.00",
"opening_balance": "1000.00",
"date_tolerance_days": 2
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"limits": {
"maxEntries": 20000,
"maxAccounts": 5000,
"maxFindings": 500,
"maxLinesPerEntry": 500,
"maxStatementLines": 20000
},
"passed": false,
"matches": [
{
"reference": "DD-ENERGY-09",
"days_apart": 0,
"matched_on": "reference",
"ledger_amount": "-120.51",
"statement_amount": "-120.5"
},
{
"reference": "INV-2001",
"days_apart": 8,
"matched_on": "reference",
"ledger_amount": "500",
"statement_amount": "500"
},
{
"reference": null,
"days_apart": 0,
"matched_on": "amount and date",
"ledger_amount": "-14.49",
"statement_amount": "-14.49"
}
],
"complete": true,
"findings": [
{
"code": "AMOUNT_DIFFERS_FOR_MATCHED_REFERENCE",
"detail": "Reference DD-ENERGY-09 is -120.5 on the statement and -120.51 in the ledger, out by exactly 0.01.",
"reference": "DD-ENERGY-09"
},
{
"code": "MATCHED_REFERENCE_OUTSIDE_DATE_WINDOW",
"detail": "Reference INV-2001 is dated 2026-09-05 on the statement and 2026-09-13 in the ledger, 8 days apart, beyond the 2-day window.",
"reference": "INV-2001"
},
{
"code": "STATEMENT_LINE_UNMATCHED",
"detail": "A statement line of -100 dated 2026-09-20 with reference DD-ENERGY-10 has no counterpart in the ledger, so money moved in the bank and not in the books.",
"reference": "DD-ENERGY-10"
}
],
"difference": "-24.99",
"reconciled": false,
"request_id": "example-request",
"service_id": "bank_statement_reconciliation",
"assumptions": [
"References are matched before amounts, because a reference is an identity and an amount is not. Matching on amount first would pair two unrelated lines that happen to agree and then report the real pa...",
"A reference match is reported even when the amount or the date disagrees, with the exact difference, rather than being discarded as a non-match. A reference that matches with the wrong amount is a mor...",
"Amount matching is exact, so two lines agree only if they agree to the last place. A date window is permitted and is published, since settlement lags posting."
],
"limitations": [
"Whether the two sets of lines supplied correspond. Not an audit opinion: whether a movement is properly recorded, authorised or classified is outside this.",
"reconciled is true only when every line on both sides matched, every matched pair agreed, and every check the caller asked for was performed."
],
"observed_at": "2026-10-02T00:00:00.000Z",
"ledger_total": "290",
"not_examined": [],
"finding_count": 5,
"matched_count": 3,
"service_version": "1.0.0",
"statement_total": "265.01",
"findings_by_code": {
"LEDGER_LINE_UNMATCHED": 1,
"STATEMENT_DOES_NOT_FOOT": 1,
"STATEMENT_LINE_UNMATCHED": 1,
"AMOUNT_DIFFERS_FOR_MATCHED_REFERENCE": 1,
"MATCHED_REFERENCE_OUTSIDE_DATE_WINDOW": 1
},
"ledger_line_count": 4,
"date_tolerance_days": 2,
"statement_line_count": 4,
"unmatched_ledger_count": 1,
"unmatched_statement_count": 1
}
}
}Cite this page
This endpoint is delisted: the page is frozen at its last observation and its live URL is the stable one. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "bank statement reconciliation on api.zfinia.com". https://tollindex.com/e/api-zfinia-com-x402-v1-bank-statement-reconciliation-18b3c0. Accessed [access date].
BibTeX
@misc{toll-e-api-zfinia-com-x402-v1-bank-statement-reconciliation-18b3c0-2026-10-13,
author = {TOLL},
title = {bank statement reconciliation on api.zfinia.com},
howpublished = {\url{https://tollindex.com/e/api-zfinia-com-x402-v1-bank-statement-reconciliation-18b3c0}},
year = {2026},
month = {10},
note = {Frozen at its last observation, 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.