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.
386 matches
Showing 351–386 · Page 8 of 8
Payment architecture & BA delivery
Payments foundations
TRICKYOUR vs SHA vs BENCompare OUR and SHA on “Who pays which charges”.
MODEL ANSWERDIRECT ANSWER
OUR: The originator pays all charges — their own bank's, the intermediaries', and the beneficiary bank's.
WHY IT MATTERS
SHA: The originator pays their own bank's charges; the beneficiary bears the charges on the receiving side, and intermediary deductions typically fall on the beneficiary side too. Under BEN, the beneficiary bears all charges, including the sending bank's — usually taken out of the payment amount itself.
Clearing & settlement
TRICKYRTGS vs deferred net settlementCompare RTGS and Deferred net settlement on “Settlement unit”.
MODEL ANSWERDIRECT ANSWER
RTGS: Each payment settles individually, at its gross (full) amount.
WHY IT MATTERS
Deferred net settlement: Many payments are accumulated and offset; only each participant's net position settles.
MEDIUMRTGS vs deferred net settlementWhat is the essential difference between RTGS and Deferred net settlement?
MODEL ANSWERDIRECT ANSWER
Real-time gross settlement settles every payment individually and immediately; deferred net settlement accumulates payments and settles only the net positions at designated times.
WHY IT MATTERS
The trade is liquidity cost against credit risk. Reach for RTGS when the amounts are large enough, or the payments urgent enough, that credit exposure between banks is unacceptable — you are paying liquidity to eliminate risk. Reach for deferred net settlement when volumes are high and values are small, and the netting benefit outweighs the managed inter-cycle exposure. Modern practice mixes the models: bulk retail on DNS, high-value on RTGS, and instant rails borrowing the gross-and-final idea with prefunded liquidity.
SWIFT & MT
TRICKYSerial vs cover routingCompare Serial routing and Cover routing on “Messages involved”.
MODEL ANSWERDIRECT ANSWER
Serial routing: One customer credit transfer (MT103, or pacs.008 in ISO 20022) travels the whole route, relayed by each bank in the chain.
WHY IT MATTERS
Cover routing: Two message streams: the customer credit transfer goes straight to the beneficiary's bank, and a separate bank-to-bank cover payment (MT202 COV, or pacs.009 COV) moves the funds through the correspondents. The COV variant exists specifically so that the cover leg repeats the underlying originator and beneficiary details instead of hiding them.
ISO 20022 & CBPR+
TRICKYUnstructured / hybrid vs fully structured addressCompare Unstructured / hybrid address and Fully structured address on “How the data is held”.
MODEL ANSWERDIRECT ANSWER
Unstructured / hybrid address: Unstructured: the whole address sits in a few free-text lines with no labelled parts.
WHY IT MATTERS
Hybrid: town and country are labelled elements, but street and building stay as free text. Fully structured address: Every component — street name, building number, town name, post code, country — is carried in its own named element.
Operations & architecture
EASYReconciliationWhat does “Reconciliation” mean in payments?
MODEL ANSWERDIRECT ANSWER
Reconciliation is the control that compares two independent records of the same activity and explains every difference between them.
WHY IT MATTERS
In payments the classic example is nostro reconciliation: a bank matches the entries it expects on its account at a correspondent against the statement the correspondent actually sends, such as an MT940. Items that do not match — a missing credit, an unexpected debit, a duplicated entry — become breaks that someone must investigate and clear. How often reconciliation runs, and how much of it is automated, varies widely between institutions.
EASYStraight-through processingWhat does “Straight-through processing” mean in payments?
MODEL ANSWERDIRECT ANSWER
Straight-through processing means a payment travels from initiation to posting with no human touching it: validation, enrichment, routing, screening, and accounting all happen automatically.
WHY IT MATTERS
The share of payments that achieve this — the STP rate — is a standard operations metric, because every payment that falls out of the automatic flow lands in a repair or investigation queue and costs disproportionate money and time. STP rates are mostly determined upstream: clean reference data, correct identifiers, and structured message formats prevent the fallout that manual teams otherwise absorb. Much of the case for ISO 20022's richer structure is ultimately an STP argument.
MEDIUMPayment controlsWhat does the four-eyes or maker-checker control achieve in payment processing?
MODEL ANSWERDIRECT ANSWER
It requires one person to create or repair a payment and a different authorized person to approve its release.
WHY IT MATTERS
The control separates duties, reduces the chance that one mistake or compromised credential can move value, and creates evidence of who prepared and approved the instruction.
COMMON MISTAKE
A second click by the same user or a purely technical validation is not independent maker-checker approval.
MEDIUMPayment enginesWhich checks should a payment engine perform before releasing a payment?
MODEL ANSWERDIRECT ANSWER
It should authenticate the instruction, validate mandatory data and account status, check funds and limits, apply routing and duplicate controls, call fraud and compliance checks, and confirm authorization before release.
WHY IT MATTERS
The exact sequence varies by product and rail. A strong design distinguishes hard validation failures, repairable data issues, compliance holds, and downstream technical failures so each outcome reaches the right queue and customer status.
EASYClient payment channelsThrough which channels can a bank receive customer payment instructions?
MODEL ANSWERDIRECT ANSWER
Common channels include online and mobile banking, branch or operations entry, host-to-host files, APIs, EBICS, SWIFT for Corporates and scheduled or bulk-payment services.
WHY IT MATTERS
Each channel has a different authentication, authorization, file or message format, cut-off, duplicate-control and acknowledgement model. The payment engine should normalize accepted instructions into a canonical form while preserving source identifiers and audit evidence.
Sanctions screening & governance
Sanctions foundations
TRICKYCustomer screening vs transaction screeningCompare Customer screening and Transaction screening on “What gets screened”.
MODEL ANSWERDIRECT ANSWER
Customer screening: Customer records: names, aliases, dates of birth, addresses, identification numbers, plus connected parties such as beneficial owners, directors, and signatories.
WHY IT MATTERS
Transaction screening: Payment messages in flight: debtor, creditor, their agents and banks, addresses, and free-text fields such as remittance information — whatever the message actually carries.
EASYSanctions listWhat does “Sanctions list” mean in payments?
MODEL ANSWERDIRECT ANSWER
A sanctions list is the published register of targets designated under a sanctions regime — people, companies, organisations, vessels, sometimes aircraft.
WHY IT MATTERS
Each entry typically carries names, known aliases, and identifiers such as dates of birth, addresses, passport numbers, or registration numbers. Issuers include OFAC in the United States, OFSI in the United Kingdom, the European Union, and the United Nations. Screening systems load these lists as reference data, so list accuracy and update speed directly determine what a bank can and cannot catch.
EASYSanctionsWhat does “Sanctions” mean in payments?
MODEL ANSWERDIRECT ANSWER
Sanctions are restrictive measures that governments and international bodies impose to pursue foreign-policy and security goals.
WHY IT MATTERS
They can target whole countries, specific sectors, named entities, individuals, vessels, or activities, and they commonly require freezing assets and refusing to process transactions for the targets. For a bank, sanctions are not a risk-appetite choice: processing a payment for a sanctioned party can breach the law of every jurisdiction whose measures apply. Which regimes bind a given institution depends on where it is incorporated, where it operates, and the currencies it clears.
EASYScreeningWhat does “Screening” mean in payments?
MODEL ANSWERDIRECT ANSWER
Screening is the control that compares the parties in a bank's data — customers at onboarding and on an ongoing basis, and the names in payment messages in flight — against sanctions lists and other watchlists.
WHY IT MATTERS
When the comparison finds a possible match, the system raises an alert for investigation before the relationship or payment proceeds. Screening is a matching discipline: it looks for designated parties. It differs from anti-money-laundering transaction monitoring, which looks for suspicious behaviour patterns, and from fraud detection, which looks for unauthorised activity.
Screening execution
TRICKYA common surname collides with the listIn “A common surname collides with the list”, how should an investigator answer: “Do any hard identifiers overlap?”?
MODEL ANSWERDIRECT ANSWER
Evidence: 1) The passport number in the beneficiary's KYC file differs from the fictional passport K0448127 recorded on the list entry 2) No alias, former name, or transliteration variant in the KYC file links to the entry Finding: No identifier connects the beneficiary to the list entry; the collision is purely a common name.
TRICKYThe alias that was the real nameIn “The alias that was the real name”, how should an investigator answer: “Is there any indication this is a different person who shares the identifiers?”?
MODEL ANSWERDIRECT ANSWER
Evidence: 1) No conflicting date of birth, nationality, or address information anywhere in the case file Finding: Nothing discounts the match; every checked attribute corroborates it.
TRICKYThe hit hiding in the remittance lineIn “The hit hiding in the remittance line”, how should an investigator answer: “Can the institution rule involvement in or out from what it already holds?”?
MODEL ANSWERDIRECT ANSWER
Evidence: 1) No invoice or transport documents are on file for this trade 2) Account history shows this is the debtor's first payment to this creditor Finding: The institution cannot determine from the message and its own records whether a designated party is actually involved in the underlying transaction.
EASYFalse positiveWhat does “False positive” mean in payments?
MODEL ANSWERDIRECT ANSWER
A false positive is a screening alert that, on investigation, does not concern the listed party — a customer or payment party merely shares a name or similar details with a watchlist entry.
WHY IT MATTERS
Common names collide constantly, so false positives are the dominant output of any screening system; the overwhelming majority of alerts close this way. They are not free: each one consumes investigator time and delays a payment or an onboarding. Programmes manage the false-positive rate through matching thresholds, better use of secondary identifiers such as dates of birth, and tuning — while protecting the ability to catch true matches.
TRICKYA common surname collides with the listWhich red flags and mitigants must be balanced in “A common surname collides with the list”?
MODEL ANSWERDIRECT ANSWER
Red flags: 1) Near-exact full-name similarity against a listed individual. 2) The alias set covers spelling variants, so this was not an artifact of one aggressive fuzzy rule. 3) The payment message alone contained nothing that could discount the match.
WHY IT MATTERS
Mitigants: 1) Date of birth from KYC differs from the list entry by 27 years. 2) No geographic overlap between the beneficiary's documented residence and the listed person's recorded location. 3) No passport, alias, or other identifier overlap.
TRICKYThe alias that was the real nameWhich red flags and mitigants must be balanced in “The alias that was the real name”?
MODEL ANSWERDIRECT ANSWER
Red flags: 1) The creditor name matches a documented alias rather than the primary list name — consistent with a listed person transacting under an alternate identity. 2) Date of birth and passport number both align with the list entry. 3) The account jurisdiction matches the listed person's recorded location. 4) A vessel purchase is a high-value asset transfer, a transaction type that warrants extra care when a designated person may be involved. Mitigants: 1) The payment was held at first-pass screening;
TRICKYThe hit hiding in the remittance lineWhich red flags and mitigants must be balanced in “The hit hiding in the remittance line”?
MODEL ANSWERDIRECT ANSWER
Red flags: 1) A listed entity's name appears verbatim in the remittance text. 2) The 'VIA' wording suggests a designated party in the transport chain of the underlying trade. 3) First-time payment between this debtor and creditor, so no established pattern to compare against. Mitigants: 1) Neither the debtor nor the creditor matched any list entry. 2) Remittance text is often copied from invoices and templates, and can name entities with no current role in the transaction.
MEDIUMPayment sanctions checksWhich sanctions checks should a payment pass before release?
MODEL ANSWERDIRECT ANSWER
The bank should screen relevant parties, agents, accounts, identifiers, countries, addresses and meaningful free text against the lists and restrictions applicable to the transaction.
WHY IT MATTERS
Controls may also need ownership, sectoral, geographic, vessel, goods or service restrictions. Screening produces candidates, not legal conclusions: potential matches must be held, investigated with reliable identifiers, documented and dispositioned under policy before release or rejection.
COMMON MISTAKE
Do not limit screening to the payer and beneficiary names or treat a low similarity score as automatic clearance.
Investigation & governance
TRICKYNot on the list, still blocked: ownership adds upIn “Not on the list, still blocked: ownership adds up”, how should an investigator answer: “Does this payment fall within the reach of that rule?”?
MODEL ANSWERDIRECT ANSWER
Evidence: 1) The payment is denominated in US dollars and routed through Meridian Bank, the institution's fictional New York correspondent 2) The institution's sanctions policy applies OFAC-style ownership analysis to all USD traffic Finding: The US-dollar leg brings the payment within the scope the institution's policy assigns to the rule.
EASYCase managementWhat does “Case management” mean in payments?
MODEL ANSWERDIRECT ANSWER
Case management is the workflow layer of a screening operation.
WHY IT MATTERS
It receives alerts, groups related ones into cases, assigns them to investigators, enforces tiered review and four-eyes checks where policy requires them, and records the evidence and rationale behind every disposition. A good case-management layer produces the audit trail regulators expect: who looked at what, when, and why the decision was made. It also feeds management information — alert volumes, ageing, false-positive rates, investigator consistency — that governance uses to tune the programme. Tooling ranges from vendor platforms to in-house builds.
TRICKYNot on the list, still blocked: ownership adds upWhich red flags and mitigants must be balanced in “Not on the list, still blocked: ownership adds up”?
MODEL ANSWERDIRECT ANSWER
Red flags: 1) A rare listed surname embedded in the counterparty's company name. 2) Aggregate ownership by listed persons of 65 percent — comfortably past the 50 percent line even though no single stake crosses it. 3) Creditor jurisdiction matches the listed persons' recorded location. 4) Shipping and charter-party structures change ownership quickly, so registry evidence goes stale fast.
List data & identifiers
TRICKYStrong name, wrong person: identifiers decideIn “Strong name, wrong person: identifiers decide”, how should an investigator answer: “Is there residual risk that the KYC file itself is wrong or stale?”?
MODEL ANSWERDIRECT ANSWER
Evidence: 1) The customer's identity documents were verified at onboarding and re-verified at the last periodic review 2) No adverse media or internal-list hits connect the customer to Fictional Programme ORION Finding: The KYC identifiers are reliable enough to rest the disposition on.
TRICKYA clean pass through the filterWhich red flags and mitigants must be balanced in “A clean pass through the filter”?
MODEL ANSWERDIRECT ANSWER
Red flags: 1) A shared surname token with a list entry is what pulled the candidate in — the same mechanism that catches real matches. 2) Had the shared token been a rare, distinctive surname rather than a common one, the same partial overlap would have deserved a closer look. Mitigants: 1) The candidate list entry is an individual while the payment names a company, and nothing suggests the company is a front for that individual. 2) No geographic overlap: the entry records Uruguay, the creditor is in Spain.
TRICKYStrong name, wrong person: identifiers decideWhich red flags and mitigants must be balanced in “Strong name, wrong person: identifiers decide”?
MODEL ANSWERDIRECT ANSWER
Red flags: 1) Token-identical name match against a listed individual. 2) The debtor's country matches the country on the list entry. 3) Nothing inside the payment message could discount the match.
WHY IT MATTERS
Mitigants: 1) The list entry carries a date of birth and a passport number — rich secondary identifiers that make a decisive comparison possible. 2) The customer's verified KYC identifiers mismatch on both counts. 3) The instant-rail reject meant no funds ever left while the alert was open.
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.