Payments Training Hub
Debtor agent PAYMENT OPERATIONS STARTED LIVE 01 Debtor agent - bank or payment service provider that holds ACTIVE 02 Creditor agent - bank that holds the creditor account QUEUED 03 Debtor and creditor banks - most payments, however, they are different QUEUED 04 Agent roles - business analyst QUEUED 05 Agent BICs - account numbers QUEUED The debtor agent is the bank or payment service provider that holds the debtor account and executes the payment instruction on behalf of the debtor. Step 1 of 5 Debtor agent STARTED Debtor agent bank or payment service provider that holds ACTIVE Creditor agent bank that holds the creditor account QUEUED Debtor and creditor banks most payments, however, they are different QUEUED Agent roles business analyst QUEUED Agent BICs account numbers QUEUED The debtor agent is the bank or payment service provider that holds the debtor account and executes the payment instruction on behalf of the debtor.
Creditor agent PAYMENT OPERATIONS IN PROGRESS LIVE 01 Debtor agent - bank or payment service provider that holds DONE 02 Creditor agent - bank that holds the creditor account ACTIVE 03 Debtor and creditor banks - most payments, however, they are different QUEUED 04 Agent roles - business analyst QUEUED 05 Agent BICs - account numbers QUEUED The creditor agent is the bank that holds the creditor account and receives the payment on behalf of the creditor. Step 2 of 5 Creditor agent IN PROGRESS Debtor agent bank or payment service provider that holds DONE Creditor agent bank that holds the creditor account ACTIVE Debtor and creditor banks most payments, however, they are different QUEUED Agent roles business analyst QUEUED Agent BICs account numbers QUEUED The creditor agent is the bank that holds the creditor account and receives the payment on behalf of the creditor.
Debtor and creditor banks PAYMENT OPERATIONS IN PROGRESS LIVE 01 Debtor agent - bank or payment service provider that holds DONE 02 Creditor agent - bank that holds the creditor account DONE 03 Debtor and creditor banks - most payments, however, they are different ACTIVE 04 Agent roles - business analyst QUEUED 05 Agent BICs - account numbers QUEUED In most payments, however, they are different banks, Step 3 of 5 Debtor and creditor banks IN PROGRESS Debtor agent bank or payment service provider that holds DONE Creditor agent bank that holds the creditor account DONE Debtor and creditor banks most payments, however, they are different ACTIVE Agent roles business analyst QUEUED Agent BICs account numbers QUEUED In most payments, however, they are different banks,
Agent roles PAYMENT OPERATIONS IN PROGRESS LIVE 01 Debtor agent - bank or payment service provider that holds DONE 02 Creditor agent - bank that holds the creditor account DONE 03 Debtor and creditor banks - most payments, however, they are different DONE 04 Agent roles - business analyst ACTIVE 05 Agent BICs - account numbers QUEUED For a business analyst, the agent roles are essential for tracing a payment and for assigning ownership of a failure. Step 4 of 5 Agent roles IN PROGRESS Debtor agent bank or payment service provider that holds DONE Creditor agent bank that holds the creditor account DONE Debtor and creditor banks most payments, however, they are different DONE Agent roles business analyst ACTIVE Agent BICs account numbers QUEUED For a business analyst, the agent roles are essential for tracing a payment and for assigning ownership of a failure.
Agent BICs PAYMENT OPERATIONS COMPLETE LIVE 01 Debtor agent - bank or payment service provider that holds DONE 02 Creditor agent - bank that holds the creditor account DONE 03 Debtor and creditor banks - most payments, however, they are different DONE 04 Agent roles - business analyst DONE 05 Agent BICs - account numbers ACTIVE The agent BICs, the account numbers, and the message references are the keys that let operations teams trace the payment across systems. Step 5 of 5 Agent BICs COMPLETE Debtor agent bank or payment service provider that holds DONE Creditor agent bank that holds the creditor account DONE Debtor and creditor banks most payments, however, they are different DONE Agent roles business analyst DONE Agent BICs account numbers ACTIVE The agent BICs, the account numbers, and the message references are the keys that let operations teams trace the payment across systems.

Key points of this lesson, in order.

0:00 / 1:47 Step 1 of 5

Debtor agent and creditor agent, the banks that act

The Payment Ecosystem, Lesson 2 of 7, Narration 1:47, D01 Foundations of money and payments

Correspondent bankingSanctions screeningSettlement

What you will learn

Your objective. By the end of this lesson, you will be able to explain debtor agent and creditor agent, the banks that act. The debtor agent is the bank or payment service provider that holds the debtor account and executes the payment instruction on behalf of the debtor.

Why it matters. For a business analyst, the agent roles are essential for tracing a payment and for assigning ownership of a failure.

Chapter objective: Learner maps the payment ecosystem, naming the roles of payer, payee, issuing bank, acquiring bank, clearing house, central bank, and network, and traces how value moves between them. Learner practises this skill on realistic banking cases, explaining the reasoning clearly and using correct terminology throughout the work.

Key learning points

  • Debtor agent
  • Creditor agent
  • Debtor and creditor banks
  • Agent roles
  • Agent BICs

Key terms

Correspondent banking: A service where one bank holds accounts for another bank so the second bank can make payments in currencies or countries where it has no branch.

Sanctions screening: Checking payment parties, countries and references against sanctions lists published by governments and international bodies.

Settlement: The final movement of funds between banks to discharge obligations created by cleared payments. Settlement is usually made in central bank money or through correspondent accounts.

Payment flow diagram showing Debtor agent and creditor agent, the banks that act.

Practise this lesson

Exercise

Handle the exception described in this lesson the way the lesson prescribes.

Use the exception type, the reason code and the recovery path in this lesson.

  1. What to do. State what happened, what the correct action is, what must not be done, and what the post-incident review should capture.

Correct result. The correct action is the one the lesson prescribes for this exception type, with the right reason code and the right message. The payment must not be resent without checking whether it already settled, because that creates a duplicate.

Why. An exception handled wrongly is worse than the exception itself. A duplicate payment is a loss, and an unlearned exception will happen again.

Check your understanding

Practice question

A payment instruction names a debtor, a debtor agent, an intermediary bank and a creditor agent. The debtor agent debits the customer and sends the payment onward. Which party actually holds the payer account and executes the instruction?

Takeaway and next step

What to remember

A payment rejected by the debtor agent never leaves the sending bank, while a payment rejected by the creditor agent may have already left the sender and must be returned.

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

Open the Payment Lifecycle Simulator →

Builds on "Debtor and creditor, the two ends of every payment".

Transcript and full text

Show transcript

The debtor agent is the bank or payment service provider that holds the debtor account and executes the payment instruction on behalf of the debtor. It validates the instruction, checks that funds are available, applies fraud and sanctions screening, debits the debtor account, and sends the payment onward through the clearing or correspondent banking chain. The creditor agent is the bank that holds the creditor account and receives the payment on behalf of the creditor. It validates the incoming instruction, checks that the account exists and can accept the payment, credits the creditor account, and notifies the creditor that funds have arrived. In a domestic payment where both parties use the same bank, the debtor agent and creditor agent are the same institution, and the payment is a simple internal book transfer. In most payments, however, they are different banks, and the payment must travel between them through a clearing system, a central bank settlement system, or a correspondent banking relationship. Each agent has its own cut off times, its own validation rules, and its own fees, and a payment can fail at either end. A payment rejected by the debtor agent never leaves the sending bank, while a payment rejected by the creditor agent may have already left the sender and must be returned. For a business analyst, the agent roles are essential for tracing a payment and for assigning ownership of a failure. If a customer says the money has left their account but has not arrived, you need to know whether the debtor agent has sent it, whether it is stuck in clearing, or whether the creditor agent has rejected it. The agent BICs, the account numbers, and the message references are the keys that let operations teams trace the payment across systems. Your requirements should always name the debtor agent and creditor agent explicitly, and should state what each agent must do on success, on rejection, and on return. Worked example with real numbers: a customer of Bank A in Paris pays EUR 25,000 to a supplier at Bank B in Berlin. Bank A is the debtor agent, because it acts for the debtor, and it debits the customer EUR 25,000 and sends a pacs.008. Bank B is the creditor agent, because it acts for the creditor, and it receives the pacs.008, credits the supplier EUR 25,000, and sends a pacs.002. The debtor agent and the creditor agent are banks, not customers, and each has duties: the debtor agent must validate, screen and debit, and the creditor agent must validate, screen and credit, and each must report its status. If Bank A sends the pacs.008 but Bank B never credits, the payment is stuck between the agents, and the investigation starts with the pacs.002, not with the customer. Failure and recovery: a debtor agent that debits the customer but never sends the pacs.008. A creditor agent that receives the pacs.008 but cannot credit, because the account is closed, returns the payment with a pacs.004, reason code AC04, and the debtor agent credits the customer. A debtor agent that sends to the wrong creditor agent, because the BIC was wrong, will have the pacs.008 rejected, and the recovery is to correct the BIC and resend. Each failure is an agent failure, and the message that proves it is the pacs.002 or the pacs.004, with the status and the reason code, so the operations team must be able to read both. For a business analyst, product owner or subject matter expert, the test is to name the debtor agent and the creditor agent for every payment, with their BICs, their duties and their reporting, and to state what each agent does when the other fails. The ISO 20022 pacs.008 carries the debtor agent and the creditor agent as separate parties, distinct from the debtor and the creditor, and the requirement must map the business agents to the message fields. A requirement that confuses the debtor with the debtor agent will write the wrong party into the message, and the payment will be rejected, or worse, sent to the wrong bank, and the error will be found by the beneficiary, not by the test team.

The debtor agent is the bank or payment service provider that holds the debtor account and executes the payment instruction on behalf of the debtor. It validates the instruction, checks that funds are available, applies fraud and sanctions screening, debits the debtor account, and sends the payment onward through the clearing or correspondent banking chain. The creditor agent is the bank that holds the creditor account and receives the payment on behalf of the creditor. It validates the incoming instruction, checks that the account exists and can accept the payment, credits the creditor account, and notifies the creditor that funds have arrived.

In a domestic payment where both parties use the same bank, the debtor agent and creditor agent are the same institution, and the payment is a simple internal book transfer. In most payments, however, they are different banks, and the payment must travel between them through a clearing system, a central bank settlement system, or a correspondent banking relationship. Each agent has its own cut off times, its own validation rules, and its own fees, and a payment can fail at either end. A payment rejected by the debtor agent never leaves the sending bank, while a payment rejected by the creditor agent may have already left the sender and must be returned.

For a business analyst, the agent roles are essential for tracing a payment and for assigning ownership of a failure. If a customer says the money has left their account but has not arrived, you need to know whether the debtor agent has sent it, whether it is stuck in clearing, or whether the creditor agent has rejected it. The agent BICs, the account numbers, and the message references are the keys that let operations teams trace the payment across systems. Your requirements should always name the debtor agent and creditor agent explicitly, and should state what each agent must do on success, on rejection, and on return.

Worked example with real numbers: a customer of Bank A in Paris pays EUR 25,000 to a supplier at Bank B in Berlin. Bank A is the debtor agent, because it acts for the debtor, and it debits the customer EUR 25,000 and sends a pacs.008. Bank B is the creditor agent, because it acts for the creditor, and it receives the pacs.008, credits the supplier EUR 25,000, and sends a pacs.002. The debtor agent and the creditor agent are banks, not customers, and each has duties: the debtor agent must validate, screen and debit, and the creditor agent must validate, screen and credit, and each must report its status. If Bank A sends the pacs.008 but Bank B never credits, the payment is stuck between the agents, and the investigation starts with the pacs.002, not with the customer.

Failure and recovery: a debtor agent that debits the customer but never sends the pacs.008. A creditor agent that receives the pacs.008 but cannot credit, because the account is closed, returns the payment with a pacs.004, reason code AC04, and the debtor agent credits the customer. A debtor agent that sends to the wrong creditor agent, because the BIC was wrong, will have the pacs.008 rejected, and the recovery is to correct the BIC and resend. Each failure is an agent failure, and the message that proves it is the pacs.002 or the pacs.004, with the status and the reason code, so the operations team must be able to read both.

For a business analyst, product owner or subject matter expert, the test is to name the debtor agent and the creditor agent for every payment, with their BICs, their duties and their reporting, and to state what each agent does when the other fails. The ISO 20022 pacs.008 carries the debtor agent and the creditor agent as separate parties, distinct from the debtor and the creditor, and the requirement must map the business agents to the message fields. A requirement that confuses the debtor with the debtor agent will write the wrong party into the message, and the payment will be rejected, or worse, sent to the wrong bank, and the error will be found by the beneficiary, not by the test team.

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.