Skip to main content
GullySystem
Financial services

Business solutions for Payment service providers

Explore software for work such as “UPI QR, soundbox and card machines for shops”. Review each business function below, including when it fits and what to check before implementation.

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.

Settlement runs

Build each payout batch from imported captures, fees, refunds and reserve holds, and show the net amount per merchant before release. The bank instruction itself stays in your banking process.

Reconciliation against partner files

Match capture files, payout batches and the sponsor bank’s statement lines, and list every break with a cause code and an owner.

Refunds and reserves

Raise a refund, a rolling reserve or a hold against a transaction or merchant, record the approver, and show the effect on the next payout.

Chargeback and dispute desk

Log each dispute by reason code and response date, attach evidence to it, and sort the queue by what expires first.

Merchant statements and support view

Give merchants a login for payout advices, refund status and monthly statements, and give support the identical screen so callers get an answer without a transfer.

Acquirer fee schedule

Each acquirer and card scheme charges its own fees on every transaction type. The schedule holds those rates with start dates. Finance compares them with merchant rates to see the margin.

Risk review log

Merchants showing sudden volume jumps or odd refund rates are placed on review. The log records the trigger, the analyst, the decision and the date. A payout hold is noted beside it.

Terminal and API key register

Merchants get API keys, terminal IDs and hosted payment page links. The register lists each one, its status and the date it was issued. Support staff revoke a lost key from here.

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.
  • Settlement batches. Build each payout batch from imported captures less fees, refunds and reserve holds, and show the net per merchant. A named approver releases it, and the bank instruction stays in your banking process.
  • Reserves and holds. Place a rolling reserve, a delayed payout or a hold on a merchant or a transaction. Record the reason, the approver and the release date, and see the effect on the next batch.
  • Partner and bank reconciliation. Match capture files, payout batches and sponsor bank statement lines. Every unmatched line carries a cause, an assigned owner and a live status, and stays on the list until someone closes it.
  • Refunds and adjustments. Raise a refund or a manual adjustment against a transaction or merchant, with approval by value. Fees returned or retained are shown on the merchant’s next advice.

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.

Payouts disagree with the sponsor bank

The payout file and the bank statement differ by a handful of lines, and tracing them takes a working day. The reason is seldom written down.

Representment deadlines slip

Visa and Mastercard disputes arrive with a response date, while the proof of delivery sits in somebody’s inbox. Reply late and the case is lost.

Merchants ring to ask about money

Support cannot see reserve balances, refunds in flight or the next payout date. Each caller is passed to an accountant.

Follow the work across teams.

This is a planning flow. Confirm the steps, owners and approval rules against your actual operation.

  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.

Roles and responsibility boundaries.

For onboarding analysts

Work the application queue, chase missing papers, record screening results and send each file to risk with the reasons attached.

For risk and compliance staff

Review tiers, approve or decline merchants, set reserves and read the audit log of every pricing and hold change.

For settlement accountants

Import captures, build and approve payout batches, reconcile against bank statements and clear breaks by cause.

For merchant support

Answer payout, refund and reserve queries from the merchant file, and route disputes and corrections to the right desk.

For merchants

Sign in to read payout advices, refund status, reserve balances and monthly statements.

Reports your managers need.

  • 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
  • Reserves held and due for release by merchant
  • Chargebacks by reason code, response date and outcome
  • Refund and adjustment volume by merchant and approver

Connections to scope

  • Payment gateway files and APIs
  • Acquirer and sponsor bank statements
  • Sanctions screening service
  • Email
  • SMS
  • Accounting export

Confirm data access, record ownership and the exchange method for each connection. Inclusion here does not mean every connection is available in a standard package.

Setup decisions and adoption risks.

Use these requirements to plan phases, data migration and user training. Agree the release sequence after reviewing your current systems.

Rate cards and fee rules

Merchant discount rates, flat fees and pass-through charges for each payment mode are keyed in exactly as the signed merchant agreements word them.

Onboarding checklist

Papers, screening steps and risk tiers follow your policy, as reviewed with your own compliance staff.

Partner file layouts

Capture, refund and fee files from each acquirer or gateway are read in the layout that partner sends.

Approval limits

Who may approve a batch, a refund or a reserve release, and above what value, is set with your finance lead.

Currency and tax settings

Settlement currencies, fee tax and statement formats are configured per country and reviewed during implementation.

Hosted by GullySystem

GullySystem hosts the system and holds access to production data under the terms in your agreement.

Limitations to settle before implementation

  • A business that only accepts card payments through a hosted checkout has no merchant base to manage and needs only its own accounts.
  • Banks that run deposits and loans will find Bank Management Software closer.

Modules to consider first.

These functions connect to the operating model above. Confirm each one against the work your business actually runs.

Choose the operation you want to improve.

Use these activities to explain your scope. Your business does not need every function in the directory.

  • UPI QR, soundbox and card machines for shops
  • Payment links for sellers who take orders on WhatsApp
  • Recurring collections and mandates
  • Payouts to vendors and sellers
  • Reconciliation and settlement reports
  • Embedded payments for platforms
  • Cross-border collections
  • Merchant onboarding and activation
Talk to us

Start with the problem your team can describe.

Bring a sample record and show where information is copied, missed or waiting for approval. Scope the first useful change from there.

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