Review questions

Review questions

Test your understanding with these questions. Marking and saved results are available with a free account.

1. Question 1A payment app says “done” at intake, but final posting has not arrived. Which state should it show?

   Pending with a trace ID until settlement confirmation Show final when the gateway accepts the message Show failure when posting is absent although settlement is unresolved Retry with a new ID before querying the first instruction
2. Question 2Evening volume rises while the settlement account cannot be funded for two hours. What measure reveals the binding constraint?

   Average prefunded balance over the month Gross evening transaction value before netting End-of-day net position alone Peak net position requiring funding during the settlement window
3. Question 3A provider fails after accepting payment instructions but before their outcomes are known. What is the safe recovery action?

   Treat provider-accepted instructions as final success Wait for the end-of-day report without showing unknown state or reconciling Query by stable ID and reconcile the ledger before any resend Resend every instruction with new IDs when the provider returns
4. Question 4A new wallet team says sign-ups prove value. Which test is closest to customer benefit?

   Compare usage with a segment lacking the same alternative Compare completion of a real payment need with the available alternative in a defined segment Compare sign-ups before and after the campaign alone Measure opened wallets without completed payment activity
5. Question 5A higher transfer price raises revenue per transaction but also abandonment and support cost. What should guide pricing?

   Contribution after cost and losses at realistic volume, alongside customer effect Use nominal revenue per transaction after the increase Count network fees alone, omitting support and loss Match the highest competitor price while assuming unchanged volume
6. Question 6A low-connectivity segment starts payment but loses connection before confirmation. What design is worth testing?

   Leave payment pending without a status query until reconnection Create a fresh payment instruction on every app reopen Show local success at send time with an unconfirmed receipt Queryable state and delayed receipt with duplicate prevention
7. Question 7A fraud complaint follows a customer-authorized transfer induced by impersonation. Where should control intervene?

   Send a monthly alert after settlement for all transfers Block every new beneficiary without verification or release Before release with independent verification and new-beneficiary context checks Make post-payment record encryption the primary control
8. Question 8A high-risk payment message lacks a beneficiary identity field. What is the controlled decision?

   Store the missing name in a side log and omit it from screening Pause processing and request documented completion under risk policy Fill the field from the closest account name without beneficiary confirmation Pass the message because it is below a manual-review threshold
9. Question 9Measured fraud falls after a new block rule, while complaints and false declines rise. What review is needed?

   Compare avoided loss with rejection cost and segment fairness Expand the rule using only aggregate loss reduction Measure fraud loss without complaints or legitimate declines Call the measured fall success despite migration to another channel
10. Question 10A provider promises an “instant” cross-border transfer, yet final settlement is delayed. Which description is accurate?

    Call the transfer instant because the send message arrives in seconds Use the first intermediary's processing time as the journey time Treat payee message acceptance as assurance both currency legs settled Fast instruction intake is distinct from funds availability and finality
11. Question 11An ISO 20022 message arrives with a truncated name after an intermediary hop. What is the first improvement?

    Truncate the name at origin so all messages match Treat ISO 20022 adoption as proof that fields are complete Locate data loss and validate field compatibility across the chain Resend the same truncated message through the same route
12. Question 12One FX leg settles before the other arrives. Which risk is exposed?

    Treat first-leg completion as evidence the second leg will complete Settlement principal risk from asynchronous legs Track only FX price movement between the two legs Count first-leg liquidity cost but omit counterparty exposure
13. Question 13A new payment channel looks profitable on paper but lacks operational access authority. How should it be treated?

    Hold it at the eligibility gate until operating rights are clear Increase expected return to compensate for missing access rights Run a small live pilot before operating rights are resolved Treat the partner's letter of intent as durable operating permission
14. Question 14A partner contract measures intake API uptime only while payments remain pending. What should it add?

    Add intake API response time alone Count accepted requests while excluding returns and unknowns Add monitoring dashboard uptime instead of an escalation owner Time bounds for funds availability and unknown-state resolution with an escalation owner
15. Question 15A small pilot passes, but return cases increase as volume grows. What is the expansion decision?

    Increase volume to diagnose the cause without checking exposure Use mean time of successes while excluding returns Pause expansion, examine the return threshold and causes, then retest Scale because the first month reached planned volume

Create a free account to mark your answers and save your progress.