Payments Academy
Once a payment instruction 1 Once a payment instruction NOW 2 AML 3 Validation clearance 4 Review process 5 Hard block vs soft Once a payment instruction is accepted, it enters a stage of validation, screening, and fraud checking that is invisible to most customers but critical to the safety of the system. Step 1 of 5 Once a payment instruction 1 NOW Once a payment instruction 2 AML 3 Validation clearance 4 Review process 5 Hard block vs soft Once a payment instruction is accepted, it enters a stage of validation, screening, and fraud checking that is invisible to most customers but critical to the safety of the system. Step 1 of 5
AML checks 1 Once a payment instruction 2 AML NOW 3 Validation clearance 4 Review process 5 Hard block vs soft It checks the payment against anti money laundering rules Step 2 of 5 AML checks 1 Once a payment instruction 2 NOW AML 3 Validation clearance 4 Review process 5 Hard block vs soft It checks the payment against anti money laundering rules Step 2 of 5
Validation clearance 1 Once a payment instruction 2 AML 3 Validation clearance NOW 4 Review process 5 Hard block vs soft If a payment passes these checks, it moves forward immediately. Step 3 of 5 Validation clearance 1 Once a payment instruction 2 AML 3 NOW Validation clearance 4 Review process 5 Hard block vs soft If a payment passes these checks, it moves forward immediately. Step 3 of 5
Review process must be fast 1 Once a payment instruction 2 AML 3 Validation clearance 4 Review process NOW 5 Hard block vs soft The review process must be fast enough to meet cut off times but thorough enough to meet regulatory expectations, and that tension is a permanent feature of payment operations. Step 4 of 5 Review process must be fast 1 Once a payment instruction 2 AML 3 Validation clearance 4 NOW Review process 5 Hard block vs soft The review process must be fast enough to meet cut off times but thorough enough to meet regulatory expectations, and that tension is a permanent feature of payment operations. Step 4 of 5
Hard block vs soft hold 1 Once a payment instruction 2 AML 3 Validation clearance 4 Review process 5 Hard block vs soft NOW You must also understand the difference between a hard block, where the payment must be rejected, and a soft hold, where it can be released after review. Step 5 of 5 Hard block vs soft hold 1 Once a payment instruction 2 AML 3 Validation clearance 4 Review process 5 NOW Hard block vs soft You must also understand the difference between a hard block, where the payment must be rejected, and a soft hold, where it can be released after review. Step 5 of 5

Steps of this lesson, in order.

0:00 / 1:56 Step 1 of 5

Validation, screening and fraud checks

Payment Lifecycle End to End, Lesson 2 of 9, Narration 1:56, D03 Payment lifecycle

CreditorDebtorReject

What you will learn

Your objective. By the end of this lesson, you will be able to explain validation, screening and fraud checks. Once a payment instruction is accepted, it enters a stage of validation, screening, and fraud checking that is invisible to most customers but critical to the safety of the system.

Why it matters. For a business analyst, this stage requires careful requirements.

Chapter objective: Learner walks a payment from initiation through validation, screening, clearing, settlement, and reconciliation, and identifies the controls and failure points at each stage of the lifecycle. Learner applies this skill in realistic banking scenarios, with clear examples and correct terminology throughout.

Key learning points

  • Once a payment instruction
  • AML checks
  • Validation clearance
  • Review process must be fast
  • Hard block vs soft hold

Key terms

Creditor: The party that is owed money and receives a payment, such as a supplier, a seller or a service provider.

Debtor: The party that owes money and makes a payment, such as a buyer, an employer or a borrower. In ISO 20022 messages the debtor is the ordering customer, with name, address and account details.

Reject: A payment instruction that is refused before settlement because it fails validation, screening or account checks.

Animated payment lifecycle showing Validation, screening and fraud checks.

Insights and practice scenarios

Worked insights and practice scenarios for this lesson. Each one is a reusable PaymentForge case, so the same case may appear in more than one lesson.

Practise this lesson

Exercise

Decide what the screening or monitoring outcome should be for the scenario in this lesson.

Use the lists, rules and thresholds in this lesson.

  1. What to do. State whether the payment is stopped, held, frozen or released, and what must be recorded for audit.

Correct result. A true match against a sanctions list stops the payment. A false positive is cleared with a reason recorded. An alert that is escalated becomes a case, and a case that meets the threshold becomes a suspicious activity report.

Why. Screening is a control, not a suggestion. A missed true match is a regulatory breach, and an unexplained clearance is an audit finding.

Check your understanding

Practice question

A payment passes validation, screening and authorisation, then reaches the clearing stage, but the beneficiary credit is delayed by a day. A junior BA writes in the incident note that settlement finality and beneficiary credit are the same event. Why is that note wrong?

Takeaway and next step

What to remember

For a business analyst, this stage requires careful requirements.

Follow a payment through every stage, from instruction to beneficiary credit, and note where it can stop.

Open the Payment Lifecycle Simulator →

Builds on "Initiation, where every payment begins".

Transcript and full text

Show transcript

Once a payment instruction is accepted, it enters a stage of validation, screening, and fraud checking that is invisible to most customers but critical to the safety of the system. The debtor agent screens the debtor, the creditor, and any intermediary parties against sanctions lists, politically exposed person lists, and internal watchlists. It checks the payment against anti money laundering rules, such as whether the amount is unusual for that customer, whether the destination is high risk, and whether the purpose is consistent with the customer profile. It also applies fraud rules, such as whether the payment is to a new beneficiary, whether it was initiated from an unusual device or location, and whether it matches a known fraud pattern. If a payment passes these checks, it moves forward immediately. If it matches a sanctions name or triggers a fraud alert, it is held for manual review by a compliance or fraud analyst, who must decide whether to release it, request more information, or reject it. A false positive, where a legitimate payment is held because a name is similar to a sanctioned person, is a common cause of delay in cross border payments, especially where names are transliterated from another script. The review process must be fast enough to meet cut off times but thorough enough to meet regulatory expectations, and that tension is a permanent feature of payment operations. For a business analyst, this stage requires careful requirements. You must document which lists are screened, at what point in the flow, what happens on a match, who can release a held payment, and how the customer is informed. You must also understand the difference between a hard block, where the payment must be rejected, and a soft hold, where it can be released after review. A payment that is held without a clear reason or without a service level for review will generate complaints and may breach scheme timelines. Clear, testable requirements for screening and for hold and release are therefore essential. Worked example with real numbers: a EUR 75,000 payment from a corporate to a new supplier in a high-risk jurisdiction is submitted at 09:00. Sanctions screening matches the supplier name against a list entry with a fuzzy score of 92 percent, so the payment is held at 09:02 for manual review. The compliance analyst reviews the match at 10:30, finds it is a false positive, because the supplier is a different company with a similar name in a different country, and releases the payment at 10:45. The hold cost 1 hour and 45 minutes, and the customer communication is the difference between a complaint and an understanding. Failure and recovery: a validation failure, such as a bad IBAN, is rejected immediately with a pain.002 and reason BE01, and the customer corrects and resubmits. A fraud check that scores the payment as high risk, because the amount is 10 times the customer normal payment, holds the payment for the fraud team, and if the team does not clear it by the cut-off, the payment is carried to the next day. A screening system that is down, because the list update failed, must fail closed, holding payments, not fail open, sending them unscreened, because sending an unscreened payment is a regulatory breach. Each check has a different owner, a different SLA and a different customer message. For a business analyst, product owner or subject matter expert, the test is to specify, for every check, when it runs, pre-debit or post-debit, what list or model it uses, what score or match triggers a hold, who reviews the hold, what the SLA is, and what the customer is told. The ISO 20022 pacs.002 carries the status, with RJCT for a rejection and ACTC for an accepted payment that is still being processed, and the requirement must map each check outcome to a status and a customer message. A requirement that says the payment is screened, without naming the timing, the list, the threshold and the SLA, will be interpreted differently by compliance, operations and the vendor, and the product will fail its first screening test.

Once a payment instruction is accepted, it enters a stage of validation, screening, and fraud checking that is invisible to most customers but critical to the safety of the system. The debtor agent screens the debtor, the creditor, and any intermediary parties against sanctions lists, politically exposed person lists, and internal watchlists. It checks the payment against anti money laundering rules, such as whether the amount is unusual for that customer, whether the destination is high risk, and whether the purpose is consistent with the customer profile. It also applies fraud rules, such as whether the payment is to a new beneficiary, whether it was initiated from an unusual device or location, and whether it matches a known fraud pattern.

If a payment passes these checks, it moves forward immediately. If it matches a sanctions name or triggers a fraud alert, it is held for manual review by a compliance or fraud analyst, who must decide whether to release it, request more information, or reject it. A false positive, where a legitimate payment is held because a name is similar to a sanctioned person, is a common cause of delay in cross border payments, especially where names are transliterated from another script. The review process must be fast enough to meet cut off times but thorough enough to meet regulatory expectations, and that tension is a permanent feature of payment operations.

For a business analyst, this stage requires careful requirements. You must document which lists are screened, at what point in the flow, what happens on a match, who can release a held payment, and how the customer is informed. You must also understand the difference between a hard block, where the payment must be rejected, and a soft hold, where it can be released after review. A payment that is held without a clear reason or without a service level for review will generate complaints and may breach scheme timelines. Clear, testable requirements for screening and for hold and release are therefore essential.

Worked example with real numbers: a EUR 75,000 payment from a corporate to a new supplier in a high-risk jurisdiction is submitted at 09:00. Sanctions screening matches the supplier name against a list entry with a fuzzy score of 92 percent, so the payment is held at 09:02 for manual review. The compliance analyst reviews the match at 10:30, finds it is a false positive, because the supplier is a different company with a similar name in a different country, and releases the payment at 10:45. The hold cost 1 hour and 45 minutes, and the customer communication is the difference between a complaint and an understanding.

Failure and recovery: a validation failure, such as a bad IBAN, is rejected immediately with a pain.002 and reason BE01, and the customer corrects and resubmits. A fraud check that scores the payment as high risk, because the amount is 10 times the customer normal payment, holds the payment for the fraud team, and if the team does not clear it by the cut-off, the payment is carried to the next day. A screening system that is down, because the list update failed, must fail closed, holding payments, not fail open, sending them unscreened, because sending an unscreened payment is a regulatory breach. Each check has a different owner, a different SLA and a different customer message.

For a business analyst, product owner or subject matter expert, the test is to specify, for every check, when it runs, pre-debit or post-debit, what list or model it uses, what score or match triggers a hold, who reviews the hold, what the SLA is, and what the customer is told. The ISO 20022 pacs.002 carries the status, with RJCT for a rejection and ACTC for an accepted payment that is still being processed, and the requirement must map each check outcome to a status and a customer message. A requirement that says the payment is screened, without naming the timing, the list, the threshold and the SLA, will be interpreted differently by compliance, operations and the vendor, and the product will fail its first screening test.

Full lesson text (all scenes)

Completing a lesson updates your progress dashboard on the homepage.

Scene timestamps are estimated by allocating the narration text proportionally across the real audio length. The audio playback position is the source of truth: pause freezes the visual, seeking restores the correct scene, replay restarts the scene animation.