{"id":55,"date":"2022-03-24T10:18:00","date_gmt":"2022-03-24T04:48:00","guid":{"rendered":"http:\/\/blog.payumoney.com\/?p=55"},"modified":"2026-02-26T15:48:14","modified_gmt":"2026-02-26T10:18:14","slug":"how-payment-gateway-integration-with-website-works","status":"publish","type":"post","link":"https:\/\/payu.in\/blog\/how-payment-gateway-integration-with-website-works\/","title":{"rendered":"How Does Payment Gateway Integration Work on Websites?"},"content":{"rendered":"

A payment gateway binds together all the stakeholders involved in a transaction with a buyer, merchant, buyer\u2019s bank and seller\u2019s bank. This is why it takes a long time for an individual to become fully comfortable in implementing a gateway in a website. A payment gateway integration is crucial for highly successful online transactions. So, we explain here the API calls that usually happen when making a transaction with a payment gateway.<\/p>\n

\"\"<\/p>\n

The image above shows the main integration steps.<\/p>\n

API Integration Steps<\/span><\/strong><\/h2>\n

Merchant website<\/strong><\/h3>\n

To initiate a transaction, the merchant generates a\u00a0POST REQUEST<\/strong>\u00a0(which is a particular mode of interaction on the internet). The request must include mandatory and optional parameters. The mandatory fields include a key (provided by gateway), txn ID (order reference number generated at merchant\u2019s end), amount product info, first name, email, phone, service_provider, and hash (checksum). Merchant also calculates a hash and sends it to the payment gateway.<\/p>\n

PayU Payment Gateway’s Website<\/h3>\n

When the POST request reaches PayU, the customer would be re-directed to payment gateway\u2019s (PayU\u2019s) payment page. The customer now selects the particular payment option on payment gateway\u2019s (PayU\u2019s) page (Credit Card\/Debit Card\/Net Banking etc)<\/a> and clicks on \u2018Make Payment\u2019. Now, payment gateway re-directs the customer to the chosen bank. The customer goes through the necessary authorization\/authentication process at bank\u2019s login page, and the bank gives the success\/failure response back to the\u00a0payment gateway<\/a>.<\/p>\n

    \n
  1. When the transaction POST request hits the payment gateway server, a new transaction entry is created in the database. To identify each new transaction in the gateway database, a unique identifier is created every time at gateway\u2019s end.<\/li>\n
  2. Our payment gateway marks the transaction status on the basis of response received from Bank.<\/li>\n
  3. A final transaction response is sent to the merchant through a\u00a0POST RESPONSE. In this response, the merchant would receive the final status of the transaction. Merchant will also receive the hash parameter here. This is done to strictly avoid any tampering attempt by the user.<\/li>\n<\/ol>\n

    Read more –<\/em> How to Integrate a Payment Gateway API into Websites<\/a><\/p>\n

    How Different Kits Ease The Payment Gateway Integration Process<\/b><\/span><\/h2>\n

    Different kits provide different APIs to automate a lot of tasks. PayU provides developers with two kinds of kits for easy integration\u2013 shopping cart integration kits and platform-based integration kits.<\/p>\n

    Shopping Cart Integration Kits<\/b><\/h3>\n

    Shopping cart kits follow an easy payment gateway integration procedure with the help of codes and APIs. Currently, the PayU provides more than 30 shopping cart integration kits. Some of which are:<\/p>\n

      \n
    1. Opencart<\/li>\n
    2. Interspire<\/li>\n
    3. Joomla VirtueMart<\/li>\n
    4. Magento<\/li>\n
    5. Prestashop<\/li>\n
    6. Zencart<\/li>\n
    7. CS-Cart<\/li>\n
    8. OScommerce<\/li>\n
    9. WordPress eCommerce<\/li>\n
    10. WordPress wooCommerce<\/li>\n
    11. Drupal Ubercart<\/li>\n
    12. WHMCS<\/li>\n<\/ol>\n

      Platform-Based Integration Kits<\/b><\/h3>\n

      PayU currently provides integration kits in 4 different environments<\/p>\n