
RCSA (Risk and Control Self-Assessment) is how a business team checks its own risks and controls, before an audit or an incident finds them. It answers one question: “What can go wrong here, and are we controlling it well enough?”
RCSA is a regular health check where each team lists its risks, checks whether its controls really work, and fixes the gaps. This post walks through it in seven simple steps.
Why RCSA matters in payments
- Proactive: finds problems before they become losses or headlines.
- Owned by the business: the teams who run payments own their risks, not just compliance.
- Continuous: updated when products, systems or rules change, not once a year.
Payments carry big volumes, fast-moving money and close regulatory attention. RCSA is how the first line (the business teams that own the risk day to day) shows it understands its risks.
The RCSA steps
Read the seven boxes from left to right. Define the process. Find the risks. Judge the risk before controls. Find the key controls and test them. Measure the risk that is left. Plan actions. The three boxes below show who does what. The first line owns the risks. The second line sets the method and challenges. The third line, audit, checks independently.
| Step | Question to answer | Payments example |
|---|---|---|
| 1. Define the process | What do we do? | Payment initiation, validation, settlement (the moment money actually moves between banks), reporting |
| 2. Identify risks | What could go wrong? | Unauthorized payment, settlement failure, data breach |
| 3. Inherent risk | How bad is it without controls? | Impact × likelihood = Low, Medium or High |
| 4. Identify controls | What protects us? | Maker-checker, access roles, limits, reconciliation (checking that every record matches) |
| 5. Test controls | Do they work? | Design: is it built right? Operation: does it work every day? |
| 6. Residual risk | How much risk is left? | Within appetite, or escalate to senior management |
| 7. Action plans | What will we fix, by when, and who owns it? | Add a new alert, close an access gap, retest |
The three lines
| Line | Who | Role in RCSA |
|---|---|---|
| 1st line | Payments, IT, operations | Own the risks and run the controls |
| 2nd line | Risk and compliance | Set the method, challenge the results |
| 3rd line | Internal audit | Independently check that it all works |
Tips for tracking actions
- Keep the action tracker live and review it weekly.
- Give every action a named owner and a due date.
- Close an action only with evidence.
- Feed the tracker into risk dashboards, and highlight high residual risks (the risk left after controls) to senior management.
The common mistake: treating RCSA as a form to fill in. Its real value is moving risk ownership to the teams who run the process every day.
My take
A good RCSA doesn’t list more risks. It makes the right people own them, tests the controls honestly, and fixes the gaps before anyone else finds them.
Working on a payments project?
I help banks and fintechs deliver real-time payments, ISO 20022, and AI-driven AML and compliance change, from strategy to go-live.
Connect on LinkedInSee how I can help