Difficulty: Hard
1. Imagine a customer sees checkout time out after submitting payment. What should the merchant check first?
A Warehouse colour code
B Existing payment status
C Search ranking position
D Customer review score
Answer: B. Existing payment status. Check the existing operation before submitting another charge.
2. When a retry uses the same idempotency key and request, what should normally happen?
A Card is replaced
B Second charge is created
C Order is automatically refunded
D Original result is reused
Answer: D. Original result is reused. An idempotent retry returns the prior operation instead of creating a duplicate.
3. Two workers handle one successful webhook simultaneously. Which design prevents duplicate fulfillment?
A Separate email templates
B Longer checkout timeout
C Atomic order-state update
D More browser redirects
Answer: C. Atomic order-state update. A transactional state change or unique constraint ensures fulfillment runs once.
4. A webhook reports capture, but its amount differs from the order. What is safest?
A Hold fulfillment for review
B Overwrite the order total
C Retry the card charge
D Ship immediately
Answer: A. Hold fulfillment for review. An amount mismatch requires investigation rather than automatic fulfillment.
5. The customer returns successfully, but no webhook arrives. How can reconciliation recover?
A Query provider transaction status
B Delete the local order
C Create a second charge
D Mark the order refunded
Answer: A. Query provider transaction status. A status query can recover an outcome when an asynchronous event is missing.
6. If a provider retries events out of order, how should current status be decided?
A Trust arrival order only
B Use authoritative event sequence
C Choose the latest email
D Reset every order pending
Answer: B. Use authoritative event sequence. Arrival order is not necessarily event order; use provider sequence or query current state.
7. Suppose a hotel authorizes a card before checkout. What does this enable?
A Reserve funds before capture
B Issue a chargeback
C Settle an immediate refund
D Guarantee final settlement
Answer: A. Reserve funds before capture. Authorization can reserve funds so capture occurs later after the service amount is known.
8. A merchant captures only delivered items. Which payment feature may help?
A Partial capture
B Hosted redirect
C Card updater
D Address verification
Answer: A. Partial capture. Partial capture allows a supported transaction to capture less than its authorization.
9. Imagine an uncaptured authorization is no longer needed. Which action is usually appropriate?
A Issue full refund
B Create chargeback
C Repeat authorization
D Void authorization
Answer: D. Void authorization. Voiding cancels an uncaptured authorization when the provider and network permit it.
10. When an extra duplicate charge has already been captured, which remedy applies?
A Repeat the capture
B Refund the duplicate
C Change the descriptor
D Void both orders
Answer: B. Refund the duplicate. A captured transaction is generally corrected with a refund, subject to provider rules.
11. If a merchant receives repeated soft declines, what is a responsible next step?
A Change customer billing data
B Retry without limits
C Ignore decline codes
D Review issuer guidance
Answer: D. Review issuer guidance. Soft-decline handling should follow issuer and provider instructions and avoid uncontrolled retries.
12. A hard decline is returned for a card. What should checkout avoid?
A Showing a clear message
B Repeated automatic retries
C Offering another method
D Saving the order
Answer: B. Repeated automatic retries. Repeated retries on a hard decline may worsen outcomes and should be avoided.
13. Suppose a timeout leaves the payment outcome unknown. How can duplicate risk be reduced?
A Reuse idempotency key
B Capture twice
C Skip status checks
D Generate a new order
Answer: A. Reuse idempotency key. Reusing the same key and checking status reduces accidental duplicate requests.
14. Imagine a delayed event says an order is paid after cancellation. What should the system do?
A Erase payment history
B Apply explicit state rules
C Always reopen fulfillment
D Charge the customer again
Answer: B. Apply explicit state rules. Guarded state transitions stop late events from blindly reversing cancellations.
15. When a payment token is saved for future use, what should the merchant retain?
A Original CVV code
B Issuer private key
C Customer permission and terms
D Unmasked card track
Answer: C. Customer permission and terms. Tokenization does not remove the need for appropriate consent and transaction records.
16. A mobile app embeds a provider's payment SDK. What should engineers review?
A Review sentiment score
B Product title length
C SDK security integration
D Warehouse packing schedule
Answer: C. SDK security integration. Payment SDKs handle sensitive flows, so their integration and provider guidance need review.
17. If a merchant routes payments across providers, which operational risk needs management?
A Avoiding order identifiers
B Eliminating issuer decisions
C Guaranteeing every approval
D Consistent status reconciliation
Answer: D. Consistent status reconciliation. Multiple providers require unified transaction references and consistent status handling.
18. Suppose a shopper taps Pay twice during a slow response. Which control helps at checkout?
A Remove order confirmation
B Hide payment status
C Disable duplicate submission
D Store card security code
Answer: C. Disable duplicate submission. Client-side controls reduce accidental repeats; server-side idempotency provides stronger protection.
19. Imagine a refund remains pending with the provider. What should support tell the customer?
A Card has been replaced
B Order was never paid
C Refund is still processing
D Funds are already received
Answer: C. Refund is still processing. Pending status should be communicated accurately without promising completion.
20. A sandbox payment succeeds but its live equivalent fails. What should be checked?
A Sandbox test card number
B Live credentials and configuration
C Customer product reviews
D Warehouse delivery labels
Answer: B. Live credentials and configuration. Production settings, account activation, and live credentials can differ from sandbox.
21. When an issuer approves payment, but the cardholder later disputes it, which statement is accurate?
A Approval guarantees legitimacy
B Gateway absorbs every loss
C Authorization is not fraud proof
D Settlement prevents disputes
Answer: C. Authorization is not fraud proof. Authorization approval does not prove identity or eliminate later disputes.
22. If a provider payout is below captured sales, what should finance compare?
A Browser versions and fonts
B Inventory counts and returns
C Product ratings and views
D Fees, refunds, and timing
Answer: D. Fees, refunds, and timing. Reconciliation accounts for fees, refunds, reserves, and timing differences.
23. Suppose a checkout uses a different settlement currency. What should be disclosed clearly?
A Internal event identifiers
B Gateway secret credentials
C Issuer risk score
D Applicable conversion terms
Answer: D. Applicable conversion terms. Conversion can affect customer cost and should be presented according to applicable rules.
24. An unapproved script appears on the payment page. What is prudent?
A Investigate and restore trusted code
B Keep checkout unchanged
C Publish all credentials
D Ignore the change alert
Answer: A. Investigate and restore trusted code. Unexpected payment-page script changes should be investigated and remediated promptly.
25. Imagine an unauthorized payment script is detected during checkout. Which action reduces exposure?
A Isolate affected payment path
B Ignore security monitoring
C Retry declined charges
D Export customer CVVs
Answer: A. Isolate affected payment path. Isolating the affected components limits exposure while the incident is investigated.