ePayment

5.4.1

ePayment Introduction

• It is the process of electronic transfer of bill data between booking and payment office

• Department of Post collects bills on behalf of a biller through its Post offices and transfers the bill data electronically from booking office to the payment office where biller desires payment

• DOP earns commission such transaction• DOP and biller enter into a MOU for this purpose• Billers can operate at the divisional, regional, circle

level and on All India level also

5.4.2

• ePayment system is also used to process eVP, NPS and RMFS transactions

• Consists ofa) Post Office component – Meghdoot latest version & Communication client - ePayment client (for communication with central server)b) Web pages for Administrators, users of MIS and billersc) Central server component

ePayment Introduction

5.4.3

• “ePayment Collection” module enables collection of bills of various types from many persons for payment to one biller e.g. collection of all kinds of bills etc

• “e-Value Payable” module enables collection of money for cash on delivery type of transactions.

• NPS module enable acceptance of NPS transactions of various types

• RMFS module enables acceptance of amount for resetting from customers and payment to OEM vendor

ePayment Introduction

5.4.4

E Payment PO Using Meghdoot for:

•Bill Payments

•eVPP

www

Node with ePayment Client

Central Server

Directorate User

Circle User

Region User

Division User

Biller creation & MISBiller

Post office of Payment

ePayment Flow chart

5.4.5

• Different levels of administrators– Central (Directorate), circle, regional, divisional

level administrators• Billers to be created by administrators (All

India, circle, regional, divisional) • Biller data created is transmitted to all

ePayment offices depending on the level where created and available for bill collection in POS module

• Divisional administrators can register ePayment offices and monitor registration status

ePayment web componets

5.4.6

• Divisional administrator will create identity for each Post office and allocate username and password.

• The POs will use these credentials to register their office as ePayment office with central server

• Upon registration, Biller details, bill & barcode details etc will be received from Central server.

• Transactions will be carried out in Post Office (Point of Sale). A customer will be able to pay without presenting bill also.

• Receipts will be generated for each transaction just like other Meghdoot transaction.

ePayment Workflow

5.4.7

• Data of bills collected will be sent to central server from collecting office only after– adjustment of accounts by POS counter with treasurer– printing of submit accounts by PA in POS and– Verifying accounts by Supervisor in POS

• The ePayment client will send bill data to Central server in the next call; Calling hours can be pre-configured for automatic calls

• POs can verify data updation through following up the transaction MIS in the ePayment site

ePayment Workflow

5.4.8

• This data will go to Central server as booked figure• The central server will transmit the ePayment

collection data from various customers to the office of payment of concerned biller

• The designated office for payment to the biller will receive the information regarding bill collection from central server when it runs the ePayment client

• Payment is made to biller through treasury module• Payment figures will also go to Central Server on

running ePayment client by payment office.• Discrepancy report will be available with Central

Server.

ePayment Workflow

5.4.9

• Billers can view the amount collected for any period.

• MIS reports are available for various levels of administrators & also for general users

• On line payment will be allowed at post office if data is made available by the biller i.e. a customer coming without bill also will be able to make payment. Post Office can check from Central server the amount payable.

ePayment Workflow

5.4.10

• No biller can be created by Post Office• Biller created at one level will not be visible at

lateral level.• Central server captures hardware information

when office is registered and checks if data exchange only from the registered machine;

• If machine is changed, registration will fail and office cannot communicate with central server; elaborate procedure for re-registration has to be followed

Security Features

5.4.11

• Messages will be generated only after accounts has been tallied with treasury and supervisor verification at the collecting office.

• HOs concerned will have to submit the schedules of ePayment collection and payment through Accounts PBS module to PAOs

• Central server will tally the transaction figures with booked (schedule) figures and give discrepancy report ( Post Office wise).

Security Features

5.4.12

ePayment DO’s

• Always use the registered machine only as ePayment client, else transactions will not be authenticated in central server.

• Ensure that server is called daily. (at least twice a day before and after transactions).

• Ensure that every day transactions are properly reflected in ePayment MIS.• If any descrepancy is noticed in MIS figures, bring to the notice of System

administrator.• As the ePayment module is linked to other Meghdoot modules, always keep

all modules up to date by updating the patches released by CEPT Mysore in www.ptcinfo.org .

• Make the ePayment machine free from viruses by installing and updating suitable anti-virus softwares.

• Always ensure that submit account and supervisor verification is done promptly.

5.4.13

ePayment Don’ts

• Do not change the calling hours configured• Do not attempt registration of another system

as ePayment client• Do not close the ePayment client• Don’t delete any files from txd and rxd folders

5.4.14

Demo

• Demonstrate the acceptance of epayment transaction, data flow to central server, MIS and payment of the collection to biller

5.4.15

Practice

• Exercise 2.16.1

5.4.16