Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Introduction

  • The module acts as a liaison between eGov apps and external payment gateways.

  • It facilitates payments, reconciliation of payments, and lookup of transactions 'status'.

The major steps involved in order to achieve the functioning of the payment gateway are:

  1. URL has to be provided by the payment gateway team

  2. Users will be redirected to the provided URL in order to complete the payment.

  3. A success or a failure message is to be displayed and then the user would be redirected back to the portal.

*Please Note: A primary condition in choosing the vendor for integrating the payment gateway is that the payment has to go into separate bank accounts of every ULB.

The technical details on how to do the code changes and the service which are to be run can be found here.

Data Definition

The details that we require in order to integrate a payment gateway:

  1. URL from the payment gateway vendor.

  2. Bank account details from the ULB/State, which have to be collected here.

  3. IP address from where the module would receive the final status of the payment.

Procedure

Below mentioned are the details which would have to be exchanged in order to get the payment gateway configured correctly:

  1. Finalize a payment gateway vendor.

  2. Get the URL for the e-Gov App(Production).

  3. IP address from where the final status would hit the payment gateway API in order to get the final status of the payment.

  4. Get the bank account details in the required format from the ULB’s.

Since all the activity for enabling the payment gateway has to be done at the code level, so as such no template is required.

  • No labels