No-Code Stripe App for Receipts: Setup and Limits
A no-code Stripe app for receipts lets you decide which customers get a receipt email without writing code or setting up webhooks. RouteReceipts is one: it installs from the Stripe App Marketplace, runs inside the Stripe Dashboard, and sends receipts only to the customers on an allowlist. This guide covers what it does, how to set it up, what it costs, and the things it does not do, so you can decide before you install.
Why Stripe's own receipt setting is not enough
Stripe's Dashboard setting for receipts is all or nothing: either every paying customer gets an email for a successful payment, or none do. In Stripe's customer email settings (Settings, Business, Customer emails) the Successful payments toggle applies to the whole account, and Stripe's receipts documentation describes the per-payment alternative as passing a receipt_email value when you create a payment, which means writing code.
That gap matters in a few common situations:
- A finance team has enterprise clients who need a receipt for every payment because they file expense reports, while hundreds of small customers do not need the email at all.
- An e-commerce owner is tired of customers getting a receipt on top of an order confirmation from the store.
- A subscription business wants only some accounts to get a monthly receipt.
The usual no-code answer is to leave receipts on and live with the noise, or to turn them off and send them by hand. A selective-sending app is the third option, and it is the one this guide covers. For a broader look at the topic, see the guide to managing Stripe receipt emails without coding.
What RouteReceipts does
RouteReceipts sends Stripe's standard receipt to customers on your allowlist and sends nothing to everyone else. When a payment succeeds, the app checks the customer against the list. For a listed customer it sets the charge's receipt email, and Stripe sends its own receipt email from there. A customer who is not listed gets no receipt.
It covers successful payments of these kinds:
- Paid invoices, whether standard, manually sent or from a subscription
- One-off charges
- Checkout and Payment Links
- Stripe Terminal payments
That includes ACH or bank-transfer payments and payments in several currencies. It does not handle refund receipts or credit notes, so those stay under Stripe's own settings.
Because Stripe sends the email, the receipt looks exactly like any other Stripe receipt. The app has no templates, branding, PDFs or sending address of its own, and it cannot add extra recipients. If you want to change how Stripe receipts look, that happens in Stripe's branding settings, covered in the Stripe receipt branding guide.
How to set it up
Setup takes about 5 minutes, and you can start routing receipts in under a minute once the app is installed. No code or webhook setup is involved.
- Install the app. Open the Stripe App Marketplace and install RouteReceipts. You need the Stripe Owner or Admin role to do it. The installation walkthrough shows each screen.
- Turn off Stripe's own receipts. In the Stripe Dashboard go to Settings, then Emails, and switch off Successful payments. Skip this and customers on your allowlist get two receipts, one from Stripe and one routed by the app. Stripe's invoice emails are a separate setting and stay on.
- Add customers to the allowlist. Open the app in the Dashboard sidebar and add an entry. An entry is a Stripe customer ID, an email address, or both, with an optional note. If you enter a customer ID, the app fills in the email from Stripe.
- Try it in test mode. The app works in Stripe test mode, so you can run a payment through before you go live. Stripe itself does not email receipts for test payments (see its documentation), so use the app's decision log to confirm what the app decided.

You can also manage entries from inside Stripe: the app adds a checkbox on the customer page, and a suppressed payment shows a suppressed status on the payment itself. The allowlist guide goes deeper on how entries behave.
How the allowlist works day to day
The allowlist is a single list per account that you search, add to and delete from one entry at a time. You can search it by customer ID, email or note. Changes apply right away to new payments.
Two details are worth knowing before you rely on it:
- A customer added after a payment was processed gets no receipt for that payment. Adding them affects future payments only.
- Removing an entry stops receipts on future payments.
A duplicate check blocks a second receipt for the same payment. Delivery uses retries, queues, delayed sends and batched receipts, so if the app is briefly unavailable the receipts are delayed rather than dropped.
What the audit trail shows
Every decision to send or suppress a receipt is logged with the Stripe event ID, the customer and the reason. Typical reasons are a monthly limit reached, no matching ID or email, or a payment processed before the customer was added. The log is a tamper-evident audit trail, shown on the app's settings page, and you can search it by customer, email, event ID or date.
This is what answers the finance question "why did this customer not get a receipt?" without anyone digging through Stripe events. The app also shows how many receipts you have used this period and how many are left.
The log has limits. It cannot be exported or downloaded, and it does not record changes to the allowlist.
What it costs
There are three plans, and they differ only in how many receipts you can send each month.
| Plan | Price | Receipts per month |
|---|---|---|
| Free | $0 a month | 20 |
| Pro | $9 a month | 300 |
| Business | $29 a month | Unlimited |
Every plan includes the full allowlist, the decision log, the dashboard interface and access to the billing portal. The Free plan needs no credit card, and there is a free trial. You upgrade through Stripe Checkout from the app's settings, and "Manage billing" opens the Stripe billing portal. A cancelled paid plan runs to the end of its billing period and then reverts to Free.
The limit is a hard stop. When you reach it, a banner appears and receipts stop until the next billing period or until you upgrade. They do not fall back to Stripe's receipt settings, and there is no overage billing. No data is lost. If your volume is close to a plan's ceiling, check the usage counter and upgrade before the month ends.
Which plan fits: a worked example
Take a software company with 60 customers on monthly subscriptions, of which 12 are enterprise accounts that need receipts for expense reports. Each of the 12 pays once a month, so the app sends 12 receipts a month and the other 48 customers get none. That fits inside the Free plan's 20 receipts with room for a few one-off charges.
If the company grows to 150 enterprise accounts paying monthly, it needs about 150 receipts a month, which fits Pro at $9. Past 300 receipts a month, Business at $29 removes the ceiling. These numbers assume one receipt per paying customer per month and are an illustration, not a measured result.
What it does not do
Knowing the limits up front saves a bad surprise after install.
- Matching is by customer ID or email only. There is no matching on email domain, metadata, plan, price, amount or country, no rules engine and no deny list.
- One list, entries added one at a time. There is no CSV or bulk import, no export of the list, and entries cannot carry tags, groups, reason codes or expiry dates.
- No resend or override. A receipt cannot be resent from the app, and a decision cannot be overridden or forced for a single payment.
- No delivery tracking. The app does not track bounces or delivery status, and it sends no notifications or alerts.
- No integrations or API. It does not connect to accounting, CRM, e-commerce or automation tools.
- Stripe only. There is no dashboard outside Stripe, no setup wizard, no way to pause routing without uninstalling, and no support for Stripe Connect or several Stripe accounts.
- Stripe's receipt, as is. No custom templates, branding, PDFs or copies to extra recipients.
If your need is rule-based routing, bulk loading thousands of customers, or an accounting sync, this app is the wrong tool. If your need is "these named customers get a receipt and nobody else does," it fits. The comparison with Stripe's native receipts sets the two side by side.
Data and permissions
RouteReceipts reads customer, invoice and charge data from Stripe and writes only the charge's receipt email field. Data is encrypted in transit and stored in a database in the United States, and requests are verified with Stripe's signature checking. It does not store payment amounts or full invoice details. It makes no SOC 2, PCI or similar compliance claims and has no roles, seats or MFA of its own. The permissions and scopes FAQ is the place to check specifics.
Frequently asked questions
Is there a no-code way to send Stripe receipts to only some customers?
Yes. Install a Stripe App such as RouteReceipts, turn off Stripe's Successful payments emails, and add the customers who should get receipts to its allowlist.
Do I need developers or webhooks?
No. Setup is done in the Stripe Dashboard with no code and no webhook configuration, and it takes about 5 minutes.
Does the customer get a special receipt?
No. The customer gets Stripe's standard receipt email. The app only decides who gets it.
What happens when I hit the monthly limit?
Receipts stop until the next billing period or until you upgrade, and nothing falls back to Stripe's settings. There is no overage charge.
Can I try it before going live?
Yes. The app works in Stripe test mode, and there is a free plan for 20 receipts a month plus a free trial.
Where do I get help?
Email support@routereceipts.app. Replies typically come within one business day.