Home/Features/Payment Portal

Payment Portal

One click to update.
Zero login friction.

A hosted page where customers update their card or pause their subscription — on your subdomain, with your branding. No password. No dev work.

Your domain

Runs on your subdomain — no Recurflux branding

1-click

Access from every dunning email — no login required

0

Lines of code needed to deploy the portal

Quick answer

A hosted payment portal is a branded page where subscribers update their card or pause their subscription without logging in. Recurflux runs the portal on your subdomain with your logo and colors, embedding a unique one-click link in every dunning email. No password, no dev work, no Recurflux branding visible to the customer.

Friction at the update step
is where recovery fails.

Without a portal

  • Dunning email asks customers to "log in and update"
  • Login friction kills half the conversions before they start
  • Customer forgets their password, gives up
  • Subscription lapses — dunning failed before the card could update

With the Recurflux portal

  • Every dunning email has a unique one-click link
  • Click → branded portal → card form, already on screen
  • No login, no password, no friction
  • Update completes in under 60 seconds from any device

What the customer
actually sees.

01

Dunning email with a unique link

Each recovery email includes a one-click portal link unique to that customer. No login, no password reset — just a link.

02

Branded portal page loads

The customer lands on your subdomain: billing.yourcompany.com. Your logo, your brand colors, your language. The page loads with their account context already populated.

03

Card update or pause option

Primary action: update payment method. From dunning step 3 onward, a secondary option appears — pause for 30 days instead of letting the subscription lapse.

04

Update confirmed

Card saved. Recurflux triggers the next retry immediately. If the retry succeeds, the dunning sequence stops and the account is marked recovered.

Your brand.
Our infrastructure.

01

Subdomain and branding

Set your preferred subdomain in settings and point a CNAME. Add your logo, brand color, and custom header text. The portal looks like your product.

02

Pause option visibility

Choose at which dunning step the pause option appears. Default is step 3. You can enable it from step 1 or disable it entirely per plan.

03

Portal visit log

See which customers visited the portal, when, and what action they took — updated card, chose to pause, or left without acting.

Hosted card update page — no code required. Connect and reduce card-update friction today.

See how this works →

Common questions.

Do customers know they are using Recurflux?

No. The portal runs on your subdomain (e.g., billing.yourcompany.com), displays your logo and brand colors, and shows no Recurflux branding. The experience is entirely yours.

How do customers get to the portal?

Every dunning email includes a unique, one-click portal link — no login, no password. The link is tied to their account. They click it and land directly on the update page.

Can customers pause instead of cancelling from the portal?

Yes. At dunning step 3, the portal surfaces a "pause for 30 days" option before the customer reaches a cancellation decision. Paused accounts resume at 40–60% vs. 10–15% after a full cancel.

How do I set up the portal subdomain?

In settings, you set your preferred subdomain and point a CNAME record at Recurflux. No code required. The portal goes live in under 5 minutes.

Is the portal mobile-friendly?

Yes. The portal is fully responsive. It renders correctly on any screen size — most customers update their card from a mobile device.

One click.
Card updated.

See pricing →

Live in under 5 minutes