Payments Training Hub
Seven-stage payment journey 1 Seven-stage payment journey NOW 2 Stage hands a specific output 3 Case the instruction 4 Banks perform 5 Good analyst documents the initiation channel 6 Answer those and the map Every payment travels through seven stages, and this chapter maps the whole journey before it looks at any one stage in detail. Step 1 of 6 Seven-stage payment journey 1 NOW Seven-stage payment journey 2 Stage hands a specific output 3 Case the instruction 4 Banks perform 5 Good analyst documents the initiation channel 6 Answer those and the map Every payment travels through seven stages, and this chapter maps the whole journey before it looks at any one stage in detail. Step 1 of 6
Stage hands a specific output 1 Seven-stage payment journey 2 Stage hands a specific output NOW 3 Case the instruction 4 Banks perform 5 Good analyst documents the initiation channel 6 Answer those and the map Each stage hands a specific output to the next, and the handover is where payments most often break. Step 2 of 6 Stage hands a specific output 1 Seven-stage payment journey 2 NOW Stage hands a specific output 3 Case the instruction 4 Banks perform 5 Good analyst documents the initiation channel 6 Answer those and the map Each stage hands a specific output to the next, and the handover is where payments most often break. Step 2 of 6
Case the instruction must capture 1 Seven-stage payment journey 2 Stage hands a specific output 3 Case the instruction NOW 4 Banks perform 5 Good analyst documents the initiation channel 6 Answer those and the map In every case the instruction must capture the debtor, the creditor, the amount, the currency, the value date and the remittance information. Step 3 of 6 Case the instruction must capture 1 Seven-stage payment journey 2 Stage hands a specific output 3 NOW Case the instruction 4 Banks perform 5 Good analyst documents the initiation channel 6 Answer those and the map In every case the instruction must capture the debtor, the creditor, the amount, the currency, the value date and the remittance information. Step 3 of 6
Banks perform 1 Seven-stage payment journey 2 Stage hands a specific output 3 Case the instruction 4 Banks perform NOW 5 Good analyst documents the initiation channel 6 Answer those and the map Some banks perform these checks in real time while the customer is still online, so that errors can be corrected immediately, while others perform them in batch after the file is received. Step 4 of 6 Banks perform 1 Seven-stage payment journey 2 Stage hands a specific output 3 Case the instruction 4 NOW Banks perform 5 Good analyst documents the initiation channel 6 Answer those and the map Some banks perform these checks in real time while the customer is still online, so that errors can be corrected immediately, while others perform them in batch after the file is received. Step 4 of 6
Good analyst documents the initiation channel 1 Seven-stage payment journey 2 Stage hands a specific output 3 Case the instruction 4 Banks perform 5 Good analyst documents the initiation channel NOW 6 Answer those and the map A good analyst documents the initiation channel Step 5 of 6 Good analyst documents the initiation channel 1 Seven-stage payment journey 2 Stage hands a specific output 3 Case the instruction 4 Banks perform 5 NOW Good analyst documents the initiation channel 6 Answer those and the map A good analyst documents the initiation channel Step 5 of 6
Answer those and the map 1 Seven-stage payment journey 2 Stage hands a specific output 3 Case the instruction 4 Banks perform 5 Good analyst documents the initiation channel 6 Answer those and the map NOW Answer those, and the map in this lesson becomes a working checklist for the chapter. Step 6 of 6 Answer those and the map 1 Seven-stage payment journey 2 Stage hands a specific output 3 Case the instruction 4 Banks perform 5 Good analyst documents the initiation channel 6 NOW Answer those and the map Answer those, and the map in this lesson becomes a working checklist for the chapter. Step 6 of 6

Steps of this lesson, in order.

0:00 / 4:14 Step 1 of 6

Initiation, where every payment begins

Payment Lifecycle End to End, Lesson 1 of 9, Narration 4:14, D03 Payment lifecycle

Remittance informationReconciliationAuthorisation

What you will learn

Your objective. By the end of this lesson, you will be able to explain initiation, where every payment begins. Every payment travels through seven stages, and this chapter maps the whole journey before it looks at any one stage in detail.

Why it matters. A good analyst documents the initiation channel, the mandatory fields, the validation rules, and the error messages for each failure, so that customers and operations teams know exactly what to fix.

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

  • Seven-stage payment journey
  • Stage hands a specific output
  • Case the instruction must capture
  • Banks perform
  • Good analyst documents the initiation channel
  • Answer those and the map

Key terms

Remittance information: Information that explains what a payment is for, such as invoice numbers, contract references or salary month.

Reconciliation: The process of comparing records from two sources, such as a bank statement and an internal ledger, to confirm they agree.

Authorisation: Approval by the issuer for a card transaction to proceed, confirming the card is valid and funds or credit are available.

Animated payment lifecycle showing Initiation, where every payment begins.

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

Trace the payment in this lesson through its lifecycle stages.

Use the lifecycle stages in this lesson: acceptance, processing, clearing, settlement, beneficiary credit, ledger posting and reconciliation.

  1. What to do. Name each stage, state what happens, and say when the payment is truly final.

Correct result. Acceptance validates the instruction. Processing prepares it. Clearing sorts and nets it. Settlement moves the funds. Beneficiary credit puts the money in the creditor account. Ledger posting records it. Reconciliation proves it. Finality is only at settlement, not at acceptance or at status update.

Why. The lifecycle is the map of a payment. If you cannot say which stage a payment is in, you cannot answer where the money is.

Check your understanding

Practice question

What is the correct order of the main stages in an end to end payment lifecycle?

Takeaway and next step

What to remember

Answer those, and the map in this lesson becomes a working checklist for the chapter.

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

Open the Payment Lifecycle Simulator →

Builds on "How the players interact, a single payment story".

Transcript and full text

Show transcript

Every payment travels through seven stages, and this chapter maps the whole journey before it looks at any one stage in detail. The seven stages are initiation, validation, authorisation, clearing, settlement, reconciliation and exceptions. Initiation is where the payment instruction is created. Validation checks that the instruction is complete, correct and allowed. Authorisation confirms that the payer has the funds and the permission to pay. Clearing sorts and nets the instructions with other payments. Settlement moves the money between banks. Reconciliation matches what was sent, what was received and what was posted. Exceptions handle everything that fails or goes wrong along the way. Hold this map in mind, because every later lesson in this chapter is one stage of it. Each stage hands a specific output to the next, and the handover is where payments most often break. Initiation hands a payment instruction to validation: debtor, creditor, amount, currency, value date and remittance information. Validation hands a clean, accepted instruction to authorisation, and rejects the rest with a reason. Authorisation hands an approved instruction with a funds hold to clearing. Clearing hands a net settlement position to settlement. Settlement hands a confirmed movement of money to reconciliation. Reconciliation hands a matched record, or a break, to exceptions. Initiation itself is the first stage, and it is where the debtor creates the payment instruction. The instruction can come from a person using online or mobile banking, from a corporate treasurer uploading a bulk file, from an enterprise system sending a payment through an API, or from a merchant initiating a collection under a direct debit mandate. In every case the instruction must capture the debtor, the creditor, the amount, the currency, the value date and the remittance information. If any of those elements is missing or wrong, the payment will fail later, and the cost of fixing it increases at each subsequent stage, so initiation is the cheapest place to get it right. The debtor agent receives the initiation and performs a series of validations before it accepts the instruction. It checks that the debtor account exists and is active, that the instruction is authenticated, that the amount is within limits, that the value date is valid, and that the creditor details are complete. It also checks for duplicate instructions, because a corporate file submitted twice can cause duplicate payments. Some banks perform these checks in real time while the customer is still online, so that errors can be corrected immediately, while others perform them in batch after the file is received. What can go wrong at initiation is often simple but costly. A wrong account number, a transposed digit, a missing reference, or a value date in the past can all cause rejection. A corporate file with a wrong format, a missing header, or an incorrect total can cause the entire file to be rejected, even if most payments in it are correct. A payment initiated without proper authorisation, such as a single authoriser approving a payment that requires dual authorisation, can create a control breach that is discovered only at audit. A good analyst documents the initiation channel, the mandatory fields, the validation rules, and the error messages for each failure, so that customers and operations teams know exactly what to fix. For the analyst, initiation is also where the lifecycle is set up for the stages that follow. The instruction must carry the identifiers that clearing, settlement and reconciliation will need: a unique payment reference, the debtor and creditor account identifiers, and the remittance data that lets the creditor match the payment to an invoice. If the reference is truncated or lost at initiation, reconciliation will fail at the end, even though the money moved correctly. So the design questions for initiation are the same as the questions for the whole lifecycle: what is captured, what is checked, what is rejected and why, and what identifier follows the payment from this first stage to the last. Answer those, and the map in this lesson becomes a working checklist for the chapter.

Every payment travels through seven stages, and this chapter maps the whole journey before it looks at any one stage in detail. The seven stages are initiation, validation, authorisation, clearing, settlement, reconciliation and exceptions. Initiation is where the payment instruction is created. Validation checks that the instruction is complete, correct and allowed. Authorisation confirms that the payer has the funds and the permission to pay. Clearing sorts and nets the instructions with other payments. Settlement moves the money between banks. Reconciliation matches what was sent, what was received and what was posted. Exceptions handle everything that fails or goes wrong along the way. Hold this map in mind, because every later lesson in this chapter is one stage of it.

Each stage hands a specific output to the next, and the handover is where payments most often break. Initiation hands a payment instruction to validation: debtor, creditor, amount, currency, value date and remittance information. Validation hands a clean, accepted instruction to authorisation, and rejects the rest with a reason. Authorisation hands an approved instruction with a funds hold to clearing. Clearing hands a net settlement position to settlement. Settlement hands a confirmed movement of money to reconciliation. Reconciliation hands a matched record, or a break, to exceptions.

Initiation itself is the first stage, and it is where the debtor creates the payment instruction. The instruction can come from a person using online or mobile banking, from a corporate treasurer uploading a bulk file, from an enterprise system sending a payment through an API, or from a merchant initiating a collection under a direct debit mandate. In every case the instruction must capture the debtor, the creditor, the amount, the currency, the value date and the remittance information. If any of those elements is missing or wrong, the payment will fail later, and the cost of fixing it increases at each subsequent stage, so initiation is the cheapest place to get it right.

The debtor agent receives the initiation and performs a series of validations before it accepts the instruction. It checks that the debtor account exists and is active, that the instruction is authenticated, that the amount is within limits, that the value date is valid, and that the creditor details are complete. It also checks for duplicate instructions, because a corporate file submitted twice can cause duplicate payments. Some banks perform these checks in real time while the customer is still online, so that errors can be corrected immediately, while others perform them in batch after the file is received.

What can go wrong at initiation is often simple but costly. A wrong account number, a transposed digit, a missing reference, or a value date in the past can all cause rejection. A corporate file with a wrong format, a missing header, or an incorrect total can cause the entire file to be rejected, even if most payments in it are correct. A payment initiated without proper authorisation, such as a single authoriser approving a payment that requires dual authorisation, can create a control breach that is discovered only at audit. A good analyst documents the initiation channel, the mandatory fields, the validation rules, and the error messages for each failure, so that customers and operations teams know exactly what to fix.

For the analyst, initiation is also where the lifecycle is set up for the stages that follow. The instruction must carry the identifiers that clearing, settlement and reconciliation will need: a unique payment reference, the debtor and creditor account identifiers, and the remittance data that lets the creditor match the payment to an invoice. If the reference is truncated or lost at initiation, reconciliation will fail at the end, even though the money moved correctly. So the design questions for initiation are the same as the questions for the whole lifecycle: what is captured, what is checked, what is rejected and why, and what identifier follows the payment from this first stage to the last. Answer those, and the map in this lesson becomes a working checklist for the chapter.

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.