Payment Gateways MCQs (Set-2)

Difficulty: Easy & Basic

1. Where should an order be created before a gateway call?

A Customer review form
B Card network directory
C Merchant order system
D Courier tracking page

2. Why match a gateway payment to an order ID?

A Connect payment and order
B Choose a product category
C Set a courier route
D Change the card issuer

3. What should an integration do before sending a payment request?

A Delete the order record
B Validate checkout details
C Disable error handling
D Email secret API keys

4. What does a server-side API key authenticate?

A Public review posts
B Merchant server requests
C Customer product searches
D Courier delivery scans

5. Why keep secret keys out of browser code?

A Browsers expose client code
B Browsers cannot load pages
C Customers need bank access
D Keys expire on weekends

6. When a customer returns from hosted checkout, what confirms final status?

A Verified provider result
B Cart still being open
C Customer clicking refresh
D Return-page appearance alone

7. What does a webhook provide?

A A customer password
B A product photograph
C Asynchronous event notification
D A shipping invoice

8. Why verify a webhook signature?

A Improve checkout styling
B Confirm message authenticity
C Increase card limit
D Estimate parcel weight

9. Why can a webhook arrive after checkout returns?

A Cards lack identifiers
B Events are asynchronous
C Browsers control settlement
D Orders require no server

10. What should happen if a webhook is delivered twice?

A Delete both records
B Create two orders
C Process idempotently
D Charge the card again

11. What can a payment authorization hold represent?

A Completed merchant payout
B Reserved available funds
C Delivered parcel
D Cancelled customer account

12. What occurs when a merchant voids an uncaptured authorization?

A A parcel is returned
B Authorization is cancelled
C A new card is issued
D A refund is issued

13. How does a refund differ from a void?

A Void updates card expiry
B Refund precedes authorization
C Refund follows captured payment
D Void ships the order

14. What can a partial capture do?

A Change the cardholder
B Reverse an issuer decision
C Create a delivery label
D Capture part of authorization

15. Why should payment retries use provider guidance?

A Avoid duplicate or harmful requests
B Remove issuer checks
C Skip reconciliation
D Guarantee approval

16. Which payment method may use a stored payment token?

A Manual banknote
B Cash on delivery
C Paper cheque
D Card-on-file payment

17. What does tokenization replace in merchant storage?

A Order description
B Customer email
C Delivery postcode
D Sensitive card number

18. What does a customer-facing statement descriptor show?

A Issuer decision rules
B Courier parcel contents
C Merchant transaction label
D Gateway API password

19. Why capture cardholder consent for recurring billing?

A Hide refund status
B Choose a colour palette
C Calculate parcel dimensions
D Document payment authorization

20. Which step may add cardholder authentication to checkout?

A 3-D Secure challenge
B Order cancellation
C Warehouse picking
D Product filtering

21. What is a frictionless 3DS flow designed to avoid?

A Transaction record
B Payment confirmation
C Issuer authorization
D Unnecessary customer challenge

22. What does a challenge flow ask the shopper to do?

A Approve merchant refund
B Re-enter shipping address
C Complete added authentication
D Rate the product

23. Why use a sandbox webhook endpoint?

A Test event handling safely
B Publish a checkout page
C Settle real transactions
D Store production passwords

24. What does a settlement report help compare?

A Customer passwords and emails
B Parcel labels and routes
C Product photographs and tags
D Processed payments and totals

25. What should an error message avoid exposing?

A Secrets and card data
B Payment status
C General next steps
D Order reference