✦ The layer after Stripe Checkout
Stripe takes the payment. After Rail records the order, hands the buyer their files from your domain, sends the email from your address, and reports the sale back to Meta and GA4 with the match data hosted checkout throws away.
Deliver files from your own domain, with links that expire, cap, and revoke
Email every buyer from your address through your Postmark or SMTP
Report the purchase to Meta, GA4, and Google Ads with the click IDs intact
Handle refunds, retries, and renewals without a spreadsheet
One chain, four links
Every purchase moves through the same chain. Each link is written before the next begins, and each is idempotent, so a webhook that arrives five times still produces exactly one order.
01 · Delivery
Buyers download from downloads.yourbrand.com and hear from hello@yourbrand.com. Links expire, cap, and revoke. The token lives only in the email; the database keeps a hash.
See the delivery timeline02 · Attribution
Hosted checkout can’t carry a pixel. The buyer pays on Stripe’s page and the event fires with no click ID, no cookie, no landing page. After Rail captures those before the redirect and carries them through to the conversion report.
See return on ad spend per pageBuilt to be predictable
Yours, not ours
The operator console
Open any order and read its life in one column: every step, every destination, every attempt. Retries are there too, because a failure you can see is one you can fix.
Orders / ord_3f9a…c2
$149.00 · alex@studio.co · paid 3 min ago · /lp/spring-launch · utm_campaign=spring_launch
Paid, recorded, entitled, emailed, downloaded, with each ad destination’s attempts underneath. Resend, revoke, or refund from the same screen.
Revenue by brand, product, and page. The storefront funnel from view to checkout to paid, and traffic sources by UTM.
Each brand has its own Stripe, sending domain, storage, and pixels. Workspaces are isolated at the row level, so one can never see another’s data.
Getting started
Three connections and a Buy button. Your site stays your site; After Rail only takes over once the buyer clicks.
Paste your Stripe keys, then copy your workspace’s webhook URL into your Stripe dashboard. Every event is logged before it is processed.
Upload straight to your R2 or S3 bucket, map a Stripe price, set the download cap and expiry. New version? Cut a new release; old buyers keep theirs.
Your Postmark or SMTP for the delivery email. Your Meta pixel, GA4 property, and Google Ads account for the conversions. Then drop the Buy button on your landing page.
For people who sell digital products
Connect Stripe, add a product, and give every buyer a secure path from payment to access. Then watch the conversions finally land where you spent the money.
Start for free After Rail is not a payment processor and never touches buyer funds. Bring your Stripe account and your existing site.