Self-service account portal with GoCardless for customer payment records
A private portal where customers check GoCardless payments and mandates, with changes routed to staff for approval.
Updated 2026-05-31
Self-service account portal with GoCardless
A self-service account portal built on GoCardless gives paying customers a private place to see their own payment position. A customer signs in, sees the payments taken against their mandate, and reads a plain summary of anything that failed or is still pending. The portal does not replace GoCardless as the record of payments. It reads from the platform so the figures match what the business collects. Gyms, property managers, cleaning companies, tutors and managed IT providers often bill regular amounts this way, and each group tends to field the same questions about dates and amounts. A portal lets those answers come from one source. Where a change is needed, such as a new bank account, the portal can route the request to a staff member or to a workflow with an approval step. Payers' bank details should stay within the platform and never be pasted into a general-purpose AI prompt.
How it works
Connect the portal to the GoCardless REST API on the server, so access credentials are never exposed in the browser.
Map each signed-in customer to their GoCardless customer record, so the portal shows only the mandates and payments that belong to that person.
Subscribe to webhooks for payment and mandate events, so the figures on screen update when a payment changes state.
Route change requests, such as a new bank account, to staff or to a workflow with an approval step before anything changes in GoCardless.
Use accounting software such as Xero to confirm that the amounts shown in the portal agree with the invoices recorded there.
Test sign-in, password reset and each payment status with staff accounts before any client is invited.
Frequently asked questions
- How does a self-service account portal connect to GoCardless?
- The portal connects through the GoCardless REST API, which exposes customer, mandate and payment records. A developer sets up access credentials on the server and tests in the sandbox environment before live data is involved. Webhooks notify an endpoint the business controls when a payment changes state, so the portal can refresh. Accounting software such as Xero can be connected so the amounts shown match invoices.
- Do I need a developer to connect a self-service account portal to GoCardless?
- Yes, in most cases. Connecting to the REST API, handling webhooks and keeping credentials secure is development work, so a developer is the right person to own it. A business with an existing web team may be able to extend its own site. The payoff is a portal where clients see their own details, matching the figures your team knows from the GoCardless dashboard.
- How does a self-service account portal stay in step with GoCardless?
- The portal stays in step through webhooks, which send event notifications when payments or mandates change state, rather than by polling the API on every page load. Each event can update the stored record the portal reads from. A scheduled check can compare the portal's records with GoCardless to catch any missed event. Staff should see when the last sync ran, so a customer is never shown figures that are out of date.
- How do I know a self-service account portal works with GoCardless?
- Check it against the sandbox first. Create test customers and mandates, make test payments, and confirm the portal shows the same status, amount and date as the GoCardless dashboard. Then repeat the checks for a failed payment, a cancelled mandate and a delayed webhook. Only after those match should a small group of real clients be invited to sign in.
- Can I start with part of a self-service account portal on GoCardless?
- Yes. A first release can show invoices, payment history and contact details, with changes routed to staff, and leave payment setup and renewals for later. This keeps the GoCardless connection read-only at the start, which reduces risk while the team learns how the portal is used. Later stages can add changes made directly by clients once approval steps and access rules have been tested.
Related
read these nextUp a level
More with GoCardless
- Customer churn report with GoCardless payment and booking data
- Invoice chasing automation for GoCardless Direct Debit payments
- Payments reconciliation for GoCardless
- Renewal reminder automation with GoCardless
- AI adoption for GoCardless businesses: training and rollout
- AI strategy for GoCardless: finding where AI pays off in collections
- Custom development for GoCardless Direct Debit businesses
- Product idea for GoCardless businesses: discovery, scope and build
- Workflow automation for GoCardless Direct Debit businesses
