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.
67 matches
Showing 51–67 · Page 2 of 2
End-to-end flows & exceptions
Clearing & settlement
TRICKYFaster Payments (FPS)What triggers the “Over the limit: reroute via CHAPS” branch in “Faster Payments (FPS)”, and what happens next?
MODEL ANSWERDIRECT ANSWER
Trigger: The payment is above the Faster Payments single-payment limit of GBP 1 million (or above Bank Alfa's own FPS limit), so it cannot go through Faster Payments and must take a different rail.
WHY IT MATTERS
Funds state: The payment is made in full through CHAPS instead of Faster Payments; the amount settles gross in central bank money. Settlement state: Settled immediately and finally, payment-by-payment (RTGS) — not deferred and not netted as it would have been on FPS. Responsible party: Bank Alfa (sending bank). Next action: Bank Alfa confirms the CHAPS payment to Riya. For amounts within the limit, Faster Payments would have been the faster, cheaper choice.
TRICKYA TARGET2 (T2) settlement (euro RTGS)What triggers the “Queued for liquidity” branch in “A TARGET2 (T2) settlement (euro RTGS)”, and what happens next?
MODEL ANSWERDIRECT ANSWER
Trigger: Bank Alfa's RTGS account does not hold EUR 2,000,000.00 of available liquidity at the moment the payment is checked.
WHY IT MATTERS
Funds state: No money has moved while the payment sits in the queue — Bank Alfa's account is untouched until cover arrives. Settlement state: Settlement is deferred until liquidity is available; the payment settles, with finality, only once its RTGS account can cover it. Responsible party: Bank Alfa (sending bank). Next action: Bank Alfa manages its intraday liquidity, using CLM transfers so high-value payments do not sit queued late in the day.
TRICKYAn India RTGS transfer (Reserve Bank of India)What triggers the “Queued until funds arrive” branch in “An India RTGS transfer (Reserve Bank of India)”, and what happens next?
MODEL ANSWERDIRECT ANSWER
Trigger: At the moment the message is checked, Bank Alfa's settlement account at the Reserve Bank does not hold INR 5,00,000.00.
WHY IT MATTERS
Funds state: The beneficiary is paid only once Bank Alfa's settlement account is funded and the queued transfer settles. Settlement state: Settlement waited on liquidity — the payment stayed queued, not rejected, until the settlement account was covered. Responsible party: Bank Alfa (remitting bank). Next action: Bank Alfa manages its intraday liquidity so high-value RTGS transfers do not sit in the queue.
TRICKYA FedNow instant payment (US, 24/7/365)What triggers the “Receiver rejects: nothing settles” branch in “A FedNow instant payment (US, 24/7/365)”, and what happens next?
MODEL ANSWERDIRECT ANSWER
Trigger: Nordbank cannot apply the payment — for example Arjun's account has been closed — so it answers negatively before any settlement takes place.
WHY IT MATTERS
Funds state: Never left Riya's account — no settlement took place, so there is nothing to reverse. Settlement state: No settlement occurred; the master accounts were never touched because the answer was negative. Responsible party: Nordbank (receiving bank). Next action: Riya checks Arjun's account details against the reason code and can try again.
TRICKYUS ACH Network — direct depositWhat triggers the “Return: entry cannot be applied” branch in “US ACH Network — direct deposit”, and what happens next?
MODEL ANSWERDIRECT ANSWER
Trigger: Nordbank cannot apply the entry to the receiver's account — for a debit the funds are insufficient (R01), or the account is closed (R02) — after the settlement window already completed.
WHY IT MATTERS
Funds state: Returned to Asha Traders after the return settled — Riya was never paid. Settlement state: Original window settled, then reversed by a separately batched and netted return in a later window. Responsible party: Nordbank (RDFI). Next action: Asha Traders confirms Riya's current account details and re-originates the payroll entry.
TRICKYIndia NEFTWhat triggers the “Wait for the next half-hourly batch” branch in “India NEFT”, and what happens next?
MODEL ANSWERDIRECT ANSWER
Trigger: The transfer reaches NEFT just after the current cycle's cut-off, so it cannot join the batch that is about to settle.
WHY IT MATTERS
Funds state: Left Riya's account at the debit, but not yet settled between banks — it waits with NEFT for the next cycle. Settlement state: No netting or settlement for this transfer yet; it will settle in the next half-hourly batch. Responsible party: NEFT (Reserve Bank of India). Next action: The transfer joins the next half-hourly batch and then follows the normal net-settlement path to Arjun.
ISO 20022 & CBPR+
TRICKYCBPR+ corporate payment — full MX lifecycleWhat triggers the “pacs.002 reject” branch in “CBPR+ corporate payment — full MX lifecycle”, and what happens next?
MODEL ANSWERDIRECT ANSWER
Trigger: Meridian rejects the pacs.008 before booking the interbank value movement.
WHY IT MATTERS
Funds state: Restored to Asha Traders after the customer-side debit was released or reversed. Settlement state: The pacs.008 was rejected before interbank settlement; no return movement was needed. Responsible party: Bank Alfa (debtor agent). Next action: Repair the interbank data or route, then tell treasury whether a fresh instruction is required.
TRICKYCBPR+ corporate payment — full MX lifecycleWhat triggers the “pacs.004 return” branch in “CBPR+ corporate payment — full MX lifecycle”, and what happens next?
MODEL ANSWERDIRECT ANSWER
Trigger: Nordbank receives settled value but cannot credit the supplier because the account is closed.
WHY IT MATTERS
Funds state: Back in Asha Traders' account after the separately settled return. Settlement state: Original settlement completed; pacs.004 created a second settlement in the opposite direction. Responsible party: Asha Traders treasury. Next action: Confirm a valid supplier account and create a genuinely new payment instruction if payment is still due.
TRICKYCBPR+ corporate payment — full MX lifecycleWhat triggers the “pain.002 reject” branch in “CBPR+ corporate payment — full MX lifecycle”, and what happens next?
MODEL ANSWERDIRECT ANSWER
Trigger: Bank Alfa cannot accept the customer instruction because the debtor account data is invalid.
WHY IT MATTERS
Funds state: Still in Asha Traders' account; no customer debit was booked. Settlement state: No interbank instruction, clearing, or settlement occurred. Responsible party: Asha Traders treasury. Next action: Correct the account data, use a new message identifier, and resubmit without duplicating accepted items.
TRICKYCBPR+ cross-border transfer (pacs.008)What triggers the “Sanctions hold at the intermediary” branch in “CBPR+ cross-border transfer (pacs.008)”, and what happens next?
MODEL ANSWERDIRECT ANSWER
Trigger: Meridian's screening flags a potential name match against a sanctions list.
WHY IT MATTERS
The payment stops until an analyst decides. Funds state: Delivered to the creditor after the screening delay. Settlement state: Settled after release from the sanctions review. Responsible party: Meridian Bank (intermediary agent). Next action: Nothing to fix in the payment; the alert, evidence, and disposition are retained for audit. Repeated false positives on this name feed tuning reviews.
SEPA & instant payments
TRICKYSEPA Direct Debit — CoreWhat triggers the “Refund: 8-week no-questions-asked” branch in “SEPA Direct Debit — Core”, and what happens next?
MODEL ANSWERDIRECT ANSWER
Trigger: Within 8 weeks of the debit date, Riya asks Bank Alfa for a refund of the direct debit.
WHY IT MATTERS
For a Core collection this refund is unconditional — no reason is required. Funds state: Returned to Riya's account after the refund settled. Settlement state: Original collection settled, then reversed by a separately settled refund. Responsible party: Riya (debtor / customer). Next action: Asha Traders resolves the disputed invoice with Riya directly; beyond 8 weeks a claim is possible only for unauthorised collections, up to 13 months, and is not automatic.
TRICKYSEPA Direct Debit — B2BWhat triggers the “Refuse: mandate not registered” branch in “SEPA Direct Debit — B2B”, and what happens next?
MODEL ANSWERDIRECT ANSWER
Trigger: Bank Alfa checks the collection but finds no matching mandate registered for this debtor and creditor.
WHY IT MATTERS
Funds state: Never left the debtor's account — no debit was booked at Bank Alfa. Settlement state: The collection was refused at or before settlement, so no net movement stands between the banks. Responsible party: Bank Alfa (debtor bank). Next action: Asha Traders arranges for the debtor to register the signed mandate with Bank Alfa before resubmitting.
TRICKYSEPA Credit TransferWhat triggers the “Reject: insufficient funds” branch in “SEPA Credit Transfer”, and what happens next?
MODEL ANSWERDIRECT ANSWER
Trigger: The debtor's account cannot cover the transfer when Bank Alfa validates the instruction.
WHY IT MATTERS
Funds state: Never left the debtor's account — no debit was booked. Settlement state: No interbank clearing or settlement occurred. Responsible party: Bank Alfa (debtor agent). Next action: The debtor funds the account or amends the instruction and resubmits.
TRICKYSEPA Instant Credit TransferWhat triggers the “Ten seconds: no confirmation yet” branch in “SEPA Instant Credit Transfer”, and what happens next?
MODEL ANSWERDIRECT ANSWER
Trigger: At ten seconds Bank Alfa still has no confirmation showing whether the original SCT Inst transfer succeeded or failed.
WHY IT MATTERS
Bank Alfa immediately restores the payer's account, but records the outcome as unconfirmed rather than rejected. It keeps the original identifiers under investigation, prevents an automatic retry and watches for a late positive or negative status. A late positive means the beneficiary received the original payment and the bank must reconcile the restored customer balance under its policy.
TRICKYTIPS — TARGET Instant Payment SettlementWhat triggers the “TIPS expiry: nothing settles” branch in “TIPS — TARGET Instant Payment Settlement”, and what happens next?
MODEL ANSWERDIRECT ANSWER
Trigger: TIPS itself expires the accepted instruction after no beneficiary confirmation arrives by its timeout threshold.
WHY IT MATTERS
TIPS releases the reservation on Bank Alfa's dedicated cash account and sends an explicit negative outcome. Bank Alfa matches that outcome to the original payment, releases its customer-balance hold and permits a controlled retry only after proving this instruction did not settle. That explicit TIPS expiry is not the same as a PSP merely seeing no status at ten seconds.
SWIFT & MT
TRICKYSWIFT serial payment (MT103)What triggers the “Return: invalid account” branch in “SWIFT serial payment (MT103)”, and what happens next?
MODEL ANSWERDIRECT ANSWER
Trigger: The beneficiary account number in the MT103 does not exist at Cassia.
WHY IT MATTERS
Funds state: Back with the ordering customer (charges may have been deducted along the way). Settlement state: Each hop settled and was then unwound by an equally settled return. Responsible party: Cassia Bank (beneficiary bank). Next action: The customer verifies the beneficiary's account number before re-sending.
Operations & architecture
TRICKYUnable to apply versus claim non-receiptWhen would you use camt.026 instead of camt.027?
MODEL ANSWERDIRECT ANSWER
Use camt.026 when a received instruction or entry cannot be applied or reconciled; use camt.027 when expected funds or cover have not been received.
WHY IT MATTERS
The first is a data or application problem around an item the receiver can identify. The second is a missing-value trace, including a received customer-payment instruction with no matching cover. Neither message moves money, and current service availability must be checked before implementation.
COMMON MISTAKE
Do not send camt.026 merely because cover is missing or treat either investigation message as evidence that settlement failed.