vaayaa Inclusive Education
Finance risk assessment

Digital Payment Systems Risk Assessment: Transaction, Fraud and Reconciliation Controls

A worked example of how a small online business finds, scores and controls the risks in its digital payment flow, from transaction processing and reconciliation to fraud, access, cash and data exposure.

Updated November 2026 8 hazards assessed Review every 6 months Highest risk: Critical to Medium
See the Digital Payment Systems course

Executive summary

This assessment shows how a small online business can find, rate and control the risks that run through its digital payment flow, from checkout and authorization to settlement, refunds and reconciliation. Eight risks were chosen because they are plausible for a merchant that uses a third party provider. Fraud, cyber exposure and processing errors carry the highest scores before controls, because each can cost money quickly and damage trust. Each risk is scored before controls and again after existing and added controls. Most fall to Medium or Low once the proposed controls are in place, but fraud remains the most serious area and stays at Medium because the impact stays serious. The first actions are matching settlements to orders, separating payout and refund rights, enabling multi-factor sign in and tuning fraud screening. The business is a teaching example, so every score illustrates method, not a real organization.

Focus area
Digital payment systems and transaction processing
Setting
Payments operations of a small online business that accepts card and bank transfer payments through a third party provider
Method
Five by five likelihood and impact risk register

Scope

This assessment covers the payment flow of a small online business, from checkout and authorization through settlement, reconciliation, refunds, payouts and reporting. It considers risks to money, customer data, legal duties and trust. Jurisdiction, card scheme rules, transaction volumes and the specific provider are not specified, so they are treated as assumptions for teaching only.

Context

The business uses a hosted checkout page, a payment provider and a bank account that receives settlements. Orders are recorded in a shop system, and a spreadsheet is used to match settlements to orders. A small team of an operations lead, a finance assistant, a developer and an IT administrator runs the flow, and an external accountant prepares annual accounts. Each hazard is scored before controls to show its natural level, then again after existing controls and the additional controls proposed here.

Objectives, assets and stakeholders

The objective is to take payments accurately and securely, settle funds on time, keep customer and payment data protected, meet tax and reporting duties, and keep the trust of customers, the provider, the bank and the owners. The assets in scope are customer payment records and order data, settlement funds and the business bank account, the shop system and payment dashboard, refund and payout permissions, and the reputation of the business. Stakeholders include the operations and finance staff, the business owner, the payment provider and its partner bank, customers, suppliers, the external accountant and tax authorities. Every hazard has one owner role, and the operations lead keeps the register current and reviews it with each owner every quarter.

Risk matrix: before and after controls

Each cell shows hazard numbers placed by likelihood and impact. Compare the two grids to see how controls move each hazard.

Before controls

Inherent risk

Risk before controls: rows are likelihood from almost certain to rare, columns are impact from insignificant to catastrophic. Cells list hazard numbers.
1
Insignificant		 2
Minor		 3
Moderate		 4
Major		 5
Catastrophic
5 Almost certain
4 Likely Likelihood 4, impact 3, score 12, high: H01 Likelihood 4, impact 5, score 20, critical: H02
3 Possible Likelihood 3, impact 3, score 9, medium: H07 Likelihood 3, impact 4, score 12, high: H03 H05 Likelihood 3, impact 5, score 15, high: H04
2 Unlikely Likelihood 2, impact 4, score 8, medium: H08 Likelihood 2, impact 5, score 10, high: H06
1 Rare

After controls

Residual risk

Risk after controls: rows are likelihood from almost certain to rare, columns are impact from insignificant to catastrophic. Cells list hazard numbers.
1
Insignificant		 2
Minor		 3
Moderate		 4
Major		 5
Catastrophic
5 Almost certain
4 Likely
3 Possible
2 Unlikely Likelihood 2, impact 2, score 4, low: H07 Likelihood 2, impact 3, score 6, medium: H01 H03 H05 H06 Likelihood 2, impact 4, score 8, medium: H02 H04
1 Rare Likelihood 1, impact 3, score 3, low: H08
  • Low 1 to 4
  • Medium 5 to 9
  • High 10 to 16
  • Critical 17 to 25

Hazard register

A summary first, then the detail for each hazard.

Summary of hazards with scores before and after controls
No.HazardBeforeAfterOwner
H01 Transaction processing and reconciliation errors 12 High 6 Medium Operations lead
H02 Payment fraud and account takeover 20 Critical 8 Medium Head of operations
H03 Weak access control and segregation of duties 12 High 6 Medium Head of operations
H04 Cyber intrusion and exposure of customer and bank data 15 High 8 Medium IT administrator
H05 Settlement timing and cash liquidity shortfall 12 High 6 Medium Finance lead
H06 Provider failure and supplier dependence 10 High 6 Medium Supplier relationship owner
H07 Tax, reporting and payment regulation duties 9 Medium 4 Low Finance lead
H08 Conflicts of interest and staff conduct 8 Medium 3 Low Operations lead
H01

Transaction processing and reconciliation errors

Operational Before 12 After 6

Payments are captured twice, refunds are posted to the wrong order, or settlement amounts are not matched to orders, so the ledger and customer records disagree with the bank.

Who or what is affected: Finance assistant, customers and the external accountant

Causes

Manual matching in spreadsheets, timing gaps between capture and settlement and unclear refund rules.

Consequences

Overpaid or unpaid customers, misstated revenue, disputes and extra work at year end.

Existing controls

  • The provider sends a daily settlement report.
  • Orders are matched to the bank statement each month.

Control gaps

Daily reports are not checked at weekends, and small differences are written off without review.

Additional controls

  • Prevent: Use automated matching of settlement lines to orders before each month closes.
  • Detect: Run daily exception reports for duplicates, unmatched refunds and missing settlements.
Likelihood 4 x impact 3 before; 2 x 3 after Owner: Operations lead Target: Within 45 days Early warning: Unmatched settlement lines older than five working days.
H02

Payment fraud and account takeover

Financial Before 20 After 8

Stolen card details, fake customer accounts or hijacked staff logins are used to place orders, change payout details or request refunds, causing direct loss and chargebacks.

Who or what is affected: Customers, finance staff and the business owner

Causes

Reused passwords, weak screening rules and high value orders placed by new accounts.

Consequences

Direct loss, chargeback fees, account suspension by the provider and loss of customer trust.

Existing controls

  • The provider runs basic fraud screening on each card payment.
  • Refunds above a set value need manager approval.

Control gaps

Screening rules are set once and never tuned against recent chargebacks.

Additional controls

  • Prevent: Enable strong customer authentication where the provider supports it and limit high value orders from new accounts.
  • Detect: Review chargeback rates and refunds sent to new addresses each week.
  • Respond: Freeze payouts and refunds when a pattern of fraud is confirmed.
Likelihood 4 x impact 5 before; 2 x 4 after Owner: Head of operations Target: Within 30 days Early warning: Chargeback rate rising for three weeks in a row or refunds sent to a changed address.
H03

Weak access control and segregation of duties

Operational Before 12 After 6

One person can change payout bank details, issue refunds and reconcile the account, or former staff keep working logins, so errors and misuse are not caught.

Who or what is affected: Finance staff, owners and the payment provider relationship

Causes

Small team size, shared admin logins and rights that are added but never removed.

Consequences

Undetected theft or error, a failed review by the accountant and loss of provider trust.

Existing controls

  • Staff use individual logins to the payment dashboard.
  • Payout changes are logged in the provider portal.

Control gaps

Access is reviewed only when someone leaves, and shared admin accounts still exist.

Additional controls

  • Prevent: Separate the rights to create, approve and reconcile payments and remove any role that combines all three.
  • Detect: Review dashboard user lists and payout change logs each quarter.
Likelihood 3 x impact 4 before; 2 x 3 after Owner: Head of operations Target: Within 30 days Early warning: A user holding both refund and payout change rights, or a login used after the person left.
H04

Cyber intrusion and exposure of customer and bank data

Technology and data Before 15 After 8

Phishing, malware or an exposed admin page lets an attacker reach the shop system, export customer details or redirect checkout, and weak handling of payment data creates a breach.

Who or what is affected: Customers, staff and the business bank account

Causes

Phishing emails, reused passwords, outdated plugins and exports saved to personal devices.

Consequences

Stolen data, false payouts, customer notices, provider suspension and legal claims.

Existing controls

  • Card data is kept by the provider rather than in the shop system.
  • Admin pages sit behind a password and are backed up daily.

Control gaps

Plugins are not patched on a set cycle, and exported files sit in shared folders.

Additional controls

  • Prevent: Enable multi-factor sign in for every admin and staff account and remove shared logins.
  • Recover: Test restoring the shop system from backup and keep a written incident plan.
Likelihood 3 x impact 5 before; 2 x 4 after Owner: IT administrator Target: Within 30 days Early warning: Unexpected login from a new location or a large export of customer records.
H05

Settlement timing and cash liquidity shortfall

Financial Before 12 After 6

Payouts arrive later than expected, provider holds and reserves are applied, or refunds exceed the cash on hand, so the business cannot pay suppliers or staff when due.

Who or what is affected: Owners, suppliers and staff

Causes

Long settlement cycles, reserves imposed by the provider and seasonal peaks in refunds.

Consequences

Missed payments, late supplier fees, higher borrowing cost and damaged relationships.

Existing controls

  • A weekly cash forecast is prepared by the finance assistant.
  • The bank balance is checked each morning.

Control gaps

The forecast does not yet include provider reserves or the timing of chargebacks.

Additional controls

  • Prevent: Keep a rolling thirteen week cash forecast that includes provider holds and expected chargebacks.
  • Respond: Agree a standby overdraft and a contact order for any cash gap.
Likelihood 3 x impact 4 before; 2 x 3 after Owner: Finance lead Target: Within 45 days Early warning: Projected cash cover falling below the agreed minimum within six weeks.
H06

Provider failure and supplier dependence

Supplier Before 10 After 6

The payment provider suffers an outage, changes its terms, freezes the account or fails, so payments stop, funds are delayed and customers cannot complete orders.

Who or what is affected: Customers, operations staff and suppliers

Causes

Heavy reliance on one provider, dependence on one bank and changes to fee terms.

Consequences

Lost sales, unpaid orders, funds held and reputational harm.

Existing controls

  • A written contract sets service levels and notice periods.
  • A second payment method is listed on the checkout page.

Control gaps

The backup method has not been tested with live orders, and the contract is not reviewed on a set cycle.

Additional controls

  • Prevent: Review the provider contract each year for termination, data return and reserve terms.
  • Detect: Monitor provider status and error rates against the agreed service level.
  • Respond: Switch checkout to the backup provider using a documented runbook.
Likelihood 2 x impact 5 before; 2 x 3 after Owner: Supplier relationship owner Target: Within 60 days Early warning: Provider error rate above the agreed level for two consecutive days.
H07

Tax, reporting and payment regulation duties

Legal and compliance Before 9 After 4

Sales tax, VAT, customer receipts, payment data rules or filing deadlines are missed or misapplied, and the records needed to prove transactions are incomplete.

Who or what is affected: Owners, regulators and the external accountant

Causes

Rules that differ by country, changing fee and tax treatments and filings left until the last minute.

Consequences

Penalties, interest, adjusted returns and regulator questions.

Existing controls

  • The external accountant reviews the annual accounts.
  • Transaction exports are kept for the period the accountant requests.

Control gaps

Jurisdiction is assumed, and no one confirms current rules before each filing.

Additional controls

  • Prevent: Keep a compliance calendar with a named owner and a backup for each filing and receipt duty.
  • Detect: Ask a qualified reviewer to test a sample of transactions against the rules that apply.
Likelihood 3 x impact 3 before; 2 x 2 after Owner: Finance lead Target: Within 60 days Early warning: A filing due within ten days with no preparer named.
H08

Conflicts of interest and staff conduct

People Before 8 After 3

A staff member has a personal link to a supplier or customer, accepts a bribe or discount, or hides a failed transaction to protect a bonus, weakening trust in the numbers.

Who or what is affected: Customers, owners and colleagues

Causes

Close relationships with suppliers, pressure on targets and unclear rules on gifts.

Consequences

Loss of independence, disciplinary action, financial loss and damage to reputation.

Existing controls

  • A code of conduct is signed each year.
  • Staff declare outside interests when they join.

Control gaps

Declarations are collected but are not compared with the supplier list.

Additional controls

  • Prevent: Require a written declaration before any supplier is approved and keep a register of gifts and discounts.
  • Respond: Provide a confidential route to raise concerns and record how each one was handled.
Likelihood 2 x impact 4 before; 1 x 3 after Owner: Operations lead Target: Within 60 days Early warning: A declared interest linked to an approved supplier or an unexplained discount.

Rating method and evaluation

Each risk is rated on two five-point scales. Likelihood runs from Rare to Almost certain, and impact runs from Insignificant to Catastrophic. Multiplying the two gives a score from 1 to 25, which falls into one of four bands: Low from 1 to 4, Medium from 5 to 9, High from 10 to 16 and Critical from 17 to 25. The score is a guide for ordering work, not a measurement. Inherent risk is the score before any controls, and residual risk is the score after existing and additional controls. Impact is judged on money lost, customers affected, time to correct, legal exposure and harm to trust. A payment or data risk is never rated down only because it has not yet happened. Critical risks need senior attention and a dated plan, High risks need a named owner and a deadline, Medium risks need routine controls, and Low risks are accepted and watched. The staff who run the flow challenge the ratings, and each rating is reviewed when a warning indicator reaches its threshold or when the provider, rules or systems change.

Likelihood, impact and rating bands

Likelihood

  • 5 Almost certain: Expected to happen in most circumstances.
  • 4 Likely: Will probably happen in many circumstances.
  • 3 Possible: Could happen at some time.
  • 2 Unlikely: Not expected, but it could happen.
  • 1 Rare: Only in exceptional circumstances.

Impact

  • 1 Insignificant: No lasting effect. Handled within routine work.
  • 2 Minor: Small effect that is quickly corrected.
  • 3 Moderate: Noticeable effect that needs managed effort to correct.
  • 4 Major: Serious effect on people, delivery or reputation.
  • 5 Catastrophic: Severe or lasting effect that threatens the whole activity.

Bands (likelihood x impact)

  • Low (1 to 4): Accept and monitor.
  • Medium (5 to 9): Manage with routine controls.
  • High (10 to 16): Senior attention and a treatment plan.
  • Critical (17 to 25): Act first. Do not proceed until reduced.

Monitoring, escalation and review

Review this assessment every 6 months, and sooner when an indicator below reaches its threshold.

Early-warning indicators and escalation thresholds
Indicator to watchEscalate when
Settlement lines unmatched to orders for more than five working days.Escalate to the operations lead when any line is older than five days, and to the business owner after ten days.
Chargeback rate rising for three weeks in a row or refunds sent to a changed address.Escalate to the head of operations at once, and pause payouts to the changed address until it is confirmed.
A user holding both refund and payout change rights, or a login used after the person left.Escalate to the head of operations the same day, and remove one right within a week.
Projected cash cover below the agreed minimum within six weeks.Escalate to the finance lead when cover is forecast to fall below the minimum, and to the business owner if it stays low for a month.
Provider error rate above the agreed service level for two consecutive days.Escalate to the supplier relationship owner, and activate the backup payment method if the level is not restored within one day.

Contingency arrangements

If a serious event occurs, such as confirmed fraud, a data breach or a provider freeze, the operations lead pauses payouts and refunds for the affected flow and informs the business owner. The IT administrator isolates affected accounts, revokes shared logins and restores the shop system from the latest tested backup. The provider and partner bank are contacted through the finance lead, and customers receive plain notice of what happened and what to do. Cash is protected by the standby overdraft and by moving orders to the backup method. Affected records are preserved for the accountant and any regulator inquiry, and legal advice is sought as required in the relevant jurisdiction.

Prioritized action plan

  1. Match every settlement line to an order before month end, owner operations lead, within 30 days.
  2. Separate payout, refund and reconciliation rights and remove shared admin logins, owner head of operations, within 30 days.
  3. Enable multi-factor sign in for all admin and staff accounts, owner IT administrator, within 30 days.
  4. Tune fraud screening rules against recent chargebacks each week, owner head of operations, within 30 days.
  5. Add provider reserves and holds to the cash forecast, owner finance lead, within 45 days.

Conclusion

Reliable digital payments depend on a few steady habits: matching every settlement, separating payment rights, protecting admin access, watching for unusual refunds and keeping a tested backup. The highest scores sit with fraud, cyber exposure and processing errors, and each has actions that lower the residual score. Treat the register as a living record, review it on the stated cycle, and seek qualified advice for any real payments, tax, data protection or legal question.

Assumptions and limitations

Assumptions

  • The business relies on an external payment provider for card capture, so full card numbers are not stored on its own systems.
  • Staff use managed laptops with individual sign in, and the shop system is cloud hosted by a supplier.
  • Jurisdiction is not specified, so legal and tax duties are described in general terms only.

Limitations

  • The scores are examples for learning and do not describe any real payment provider, merchant or audit.
  • Payment, data protection, card and tax rules differ by country and change over time, so specialist review is needed.
  • This is educational content and is not financial, legal, payments or security advice.

Related frameworks to study

  • Internal control framework with control activities and monitoring
  • Three lines model of risk ownership
  • Hierarchy of controls
  • General payment security guidance for handling card and bank data

Finance Risk Assessment

China, India, United States, Indonesia, Pakistan, Nigeria, Brazil, Bangladesh, Russia, Japan, Mexico, Philippines, Vietnam, Egypt, Turkey, Germany, United Kingdom, France, Italy, Canada, South Korea, Australia, Spain.

For Learning Reference Only: This assessment demonstrates how risk assessment principles are applied in a practical setting, providing a useful reference for learning and understanding. Actual assessments may be adapted to suit specific site conditions and circumstances.

Keep learning

Study the subject behind this assessment.

Digital Payment Systems course Read the best practices for this course

More Finance risk assessments

Hourly Active: 39,499 Learners