i. S: For Successful transaction ii. F: For Failure Transaction. i. Returning string (B02) received and having status S and correct CIN.

(1)

e Payment Module

•

Process flow:

1. Dealer logs in on the Department’s website https://www.dvat.gov.in 2. Dealer clicks on e-payment option available on the website

3. Dealer selects the type of tax (VAT/CST) for which the payments have to be made 4. Dealer fills details in Challan - Tax Period (From Date and To Date), amount 5. Dealer clicks on 'Next' button

6. Dealer selects the bank through which the payment has to be made and presses the 'Proceed for Payment' button

7. Application connects to the respective bank’s website. Basic details will flow to Bank’s website in the encrypted form (String format mentioned below B01)

8. Dealer makes payment through internet banking on the website. The payment amount shall not be modifiable on bank’s portal

9. CIN number and transaction status (Success/Failure/Pending) will be send back to the tax department server along with the other details on real time basis in encrypted form. In case of transaction pending at checker level the return status shall be ‘P’. The final authorizer must complete the transaction on the same day otherwise transaction shall deem void. (String format mentioned below B02)

10. Department will generate and provide e-Challan to the dealers after successful transaction.

11. The banks need to upload Bank Transaction Scroll (Format mentioned below B03) on the Sales Tax Department website http://www.dvat.gov.in. This scroll have detail of all those transaction which is done based on today’s request from department site as well as all those transaction done at bank against the previous pending request.

12. Department will create Department Transaction Scroll based on Bank Transaction Scroll on real time. The file containing all the fields desired by Banks against the successful transactions only. This file is visible on our site with option of downloading.

13. The bank needs to send payment advice, branch scroll, and nodal bank scroll along with pay-out to RBI Delhi for successful transaction based on Department Transaction Scroll. In case of failure transaction according to Department Transaction Scroll, Amount collected by banks should be reversed.

14. Bank will also upload the branch scroll and nodal bank scroll which is sent to RBI on department site.

Business Logic:

Based on bank scroll, Department scroll will be generated on real time. In the departmental scroll, we maintain two types of status under final status.

i. S: For Successful transaction ii. F: For Failure Transaction.

Based on department scroll, Bank will send the data to the RBI for transaction which status is ‘S’, Reverse the payment, if payment is made for transaction which status is ‘F’.

Transaction Considered as Successful:

i. Returning string (B02) received and having status ‘S’ and correct CIN.

ii. Success Transaction status with correct TIN is obtained with specified period against the pending transaction.

(2)

All Transactions are considered as Failure which is not successful, like: i. Returning string (B02) not received due to any reason.

ii. All status other than ‘S’ and ‘P’ in the string returned by Bank (B02). iii.All status other than ‘S’ and ‘P’ in Bank Transaction Scroll (B03).

iv.Status is ‘S’ of the pending payments after date of expiry of that payment. v. Either CIN or Payment Date & Time is not provided or in wrong format as per

document and Status is even ‘S’ in Bank Transaction Scroll against pending payment.

Issues & Assumptions :

i. What happens if string B02 have the status as ‘S’ and B03 have different status than ‘S’?

Department issues the Challan against the successful transaction based on the string B02. Actually, Department consider the status of only those transaction from bank transaction scroll (B03) which is initially pending.

ii. Department have no information of RBI Date.

Bank will upload the scroll which he sent to RBI. By this we will be able to know the RBI Date.

• Format of Communicating String/ Report

1. String to be send to Banks by DVAT for initiating payment (B01)

S. No. Variable Name Description Data Type Length 1 MerchantID Merchant id, given by bank to our

department Text Maximum 25

2 TranReqID Transaction Request ID Numeric 15

3 PayReqDT Payment Date and Time in GMT (DD/MM/YYYY HH:MM:SS AM/PM)

Datetime 22

4 PayReqAmt Payment Amount Decimal 12,2

5 B01Checksum Checksum

Separator: ~ (tilde)

(3)

S. No. Variable Name Description Data Type Length

1 BankID Bank id, given by department to bank Numeric 3

3 PaidByBankAmt Paid Amount, (It will be zero in case of status is ‘F’).

Decimal 12,2

4 Status Status (S for success, P for pending, F for failure)

Char 1

5 CIN CIN/ Transaction Reference ID of Bank Numeric 22

6 PaidByBankDT Transaction Date with Time (DD/MM/YYYY

HH:MM:SS AM/PM) Datetime 22

7 B02Checksum Checksum

Separator: ~ (tilde)

3. Bank Transaction Scroll (B03)

S. No. Variable Name Description Data Type Length

1 BankScrollDate Scroll Date (DD/MM/YYYY) DateOnly 10

2 BankId Bank id, given by department to bank Numeric 3

4 PaidByBankAmt Paid Amount, (It will be zero in case of

status is ‘F’). Decimal 12,2

7 Status Status (S for success, P for pending, F for

failure) Char 1

5 CIN CIN / Payment Transaction Reference ID Numeric 22

6 PaidByBankDT Transaction Date with Time (DD/MM/YYYY HH:MM:SS AM/PM)

Datetime 22

Separator: ~ (tilde) File Format: .txt File Name: B03BANKIDDDMMYYYY 4. Department Transaction Scroll (B04)

S. No. Variable Name Description Data Type Length 1 MerchantID Merchant ID

2 PayReqDT Payment Date and Time by Department (DD/MM/YYYY HH:MM:SS AM/PM)

Datetime 22

3 TranReqID Transaction Request ID by Department Numeric 15

4 PaidByBankAmt Payment Amount Decimal 12,2

5 CIN CIN / Payment Transaction Reference

number by Bank text 22

6 PaidByBankDT Payment Date & Time as per Bank

(DD/MM/YYYY HH:MM:SS AM/PM) Datetime 22

7 BankStatus Status (S for success, P for pending, F

(4)

8 FinalStatus Transaction Final Status as recorded by the Department (S is successful, F is failure, P for Pending)

Text 1

9 TIN TIN Text 11

10 DealerName Name Text 150

11 DealerAddress Address Text 200

12 FromDT From Date (DD/MM/YYYY) DateOnly 10

13 ToDT To Date (DD/MM/YYYY) DateOnly 10

14 PaymentType Payment Type Text 15

15 TaxAmt Tax Amount Decimal 12,2

16 IntAmt Interest Amount Decimal 12,2

17 PenAmt Penalty Amount Decimal 12,2

18 ComAmt Composite Amount Decimal 12,2

19 OthAmt Other Amount Decimal 12,2

20 TotAmt Total Amount Decimal 12,2

Separator: ~ (tilde) File Format: .txt File Name: B04MerchantIDDDMMYYYY

•

Workflow Cases for BANK

In case workflow concept is applicable for the users, the Challan details and tax amount should be available to the approver for authorisation. Maker should be provided with the preview details with status as “Pending for approval”.

Pending approval list:

Checker/Approver should be able to view the preview details for verification at his end.

Last authoriser must provide authorisation within the time frame decided by the department and shall be reversed by the bank as per business logic defined by the department after department confirmation.

Challan Identification Number (CIN):

Challan Identification Number - unique reference number generated at banks end BSRCODEDDMMYYYYXXXXXX

BSRCODE – Seven-digit (7) BSR code of the branch (allotted by RBI) DDMMYYYY - Date of realization at the branch (8)

XXXXXXX - 7 digit running serial number for the Realization Date

•

Cut-Off time /CIN generation for Challan Payment:

Cut-off Mapping: 8:00 pm to 8:00 pm – Transaction posted after 08:00 pm will be considered in next working day.

Eg.

 Normal Cut-off Scenario: Transaction initiated on Monday after 08:00 pm to be considered for posting on Tuesday (provided Tuesday is working day).

 Transaction initiated on Saturday (after cut-off) 08:00 pm till Sunday 08:00 pm will be considered as Sunday Transaction date.

 The payment date/bank date should be same in Reconciliation report, E-scroll, CIN date should be the payout date if payment is done after the cut-off time.

(5)

• Sample Report to be sent for e-payment to RBI along with remittance pay-order /Cheque

o Branch Scroll each for VAT and CST o Nodal Branch Scroll each for VAT and CST o RBI Payout Daily Advice

<Formats for each to be attached> • Resource Sharing

• To be Provided by Bank

o Merchant ID for our department o URL for receiving the string B01

o URL for receiving Department Transaction Scroll (B04). o DLL for check sum. This DLL should have two methods.

 Encrypt: For encrypting string B01  Decrypt: For decrypting string B02

o Email ids data sharing. • Provided by Department

o Bank ID for the bank. (Provided after notification. Temp Bank ID will be provided for testing)

o URL for receiving the message B02.

http://www.dvatonline.gov.in/ onlinepayment /frmprintreceipt.aspx? R

eceipt=

o URL of the test server for uploading bank scroll through your temp bank id. http://www.dvatonline.gov.in/Bank/ onlinepaymen