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.
8 matches
Showing 1–8 · Page 1 of 1
Current standards & regulatory change
ISO 20022 & CBPR+
TRICKYSwift offers a free address-structuring tool ahead of the 2026 deadlineHow should a bank use an automated address-structuring tool without weakening data governance?
MODEL ANSWERVERIFIED 2026-07-18DIRECT ANSWER
To help institutions meet the structured-address requirement, Swift has made an address-structuring model available as a free, open-source tool that converts free-text postal addresses into the structured or hybrid ISO 20022 format, so the roughly two-thirds of messages still carrying unstructured addresses can be cleaned up before enforcement.
TRICKYCBPR+ payment-instruction coexistence ended; contingency treatment beganWhat changed when CBPR+ MT–MX coexistence ended in November 2025?
MODEL ANSWERVERIFIED 2026-07-18DIRECT ANSWER
On 22 November 2025, normal coexistence ended for in-scope CBPR+ FI-to-FI payment instructions; it did not retire every MT conversation.
WHY IT MATTERS
Native ISO 20022 is the target state, but post-cutover treatment is message-specific. Some MT instructions are NAKed, while selected messages can enter temporary, chargeable contingency conversion into ISO 20022 and FINplus. Reporting, payment-initiation relay, correspondence and investigations follow separate roadmaps. A strong answer therefore names the exact payment-instruction scope and distinguishes contingency processing from the former coexistence service.
TRICKYCBPR+ removes fully unstructured addresses from 14 November 2026What changes for postal addresses in in-scope CBPR+ traffic from 14 November 2026?
MODEL ANSWERVERIFIED 2026-07-18DIRECT ANSWER
In-scope CBPR+ traffic must use hybrid or fully structured postal addresses from 14 November 2026, subject to Swift's published message exceptions; EPC scheme rulebooks use 15 November 2026.
WHY IT MATTERS
The rule removes the fully unstructured option; it does not prohibit every AdrLine because a hybrid address uses structured town and country with limited address lines. Channel, customer-master and host-to-host changes matter more than a gateway-only conversion. Apply the rule by message and profile, and keep the CBPR+ and EPC dates separate.
TRICKYCBPR+ migration continues after the payment-instruction cutoverWhy is ISO 20022 migration work still continuing after the 2025 CBPR+ cutover?
MODEL ANSWERVERIFIED 2026-07-18DIRECT ANSWER
Because the 2025 deadline covered a defined payment-instruction scope, while reporting, payment-initiation relay, correspondence and investigations have separate migration work.
WHY IT MATTERS
Do not place one retirement date against the whole FIN estate. Inventory each business conversation and check its current Swift roadmap: native ISO 20022, NAK, temporary contingency conversion, mandatory-to-receive obligations and eventual retirement can differ. MT940/950 reporting, MT101 relay and MT199-style correspondence are therefore separate delivery decisions rather than leftovers automatically retired with MT103 and MT202 payment instructions.
TRICKYClassic investigations versus Case ManagementCan camt.110 and camt.111 simply replace every camt.026, camt.027 and camt.028 exchange?
MODEL ANSWERDIRECT ANSWER
No. The messages model different investigation patterns, and production replacement depends on the current service, reachability, orchestration and migration rules.
WHY IT MATTERS
camt.026, camt.027 and camt.028 describe classic unable-to-apply, non-receipt and additional-information cases. camt.110 and camt.111 carry orchestrated investigation requests and responses through Case Management. A migration design must map business purpose and case state, not only message names.
COMMON MISTAKE
Do not send Case Management messages as ordinary bilateral XML or assume a date retires every classic investigation message in every corridor.
Investigation & governance
TRICKYFATF launches a 2026-2028 roadmap on combating fraudWhat does FATF's 2026–2028 fraud roadmap require payment firms to implement today?
MODEL ANSWERVERIFIED 2026-07-18DIRECT ANSWER
On 1 July 2026, the Financial Action Task Force (FATF) launched a two-year roadmap to tackle fraud, the first initiative of the incoming UK Presidency.
WHY IT MATTERS
The roadmap is a plan of work, not a new rule: FATF will gather data on fraud typologies through October 2026 before proposing what more the existing FATF toolkit can do. The Financial Action Task Force sets the global standards that countries and their financial institutions follow to counter money laundering and the financing of terrorism. A roadmap in FATF terms is a plan of work rather than a binding rule: it signals a priority and a timeline for study, after which FATF may issue guidance or propose changes to its recommendations. This roadmap makes fraud a focus for the two-year UK Presidency.
SEPA & instant payments
TRICKYSEPA Verification of Payee became mandatory in the euro areaWhat does Verification of Payee add before a SEPA credit transfer is sent?
MODEL ANSWERVERIFIED 2026-07-18DIRECT ANSWER
Under the SEPA Verification of Payee scheme, euro-area payment service providers were required to offer a payee name-and-account check from 9 October 2025, giving payers a match result before an instant or standard credit transfer is sent.
WHY IT MATTERS
Verification of Payee (VoP) is a check that compares the payee name a payer enters against the name held for that account, returning a match, close-match or no-match result before the payment is sent. Its purpose is to cut misdirected payments and to make authorised push payment fraud harder, by giving the payer a clear warning when the name and the account number do not line up. Under the European Payments Council scheme, euro-area payment service providers were required to offer VoP from 9 October 2025, ahead of the broader instant-payments obligations in the same programme. For payers, the visible change is a name-check step at the point of initiation;
Clearing & settlement
TRICKYFedwire Funds Service completed its ISO 20022 cutoverWhat was operationally distinctive about Fedwire's ISO 20022 migration?
MODEL ANSWERVERIFIED 2026-07-18DIRECT ANSWER
The Federal Reserve's Fedwire Funds Service completed its single-day migration to the ISO 20022 message format on 14 July 2025, moving US large-value settlement onto the same standard used by other major market infrastructures.
WHY IT MATTERS
The Fedwire Funds Service is the Federal Reserve's real-time gross settlement system for US large-value payments — the rail behind time-critical, high-value transfers between banks. Unlike migrations that run a long coexistence period, Fedwire moved in a single step: on 14 July 2025 it switched from its long-standing proprietary message format to the ISO 20022 standard in one cutover. The change put US large-value settlement on the same message standard used by other major market infrastructures, including the Eurosystem's T2 and The Clearing House's CHIPS, which supports richer, more structured remittance and party data travelling end to end.