Scribd
Upload
226 views3 pages

Billdesk Sheet

This document describes the code flow for several payment gateway request and response pages. It includes: 1) BillDesk request and response pages which validate checksums, construct pipe separated strings for the payment gateway, and log data to a database. 2) A BillDesk-SI page for products with savings insurance which additionally sets the merchant ID and submits data to the payment gateway. 3) A Paytm page which checks the request domain, generates checksums, creates an XML log, and posts data to the payment gateway form. 4) A Paytm response page which reads the response, verifies the checksum, sets portal status values, and returns a piped string response to the portal

Uploaded by

Anonymous hB4J8ZTruE
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
226 views3 pages

Billdesk Sheet

This document describes the code flow for several payment gateway request and response pages. It includes: 1) BillDesk request and response pages which validate checksums, construct pipe separated strings for the payment gateway, and log data to a database. 2) A BillDesk-SI page for products with savings insurance which additionally sets the merchant ID and submits data to the payment gateway. 3) A Paytm page which checks the request domain, generates checksums, creates an XML log, and posts data to the payment gateway form. 4) A Paytm response page which reads the response, verifies the checksum, sets portal status values, and returns a piped string response to the portal

Uploaded by

Anonymous hB4J8ZTruE
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 3

** BillDesk Request page **

RU - Return URL
WO - Want Output
- "MType is used to moniter PG"
- "BilldeskPG" this is class used for PG
- "BILLDESK_WAP_RU" request URL page for billdesk.
- "BillDeskUrl" PG Url
- there two type of APP_TYPE given by PG are 1)WAP 2)WEB it is given by PG vendo
r.
- "AddLogService" object is used for loging data in DB.
- "PortalCheckSum" Sevice is used for checksum(Security) PG
- "TransactionService" Service is used to save or update transaction detail in D
B.
- Get Values from Previous Page assign to properties.
- Validated checksum for security purpose. eg-- Request.Form["txtPGCustCode"] =
oPortalCheckSumService.GetPortalCheckSum(oBilldeskPG.CUST_ID, oBilldeskPG.TXN_A
MOUNT);
- Form Pipe Seprated string as per requirement of PG using method "GetBillDeskEn
codedString".
Code Undestanding GetBillDeskEncodedString
- get value from config of BillDeskTypeField1,BillDeskTypeField2,BillDeskCurrenc
y
- get value of security Id and security Key.
- form pipe seprate string as per PG requirement.
- BILLDESK_WEB_KEY is added for security
- post pipe seprated string to PG DLL shared with us if it return true checksum
will be added to string.
- InsertBillDeskRequest by using this method data will be inserted in DB "common
portal"
- Finally request will be post to PG.
**BillDesk Responce page **
- "MType is used to moniter PG"
- We will recieve data in eg Request.Form["msg"]
- Assign value to properties from response "Msg"
- Get oldChecksum value by comparing "strArray.Length == 26" bcz in past msg len
gth was more than 26 so for safer side these check is added.
- Secret_Key is added accoding to merchant Id and then it is set in to string ar
ray
- SI value "PGSI" is replace by 1 if present else 0 two array is maintain strPro
cessedMsg and strFinalMsg this array carry same data which is recieved from PG
- strFinalMsg array is used for checksum and processed array is send to portal
- Finally request will be post to Portal.
** BillDesk-SI Request page **
-

"MType is used to moniter PG".


"BilldeskPG" this is class used for PG.
get list of SI product from config eg.BILLDESK_SI_PRODUCT_LIST.
Get Values from Previous Page.
set merchantID accoding to productID if It contain SI opted.
Validated checksum for security purpose. eg-- Request.Form["txtPGCustCode"] =
oPortalCheckSumService.GetPortalCheckSum(oBilldeskPG.CUST_ID, oBilldeskPG.TXN_A
MOUNT);

- Make Pipe seprated string eg.string BilldeskPipeString = oPortalCheckSumServic


e.GetBillDeskEncodedString(oBilldeskPG.APP_TYPE, oBilldeskPG.CUST_ID, oBilldeskP
G.TXN_AMOUNT, oBilldeskPG.ADDITIONALINFO1, oBilldeskPG.ADDITIONALINFO2, oBilldes
kPG.ADDITIONALINFO3, oBilldeskPG.ADDITIONALINFO4, oBilldeskPG.ADDITIONALINFO5, o
BilldeskPG.ADDITIONALINFO6, oBilldeskPG.ADDITIONALINFO7, oBilldeskPG.RESPONSE_UR
L);
- Get merchant-ID from string for logging purpose eg. oBilldeskPG.MID = strPipeA
rray[0].ToString();
- Bind URL to submit button
** BillDesk-SI Responce page **
- "MType is used to moniter PG"
- We will recieve data in eg Request.Form["msg"]
- Assign value to properties from response "Msg"
- Get oldChecksum value by comparing "strArray.Length == 26" bcz in past msg len
gth was more than 26 so for safer side these check is added.
- Secret_Key is added accoding to merchant Id and then it is set in to string ar
ray
- SI value "PGSI" is replace by 1 if present else 0 two array is maintain strPro
cessedMsg and strFinalMsg this array carry same data which is recieved from PG
- strFinalMsg array is used for checksum and processed array is send to portal
- Finally request will be post to Portal.

** PayTm Request page **


- "MType is used to moniter PG" current not present
- check wheather request is come from old or new domain string RedirectFlag = ""
;
if (strPrevUrl.Contains("netinsure")) //netinsure.
RedirectFlag = "O";
else
RedirectFlag = "N";
- required configuration is read from web config
- Get Values from Previous Page
- Generated XMl for logging purpose
- Portal Internal CheckSum Validation
- Generate Paytm CheckSumHash
- Set Control Values for final posting data to PG
- Data will be post in form of "form".
- bind postback url to btnsubmit
- Finally request will be post to PG.
** PayTm Responce page **
- "MType is used to moniter PG"
- Paytm give fix response on PaytmResponse.aspx page.
- paytm give us response in form of post.
- Read Response Parameters
- create XML for logging purpose
- PORTAL_STATUS_TEXT,PORTAL_AUTH_STATUS set response as per portal requirement.
- CheckSum Verified - Now Check for Payment Status
- Generate pipe seprated string for response to portal using "GetPipeSeparatedRe
ponseForPaytm".
- Get product URL to send response eg.HSP,HSTOP,Travel
- final response to portal
** CSC Request page **
- "MType is used to moniter PG" current not present

- Class is intialized.
- catch data from previous page
- check EMIMode if null then add full EMIMode type
- check EMIMode if null then add full EMIMode type
- Validate CheckSum recived in request and generated using portal checksum servi
ce

You might also like