Know the answer. Explain the payment.
Genuine questions a payments interviewer can reasonably ask, from foundations to senior-level exceptions. Every answer starts directly, adds operational context, and links back to the teaching or official evidence that supports it.
Shubham Mathure
Senior Business Analyst SME in payments technology, with expertise in SWIFT, ISO 20022, payment operations, and financial messaging. Creator of Payments Signal—making complex payment infrastructure clear and practical for everyone.
Interview-worthy coverage, without filler.
The bank is explicitly curated by domain. New site content does not become a question automatically: it must test a concrete concept, decision, lifecycle, control, or troubleshooting skill and pass the editorial quality checks.
Build your interview set.
13 matches
Showing 1–13 · Page 1 of 1
ISO 20022 & CBPR+
ISO 20022 & CBPR+
TRICKYpain, pacs, and camt checkpointA bank receives this fictional fragment. Which family does it belong to, and what leg of the payment is it?
MODEL ANSWERDIRECT ANSWER
Correct answer: It is from a pain.001 — a customer's instruction to its own bank, on the initiation leg, carrying the instructed amount..
WHY IT MATTERS
The vocabulary betrays the leg: InstdAmt is the customer's instructed amount, and the debtor-account-plus-transactions structure is how pain.001 groups a customer's instructions. Once the debtor agent accepts this, it will create a pacs.008 for the interbank leg — same payment, different message, different amount semantics. All parties and IBANs are fictional.
EASYMT–MX translation checkpointA payment crosses four banks, and along the way it is translated between MT and ISO 20022 formats. What lets all four banks (and their customers' banks) track it as one payment?
MODEL ANSWERDIRECT ANSWER
Correct answer: The UETR — a unique end-to-end transaction reference that stays with the payment across every hop and both message formats..
WHY IT MATTERS
The UETR is generated once and carried unchanged by every bank in the chain, in both MT (block 3) and ISO 20022 messages, surviving translation between them. It is what turns 'where is my payment?' from a chain of bilateral queries into a single lookup — which is why investigations teams treat it as the first thing to capture.
EASYpain, pacs, and camt checkpointA payment settled yesterday. Today two different things could happen: the beneficiary bank sends money back because the account is closed, or the ordering bank asks for the money back because it was sent twice. Which messages carry these two events?
MODEL ANSWERDIRECT ANSWER
Correct answer: Return of funds: pacs.004.
WHY IT MATTERS
Request to get funds back: camt.056.. The direction of initiative decides the message. When the beneficiary side sends funds back on its own initiative, that is a return: pacs.004, referencing the original payment. When the ordering side wants funds back, it can only ask — camt.056 — and the answer may be a pacs.004 (funds returned) or a camt.029 (resolution, including refusal). A recall request is never a guarantee of recovery.
EASYISO 20022 model checkpointCompared with free-text fields in older formats, what is the practical benefit of ISO 20022's structured elements — for example, a postal address broken into named components?
MODEL ANSWERDIRECT ANSWER
Correct answer: Machines can process the data reliably: validation, straight-through processing, and screening can target specific elements instead of parsing prose..
WHY IT MATTERS
When a screening engine knows that an element is a town name rather than part of a person's name, it can match more precisely and raise fewer false alerts; when a validation engine knows which element holds the IBAN, it can check it before the payment leaves. That element-level certainty is the working argument for ISO 20022 in operations and compliance teams alike.
TRICKYMT–MX translation checkpointDiagnose what is happening and choose the right response for Bank Alfa.
MODEL ANSWERDIRECT ANSWER
Correct answer: Respond to the request through the proper channel with accurate, complete information about the customer and the payment's purpose, and keep the customer informed that the payment is under review..
WHY IT MATTERS
A compliance hold with a request for information is a normal, defined part of cross-border payments: the intermediary needs facts it does not have before it can release, reject, or escalate. The only sound move is to answer promptly and truthfully through official channels. Attempting to route around a screening hold is the textbook evasion pattern that compliance teams are trained to detect.
EASYISO 20022 model checkpointIn a message name like pacs.008, what do the two parts tell you?
MODEL ANSWERDIRECT ANSWER
Correct answer: 'pacs' is the business area (payments clearing and settlement) and '008' identifies the specific message within it — here the customer credit transfer..
WHY IT MATTERS
ISO 20022 names follow a pattern: a four-letter business area (pain, pacs, camt, and others), a message number, and — in the full form like pacs.008.001.xx — variant and version identifiers. Reading 'pacs' immediately tells you this is an interbank clearing and settlement message before you have opened a single element.
EASYISO 20022 migration checkpointWhat does 'coexistence' mean in the ISO 20022 migration?
MODEL ANSWERDIRECT ANSWER
Correct answer: A period in which MT and ISO 20022 messages both travel the network, so a payment can be sent in one format and received in the other while institutions migrate..
WHY IT MATTERS
Coexistence is the heart of a phased migration: for a defined window both MT and ISO 20022 are supported, so no one has to cut over on the same instant. For cross-border payments on SWIFT that window ran from March 2023 to November 2025.
EASYISO 20022What does “ISO 20022” mean in payments?
MODEL ANSWERDIRECT ANSWER
ISO 20022 is the open standard for financial messaging.
WHY IT MATTERS
Its core idea is a shared business model and data dictionary from which concrete message definitions are generated, so the same concept — a debtor, an amount, a settlement date — is expressed the same way across messages. Payments use families like pain (customer initiation), pacs (interbank clearing and settlement), and camt (cash management and investigations), usually in XML syntax. Compared with MT, ISO 20022 carries richer, more structured data, which helps automation and screening. Communities of users publish usage guidelines, such as CBPR+ and HVPS+, that restrict the standard for a specific rail.
EASYMT–MX translation checkpointWhat is CBPR+?
MODEL ANSWERDIRECT ANSWER
Correct answer: The usage guidelines that define how ISO 20022 messages are used for cross-border payments and reporting in correspondent banking over the SWIFT network..
WHY IT MATTERS
Base ISO 20022 messages are deliberately flexible; usage guidelines like CBPR+ narrow that flexibility so that every bank fills the same elements the same way in cross-border correspondent payments. Without such guidelines, 'we both speak ISO 20022' would still leave plenty of room for incompatibility.
EASYpain, pacs, and camt checkpointWhat is the role of a pacs.002 in an interbank flow?
MODEL ANSWERDIRECT ANSWER
Correct answer: It is a payment status report: it tells the sender of an interbank payment whether the instruction was accepted or rejected, with reason codes.. pacs.002 closes the loop on an interbank instruction: accepted, rejected, or — in some schemes — intermediate statuses, each with machine-readable reason codes. In instant payment schemes it is the message that makes or breaks the customer experience, because the originator bank needs it before it can tell the customer the payment succeeded.
EASYpain, pacs, and camt checkpointWhich description correctly maps the three message families?
MODEL ANSWERDIRECT ANSWER
Correct answer: pain: customer-to-bank payment initiation; pacs: bank-to-bank clearing and settlement; camt: cash management, reporting, and investigation messages..
WHY IT MATTERS
The families map onto the legs of a payment. The customer instructs their bank with pain messages, banks move the payment between themselves with pacs messages, and camt messages report on accounts and carry investigations. When you see an unfamiliar message, the prefix alone tells you which conversation it belongs to.
EASYMT–MX translation checkpointWhich MT-to-MX correspondence is right for the two core payment messages?
MODEL ANSWERDIRECT ANSWER
Correct answer: MT103 corresponds to pacs.008 (customer credit transfer); MT202 and MT202 COV correspond to pacs.009 (financial institution credit transfer, with a COV usage)..
WHY IT MATTERS
The mapping follows function: customer credit transfer to customer credit transfer (MT103 to pacs.008), bank-to-bank transfer to bank-to-bank transfer (MT202 to pacs.009), with the cover variant preserved (MT202 COV to pacs.009 COV usage). Knowing the pairs lets you follow one payment across a mixed MT/MX chain without losing the thread.
EASYISO 20022 model checkpointWhich statement best describes what ISO 20022 is?
MODEL ANSWERDIRECT ANSWER
Correct answer: A standard built on a shared business model and data dictionary, from which concrete messages (commonly expressed in XML) are derived..
WHY IT MATTERS
The lasting value of ISO 20022 is the shared dictionary: when two systems both say 'debtor' or 'interbank settlement amount', they mean precisely the same defined concept. The XML messages are generated from that model, which is why the same business content can appear consistently across payment initiation, clearing, and reporting messages.