World Library  
Flag as Inappropriate
Email this Article

Payment gateway

Article Id: WHEBN0003187076
Reproduction Date:

Title: Payment gateway  
Author: World Heritage Encyclopedia
Language: English
Subject: EWay, ESewa, Netbanx, Payment service provider, Braintree (company)
Collection: Electronic Funds Transfer, Merchant Services
Publisher: World Heritage Encyclopedia
Publication
Date:
 

Payment gateway

A payment gateway is an e-commerce application service provider service that authorizes credit card payments for e-businesses, online retailers, bricks and clicks, or traditional brick and mortar.[1]

A payment gateway facilitates the transfer of information between a payment portal (such as a website, mobile phone or interactive voice response service) and the Front End Processor or acquiring bank.

Typical transaction process

When a customer orders a product from a payment gateway-enabled merchant, the payment gateway performs a variety of tasks to process the transaction.[2]

  1. A customer places order on website by pressing the 'Submit Order' or equivalent button, or perhaps enters their card details using an automatic phone answering service.
  2. If the order is via a website, the customer's web browser encrypts the information to be sent between the browser and the merchant's webserver. In between other methods, this may be done via SSL (Secure Socket Layer) encryption. The payment gateway may allow transaction data to be sent directly from the customer's browser to the gateway, bypassing the merchant's systems. This reduces the merchant's Payment Card Industry Data Security Standard (PCI DSS) compliance obligations without redirecting the customer away from the website.
  3. The merchant then forwards the transaction details to their payment gateway. This is another (SSL) encrypted connection to the payment server hosted by the payment gateway.
  4. The payment gateway forwards the transaction information to the payment processor used by the merchant's acquiring bank.
  5. The payment processor forwards the transaction information to the card association (e.g., Visa/MasterCard/American Express). If an American Express or Discover Card was used, then the card association also acts as the issuing bank and directly provides a response of approved or declined to the payment gateway. Otherwise [e.g.: a MasterCard or Visa card was used], the card association routes the transaction to the correct card issuing bank.
  6. The credit card issuing bank receives the authorization request and credit or debit checks and then sends a response back to the processor (via the same process as the request for authorization) with a response code [e.g.: approved, denied]. In addition to communicating the fate of the authorization request, the response code is used to define the reason why the transaction failed (such as insufficient funds, or bank link not available). Meanwhile, the credit card issuer holds an authorization associated with that merchant and consumer for the approved amount. This can impact the consumer's ability to further spend (e.g.: because it reduces the line of credit available or because it puts a hold on a portion of the funds in a debit account).
  7. The processor forwards the authorization response to the payment gateway
  8. The payment gateway receives the response, and forwards it on to the website (or whatever interface was used to process the payment) where it is interpreted as a relevant response then relayed back to the merchant and cardholder. This is known as the Authorization or "Auth"
  9. The entire process typically takes 2–3 seconds.[3]
  10. The merchant then fulfills the order and the above process is repeated but this time to "Clear" the authorization by consummating the transaction. Typically, the "Clear" is initiated only after the merchant has fulfilled the transaction (e.g.: shipped the order). This results in the issuing bank 'clearing' the 'auth' (i.e.: moves auth-hold to a debit) and prepares them to settle with the merchant acquiring bank.
  11. The merchant submits all their approved authorizations, in a "batch" (e.g.: end of day), to their acquiring bank for settlement via its processor.
  12. The acquiring bank makes the batch settlement request of the credit card issuer.
  13. The credit card issuer makes a settlement payment to the acquiring bank (e.g.: the next day)
  14. The acquiring bank subsequently deposits the total of the approved funds into the merchant's nominated account (e.g.: the day after). This could be an account with the acquiring bank if the merchant does their banking with the same bank, or an account with another bank.
  15. The entire process from authorization to settlement to funding typically takes 3 days.

Many payment gateways also provide tools to automatically screen orders for fraud and calculate tax in real time prior to the authorization request being sent to the processor. Tools to detect fraud include geolocation, velocity pattern analysis, OFAC list lookups, 'black-list' lookups, delivery address verification, computer finger printing technology, identity morphing detection, and basic AVS checks.

See also

References

  1. ^ "eCommerce: Payment Gateways". digitalbusiness.gov.au. Retrieved 20 November 2012. 
  2. ^ Gulati, Ved Prakash. "The Empowered Internet Payment Gateway" (PDF). Computer Society of India. Retrieved 22 May 2013. 
  3. ^ "eCommerce: Choosing your payment methods". digitalbusiness.gov.au. Retrieved 19 November 2012. 
This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and USA.gov, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for USA.gov and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
 
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
 
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.
 


Copyright © World Library Foundation. All rights reserved. eBooks from Project Gutenberg are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.