Issue structured data
A merchant, POS system or webshop submits the receipt through Cheqi's API or SDK. The purchased items are encrypted before reaching Cheqi's backend.
Cheqi is a privacy-first digital receipt platform and API based in Delft, the Netherlands. Retailers, supermarkets, POS providers, restaurants, webshops and unmanned self-service stations use it to issue electronic receipts. Receipt contents are end-to-end encrypted before reaching Cheqi’s core routing service.
Cheqi provides receipt issuance, payment-linked receipt delivery and receipt routing for staffed and unattended checkouts, including kiosks, fuel pumps and EV charging stations. Operators integrate once with the API and SDKs to reach customer wallets and authorized accounting or expense tools. Automatic delivery requires a participating issuer and a matched customer.
Digital receipts, electronic receipts and e-receipts describe purchase records issued and delivered digitally. For POS teams, Cheqi supplies the API and SDKs; for customers, the Cheqi app and browser wallet provide ways to receive and manage those receipts.
A merchant, POS system or webshop submits the receipt through Cheqi's API or SDK. The purchased items are encrypted before reaching Cheqi's backend.
Cheqi uses the routing information needed to find eligible recipients and delivers the encrypted receipt to their devices and authorized destinations.
When no Cheqi recipient is matched, a merchant can offer a client-encrypted browser receipt through a QR code or link. The decryption key stays in the link, outside Cheqi's backend.
Add electronic receipt issuance to supermarkets, stores, restaurants, webshops, self-checkout kiosks and unmanned fuel or charging stations through one API and SDK integration.
Receive receipts automatically from participating merchants in the Cheqi app, or open a browser receipt when offered one.
Route structured receipts to authorized accounting and expense software. Employees can also submit selected business receipts from purchases paid with their own card to their employer’s connected expense workflow.
Cheqi’s merchant issuance flow starts with structured receipt data. Receiving integrations can accept CHEQI JSON and applicable UBL Invoice, UBL Purchase Receipt and UBL Credit Note documents. Line items, VAT and totals remain machine-readable, without reconstructing a paper receipt through OCR.
On the standard encrypted delivery routes, Cheqi knows the identity and payment metadata required for matching but cannot read the receipt contents: what was bought. Cheqi-operated integrations may use a different, explicitly disclosed access model; review each integration before connecting it.
Receipts arrive when a participating retailer or software provider issues through Cheqi. Automatic payment-linked delivery depends on the identifiers available from the checkout and payment provider. Check the integration documentation for supported workflows, setup requirements and limitations.
Yes. At participating checkouts, Cheqi matches eligible card or account payment identifiers to recipients and delivers electronic receipts automatically. Matching depends on information supplied by the checkout and payment provider. The payment provider processes the payment; Cheqi handles receipt matching and delivery.
Receiving integrations can accept CHEQI JSON and applicable UBL Invoice, UBL Purchase Receipt and UBL Credit Note documents. The customer’s device prepares documents for authorized destinations according to their accepted formats, then encrypts each recipient’s copy.
Cheqi's merchant issuance flow uses structured receipt data from the source. It does not depend on scanning paper or OCR to create those e-receipts.
Yes, when the merchant enables browser receipts, a customer without a Cheqi match can open one from a secure QR code or link.
No. Automatic delivery depends on participating merchants and integrations. A merchant can offer browser receipts to customers who do not use Cheqi.
Choose the path that fits what you want to do with electronic receipts.