Cheqi offers two ways for a customer to receive a receipt. Your integration supplies one definitive ReceiptPayload and follows the route returned by recipient resolution.
| Route | Merchant action | Customer experience |
|---|---|---|
DIGITAL | Encrypt and submit the receipt for the returned recipients. | The receipt arrives in the Cheqi app automatically. |
DOWNLOAD_FALLBACK | Create the encrypted receipt link and share it in a way that suits your checkout. | The customer opens the receipt in the web wallet, or collects it in the app. |
An email address can identify an existing Cheqi user for app delivery. If it does not match a user, an enabled download route can provide a web wallet link.
If a card terminal supplies only the last four digits, those digits do not identify a customer at checkout. Include them in the encrypted ReceiptPayload.paymentDetails.cardLastFour when offering an enabled web wallet link.
If recipient resolution returns routeFound: false, no delivery route is enabled for that request. End the Cheqi flow and continue with your existing receipt process; do not create a link through the low-level download endpoint. A temporary API outage is a separate case: integrations that support offline issuance can retain a link and complete its encrypted upload when service returns. See Download Links.
The receipt body, including line items, totals, taxes, and payment details, stays encrypted during delivery. Cheqi uses the information needed to match and deliver the receipt. Customers can choose whether to provide their first and last name; the wallet does not require them.
For current SDK-issued receipts, Cheqi does not hold the keys needed to decrypt the receipt body. The sandbox test customers are an exception: authorized issuing-company admins can inspect submitted test input. Use fake data for those customers. This preview is unavailable in production.
- Read Web Wallet to understand what a receipt link gives the customer.
- Try the sandbox to issue a test receipt.
- Use Recipient Resolution to select a route.
- Build the Receipt Payload and send the receipt.
- For the link route, use Download Links for the upload and retry contract.
Authorized third-party delivery is described in Webhooks.