Surfaces
What your subscribers see
Every subscriber-facing surface — migration email, checkout, billing portal, and help — renders in your brand, on your domain, with Recurr out of sight.
What carries over
- Same account
- Wallet checkout
- App access continues
- Billing support in your brand
The showcase
The subscriber view, in your brand
Migration email, checkout, billing, and help all run through Recurr surfaces, but render as your subscriber experience.
Sent from your domain and signed with your DNS. The migration ask arrives as another message from the app they already pay for, not as a notice from a vendor they have never heard of.
Example brand
Two example design systems on the same Recurr surfaces. Colour, type scale, corner radius, and voice all come from the brand you hand off.
Inventory
Four surfaces, one subscriber relationship
Branded migration and lifecycle email, timed to each subscriber and motion.
Checkout
Wallet-first web checkout on your rail, carrying offer and account context.
Billing portal
Plan changes, payment methods, invoices, and billing support.
Help center
Guidance for migration, billing, cancellation, and recovery moments.
Configuration
What you hand off, and what you keep
Four decisions set every surface. You make them once, during the migration build; Recurr renders and operates against them from there.
Domains and sender identity
Checkout, billing, and help each run on a sub-domain you own. Email sends from your sender domain, authenticated against your SPF and DKIM records.
Brand tokens and copy
Colour, type, logo, and corner radius come from your design system. Ongoing copy is self-serve — migration copy is workshopped with our team before the first wave.
Checkout and payment methods
Wallets, cards, and the local methods your base already uses, with currency and presentment following the market the subscriber is in.
Support and billing language
Cancellation, refund, and dunning language matches the tone your support team already writes in, so an escalation never arrives in a voice they have to explain.
The rail changes. The subscriber experience stays yours.
See it on your book
The audit maps the subscriber surfaces your migration needs, from first email through checkout, billing, and help.