failabsent from every registry#7 by calls of 15 on this host
0.18 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-10-04 21:22 UTC · method
- Validation state
- fail
- Uptime, 7 / 30 / 90 days
- — / 0% / 0%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-10-04 08:38 UTC
- First observed by TOLLderived
- 2026-10-04
- Pricederived
- 0.18 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 2 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.
The sweep of 2026-10-04 found payment allocation audit unreachable.
TOLL files payment allocation audit under the "other" category: a POST endpoint on api.zfinia.com, listed in neither registry at the last pull.
payment allocation audit is priced at 0.18 USDC on Base.
Callers of payment allocation audit supply a json body with the fields invoices, payments and allocations.
A response from payment allocation audit, as declared, includes limits, passed, complete, findings, invoices, payments and 2 others.
payment allocation audit drew a single call from a single payer in the trailing 30 days.
The last call to payment allocation audit came 9 days before the snapshot, 2026-10-04.
payment allocation audit shares api.zfinia.com with 14 other listed endpoints and is tied 7th by calls with 9 others.
payment allocation audit takes 4% of the calls counted across api.zfinia.com.
Most comparable listings in the "other" category, 98%, ask less.
payment allocation audit sits nearest in price to services vulnerability audit (www.cultos.dev) and tiers prototype (api.run402.com) among listings in the "other" category.
The wallet paid by payment allocation audit is the payee of 179 endpoints across 5 hosts.
Seller tags: accounts receivable, cash application, exact arithmetic and finance operations.
payment allocation audit was missing from the Coinbase registry at the pull of 2026-10-05, confirmed at the pull of 2026-10-05; 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-04 21:22 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.18 USDC | exact | 0x25e824…6a9608 |
the checks, as of 2026-10-04 13:10 UTC · methodendpoint answered HTTP none
endpoint_reachable· the endpoint answered at all
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-04 13:10 UTC | fail | 1 | daily-2026-10-04 |
| 2026-10-04 12:37 UTC | fail | 1 | 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:38 UTC · method
The input and output block
{
"input": {
"body": {
"invoices": [
{
"id": "INV-1",
"amount": "500.00",
"currency": "AUD"
},
{
"id": "INV-2",
"amount": "250.00",
"currency": "AUD"
},
{
"id": "INV-3",
"amount": "100.00",
"status": "cancelled",
"currency": "USD"
}
],
"payments": [
{
"id": "PAY-1",
"amount": "600.00",
"currency": "AUD"
},
{
"id": "PAY-2",
"amount": "100.00",
"currency": "AUD"
}
],
"allocations": [
{
"amount": "500.01",
"invoice": "INV-1",
"payment": "PAY-1"
},
{
"amount": "50.00",
"invoice": "INV-2",
"payment": "PAY-1"
},
{
"amount": "100.00",
"invoice": "INV-3",
"payment": "PAY-2"
},
{
"amount": "0",
"invoice": "INV-9",
"payment": "PAY-2"
}
]
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"limits": {
"maxEntries": 20000,
"maxAccounts": 5000,
"maxFindings": 500,
"maxLinesPerEntry": 500,
"maxStatementLines": 20000
},
"passed": false,
"complete": true,
"findings": [
{
"code": "CURRENCY_MISMATCH",
"detail": "Allocation 3 applies a AUD payment to a USD invoice. That is a conversion at a rate this data does not state.",
"invoice": "INV-3",
"payment": "PAY-2"
},
{
"code": "ALLOCATION_TO_UNPAYABLE_INVOICE",
"detail": "Allocation 3 applies 100 to invoice INV-3, whose status is cancelled. Money applied to an invoice in that state is in no receivable figure.",
"invoice": "INV-3",
"payment": "PAY-2"
},
{
"code": "ALLOCATION_TO_UNKNOWN_INVOICE",
"detail": "Allocation 4 applies 0 to invoice INV-9, which is not in the set supplied.",
"invoice": "INV-9",
"payment": "PAY-2"
}
],
"invoices": [
{
"amount": "500",
"status": null,
"invoice": "INV-1",
"currency": "AUD",
"allocated": "500.01",
"outstanding": "-0.01"
},
{
"amount": "250",
"status": null,
"invoice": "INV-2",
"currency": "AUD",
"allocated": "50",
"outstanding": "200"
},
{
"amount": "100",
"status": "cancelled",
"invoice": "INV-3",
"currency": "USD",
"allocated": "100",
"outstanding": "0"
}
],
"payments": [
{
"amount": "600",
"payment": "PAY-1",
"currency": "AUD",
"allocated": "550.01",
"unallocated": "49.99"
},
{
"amount": "100",
"payment": "PAY-2",
"currency": "AUD",
"allocated": "100",
"unallocated": "0"
}
],
"reconciled": false,
"request_id": "example-request",
"service_id": "payment_allocation_audit",
"assumptions": [
"Every total is exact, so an over-allocation of one cent is reported as one cent rather than disappearing into a rounding comparison.",
"An over-allocated invoice and an over-allocated payment are separate findings, because they are different events: one is money applied beyond what was owed and the other is money applied that was neve...",
"A cross-currency allocation is reported as a conversion at a rate the data does not state, rather than being converted on an assumption."
],
"limitations": [
"Whether the allocations supplied are arithmetically consistent with the invoices and payments supplied. Not an audit opinion and not accounting advice: whether a payment was genuinely received, or an ...",
"reconciled is true only when every allocation resolved, no total was exceeded, and nothing was left sitting unallocated."
],
"observed_at": "2026-10-02T00:00:00.000Z",
"not_examined": [],
"finding_count": 6,
"invoice_count": 3,
"payment_count": 2,
"total_invoiced": "850",
"total_received": "700",
"service_version": "1.0.0",
"total_allocated": "650.01",
"findings_by_code": {
"CURRENCY_MISMATCH": 1,
"INVOICE_OVER_ALLOCATED": 1,
"ALLOCATION_MOVES_NOTHING": 1,
"PAYMENT_PARTLY_UNALLOCATED": 1,
"ALLOCATION_TO_UNKNOWN_INVOICE": 1,
"ALLOCATION_TO_UNPAYABLE_INVOICE": 1
},
"total_outstanding": "199.99"
}
}
}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, "payment allocation audit on api.zfinia.com". https://tollindex.com/e/api-zfinia-com-x402-v1-payment-allocation-audit-800f2d. Accessed [access date].
BibTeX
@misc{toll-e-api-zfinia-com-x402-v1-payment-allocation-audit-800f2d-2026-10-13,
author = {TOLL},
title = {payment allocation audit on api.zfinia.com},
howpublished = {\url{https://tollindex.com/e/api-zfinia-com-x402-v1-payment-allocation-audit-800f2d}},
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.