The document outlines the functional and technical requirements for a mobile banking solution that supports IMPS and UPI transactions. It includes requirements for supporting various platforms and communication modes, integrating with core banking and other systems, performing account-related and funds transfer functions securely, and providing personalization, maintenance, reporting and regulatory compliance capabilities. The bidder responds "yes" to indicate their solution meets each requirement.

1. Sr.
No
Functional Requirement for Mobile Banking Solution
,IMPS and UPI
Bidder's
Response
Remarks
1 Mobile Banking yes
1.1 Support : Platforms yes
1.2 Android yes
1.3 iPhone/iOS yes
1.4 Windows/JAVA (J2ME) yes
1.5 Any other platforms as per the latest technologies yes
2 Support: Communication Mode
2.1 GSM yes
2.2 CDMA yes
2.3 WAP/SMS/Web Browser yes
2.4 Any other technology implemented in future yes
3 Integration with Systems
3.1 Core Banking solution yes
3.2 ATM Switch yes
3.3 IMPS Switch yes
3.4 Internet Banking yes
3.5 SMS gateway yes
3.6 UPI/BHIM yes
3.7 BBPS (Bharat Bill Payment System) yes Integration
required
4 Support : Functionalities
4.1 Account Information yes
4.2 In case a customer has multiple accounts with the Bank, the
vetted list must be displayed, so that only authorized
accounts are shown.
yes
4.3 Balance Enquiry for all Accounts (SB, CA, CC, OD,
Loans, RD, FD etc.)
yes
4.4 Statement of Account yes
4.5 Mini statement yes
4.6 Cheque Status yes
4.7 Due date and instalment amount due for payment (For
Loan Accounts)
yes
4.8 Monitor Term deposit accounts yes
5 Should Perform following Transactions
5.1 Within own Accounts transfer yes
5.2 Third party account transfer within Bank yes
5.3 Interbank Fund Transfer via. NEFT / IMPS / RTGS /
UPI/BHIM etc.
yes
5.4 Fund Transfer for MMID / Account & IFSC Based (P2A /
P2P/ P2U) / P2M etc.
yes
5.5 Bill presentment and payment services through Bill
Aggregators
yes Integration
required
5.6 Fee payments Integration
required
5.7 Mobile Recharge Integration
required
5.8 Online ticket Booking service (IRCTC/ AIR/ Bus/Movie
etc.)
Integration

2. required
5.9 Online Tax payment / Govt. Duty payment / Statutory Fee
Payment etc.
Integration
required
5.10 Credit card bill payment for the bank’s customers as well
as other banks (aggregator services)
yes Integration
required
6 Support : Request Services
6.1 Request for ATM Debit card yes
6.2 Block debit card yes
6.3 Request for Internet Banking (Registration / Password Re-
generation)
yes
6.4 Request for TDS statement yes
6.5 Stop cheque Customizable
as per your
Requirement
6.6 Revoke cheque Customizable
as per your
Requirement
6.7 Request for Cheque book Customizable
as per your
Requirement
6.8 Email alert configuration yes
6.9 SMS Alert configuration yes
6.10 Reminders on schedule bill payments yes
6.11 View status of fund transfer yes
7 Content based services yes
7.1 Geo-location based Push / Notification Services Customizable
as per your
Requirement
7.2 Bank’s Branch locator integrated with Open Source Maps Customizable
as per your
Requirement
7.3 Bank’s ATM locator integrated with Open Source Maps Customizable
as per your
Requirement
7.4 New Product information (Configurable) Customizable
as per your
Requirement
7.5 IFSC search / lookup yes
7.6 New Product information (Configurable) yes
8 Personalization
8.1 Application support for customer preferred language Customizable
as per your
Requirement
8.2 Application support for Theme / Skin personalization Customizable
as per your
Requirement
8.3 Customer personalized default beneficiary list yes
8.4 Color coding for debit and credit figures in statement yes
8.5 Customer originated grouping of default transactions yes
8.6 Auto up-gradation of the Application as per OS version yes

3. 8.7 Recharge using phone book numbers Customizable
as per your
Requirement
8.8 Application capability to be refreshed to fetch details of
payees,billers account information, etc.
yes
8.9 Feature to provide M-Passbook through the application
wherein the customer can download a copy of the same
locally, depending on the storage capacity of the handset
yes
9 Integration with third party service providers/
software/middleware
9.1 National Payments Corporation of India (NPCI) for
Immediate Payment Services (IMPS) transactions
Customizable
as per your
Requirement
9.2 National Payments Corporation of India (NPCI) for
NUUP-USSD based mobile banking and transactions
Customizable
as per your
Requirement
9.3 National Payments Corporation of India (NPCI) for
Unified Payment Interface (UPI) transactions
Customizable
as per your
Requirement
9.4 National Payments Corporation of India (NPCI) for Bharat
Interface for Money (BHIM) transactions
Customizable
as per your
Requirement
9.5 Tie-up with third party service providers for Utility bill
payment/m-commerce/ value added services
Customizable
as per your
Requirement
9.6 Integration with any other specified Regulatory / Statutory
bodies for data submission and monitoring
Customizable
as per your
Requirement
9.7 Integration with the payment aggregators for the various
Merchant payments
Customizable
as per your
Requirement
9.8 Message format ISO 8583 /ISO20022 yes
9.9 Socket connection yes
9.10 Web services/XML over HTTP/HTTPS yes
9.11 SFTP, etc. yes
10 Registration and Download activity of mobile banking
application
10.1 Registration Method : Branch, ATM, Internet banking,
SMS Request, Multifunction KIOSK,Web portal
yes
10.2 Download URL sent in the SMS for successfulregistration yes
10.3 Google Play Store for Android/App Store for IOS (Apple) yes
10.4 Referralby active Mobile banking users yes
11 Security
11.1 Multi-factor authentication (PIN/OTP / CAPTCHA/
Security Question, etc.). Minimum Two factor
authentication
yes
11.2 One of the factors of Authentication shall be mPin or
higher
yes
11.3 Where mPin is used, end-to-end encryption of mPin is yes

4. mandated
11.4 Data transmission with end to end encryption (Standard
encryption algorithms like 3DES, AES, RSA, PKI scheme,
with minimum encryption strength of 256 bit)
yes
11.5 Platform support for SSL transactions and external
certifying authority
yes
11.6 Support to store data in the platform database in encrypted
format
yes
11.7 Application-level encryption should be facilitated over the
network and transport layer encryption to maximum extent
possible
yes
11.8 Application PIN for accessing the application and non-
financial transactions. (In case the customer forgot the
APIN,it should be generated online using ATM
authentication)
yes
11.9 MPIN for securing financial transactions (In case the
customer forgot the MPIN,it should be generated online
using ATM authentication)
yes
11.10 Ability to lock the application due to multiple incorrect
MPIN/APIN attempts,remotely block access,with auto
activation after 24 hours for accounts locked due to three
incorrect attempts
yes
11.11 Terminate mobile banking session and automatic log off
application after lapse of defined period of inactivity
(configurable) or when customer presses the back
button twice and application should prompt "please press
back button to exit"
yes
11.12 Auto blocking/locking of account upon reaching maximum
limit of defined transactions
yes
11.13 Audit trails and logging features available in Application
server,Web server and Database
yes
11.14 Ability to deny access to handset that does not meet
industry standard
Customizable
as per your
Requirement
11.15 Security alert on registered mobile number on account of
excessive activity in the Account
yes
11.16 Cross-border inward and outward transfer are prohibited.
Only Indian Rupee based domestic services should be
supported
yes
12 Scalability and Availability
12.1 No. of concurrent users the platform can support and
handle requests per Second
yes
12.2 Total time for a typical fund transfer transaction execution Yes
12.3 Restart or recovery process inbuilt in the application in the
event of transaction or process failure
yes
12.4 Control features within the application to ensure integrity
of data (input and update, maintained totals, audit trails,
error reports, etc.)
yes
12.5 Support available for load balancing circumstances yes
12.6 Application scalability to meet the future up gradations to
and all new handset/platform coming in the industry
yes
12.7 Application support to work on 2G/3G/4G/5G environment yes

5. / platform
12.8 Application capability to work on encrypted/non-
encrypted mode as per the requirement of the Bank
yes
12.9 Application platform support for native, hybrid-web,
hybrid combination (hybrid with additional native UI and
code capability) and mobile web app
yes
12.10 Block stolen handset number Customizable
as per your
Requirement
12.11 Change mobile number / handset Customizable
as per your
Requirement
12.12 Application should support simulator environment for
testing of new features across all devices and respective OS
yes
12.13 Capability of the proposed solution to push notifications
regarding new changes over the air without frequent
uploading on App store of various platforms
yes
13 Support and Maintenance
13.1 Provision to inform System downtime activity to the bank
48 hours before the schedule maintenance activity through
email
yes
13.2 Provision to send prior notification to Bank through email
and telephone, In case of exigency, if any unscheduled
system maintenance activity that needs to be carried out to
keep the system up
yes
13.3 Ability to provide a 365x24x7 telephone number and email
ID to be used for reporting
yes
13.4 Issues and problem resolution. Escalation matrix with
email ID and problem classification with time period for
resolution
yes
13.5 Availability of an experienced support team for quick
problem resolution and corrective measures
yes
13.6 Provision for Push notification of system down to
customers through the application over the air, if required
by Bank
yes
14 Statutory and regulatory requirements / enhancements
14.1 Ability of the solution offered to comply with all the
Operative Guidelines for Mobile Banking Transactions in
India issued by RBI/NABARD/NPCI and any other
regulatory body with any further guidelines and mandates
issued for Mobile Banking Transactions
yes
14.2 Ability to propose a version update plan with new
enhanced features with scheduled timelines of deployment
yes
15 Standard for Mobile banking solution
15.1 Mandatory compliance of the mobile banking application
with the PA-DSS guidelines/standards
Customizable
as per your
Requirement
15.2 The proposed mobile banking solution should offer
protection against the following specified risks:-
yes
15.3 Protecting customer’s sensitive information from exposure
to unintended third parties
yes

6. 15.4 Preventing identity impersonation from lost or stolen
mobile devices or device credentials
yes
15.5 Preventing account takeover or identity impersonation from
credentials harvested via key loggers or other malware
Customizable
as per your
Requirement
15.6 Prevent money laundering from the use of compromised
accounts
yes
15.7 The mobile banking solution should comply with the
security principles and practices for authentication of
mobile banking transactions as stated by The Reserve Bank
of India
yes
15.8 Capability of the Application to read SIM serial no. and
IMEI (International Mobile Equipment Identity) number
yes
15.9 Blacklisting/Blocking of older versions of the Application
on the back end, if there is a security breach
Customizable
as per your
Requirement
15.10 Security logging where all security events that
happen inside the application should be logged and sent
to the back-end server
Customizable
as per your
Requirement
15.11 Mobile system/setup should be capable to record every
type of transaction done by the customer with complete
detail (Like user id, mobile number, Financial transaction
details, Non-Financial detail like balance inquiry,
Statements, Cheque Book request,Card Block, etc).
Vendor should maintain the call detail at least for
the last one year
yes
15.12 Mobile Banking Application should be registered on such
device in which registered mobile number is used after
reading the Serial Number of SIM
yes
16 Reports / MIS, Reconciliation and Monitoring
16.1 Administrator Web portal for reports/MIS, monitoring and
reconciliation Reports
yes
16.2 Compliance of web portal with OWASP (Open Web
Application Security Project) standards/guidelines
yes
16.3 Provision to assign specific rights / privileges to platform
administrators for secure and restricted access
yes
16.4 Provision to create different user groups with different sets
of rights and permission
yes
16.5 Administrator Web portal capability for:- yes
16.6 Search customer record /Approving user creation/ Register
and De-register users for mobile banking application
/Terminate the users /Maintenance of activation requests
etc.
yes
16.7 The web portal support to work on maker and checker
concept for any addition, deletion, modification request
made by the authorized users
yes
16.8 Transaction wise report (with various filters such as type of
transaction / Mode of transaction / Amount wise / Branch
wise / Group wise / Financial / Non-Financial)
yes
16.9 Provision to download reports in standard formats namely
txt, xls, csv, xml, pdf, etc.
yes

7. 16.10 Provision for settling limits for each user / group. The
limits include per day/week/month/year limit, maximum
and minimum amount per transaction depending on the
type of transactions
yes
16.11 Provision to generate report for transactions monthly /
quarterly / half- yearly /yearly
yes
17 Compliance to Usability Audit - Best design practices to
benchmark
Customizable
as per your
Requirement
17.1 Branding, positioning and persuasion yes
17.2 Home screen / Layout and landing screens yes
17.3 Navigation yes
17.4 Information architecture yes
17.5 Graphics and Animation / Text yes
17.6 System User Dialogue and Forms yes
17.7 Accessibility /Task efficiency /Language yes
18 Fastag
18.1 Apply for Fastag Integration
required
18.2 Fastag Top-up Integration
required
18.3 Enable, disable Fastag Integration
required
18.4 View Details & Transaction History Customizable
as per your
Requirement
19 IMPS (Immediate Payment Service) Integration
required
19.1 IMPS Solution will support existing IMPS services through
Mobile Banking Application i.e. P2P,P2A,P2M, P2U, as
per latest IMPS specifications document issued by the
NPCI.
yes
19.2 IMPS solution will support exchange messages for IMPS
transactions with NPCI interface using ISO8583/ISO20022
or any other type used by NPCI.
yes
19.3 To provide standard API/services for realtime integration
with Banking channels & Merchants.
yes
19.4 The bidder’s IMPS solution will integrate, configure, and
support etc. with the existing IMPS switch initiate/perform
the transaction through Mobile Banking Application
Soultion.
yes
19.5 Bidder will provide comprehensive Annual Technical
Support. All software licenses and customization should be
covered under comprehensive ATS.
Bidder has to undertake Software upgrades during ATS
period as per Bank's requirement.
yes
19.6 Bidder should do Certification with NPCI for IMPS
services.
yes
20 UPI (Unified Payment Interface)
20.1 The architecture of the UPI solution should allow Bank’s
system to be easily integrated and the technology used
yes

8. should be easily adoptable and portable to the bank system
20.2 Integrate UPI with our all Alternate delivery channels such
as CBS, Data Ware House,FI Server, CMS, Mobile
Banking, Mobile Wallet, ATM switch, Internet Payment
Gateway etc.
Customizable
as per your
Requirement
20.3 Integrate of UPI application with Banks Analytics
solution, Fraud management solution etc.
yes
20.4 Merchant On-boarding portal, User Portal, Admin Portal,
Customer Complaint module, Marketing Module (Email,
SMS etc.) and other interface required to handle UPI
transactions.
Customizable
as per your
Requirement
20.5 Virtual Payment Address (VPA) Management yes
20.6 Application should be enabled with send/receive
notification through GCM (Google cloud Messaging) and
SMS
Customizable
as per your
Requirement
20.7 UPI Mobile Application should support UPI functionalities
as per NPCI specifications published on their website
during the contract period from
time to time
Customizable
as per your
Requirement
20.8 The UPI solution should have its own security features,so
it does not process any request that comes from outside
banking host system
yes
20.9 The system should have provision to provide front end for
capturing the outward UPI transactions with required AML
checks and Maker checker concept.
Customizable
as per your
Requirement
20.10 Additional features of the UPI solution yes
20.11 Enable / Disable on screen log yes
20.12 Enable / Disable file log yes
20.13 Reset on screen log yes
20.14 Complaint Management & Dispute Management Customizable
as per your
Requirement
20.15 Transactions per second TPS yes Reports
20.16 Number of success transaction yes Reports
20.17 Number of status unknown transaction yes Reports
20.18 Number of failed transaction with response code yes Reports
20.19 Status of original and Verification requests for a given
transaction
yes Reports
20.20 Business decline transactions for the day/month/year yes Reports
20.21 Technical decline transactions for the day/month/year yes Reports
20.22 No of ReversalProcessed (Debit & Credit) yes Reports
20.23 No of Registration Done for the day/month/year yes Reports
20.24 Profiling, Simulation and Debugging of UPI Scenario in
production by configuring at User Leveland/or Service
Level
yes APM
20.25 Reconciliation yes
20.26 The bidder will provide the Reconciliation Solution on per
transaction basis wherein the required reconciliation
software,hardware,database license, OS license or any
other licenses required for the application and the
manpower for reconciliation services is to be provided by

9. the bidder and to be sized adequately to meet the current
and projected requirement.
20.27 All successfulfinancial Transactions only performed
through all delivery channels (Mobile Banking, IMPS, UPI
and BBPS) needs to be considered for reconciliation.
Customizable
as per your
Requirement
20.28 The bidder to ensure security and confidentiality of the data
or information obtained from the Bank and should comply
with the IT security / IS policy of the Bank from time to
time.
Customizable
as per your
Requirement
20.29 The bidder needs to support Bank staff to handle all
delivery channel (Mobile Banking, IMPS, UPI & BBPS)
disputes.
yes
20.30 The bidder should provide a portal to Bank HO & Branch
staff generate all delivery channel reconciliations reports
(reconciled, un-reconciled as well as reports suggested by
Bank time to time, to register dispute all digital transactions
(IMPS,UPI,BBPS, AEPS,Payment gateway,ATM, BNA
etc.)
yes