Customer self-service portal: what to include for billing

A customer self-service portal for billing is a secure page where your customers can see and pay their invoices, download receipts and manage their own subscription without emailing you. The best portals cover the handful of tasks customers ask about most often, and enforce your business rules so self-service never means customers can do anything they like.

This guide covers what to include, what to leave out, how customers should sign in, and how to roll a portal out without confusing existing customers.

Why offer a billing portal at all?

Most billing questions are simple: "Can you resend my invoice?", "Did my payment go through?", "How do I update my card?", "Can I move to the smaller plan?". Each one takes a few minutes of someone's time and delays the customer. A portal turns those into things the customer can do at 10pm on a Sunday.

There are also less obvious benefits:

• Faster payment. A customer who can see an overdue invoice with a pay button tends to pay sooner than one who has to find the email.
• Fewer disputes. When customers can see every invoice and receipt, there's less "I never got that".
• Cleaner data. Customers updating their own billing contact and payment method means fewer bounced emails and failed payments.

For more on cutting down inbound questions, see how to reduce billing support queries.

What a customer self-service portal should include

Must-haves

Nice-to-haves

• Pause a subscription for a set period instead of cancelling, useful for seasonal businesses.
• Update payment method, where your gateway supports it.
• Apply a coupon during a plan change.
• Statement of account for a date range. Our customer statement of account guide covers what that should show.

What to leave out

A portal isn't the place for everything. Keep these with your team:

• Negotiated pricing, refunds and credit notes, which need judgement.
• Anything that changes a debit order mandate, which has its own authorisation process.
• Account ownership changes, which should be verified by a person.

Setting the rules: self-service within limits

Self-service works because you decide what customers are allowed to do. Before launching, answer these:

1. Which plans can customers switch between? You may not want customers on a legacy plan moving to another legacy plan.
2. When do plan changes take effect? Immediately with proration, or at the next renewal? Upgrades are often immediate; downgrades often wait for the renewal date.
3. Can customers pause, and for how long? One to three months is common. Decide whether you bill anything during a pause.
4. When does cancellation take effect? Most subscription businesses let access run to the end of the paid period.
5. Is there a minimum term? If customers signed a 12-month agreement, the portal should respect it.

Write these rules down in your terms and make sure the portal shows the customer what will happen before they confirm.

How customers should sign in

Billing portals hold invoices, addresses and payment history, so sign-in needs to be secure but low-friction. Customers visit rarely, so they forget passwords.

Common options:

• One-time email codes. The customer enters their email and receives a short code. Nothing to remember, and access is tied to the billing email you already have.
• Magic links. Similar, but the email contains a link rather than a code.
• Passwords. Familiar but they get forgotten, reused and phished, and create reset tickets of their own.

For most billing portals, one-time codes or links are the right balance. Make sure codes expire quickly and can only be used once.

Rolling out the portal

1. Link to it everywhere: invoice emails, receipts, payment reminders and your website's footer.
2. Tell existing customers in a short email: what they can do in the portal and how to sign in.
3. Update your support replies. When someone asks for an invoice copy, send it and mention the portal for next time.
4. Watch what customers try to do. If many people email asking to do something the portal doesn't allow, decide whether it should.

Privacy and POPIA

A billing portal processes personal information, so the usual POPIA principles apply: only show the customer their own data, keep access secure, and log who did what. Make sure your privacy notice covers the portal, and that staff access to the same data is limited by role.

How CentraPoint helps

CentraPoint includes a customer self-service portal. Customers sign in with a one-time email code, view and pay their invoices, download receipts, and change plan, pause or cancel their subscription within the rules you set. Payments made in the portal go through the gateways you've enabled, and invoices and receipts are the same branded PDFs you send by email. On your side, roles and permissions control which staff can see customer billing data. See how customers work in the docs.

Frequently asked questions

What is a customer self-service portal?

It's a secure area where customers manage their own account: viewing and paying invoices, downloading receipts and managing their subscription, without contacting your team.

Should customers be able to cancel in the portal?

Generally yes. Making cancellation easy builds trust and reduces chargebacks. You can still set when cancellation takes effect and offer a pause or cheaper plan first.

Do customers need a password for a billing portal?

Not necessarily. One-time email codes are common for billing portals because customers visit rarely and forget passwords.

Can customers change their plan without contacting us?

Yes, if you allow it. Set which plans customers can move between and whether changes take effect immediately or at the next renewal.