Payment gateway

From Wikipedia, the free encyclopedia
  (Redirected from Payment gateways)
Jump to: navigation, search

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]

It is the equivalent of a physical point of sale terminal located in most retail outlets. Payment gateways protect credit card details by encrypting sensitive information, such as credit card numbers, to ensure that information is passed securely between the customer and the merchant and also between merchant and the payment processor.[2]

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[edit]

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

  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 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 processor 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 does fraud 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.[4]
  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.

Security[edit]

  • Since the customer is usually required to enter personal details, the entire communication of 'Submit Order' page (i.e. customer - payment gateway) is often carried out through HTTPS protocol.
  • To validate the request of the payment page result, signed request is often used - which is the result of the hash function in which the parameters of an application are confirmed by a «secret word», known only to the merchant and payment gateway.
  • To validate the request of the payment page result, sometimes the IP of the requesting server has to be verified.
  • There is a growing support by acquirers, issuers and subsequently by payment gateways for Virtual Payer Authentication (VPA), implemented as 3-D Secure protocol - branded as Verified by VISA,[5] MasterCard SecureCode[6] and J/Secure by JCB along with Card Verification Value, which adds additional layer of security for online payments. 3-D Secure promises to alleviate some of the problems facing online merchants, like the inherent distance between the seller and the buyer, and the inability of the first to easily confirm the identity of the second.
  • Payment Gateway providers follow PCI DSS, the Payment Card Industry Data Security Standard, which ensure safety of the cardholder's data

See also[edit]

References[edit]

  1. ^ "eCommerce: Payment Gateways". digitalbusiness.gov.au. Retrieved 20 November 2012. 
  2. ^ "Processing Electronic Transactions with a Payment Gateway". Bank Card USA. Retrieved 22 May 2013. 
  3. ^ Gulati, Ved Prakash. "The Empowered Internet Payment Gateway". Computer Society of India. Retrieved 22 May 2013. 
  4. ^ "eCommerce: Choosing your payment methods". digitalbusiness.gov.au. Retrieved 19 November 2012. 
  5. ^ "Visa Australia - secure online shopping". Visa. Retrieved 19 November 2012. 
  6. ^ "MasterCard SecureCode". MasterCard. Retrieved 19 November 2012.