risk data for machine payments
Endpoint
api.invoket.com/invoice/vat-treatment/batch
A sales ledger or an order book judged in one call: up to 200 transactions, one VAT determination each, one settlement. Same verdicts as /invoice/vat-treatment - place of supply, person liable, standard VAT, reverse charge, intra-Community exemption or out of scope, the rate in force at the date of each line, the compulsory invoice mentions and the articles of Directive 2006/112/EC they rest on. A malformed item is reported at its position instead of failing the batch; only an empty or oversized batch is a 400. Legal bases and caveats are shared across the batch and cited by key, and the summary counts the five mechanisms. Customer VAT numbers are taken AS DECLARED (zero network by design) - verify them with /company/vat; uncovered regimes (OSS/IOSS, import VAT, margin schemes, triangular transactions) come back as a motivated undetermined, never a plausible default.
Score
The score is built from observations we collect ourselves: how the endpoint responds, what the envelope contains, how stable the price and the recipient are, who pays and how often. It is deterministic — the same input always produces the same result.
We do not publish the exact methodology yet. If you own this endpoint, write to us and we will show you, item by item, what drags the score down.
Recent probes
| When | Code | Latency | Scheme and network | Recipient | Price | Findings |
|---|---|---|---|---|---|---|
| 1h ago | 402 | 31 ms | exact eip155:8453 |
0x4465…28ee | 0.010000 | clean |
| 4d ago | 402 | 413 ms | exact eip155:8453 |
0x4465…28ee | 0.010000 | clean |
| 4d ago | 402 | 415 ms | exact eip155:8453 |
0x4465…28ee | 0.010000 | clean |
Reference
| URL | https://api.invoket.com/invoice/vat-treatment/batch |
| Sources | well-known |
| Recipient per catalogue | 0x4465825B0ac713aA2Fa07Ea29023020804A128ee |
| Machine access | /v1/endpoint · /full · badge |
Is this your endpoint?
The score is built only from public observations. If something we recorded is wrong — say our prober hit you during maintenance — write to us. We will recheck and publish your reply next to the score.
We do not delete accurate observations. The prober makes at most one request per second per host and only asks for the payment challenge — it never pays and never takes content.