Payment Gateway Solutions

Integration with Payment Gateways for Online Shopping & Donations

A payment gateway is a software program integrated to a merchant's website to transmit transaction data to the credit card / Net Banking acquirer for authorization and settlement. Merchants gain the ability to perform real-time credit card authorizations from a web site over the Internet. Customers can pay for purchases across the Internet through credit cards within seconds, after the gateway obtains authorization from the credit card institutions.

In simpler words: A Payment Gateway is an e-commerce service that authorizes payments for e-businesses, online retailers, bricks and clicks or traditional brick and mortar. It is the equivalent of a physical POS(Point-of-sale) terminal located in most retail outlets. Payment gateways encrypt sensitive information, such as credit card numbers, to ensure that information passes securely between the customer and the merchant

Webbing Systems has expertise in integrating payment gateways like ccavenue.com & ccnow.com with built-in as well as custom programmed shopping carts developed in ASP.NET.

 

How payment gateways work

A payment gateway facilitates the transfer of information between a payment portal (such as a website) and the Front End Processor or acquiring bank, quickly and securely.

When a customer orders a product from a Payment Gateway enabled merchant, the payment gateway performs a variety of tasks to process the transaction, completely invisible to the customer.

For example:

Step 1: A customer places order on website by pressing the 'submit order' or equivalent button.

Step 2: The customer's web browser encrypts the information sent between their browser and the merchant's web server. This is usually done via SSL (Secure Socket Layer) encryption.

Step 3: The merchant then forwards the transaction details through to their payment gateway who hold the details of their merchant account. This is often another SSL encrypted connection to the payment server hosted by the payment gateway.

Step 4: The payment gateway who receives the transaction information from the merchant then forwards the information to the merchants acquiring bank.

Step 5: The acquiring bank then forward the transaction information to the issuing bank (the bank that issued the credit card to the customer) for authorization.

Step 6: The card issuing bank receives the authorization request, and sends a response back to the payment gateway (via the acquiring bank) with a response code. In addition to determining the fate of the payment, (i.e. Approved or Declined) the response code is used to define the reason why the transaction failed (such as insufficient funds, or bank link not available).

Step 7: 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 and a relevant response then relayed back to the customer.

The entire process typically takes 10-20 seconds

At the end of the bank day (or settlement period) the acquiring bank deposits the total of the approved funds in to the Merchants nominated account.