Scalability and responsiveness in online payment gateway is
not an option, it is a requirement. Some optional steps/process in a payment
gateway performed in a parallel/asynchronous way can help in maintaining
scalability of the system. This parallelism
will enable the system for betterment in latency and throughput. While some
processes can only be performed in a sequential fashion, but the system
designer should always check for processes which can be performed in an
asynchronous way.
Following are some
optional processes in an online payment gateway, which I think can be performed
in parallel:
-
Fraud and Risk Prevention check: A check made
for detection of a possible fraud in the transaction under process
-
Sending Email: Sending emails to buyers,
merchants, self and any other third parties.
-
Sending SMS: SMS to the buyer
-
Dynamic currency conversion related processing: Dynamic
currency conversion can sometime be performed in parallel
-
Sending online notifications to merchants: Some
payment systems send HTTPS notifications to merchants
- Account updater: When card details of the buyer has changed, and an update is required
- Tokenization/One-Click-Checkout process: Tokenization or one-click-checkout or easy checkout is sometime used to speed up the checkout process, and this is mainly achieved by storing the card details for future use
Follow Payment Technologies for more updates.
Thanks for reading. Feel free to comment
