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 101–114 · Page 3 of 3
Messages & MT ↔ MX migration
SWIFT & MT
TRICKYMT196 → camt.111What migration caveat must you remember for MT196 → camt.111 (1)?
MODEL ANSWERDIRECT ANSWER
MT196 could answer multiple category-1 queries; choose camt.111 only for the applicable modern investigation context.
TRICKYMT199 answer → camt.111What migration caveat must you remember for MT199 answer → camt.111 (1)?
MODEL ANSWERDIRECT ANSWER
A generic MT199 may not contain enough reliable structure for automated translation.
TRICKYMT199 query → camt.110What migration caveat must you remember for MT199 query → camt.110 (1)?
MODEL ANSWERDIRECT ANSWER
Free-format MT199 text can be ambiguous; some content may require manual enrichment before camt.110 can be produced safely.
TRICKYMT202 → pacs.009What migration caveat must you remember for MT202 → pacs.009 (1)?
MODEL ANSWERDIRECT ANSWER
pacs.009 has no customer parties — if an underlying customer payment exists, the COV variant and its mapping apply instead.
TRICKYMT202 COV → pacs.009 COVWhat migration caveat must you remember for MT202 COV → pacs.009 COV (1)?
MODEL ANSWERDIRECT ANSWER
The COV structure exists precisely so every bank in the cover chain can screen the underlying customer parties — dropping sequence B data in translation is a compliance failure, not a formatting nit.
TRICKYMT900 → camt.054What migration caveat must you remember for MT900 → camt.054 (1)?
MODEL ANSWERDIRECT ANSWER
camt.054 can batch several entries; MT900 is a single debit advice.
TRICKYMT910 → camt.054What migration caveat must you remember for MT910 → camt.054 (1)?
MODEL ANSWERDIRECT ANSWER
camt.054 can carry debit and credit entries and may batch them; MT910 is a single credit advice.
TRICKYMT940 → camt.053What migration caveat must you remember for MT940 → camt.053 (1)?
MODEL ANSWERDIRECT ANSWER
MT940 field 86 conventions vary by bank; there is no safe universal parser.
TRICKYMT941 → camt.052What migration caveat must you remember for MT941 → camt.052 (1)?
MODEL ANSWERDIRECT ANSWER
MT941 is primarily a balance report; camt.052 can also carry detailed intraday entries.
TRICKYMT942 → camt.052What migration caveat must you remember for MT942 → camt.052 (1)?
MODEL ANSWERDIRECT ANSWER
Field 86 is commonly bank-specific; translation quality depends on a proven parsing profile.
TRICKYMT950 → camt.053What migration caveat must you remember for MT950 → camt.053 (1)?
MODEL ANSWERDIRECT ANSWER
camt.053 supports richer party and reference data than MT950; do not fabricate missing values.
TRICKYMT2xx institution transfersHow do MT200, MT201, MT202, MT203 and MT210 differ?
MODEL ANSWERDIRECT ANSWER
MT200 moves a bank's own funds, MT201 groups multiple MT200 transfers, MT202 carries a general institution transfer, MT203 groups multiple MT202 transfers, and MT210 is a notice that funds are expected.
WHY IT MATTERS
MT200 and MT201 are transfers for the sender's own account; MT202 and MT203 are institution-to-institution transfer instructions. MT210 is an advice, not the funds-transfer instruction itself. MT202 COV is a separate variant used when the transfer covers an underlying customer credit transfer.
COMMON MISTAKE
Do not use a plain MT202 for a cover leg that must carry underlying customer information.
MEDIUMMT101 initiation choicesIs MT101 mandatory for a corporate to initiate a payment?
MODEL ANSWERDIRECT ANSWER
No. MT101 is one standardized initiation channel, but a bank may also accept pain.001 files, APIs, host-to-host files, online banking instructions or branch requests.
WHY IT MATTERS
The permitted channel depends on the bank's product, customer agreement, market and security model. Once accepted, the bank validates and transforms the instruction into the interbank message required by the selected route. MT101 does not itself prove that the interbank payment settled.
ISO 20022 & CBPR+
MEDIUMpacs.028 status requestWhat does pacs.028 prove about the original payment?
MODEL ANSWERDIRECT ANSWER
Nothing by itself: pacs.028 only requests an FI-to-FI business status for an earlier instruction.
WHY IT MATTERS
The answer must arrive through the status mechanism supported by the bilateral agreement, scheme or service. A network acknowledgement proves technical receipt of the request, not acceptance, settlement or customer credit of the original payment.
COMMON MISTAKE
Do not convert 'status request delivered' into 'payment accepted' or send repeated requests without an agreed timer and idempotency control.