GDPR processor checklist
● Livehalowerk.com
Checklist after Art. 28 GDPR (Regulation (EU) 2016/679 Art. 28 (GDPR), https://eur-lex.europa.eu/eli/reg/2016/679/oj, German and English text retrieved from the EU Publications Office 2026-11-01): Art. 28(3) sentence 1 (subject-matter, duration, nature and purpose, type of personal data, categories of data subjects, obligations and rights of the controller), points (a) documented instructions incl. third-country transfers, (b) confidentiality of authorised persons, (c) Art.
- Price
- $0.005
- Asked in its payment challenge
- Chain
- Base
- Paid in
- USDC
- Live
- 4 of 4 checks
Endpoints
50 more endpoints · on x402 Bazaar
Checks and payment terms on this page refer to the first endpoint's example. Other endpoints have not been checked individually.
- POSThttps:
//format.halowerk.com /v1 /zugferd-generate$0.005Builds the structured invoice as XRechnung 3.0 in UN/CEFACT CII syntax, validates it with the KoSIT validator 1.6.3 (XRechnung configuration 3.0.2) and only then creates the hybrid PDF: PDF/A-3b with embedded fonts (Liberation Sans, OFL) and sRGB output intent, XMP metadata with the Factur-X extension schema (conformance level XRECHNUNG), and the XML attached as xrechnung.xml with AFRelationship Alternative, as required for the ZUGFeRD 2.3 profile XRECHNUNG. Example
curl -i -X POST 'https://format.halowerk.com/v1/zugferd-generate' \ -H 'Content-Type: application/json' \ -d '{"buyer":{"city":"Münster","name":"Beispielbehörde","street":"Amtsweg 2","country":"DE","postcode":"48143","electronic_scheme":"0204","electronic_address":"991-33333TEST-33"},"lines":[{"name":"Sensor maintenance","quantity":3,"vat_rate":19,"unit_code":"HUR","unit_price":95},{"name":"Technical handbook","quantity":1,"vat_rate":7,"unit_code":"C62","unit_price":20}],"number":"RE-2026-0042","seller":{"city":"Gronau","name":"Beispiel Manufaktur GmbH","street":"Musterweg 1","vat_id":"DE123456788","country":"DE","postcode":"48599","contact_name":"Buchhaltung","contact_email":"[email protected]","contact_phone":"+49 2562 0000","electronic_address":"[email protected]"},"payment":{"iban":"DE89370400440532013000","terms":"Payable within 14 days without deduction.","means_code":"58"},"due_date":"2026-11-13","language":"de","issue_date":"2026-10-30","delivery_date":"2026-10-28","buyer_reference":"991-33333TEST-33"}'
A dash means the listing gives no price or method. {Braces} mark a value you fill in. Copy buttons copy an example URL.
Showing 1 of 51 endpoints. First endpoints
Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/format.halowerk.com
Recent checks
- Median response
- 517 ms
- Last checked
- 17 Nov, 15:23 UTC
Our probes look for a payment challenge. They don't test payment or delivery.
All 4 checks
| When (UTC) | Result | HTTP | Response |
|---|---|---|---|
| 17 Nov, 15:23 UTC | Live | 402 | 547ms |
| 16 Nov, 03:24 UTC | Live | 402 | 357ms |
| 14 Nov, 15:21 UTC | Live | 402 | 1932ms |
| 13 Nov, 00:24 UTC | Live | 402 | 487ms |
Questions
Did our last probe detect a payment challenge?
At our last probe on 17 Nov, 15:23 UTC, it returned HTTP 402 or another detected payment-challenge signal.
What payment terms does format.halowerk.com advertise?
The listing advertises x402, Base and USDC. It names cdp as its facilitator. Check the seller's current payment challenge and authentication requirements before paying.
Something wrong on this page? Tell us.