One consent, then receipts arrive automatically
The cardholder consents once, inside your app. From then on, any purchase at a store that sends receipts through Smartbills is matched to their transaction and the receipt appears under it.
Embedded receipts, right inside your app
An embedded receipts API for banks, fintechs, retailers and third-party apps: the itemized merchant receipt inside your own product, under the transaction it belongs to. Nothing for your users to install.
Smartbills matches the store's receipt to the transaction and serves it to your app, by API or a drop-in component.
SDKs
Show the receipt in your own app
Fetch the receipt behind a transaction and render it with one React component, in English or French.
- TypeScript
@smartbills/sdk - React
@smartbills/react-sdk - .NET
Smartbills.SDK - Python
smartbills
import { SmartbillsClient } from "@smartbills/sdk";const smartbills = new SmartbillsClient({ accessToken: process.env.SMARTBILLS_TOKEN, businessId: 123,});// The itemized receipt behind a transactionconst receipt = await smartbills.receipts.getById(343);Result
For any app that shows a purchase
A bank or credit union puts the receipt under the card transaction. A fintech adds it to a card, budgeting or expense app. A retailer shows every in-store receipt in its own app, next to online orders. Any third-party app gets the same receipt through the API, with its users' consent.
- Banks, credit unions and card issuers
- Fintech card, budgeting and expense apps
- Retailer apps and third-party apps on the API
Maple & Rye4398 Rue Saint-Denis, MontréalDirections
A receipt view inside your app
Use the JSON API if you're building the screen yourself, or drop in a component that picks up your typography and colors. Either way the cardholder stays in your product.
- REST API returning items, quantities, tax and tender
- Or an embeddable component that takes your design tokens
- No redirect, no co-branding, no Smartbills account
Coverage measured on your own transactions
No receipt network covers every merchant. We measure coverage on a sample of your transactions before you commit. Transactions without a receipt still come back enriched.
The controls a risk team asks for
Data stays resident in-region, consent records can be produced on demand and every receipt carries its own audit trail. Smartbills never needs to know who the cardholder is.
How embedded receipts works
Link a card
The cardholder agrees once in your app. The card is tokenized through the network and the card number never moves.
Pay as usual
An ordinary purchase at a store that sends receipts through Smartbills. Nothing changes at checkout.
Receipt meets transaction
The merchant's point of sale sends the itemized receipt, which is matched to the card transaction by token, amount and time.
Your app shows it
Under the transaction in your own interface, through the API or our component, usually seconds after the payment clears.
Keep exploring
See all products- ProductTransaction enrichmentResolve a card descriptor into a business your customer recognizes, with logo, location and category, plus the itemized receipt when the merchant sent us one.
- ProductDispute defenceChargeback prevention that explains a charge right on the transaction screen, with the merchant's evidence ready for the disputes that open anyway.
- ProductDigital receiptsDigital receipt software that turns every sale at your POS into an itemized electronic receipt, hosted online and delivered by app, SMS, email or API.
FAQ
Frequently asked questions
What people ask us before they sign up.
Embedded receipts are itemized receipts shown inside your own app, under the transaction they belong to. Banks, fintechs, retailers and third-party apps use them so customers see what they bought without leaving the app, under the app's own brand.
Any company whose app shows a purchase: banks, credit unions and card issuers in the transaction screen, fintechs in card, budgeting and expense apps, retailers in their own shopping app, and third-party apps that call the API with their users' consent.
No. Card linking is tokenized through the card networks. What we hold is a token that matches a receipt to a transaction, never a card number. The cardholder's identity stays in your environment.
It depends on your market and your customers' spending mix, which is why we measure it on a sample of your own transactions before you commit. Coverage comes from point-of-sale platforms rather than individual stores. It grows without integration work on your side or the merchant's.
No. The receipts live in your app and Smartbills only supplies the data. Someone who also uses the Smartbills app will find the same receipts there, but nothing in your integration depends on it.
The transaction still comes back enriched with the merchant's name, logo, location and category, because Transaction Enrichment runs underneath this product. The response tells your interface which of the two states it's in. The detail screen always has something to show.
Yes, entirely. The API returns structured data only. The look is yours to design, and the drop-in component takes your design tokens if your team would rather not build the screen.
Canada has the deepest merchant network, since that's where it started. It grows through point-of-sale platforms rather than one market at a time. Ask us for current coverage in the markets you care about.
Get started
See your coverage before you write code.
We'll measure receipt coverage on a sample of your own transactions first.