Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction

...

DIGIT has modules which require the user to pay for the service that he/ she is availing for example property tax, trade license etc. . In order to achieve the functionality we have a common payment gateway developed which acts a liaison between

...

DIGIT apps and external payment gateways( which depends on the clients requirements).

...

This module facilitates payments and lookup of

...

transaction status

...

**Please note:This is a sample table, the details mentioned in this are just for explanation purpose, not to be misused.

For every ULB this detail would have to be submitted across the state.

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.

Data Definition

Following is the description of various fields that are being used in the template:

  1. ULB Name : The name of the ULB for which the account is being taken into consideration.

  2. Bank Name : The name of the bank in which the payments collected from the citizen are to be transferred.

  3. Bank Branch : The Bank Branch city’s name where the account is stored.

  4. Bank Account Number: The account number of the branch where the amount is to be deposited.

  5. IFSC Code : Indian Financial System Code which is used to identify the bank branch which is participating in receiving the transactions.

  6. Account Type : The type of the bank account in which is the transaction is occurring(Savings/Current etc).

  7. Unique Code : This is the code of the ULB which is required by the payment gateway in order to facilitate multiple account transfer.

Validations

  1. Please make sure the vendor that is being chosen has to be the one which supports transactions into multiple bank accounts on the basis of tenantId(ULB).

  2. IFSC code should be of 11 digits.

  3. Unique code has to be of the format : <state code>.<ulb code>.

Attachments

Attached is the template of the bank account details which are required.

...

.

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 Table

For achieving the above mentioned steps we would be needing the below details:

  1. URL from the payment gateway vendor.

  2. Bank account details from the ULB/State.

Below mentioned is the table which is to be filled in with the data sent by the state/ ULB which is to be further sent to the payment gateway vendor:

...

Sr. No.

...

ULB Name

...

Bank Name

...

Bank_Branch

...

Bank_Account_Number

...

IFSC Code

...

Account_Type

...

Unique code

...

1

...

Dehradun

...

Axis Bank

...

Dehradun

...

02670200009851

...

UBIN0554391

...

 Saving A/C

...

uk.dehradun

...

2

...

Haldwani

...

Yes Bank

...

Haldwani

...

09170200009011

...

BARB0HALDWA

...

Saving A/C

...

uk.haldwani

Data Table

Following are the details required from the payment gateway vendor in order to configure the payment gateway:

Sr. No

Integration Kit

API Documentation

Redirect Working Key

Merchant Id 

Test credential of Debit Card/ Net banking

1.

File Name

File Name

XYZ#123

UDDUK

File Name

Note: Data given in the table is a sample data.

Procedure

Data Definition

Sr. No.

Column Name

Data Type

Data Size

Is Mandatory?

Definition/ Description

1

Integration Kit

Document

NA

Yes

This is a document that is sent by vendor which contains information on how to integrate the service.

2

API Documentation

Document

NA

Yes

This is a separate document which is sent by vendor in order to help ideally helps us to retrieve the transaction status.

3

Redirect Working Key

Alphanumeric

64

Yes

Working key is provided by vendor for the generation of redirection URL.

4

Merchant Id 

Alphanumeric

64

Yes

 Merchant id provided by vendor.

5

Test credential of Debit Card/ Net Banking

Document

NA

Yes

These are the details of the debit/credit card or net banking credentials which would help us test the gateway.

This contains the card number/Code/Account number etc. .

Steps to fill data

The payment gateway is a vendor oriented service that is integrated with different modules in order to facilitate the transactions. Below mentioned are the steps which are followed:

  1. Client has to finalize a payment gateway vendor( for example PAYU , paytm, HDFC, AXIS atc.) depending upon the requirements.

  2. Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.

  3. In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.

  4. After which the details/ documents mentioned in the template would be provided by the vendor.

  5. These details are to be received separately for both prod as well as UAT.

  6. Get the IP address for UAT and Production environments whitelisted from the vendor.

  7. Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.

Checklist

The checklist is a set of activities to be performed one the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.

Common Checklist

This checklist covers all the activities which are common across the entities.

Sr. No.

Checklist Parameter

Example

1

Make sure that each and every point in this reference list has been taken care of.

Checklist

Entity Specific Checklist

This checklist covers the activities which are specific to the entity.

Sr. No.

Checklist Parameter

Example

1

While finalizing a payment gateway vendor make sure that the vendor should support transactions into multiple bank accounts based on the key( which would be tenantid).

-

2

Do get the details for both the environments separately i.e UAT and Production.

-

Attachments

1.Configurable Data Template - Payment Gateway Configuration V1

View file
nameConfigurable Data Template - Payment Gateway Configuration - V1.xlsx