# Receipt Out > Receipt Out is building a universal digital receipt destination. Consumers can create a passwordless account, receive and search receipts, and manage their stored receipt data. Retailers and POS systems can use the Receipt Out v1 API to deliver authenticated itemized digital receipts to activated customer accounts. ## Canonical website - Home: https://receiptout.com/ - How it works: https://receiptout.com/how-it-works - For retailers: https://receiptout.com/retailers - Developer documentation: https://receiptout.com/developers - OpenAPI specification: https://receiptout.com/openapi.json - Retailer pilot request: https://receiptout.com/retailers#pilot-request - Privacy: https://receiptout.com/privacy ## Current status Receipt Out is in early development. Consumer accounts, permanent Receipt Out checkout IDs, revocable QR credentials, retailer-account linking, a searchable receipt inbox, a retailer/POS demo store, and the v1 receipt-delivery API are operational. The customer web app is installable as a PWA and an Android 0.1.0 test APK is available. Native iOS project source exists but still requires Apple/Xcode signing before TestFlight distribution. Receipt Out should not be described as currently integrated with a specific national or regional retailer unless that retailer is explicitly identified by Receipt Out in the future. The existence of the API means retailer integration is technically available; it does not imply a production partnership with any named retailer. ## Consumer product - Passwordless email sign-in. - Permanent Receipt Out ID in the form RO-XXXX-XXXX. - Revocable/versioned checkout QR credential. - One-time retailer loyalty/customer-account linking with customer disconnect controls. - Searchable receipt inbox. - Individual itemized receipt views. - Receipt search by retailer, item, transaction identifier, or amount. - Account data export. - Account and stored-receipt deletion. - Clearly marked demo receipts can be used during testing. ## Retailer API Production endpoint: POST https://receiptout.com/api/v1/receipts The API uses retailer-specific Bearer API keys and requires an Idempotency-Key header for every delivery. - Test API keys create receipts marked DEMO. - Live API keys create normal customer receipts. - Customers must already have an activated Receipt Out account. - Receipts can be routed using customer.qr_code, customer.receiptout_id, a linked customer.external_id, or customer.email as fallback. - Retailers can link their own customer/loyalty ID to a scanned Receipt Out QR with POST /api/v1/customer-links. - Money values are submitted as integer cents. - Receipt Out validates line-item totals, subtotal, discounts, tax, and final total. - Duplicate transaction IDs are rejected. - Safe retries with the same idempotency key return the original receipt instead of creating a duplicate. - The current request-body limit is 512 KB. - The current maximum is 200 line items per receipt. - The current accepted-delivery rate limit is 120 per minute per API client. See: https://receiptout.com/developers Machine-readable spec: https://receiptout.com/openapi.json ## Core product idea - One place for receipts from participating retailers. - Digital itemized receipts delivered after checkout. - Searchable purchase history. - Planned support for returns, warranties, business expenses, and other receipt-related organization. - Receipt Out is intended to complement, not replace, a retailer's checkout, loyalty program, app, or customer relationship. - The long-term goal is a standardized receipt-delivery layer that can work across many retailers, from independent businesses to large national chains. ## Privacy principles Receipt Out is being designed around the principle that a customer's receipts and purchase history are the customer's records. Receipt Out is not being built as a service for selling individual item-level purchase histories to advertisers or competing retailers. See: https://receiptout.com/privacy ## Consumer flow 1. A customer activates a Receipt Out account and receives a permanent Receipt Out ID plus a revocable QR credential. 2. At checkout, a participating retailer can scan the QR, use the permanent Receipt Out ID, use a previously linked retailer customer ID, or fall back to email. 3. The retailer or POS system delivers an authenticated itemized receipt through the Receipt Out API. 4. The receipt appears in the customer's Receipt Out inbox. 5. If the retailer account was linked once, future receipts can route automatically without another QR scan. 6. The customer can regenerate the QR, disconnect retailer links, search/view receipts, export data, or delete the account. ## Brand - Name: Receipt Out - Tagline: "Paper receipts are out." - Website: https://receiptout.com/