# GoCardless payer lookup for support and finance teams

> Search any Direct Debit payer, see their mandates, payments and refunds in one timeline, and retry, refund or cancel without sharing dashboard logins.

- Workflow type: app
- Services: GoCardless, Gmail
- Categories: Customer Support, Finance
- Published: 2026-08-22

## What it does

- Search your Direct Debit payers by name or email and open anyone's full history in one place, so nobody has to be given a GoCardless dashboard login.
- One timeline per payer shows their mandates and current status, active subscriptions, every payment with what happened to it, refunds already issued, and the bank account on file with only the last four digits visible.
- Act straight from a row: retry a failed payment, take a one-off payment against an existing mandate, issue a refund, cancel a subscription, or reinstate a cancelled mandate. Every action asks you to confirm first because it moves real money.
- Press Explain this account and a background assistant reads the payer's whole payment and mandate history, writes a plain English summary of what happened and why into the app, and prepares a customer-ready reply as a Gmail draft for a human to review and send.

## What you'll need

- A GoCardless account, with permission to view customers and collect payments if you want the action buttons enabled
- A Google account for the drafted customer replies
- The names or email addresses your payers are stored under, which is all anyone needs to look someone up

## Prompt

Build me an internal app that my support and finance team opens whenever a payer emails us about their Direct Debit, so nobody has to be handed a GoCardless dashboard login just to answer a question.

The main screen is a search box over our GoCardless customers. I type a name or an email address and get back matching payers with their name, email and when they were created, using List Customers to fetch and filter, and Get Customer to load a single payer once I pick one. Searching should feel like the only thing on the page, because looking someone up is what people came here to do.

Opening a payer shows one page with a single timeline of everything about them. Their mandates and each mandate's current status from List Mandates. Their active subscriptions with amount and frequency from List Subscriptions. Every payment with its status, amount, charge date and, where it failed, the failure reason, from List Payments. Refunds already issued from List Refunds. And the bank account on file from List Customer Bank Accounts, showing only the last four digits alongside the bank name, never the full account number. All of these are filtered to that customer, and the payments and refunds read as one chronological story rather than five separate tables stacked on the page.

From a row I can act. Retry a failed payment with Retry Payment. Take a one-off payment against an existing mandate with Create Payment, where I enter the amount and a description. Issue a refund against a payment with Create Refund, full or partial. Cancel a subscription with Cancel Subscription. Reinstate a cancelled mandate with Reinstate Mandate. Every one of these sits behind a confirmation step that restates the payer, the amount in real currency and exactly what is about to happen, because these move real money. After an action succeeds, refresh that payer's timeline so the new state is visible immediately, and if GoCardless rejects the action, show the reason it gave in plain language rather than a raw error.

Add an Explain this account button on the payer page that kicks off a background agent. The agent reads the payer's full payment and mandate history through List Payments, List Mandates, List Subscriptions and List Refunds, works out the story of what actually happened and why, for example a mandate that was cancelled by the bank causing the last three payments to fail, and writes a plain English summary back into the app so it appears on that payer's page for anyone who opens it next. The agent also prepares a customer-ready reply and saves it as a Gmail draft with Create a Draft, addressed to the payer, explaining their situation and any next step. It never sends the email. A human reads the draft, edits it and sends it. While the agent is running, show that it is working on the payer page, and keep previous summaries so the team can see what was explained before.

Three things to bake in throughout. GoCardless amounts are integers in the smallest currency unit, so pence and cents, and must be formatted with the correct currency before anyone sees them. A failed payment can only be resubmitted three times, so each failed row should show how many retries remain and disable the retry button once they are used up. And bank debit takes several working days to clear, so pending is normal rather than broken, and the app should label pending payments in a way that stops people chasing a customer who has done nothing wrong.

## How to customize

- Decide which actions each team gets, for example letting support retry failed payments while only finance can issue refunds
- Set the tone, opening line and signature used for the drafted customer reply
- Change what the timeline leads with, such as showing only failed and pending payments first, or extending how far back it reaches

## FAQ

### Does everyone on the team need their own GoCardless login?

No, and that is the point. The app connects to GoCardless once, and your support and finance colleagues work inside the app instead of signing in to the payments dashboard.

### Why do payments sit as pending for days?

Bank debit is not a card payment. It takes several working days to clear, so a pending payment is normally healthy rather than broken. The app labels pending payments that way so nobody chases a customer too early.

### How many times can a failed payment be retried?

Three. GoCardless caps resubmissions at three attempts per payment, so every failed row shows how many retries are left, and the retry button switches off once they are used up.

### Will the app email customers on its own?

No. The Explain this account button prepares a reply and saves it as a draft in Gmail. A person still reads it, edits anything they want, and sends it.

### Can the team see full bank account details?

No. The bank account on file is shown as the last four digits with the bank name, which is enough to confirm you are talking about the right account without exposing the full number.

### What stops someone refunding the wrong payment by accident?

Each action opens a confirmation step that restates the payer, the amount in real currency and what is about to happen, so a refund or cancellation never fires from a single click.

Use this prompt in General Input: https://www.generalinput.com/prompts/gocardless-payer-lookup-for-support-and-finance-teams