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.
114 matches
Showing 51–100 · Page 2 of 3
Messages & MT ↔ MX migration
ISO 20022 & CBPR+
MEDIUMpacs.008In pacs.008, what does GrpHdr/CreDtTm (Creation date and time) mean, and what can go wrong?
MODEL ANSWERDIRECT ANSWER
MANDATORY in Base ISO 20022 message definition.
WHY IT MATTERS
When this message was created — a timestamp for the message, distinct from the settlement date of the payment.
TRICKYpacs.008In pacs.008, what does GrpHdr/MsgId (Message identification) mean, and what can go wrong?
MODEL ANSWERDIRECT ANSWER
MANDATORY in Base ISO 20022 message definition.
WHY IT MATTERS
A unique reference for this message, assigned by the instructing agent. It changes at every hop; end-to-end references live at transaction level. Point-to-point duplicate detection keys on MsgId between adjacent agents. It is not the reference to quote to the customer. Pitfall: Confusing MsgId with EndToEndId in reconciliation logic breaks matching as soon as a payment crosses more than one hop.
MEDIUMpacs.009In pacs.009, what does GrpHdr/CreDtTm (Creation date and time) mean, and what can go wrong?
MODEL ANSWERDIRECT ANSWER
MANDATORY in Base ISO 20022 message definition.
WHY IT MATTERS
When this message was created.
MEDIUMpacs.009In pacs.009, what does GrpHdr/MsgId (Message identification) mean, and what can go wrong?
MODEL ANSWERDIRECT ANSWER
MANDATORY in Base ISO 20022 message definition.
WHY IT MATTERS
A unique reference for this message, assigned by the instructing agent for this hop.
MEDIUMpain.001In pain.001, what does GrpHdr/CreDtTm (Creation date and time) mean, and what can go wrong?
MODEL ANSWERDIRECT ANSWER
MANDATORY in Base ISO 20022 message definition.
WHY IT MATTERS
When the message was created. This is a timestamp for the instruction, separate from when the customer wants the payment executed. Useful in investigations to reconstruct the order of events when several versions of a file were exchanged.
TRICKYpain.001In pain.001, what does GrpHdr/MsgId (Message identification) mean, and what can go wrong?
MODEL ANSWERDIRECT ANSWER
MANDATORY in Base ISO 20022 message definition.
WHY IT MATTERS
A unique reference for this message, assigned by the initiating party. It identifies the file or message itself, not the individual payments inside it. Banks use MsgId as a first line of duplicate-file detection, so uniqueness matters across the sender's history, not just within a day. Pitfall: Reusing a MsgId — for example after a resend of a corrected file — is a common cause of duplicate rejections or, worse, silently ignored files.
TRICKYpain.002In pain.002, what does GrpHdr/CreDtTm (Creation date and time) mean, and what can go wrong?
MODEL ANSWERDIRECT ANSWER
MANDATORY in Base ISO 20022 message definition.
WHY IT MATTERS
When this status report was created. Ordering matters when several reports about the same file arrive. Pitfall: Processing status reports out of order can overwrite a final status with an earlier interim one.
MEDIUMpain.002In pain.002, what does GrpHdr/MsgId (Message identification) mean, and what can go wrong?
MODEL ANSWERDIRECT ANSWER
MANDATORY in Base ISO 20022 message definition.
WHY IT MATTERS
A unique reference for this status report itself, assigned by the bank sending it. Distinct from the original message's identification — a single pain.001 can generate several pain.002 messages over its life as statuses evolve.
EASYcamt.029What is camt.029, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Answers an investigation case — most commonly a cancellation request sent as camt.056.
WHY IT MATTERS
It tells the requester what happened: the cancellation was accepted, it was rejected with a coded reason, or it is still pending. It closes (or updates) the case; if funds actually come back, they travel separately in a pacs.004. Like all camt investigation messages, it carries information, never money. Sent by the case assignee — the agent that was asked to cancel or investigate — back to the case creator or assigner that sent the request. the full camt.029 message definition covers more than cancellation answers, including modification and claim-related resolutions, compensation, and corrective transaction references.
EASYcamt.052What is camt.052, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Reports balances and account entries during the day.
WHY IT MATTERS
It gives an account owner an interim cash position before the definitive statement is produced; delivery frequency, included balances, and whether empty reports are sent are service-agreement choices. Sent by an account servicing institution to the account owner or an authorised recipient, often several times during the business day. camt.052 can carry richer balance, entry, transaction, charge, party, and pagination detail; the applicable service and usage guideline decide which elements are populated.
EASYcamt.053What is camt.053, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Provides the booked statement for an account, normally covering a completed reporting period with opening and closing balances plus the entries booked during that period.
WHY IT MATTERS
Sent by an account servicing institution to the account owner or an authorised recipient, commonly at end of day. The full statement supports balances, entries, transaction details, parties, charges, rates, remittance, pagination, and supplementary data; requirements depend on the service guideline.
EASYcamt.054What is camt.054, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Notifies an account owner about one or more debit or credit entries, often promptly or with transaction-level detail for a bulk booking.
WHY IT MATTERS
It reports entries already booked or advised; it does not move value. Sent by an account servicing institution to the account owner or authorised recipient when the agreed notification trigger occurs. The message supports multiple notifications, entries, and detailed underlying transactions; the trigger, status usage, and level of detail are contracted service choices.
EASYcamt.055What is camt.055, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
It lets an initiating party ask its bank or forwarding agent to cancel a previously sent customer payment initiation such as pain.001.
WHY IT MATTERS
It is the customer-side request; if the payment has gone interbank, the bank may need to raise a separate camt.056 downstream. Sent by the initiating party or debtor to the party handling the original customer payment instruction, directly or through a forwarding agent. camt.055 can target original groups, payment-information blocks, or transactions and carries richer case and reason information; the current message definition and service rulebook control usage.
EASYcamt.056What is camt.056, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Asks the receiving agent to cancel a previously sent interbank payment — or, if it already settled, to send the funds back.
WHY IT MATTERS
It opens a case: the sender identifies the original payment, gives a coded reason, and waits for an answer. It is a request, not an instruction. No money moves, nothing is guaranteed, and the answer can be no. Sent by the case assigner — typically the debtor agent that wants its payment back — to the case assignee, the next agent in the original payment's chain, and relayed hop by hop or through a clearing mechanism until it reaches the agent holding the funds. the full camt.056 message definition contains more elements, including case blocks, control data, and the full original transaction reference.
EASYcamt.110What is camt.110, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Opens a structured payment investigation through Swift Case Management, replacing recurring MT195/199-style queries with a message that carries case, original-payment, request, and routing data in labelled elements.
WHY IT MATTERS
Sent through the Case Orchestrator by the institution opening or forwarding an investigation to the institution expected to answer. The ISO message and Swift usage guideline contain more orchestration, party, status, and underlying-payment structure; validate exact paths against the version in force.
EASYcamt.111What is camt.111, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Answers a camt.110 investigation through Swift Case Management with structured status, evidence, and links to the original payment and case.
WHY IT MATTERS
Sent through the Case Orchestrator by the institution answering or forwarding the investigation response. The full message supports richer response, status, routing, and underlying-payment information; consult the current ISO definition and Swift usage guideline.
EASYpacs.002What is pacs.002, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Reports the status of a previously received interbank payment message — typically a pacs.008 or pacs.009 — back toward its sender.
WHY IT MATTERS
It can accept, reject, or report intermediate statuses, with coded reasons for negative outcomes. It is the interbank sibling of pain.002: it reports on payments, it never moves money. Sent by the agent (or clearing and settlement mechanism) that received an interbank payment message, back to the agent that sent it. the full pacs.002 message definition contains many more elements, including instructing/instructed agent identification, original transaction references, and charges. Requirement flags summarise the single context named on each field;
EASYpacs.004What is pacs.004, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Returns the funds of a payment that already settled — because the credit could not be applied (closed account, deceased beneficiary), because a recall was accepted, or because the receiving agent must send the money back for another coded reason.
WHY IT MATTERS
Unlike a status report, a pacs.004 moves money: it settles in the opposite direction and stays linked to the original payment through echoed references. Sent by the agent that holds the funds — typically the creditor agent of the original payment — back along the chain toward the original debtor agent. the full pacs.004 message definition contains many more elements, including the return chain of parties, compensation, and original transaction reference data. Requirement flags summarise the single context named on each field;
EASYpacs.007What is pacs.007, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Reverses an interbank payment when the initiating financial institution is correcting its own erroneous payment event.
WHY IT MATTERS
It is distinct from a receiver-initiated pacs.004 return and from a camt.056 request that may be refused. Sent by the financial institution initiating the reversal to the next agent in the original interbank chain, directly or through the relevant payment infrastructure. The base ISO message supports group and transaction reversals plus richer party, agent, compensation, and original-transaction data; whether pacs.007 is permitted for a credit-transfer scenario is scheme-specific.
EASYpacs.008What is pacs.008, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Carries a customer credit transfer between financial institutions — the interbank leg of a payment where the debtor, the creditor, or both are non-bank customers.
WHY IT MATTERS
It is the ISO 20022 counterpart of the MT103: it moves the payment obligation from the debtor agent toward the creditor agent, carrying the customer parties, amounts, charging arrangement, and remittance information with it. Sent by the debtor agent (or an instructing agent acting for it) to the next agent in the chain — directly, through intermediary agents, or through a clearing and settlement mechanism — until it reaches the creditor agent, which credits the creditor.
EASYpacs.009What is pacs.009, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Moves funds between financial institutions where both the debtor and the creditor are themselves banks — the ISO 20022 counterpart of the MT202.
WHY IT MATTERS
In its core usage it settles bank-to-bank obligations such as treasury and liquidity movements. In its COV usage it is the cover leg of the cover method: it moves the funds for an underlying customer payment (a pacs.008 sent directly to the creditor agent) and carries a copy of that customer payment's details. Sent by or on behalf of the debtor financial institution to the next agent in the chain — its correspondent, an intermediary, or a settlement system — toward the creditor financial institution.
EASYpain.001What is pain.001, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Carries a customer's instruction to its payment service provider (PSP) to make one or more credit transfers.
WHY IT MATTERS
It is the customer-to-bank message that starts the payment: nothing has moved between banks yet, and no interbank settlement happens until the debtor agent turns the instruction into an interbank message such as pacs.008. Sent by the initiating party — the account owner or a party instructing on its behalf, such as a shared service centre — to the debtor agent (the PSP holding the account to be debited), sometimes via a forwarding agent. the full pain.001 message definition contains many more elements, rules, and code lists. Requirement flags summarise the single context named on each field;
EASYpain.002What is pain.002, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Reports the status of a previously sent initiation message — usually a pain.001 — back to the party that sent it.
WHY IT MATTERS
It can accept or reject a whole file, a payment block, or individual transactions, and carries coded reasons explaining negative outcomes. It reports; it never moves money. Sent by the debtor agent (or a forwarding agent) back to the initiating party that submitted the original pain.001. the full pain.002 message definition contains many more elements, including original transaction references and charges information. Requirement flags summarise the single context named on each field; check the official ISO 20022 message definition and the reporting profile your bank actually implements.
SWIFT & MT
EASYMT101What is MT101, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Requests the receiving bank to debit an account it services and move the funds onward.
WHY IT MATTERS
It is a payment initiation message, not an interbank settlement message: corporates use it to instruct their banks from a central treasury, and banks relay it to each other on a customer's behalf. One MT101 can carry many transactions against the same debit account and execution date. Sent by a corporate over SWIFT for Corporates, or by a bank acting as a relay, to the financial institution that services the account to be debited and will execute the transfers. the official SWIFT Standards MT documentation is the complete specification.
EASYMT192What is MT192, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Requests the receiver to consider cancelling a previously sent Category 1 message, most commonly an MT103 customer payment.
WHY IT MATTERS
It is a request, not a reversal, and should carry structured references and reason codes rather than rely on free text. Sent by a financial institution to the institution that received or forwarded the original Category 1 message. The official Standards MT handbook and current market-practice guidance define the complete format, allowed codes, and cancellation handling.
EASYMT195What is MT195, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Requests information about, or an amendment to, a previous Category 1 message.
WHY IT MATTERS
It is the structured legacy query message; recurring payment investigations are migrating toward camt.110 through Swift Case Management. Sent by a financial institution to the counterparty expected to answer a query about a previous Category 1 message. The official Standards MT handbook and market-practice guidance define complete query codes, repetition rules, and response conventions.
EASYMT196What is MT196, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Answers an MT195 query, MT192 cancellation request, or another Category 1 case without its own response type.
WHY IT MATTERS
The same message shell can therefore carry a cancellation outcome or an investigation answer, distinguished by structured content. Sent by the institution answering the earlier Category 1 request to the institution that opened the case. MT196 answer codes and narrative structure depend on the request being answered; consult the current Standards MT handbook and market-practice guidance.
EASYMT199What is MT199, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Carries Category 1 information for which no more specific message type is defined.
WHY IT MATTERS
It has been widely used for payment queries and explanations, but structured cancellation and investigation messages are preferred because free text is difficult to automate. Sent between financial institutions, or in supported corporate arrangements, when information about a Category 1 payment cannot be expressed in a more specific MT. MT199 intentionally has little structure; the official handbook and applicable market-practice guidance govern references, authentication, and any coded narrative conventions.
EASYMT202 COVWhat is MT202 COV, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
A variant of the MT202 used only to provide cover — the interbank settlement leg — for an underlying customer credit transfer that travels separately, classically an MT103 sent directly to the beneficiary's bank.
WHY IT MATTERS
A mandatory second sequence repeats the underlying ordering and beneficiary customers so every bank moving the money can screen the real parties. Sent by the ordering customer's bank into the correspondent chain that actually moves the funds, in parallel with the underlying customer message sent directly to the beneficiary's bank. the official SWIFT Standards MT documentation is the complete specification.
EASYMT202What is MT202, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Moves funds between financial institutions where both principal parties are banks: funding and repositioning of nostro accounts, settlement of interbank obligations such as foreign-exchange or money-market deals, and other bank-to-bank transfers with no underlying customer payment attached. Sent by the ordering institution, directly or through correspondents, to the institution that will apply the funds for the beneficiary institution.
EASYMT900What is MT900, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Advises an account owner that a specific debit has been posted to its account.
WHY IT MATTERS
It is an entry confirmation, not a payment instruction and not proof that the ultimate beneficiary received funds. Sent by the account servicing institution to the account owner or an authorised recipient after the relevant debit is booked. The complete Standards MT specification defines all field options, network rules, and party combinations.
EASYMT910What is MT910, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Confirms to an account owner that its account with the sender has been credited.
WHY IT MATTERS
It is an advice for a single credit — typically an incoming cover payment or another expected receipt — sent close to the event, not a periodic statement. Sent by the account-servicing institution (for example, a nostro correspondent) to the account owner or to a party the owner has authorised to receive it. the official SWIFT Standards MT documentation is the complete specification.
EASYMT940What is MT940, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Carries account statement information for one account over one period: an opening balance, individual booked entries, and a closing balance.
WHY IT MATTERS
Banks send it for the nostro accounts they service; corporates receive it — often relayed or over non-Swift channels — for cash management and reconciliation. Sent by the account-servicing institution to the account owner, or to another institution authorised to receive the statement on the owner's behalf. the official SWIFT Standards MT documentation is the complete specification.
EASYMT941What is MT941, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Reports balances for an account at a point during the day without providing the full transaction detail of an MT942.
WHY IT MATTERS
It supports cash positioning and liquidity decisions. Sent by the account servicing institution to the account owner or an authorised recipient under an agreed intraday reporting service. The complete MT941 definition and bilateral service agreement control balance types, timing, and field options.
EASYMT942What is MT942, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Reports account transactions during the day before the final statement.
WHY IT MATTERS
It lets an account owner see recent debits and credits and begin reconciliation early. Sent by the account servicing institution to the account owner or authorised recipient at agreed intraday intervals or triggers. The complete MT942 format includes control totals, floor limits, repetition, and field options governed by the service agreement.
EASYMT950What is MT950, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Reports all entries booked to an account over a statement period in a compact bank-to-bank statement format.
WHY IT MATTERS
It is widely used for financial-institution account reconciliation. Sent by an account servicing institution to the financial institution that owns the serviced account. The complete MT950 specification defines field options, repetition, pagination, and balance rules.
MEDIUMMT101 → pain.001What is the business context for the MT101 → pain.001 mapping?
MODEL ANSWERDIRECT ANSWER
Request-for-transfer to customer credit transfer initiation.
WHY IT MATTERS
Corporates migrating channel formats meet this mapping first.
MEDIUMMT202 → pacs.009What is the business context for the MT202 → pacs.009 mapping?
MODEL ANSWERDIRECT ANSWER
General financial-institution transfer translation.
WHY IT MATTERS
Educational summary of common correspondences.
MEDIUMMT940 → camt.053What is the business context for the MT940 → camt.053 mapping?
MODEL ANSWERDIRECT ANSWER
Customer statement migration from compact FIN lines to structured ISO 20022 entries.
MEDIUMMT941 → camt.052What is the business context for the MT941 → camt.052 mapping?
MEDIUMMT942 → camt.052What is the business context for the MT942 → camt.052 mapping?
TRICKYMT101 → pain.001What migration caveat must you remember for MT101 → pain.001 (1)?
MODEL ANSWERDIRECT ANSWER
pain.001 is a customer-to-bank message; MT101 can also travel bank-to-bank as a relay — the operational context differs even where fields align.
TRICKYMT192 → camt.056What migration caveat must you remember for MT192 → camt.056 (1)?
MODEL ANSWERDIRECT ANSWER
A cancellation request does not reverse settled funds; an accepted recall normally leads to a separate return of value.
TRICKYMT195 → camt.110What migration caveat must you remember for MT195 → camt.110 (1)?
MODEL ANSWERDIRECT ANSWER
camt.110 is not just XML-wrapped narrative; its value is structured case, underlying payment, and requested-information data.
TRICKYMT196 → camt.029What migration caveat must you remember for MT196 → camt.029 (1)?
MODEL ANSWERDIRECT ANSWER
A positive resolution is not itself the return of value; expect a pacs.004 and corresponding account entry where funds come back.
Payments foundations
EASYMT103What is MT103, who sends it, and why is it used?
MODEL ANSWERDIRECT ANSWER
Instructs a transfer of funds where the ordering party, the beneficiary, or both are non-bank customers.
WHY IT MATTERS
It is the classic cross-border customer credit transfer: one message per payment, carrying the parties, amounts, charging arrangement, and remittance detail from the ordering customer's bank toward the beneficiary's bank. Sent by or on behalf of the ordering customer's bank to the beneficiary's bank — directly, hop by hop through correspondents in the serial method, or straight to the beneficiary's bank with a separate MT202 COV carrying the funds in the cover method. the official SWIFT Standards MT documentation is the complete specification.
MEDIUMMT103 → pacs.008What is the business context for the MT103 → pacs.008 mapping?
MODEL ANSWERDIRECT ANSWER
Cross-border customer credit transfer translation, in the spirit of public CBPR+ and PMPG translation guidance.
WHY IT MATTERS
Educational summary — the applicable usage guideline is the rule.
TRICKYMT103 /REJT/ convention → pacs.002What migration caveat must you remember for MT103 /REJT/ convention → pacs.002 (1)?
MODEL ANSWERDIRECT ANSWER
pacs.002 has no dedicated MT equivalent; legacy implementations reused payment messages and bilateral /REJT/ conventions.
TRICKYMT103 /RETN/ convention → pacs.004What migration caveat must you remember for MT103 /RETN/ convention → pacs.004 (1)?
MODEL ANSWERDIRECT ANSWER
pacs.004 is a new value-carrying return after settlement, not merely a negative status.
TRICKYMT103 → pacs.008What migration caveat must you remember for MT103 → pacs.008 (1)?
MODEL ANSWERDIRECT ANSWER
Translation preserves syntax; transformation preserves meaning.
WHY IT MATTERS
A field-by-field translation that ignores business context can be syntactically valid and operationally wrong.