Skip to main content
GullySystem
Financial services

Client Portal for Payment service providers

Give customers controlled access to account documents and requests.

Finance & Accounting

Does this function belong in your operation?

Use when customers repeatedly request copies, statements or account updates.

Customers need their own financial records or updates.

Merchants log in to see their card and bank transfer transactions, payout batches, statements and open disputes. Evidence for a chargeback is uploaded here. Payout dates show before the money lands.

Bring the records the workflow depends on.

  • Customer contacts
  • Available documents
  • Access rules

Outputs to check

  • Customer account view
  • Document-access record
  • Customer request and response history

Follow the client portal workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Authorise the contact

    Verify the person and the account they may access.

  2. 2. Prepare account data

    Choose approved documents and reconcile balances with the source.

  3. 3. Publish the view

    Expose only the permitted records and their data date.

  4. 4. Handle requests

    Route customer questions to the responsible account owner.

  5. 5. Maintain access

    Review departed contacts, document changes and resolved queries.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

The client’s accounts assistant

Downloads the bill and the statement when it suits them, even after your office has shut.

Your accounts desk

Stops attaching PDFs all morning, and sees which clients have opened their bills.

Account manager

Reads the requests raised, and answers before the client escalates to the owner.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Contact leaves the customer

Remove that person's access while retaining the business account.

Disputed invoice

Record the query without changing the issued invoice or outstanding balance automatically.

Outdated statement

Display the data date and reconcile the source before presenting it as current.

Can this work independently?

The portal needs approved customer-account data and login access. Financial documents come from invoicing or accounting, either through imports or agreed connections. Online payment and support-ticket creation are separate handoffs; customer access does not grant editing rights over the ledger.

Systems and records it connects with

  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Receipts management: Recorded customer payments and invoice allocations.
  • Ticket management: Numbered requests, ownership and resolution history.
  • Payment gateways and bank transfers: Payment references and reconciled settlement or bank evidence.

Configure, test and introduce the workflow.

  • We list the documents and actions you want to expose. You decide what stays internal. A written view of the portal pages comes back.
  • Customer records are matched to login holders. You supply contact names, and we return a trial import to check. Logo, colours and domain are applied. You get a private link to try the portal as a client would.
  • A small group goes in early. Their notes on wording and missing documents come back to you as a short list. Invitations go out in groups. Your accounts desk learns the reply screens, and phone requests for copies fall away as clients get used to the page.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Customers cannot view other accounts.
  • Balances reconcile with the ledger.
  • Requests retain submission dates.
Payment service providers

How the business operates.

A payment business keeps two kinds of record. One is the transaction stream from your gateway or acquiring partner. The other is the context around it: who the merchant is, which merchant discount rate applies, what was paid out, what sits in reserve and what is disputed.

Merchant onboarding file

Keep application, KYC papers, sanctions screening result, MCC and approval on a single file per merchant, with a checklist, a named reviewer and the status of each document.

Rate cards and pricing

Record the discount rate, per-transaction fee and scheme pass-through by payment mode and merchant, with effective dates, so each payout uses the rate in force on the day of capture.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Merchant application and KYC file. Open one file per merchant with the application, ownership papers, director identity documents for know-your-customer checks, bank proof and website review. A checklist shows which paper is missing and who is chasing it.
  • Screening and risk review log. Record each sanctions and adverse-media check with its result, reviewer and date. Assign the merchant category code and a risk tier, and keep the reasoning for an approval or a decline.
  • Contracts and rate cards. Store the signed merchant agreement beside its pricing: discount rate, per-transaction fee, scheme pass-through and payout terms by payment mode, each with an effective date.
  • Capture and transaction file import. Load the capture, refund and fee files from your gateway or acquirer in the layouts they send. Totals per merchant and per day are shown before any payout is built.

Operational bottlenecks to check

Onboarding stalls on one paper

One identity-check file is parked for a director’s address proof, but the team cannot count other files waiting for the same document. Merchants sign with a rival gateway.

Rate cards live in a spreadsheet

Someone keys the negotiated rate by hand. The payout then runs at the standard rate. Finance posts a reversal a fortnight later.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Application

    A merchant applies through a form or a sales contact. The business type, expected volume, payment modes and website are captured, and an analyst is assigned.

  2. 2. KYC and screening

    Papers are collected against a checklist. Ownership is mapped, names are screened, a category code and risk tier are set, and approval is recorded with its reasons.

  3. 3. Pricing and go-live

    The signed agreement and rate card are attached with effective dates. Settlement account details are verified before the merchant is switched on in your gateway.

  4. 4. Capture and payout

    Capture and fee files are imported each cycle. A batch is built net of fees, refunds and reserves, reviewed by an approver and passed to the bank process.

  5. 5. Reconciliation

    Batches are matched with the sponsor bank statement and partner files. Breaks get a cause and an owner, and clear before the cycle is closed.

  6. 6. Disputes and support

    Chargebacks, refunds and merchant queries are worked from one desk. Evidence is attached, deadlines watched, and outcomes posted to the next payout advice.

Industry reports to connect with

  • Applications by stage, reviewer and missing document
  • Merchants by risk tier, category code and payment mode
  • Payout batches by cycle, with fees, refunds and reserves deducted
  • Reconciliation breaks by cause, age and owner

Questions before implementation.

When should payment service providers consider client portal?

Use when customers repeatedly request copies, statements or account updates. Customers need their own financial records or updates.

What should we bring to the requirements discussion?

Bring anonymised examples of Customer contacts; Available documents; Access rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Give customers controlled access to account documents and requests. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Payments, signing and identity connections need separate scope confirmation.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Customers cannot view other accounts. Use this check when reviewing the first working version.

Talk to us

Discuss client portal for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements