Cheqi helps merchants issue digital receipts that customers can keep in the Cheqi app or open in the web wallet. Your integration supplies the final receipt details; Cheqi helps find the customer and deliver the receipt securely.
The SDKs handle customer matching, encryption, and submission for you. Pick yours to get started:
| SDK | Install |
|---|---|
| Java | Maven or Gradle: io.cheqi:cheqi-sdk |
| .NET | dotnet add package cheqi-sdk |
| JavaScript & TypeScript | npm install @cheqi/sdk |
| Python | pip install cheqi-sdk |
Prefer the command line? Use the Cheqi CLI. Working in another language? Use the API Reference, or see the SDK overview to request an SDK.
| Destination | When to use it | Customer experience |
|---|---|---|
| Cheqi app | A supported identifier, such as a payment account, pairing code, or email address, matches a Cheqi user. | The receipt arrives in the app automatically. |
| Web wallet | No app recipient is available, or your integration offers a receipt link with this route enabled. | The customer opens a link to view and save the receipt in a browser without an account. The same link can also be collected in the app. |
You choose how to share a web wallet link: a button on a webshop page, an order email, a text message, or a QR code at a physical checkout. The link is the receipt destination; a QR code is one way to present it. Learn more in Web Wallet.
Cheqi also supports credit notes, encrypted delivery to authorized accounting and expense integrations, and webhooks for those integrations. Receipt contents stay encrypted during delivery. Customers can choose whether to provide their first and last name.
- Ask Cheqi to match the customer using available identifiers, such as a card PAR, IBAN, email address, or pairing code.
- If the customer is matched, build the definitive receipt payload, encrypt it for the returned devices, and send it to their Cheqi app.
- If no customer is matched, offer an encrypted web wallet link when download fallback is enabled, or continue with your existing receipt process.
- Record the outcome and handle any pending upload or retry for a Cheqi receipt.
The Delivery Options page explains when each route applies. The SDKs handle the encryption and submission steps.
- Read Delivery Options and Web Wallet to understand what customers receive.
- Try the sandbox to issue a test receipt.
- Choose API key or OAuth authentication and an SDK: Java, .NET, JavaScript, or Python.
- Follow Recipient Resolution, Receipt Creation, and Sending Receipts.
- If you offer web wallet links, continue with Download Links for upload and retry behavior.
You can also use the API Reference or the Odoo connector. For receipt sharing with other systems, see Webhooks and Credit Notes.
Contact support@cheqi.io for integration help or to request an SDK for another language.