XML for the systems
that still ask for it.
Some accounting systems, EDI pipelines, and government filings still want XML. Ours is well-formed XML 1.0 with UTF-8 encoding, ISO 8601 dates, attributes for ids and metadata, and elements for content. Validates against a published XSD.
receipt_2yK3pQ.xml
XML<?xml version="1.0" encoding="UTF-8"?>
<receipt id="rcpt_2yK3pQ" status="completed" language="en-US" currency="USD">
<merchant>
<name>Brew & Butter</name>
<address>128 Palm St</address>
</merchant>
<payment method="card" brand="visa" last4="4242"/>
<items>
<item id="item_01" confidence="96">
<name>Oat milk latte</name>
<variant>Large</variant>
<category>Drinks</category>
<quantity>1</quantity>
<price>5.50</price>
<tax_rate>0.085</tax_rate>
</item>
</items>
<totals subtotal="25.00" tax="2.13" total="27.13"/>
<summary>Five drinks and pastries from a coffee shop, paid by card.</summary>
</receipt>When to use
- Your downstream system or partner requires XML (EDI, government filing, legacy ERP)
- You're plugging into XSLT pipelines
- You need to validate against a published XSD
Probably not the right pick when
- You have any choice in the matter (JSON or CSV are both more ergonomic)
- You're piping into a modern web stack
- Your audience is a human (the dashboard or CSV is friendlier)
The endpoint
POST /v1/receipts/:id/export?format=xmlFAQ
About the
.xml export.
Is there a published XSD?
Yes, served at api.ripceipt.com/v1/receipt.xsd. It validates the exact shape we return so your XSLT or validating parser can rely on it.
How is escaping handled?
Standard XML escaping for &, <, >, and quoted attributes. Element values get the full set; attributes get the appropriate subset. CDATA blocks are not used.
Why attributes for some fields and elements for others?
Identifiers, codes, and metadata go in attributes (compact, queryable via XPath). Human-readable content goes in elements (allows entity references, easier to read). Standard tradeoff.
Can I get the namespace URL?
Yes, ripceipt.com/schema/v1/receipt. Versioned alongside the API, so the namespace itself signals the schema version.