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 16 Next »

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.

Data Table

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

Sr. No

Paramter

(Sample) Values

Description

Integration Kit

N/A

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

2.

API Documentation

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

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

4

Merchant Id 

 Merchant id provided by vendor.

5

Test Debit Card/ Net banking details

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. .

*Mandatory Columns

Please note: These parameter values would differ for the test and production environments, please get them separately.

Procedure

Steps

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. After which the details/ documents mentioned in the template would be provided by the vendor.

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

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

Validations

  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).

Do’s and Don’ts

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

Attachments

Following is the attached template for getting the details:

  • No labels