RouteReceipts Stripe App Permissions and Scopes FAQ

RouteReceipts Stripe App Permissions and Scopes FAQ

Security reviewers usually want the same few answers before approving a Stripe app: what it can read, what it can change, where the data lives, how long it stays, and what compliance evidence exists. This FAQ answers them for RouteReceipts, and says plainly where there is no claim to make. For the product itself, start with the complete user guide.

What does RouteReceipts do, in security terms?

RouteReceipts is a Stripe App that decides which customers get Stripe's standard receipt, and it does that from inside the Stripe Dashboard sidebar. It is installed from the Stripe App Marketplace and has no separate login, dashboard or webhook endpoint for you to configure.

When a payment succeeds, the app checks the customer against your allowlist. If the customer ID or email matches, it sets the charge's receipt email and Stripe sends its own receipt. If not, no receipt goes out. The app never sends email itself, and it has no sending address, templates or extra recipients.

What Stripe permissions and scopes does the app need?

The app reads customer, invoice and charge data from Stripe and writes only the charge's receipt email field.

Stripe grants app access per API object, using names such as customer_read or invoice_read, and each permission carries a purpose string that the installer sees. Stripe requires the person installing an app to accept the listed permissions before using it, per Stripe's permissions reference. The install screen is therefore the authoritative list of what RouteReceipts requests, and it is the thing to screenshot for your review file.

Data Access Why it is needed
Customer data Read Match a payment to an allowlist entry by customer ID or email
Invoice data Read Cover paid invoices, including subscription and manually sent ones
Charge data Read Identify the successful payment
Charge receipt email field Write The only change the app makes

One point for strict reviewers: Stripe permissions are granted per object, not per field. "Writes only the receipt email field" describes what the app does with its access, so treat it as a vendor statement to verify in the decision log rather than a limit Stripe enforces field by field.

Who can install it, and who controls access afterwards?

Installing RouteReceipts requires the Stripe Owner or Admin role, and the app has no roles, seats or MFA of its own.

Because it runs inside the Dashboard, access to it follows whatever you have set up in Stripe. There is no second user directory to provision or audit. Setup takes about 5 minutes with no code, and the app works in Stripe test mode, so a security team can install it against test data first. The installation walkthrough shows the steps.

There is no pause switch, so the only way to stop routing is to uninstall the app.

Where is the data stored, and how is it protected?

Data is encrypted in transit with TLS and stored in a PostgreSQL database on DigitalOcean in the United States.

Incoming requests are checked with Stripe's signature verification. RouteReceipts does not store payment amounts, full invoice details or other sensitive financial data. If your policy requires data residency outside the US, this is the point to raise with support before approving.

What does the app store, and for how long?

The app keeps your allowlist and a decision log, and it has no retention or redaction settings.

Each allowlist entry is a Stripe customer ID, an email address or both, plus an optional note. Each log entry records the Stripe event ID, the customer and the reason for a send or suppress decision, such as the monthly limit or no matching ID or email. The log is kept while the account is active. Two limits matter for a data-protection review:

  • The log cannot be exported or downloaded, and it does not record allowlist changes.
  • There is no setting to shorten retention or redact an entry.

This section does not cover what happens to the allowlist or log after removal. Ask support@routereceipts.app for a written answer if your review needs one.

How does this relate to GDPR and data retention for Stripe apps?

RouteReceipts makes no GDPR certification claim here, so a GDPR review should rest on the data described above and on Stripe's rules for app developers.

Stripe's Apps Agreement sets the baseline for every developer: Business Account Data may be used only to provide or improve the experience of the business that installed the app, it may not be sold, data must be transmitted and stored securely, and it must be deleted when retention is no longer necessary or the business user requests deletion. A reviewer can use those clauses as a checklist of questions for any Stripe app vendor, RouteReceipts included.

The data minimisation points in RouteReceipts' favour are factual and short: no payment amounts stored, no full invoice details, and a single write to one field. Customer emails do appear in the allowlist and the log, so treat both as personal data in your records of processing.

Does RouteReceipts have SOC 2 or other compliance certification?

No. RouteReceipts makes no SOC 2, PCI or MTD compliance claims, so it cannot supply a SOC 2 report.

Stripe is different. It issues SOC 1 Type II, SOC 2 Type II and SOC 3 reports, and account Owners and Administrators can download them from the Compliance & Documents section of the Dashboard, as Stripe's help page explains. Those reports cover Stripe's environment, not the apps installed on it.

For a vendor-risk file, that leaves RouteReceipts as a small third party with a narrow data footprint and no attestation of its own. The evidence it can offer is the install-screen permission list, the written data-handling facts on this page and the decision log. Decide whether that fits your risk tier before the pilot, not after.

What audit evidence does the decision log give me?

The decision log is a full, tamper-evident record of every send or suppress decision, searchable in the app by customer, email, event ID or date.

It lives on the app's settings page inside Stripe. A reviewer can look up a payment by its Stripe event ID and see the customer and the reason. The app also shows receipts used and left this period. What it does not give you is an export, a record of allowlist edits or delivery tracking, since it does not track bounces or delivery status.

Worked example: tracing one payment

A finance team keeps one enterprise customer, Northwind Ltd, on the allowlist so it receives receipts for expense reports. A reviewer asks for proof that a given Northwind payment was handled correctly.

  1. Find the payment's Stripe event ID in the Dashboard.
  2. Open the RouteReceipts settings page and search the decision log by that event ID, or by Northwind's email.
  3. Confirm the entry shows the customer and a send decision.
  4. Search a non-allowlisted customer's email the same way and confirm the reason reads as no matching ID or email.

A payment processed before a customer was added shows its own reason, and that customer gets no receipt for it. The allowlist guide explains how entries are added and removed.

What happens if RouteReceipts is unavailable or hits its limit?

If RouteReceipts is unavailable, receipts are delayed, and at the monthly limit receipts stop until the next period or an upgrade.

Delivery uses retries, queues, delayed sends and batched receipts, and a duplicate check blocks a second receipt for the same payment. At the limit a banner appears and receipts do not fall back to Stripe's own settings. No data is lost and there is no overage billing. Plans are Free at $0 for 20 receipts a month, Pro at $9 a month for 300 and Business at $29 a month for unlimited. Every plan has the full allowlist and decision log, so security features do not depend on the tier.

Which payments and features are out of scope?

The app covers successful payments only, so it does not handle refund receipts or credit notes.

It also has no API, no notifications, no accounting or CRM integrations, no Stripe Connect or multi-account support and no dashboard outside Stripe. If your process needs any of those, see how the app differs from Stripe's own settings in the native receipts comparison.

How do I get a security question answered?

Email support@routereceipts.app, and replies typically arrive within one business day.

There is no support portal, live chat, sales contact or onboarding session, so put the full question in the first message. Name the control you need evidence for, such as data location or retention, and say what format your review requires.