SBI Enpanelment
SBI Enpanelment
SBI Enpanelment
OF
STARTUPS, FINTECHS, AND DIGITAL CAPABILITY
PARTNERS (DCPs)
FOR
DEVELOPMENT, CUSTOMIZATION, AND
INTEGRATION OF DIGITAL SOLUTIONS
Ref: SBI/CC/DB&T/DB&T-Retail/TI&SP/RFE/2024-25/02
Date: 22/07/2024
Schedule of Events
Page 2 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Page 3 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Part-I
Page 4 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Part-II
APPENDIX INDEX
A BID FORM
B EVALUATION CRITERIA
C BIDDER’S ELIGIBILITY CRITERIA
D BIDDER DETAILS
E NON-DISCLOSURE AGREEMENT
F TECHNICAL CAPABILITY REQUIREMENTS & SCOPE OF WORK
G PROFORMA OF CERTIFICATE TO BE ISSUED BY THE BANK
AFTER SUCCESSFUL COMMISSIONING AND ACCEPTANCE OF
THE SOFTWARE SOLUTION/ SERVICES
H QUERY FORMAT FOR BIDDERS
I FORMAT FOR SUBMISSION OF CLIENT REFERENCES
Page 5 of 68
RFE for onboarding of Startups, Fintechs and DCPs
1. INVITATION TO BID:
i. State Bank of India (herein after referred to as ‘SBI’ / ‘the Bank’), having its
Corporate Centre at Mumbai, various other offices (LHOs/ Head Offices /Zonal
Offices/Global Link Services, Global IT Centre, etc.) of State Bank of India,
branches/other offices, available at various locations and managed by the Bank
(collectively referred to as State Bank Group or ‘SBG’ hereinafter). This Request
for Empanelment (RFE) has been issued by the Bank on behalf of SBG for
empanelment of Startups, Fintechs & Digital Capability Partners (DCP).
ii. In order to meet the Software Solution/ service requirements, the Bank proposes to
invite online Bids from the eligible Bidders for empanelment as per details/scope
of work mentioned in Appendix-F of this RFE document.
iii. Bidder shall mean any entity (i.e. juristic person) who meets the eligibility criteria
given in Appendix-C of this RFE and willing to provide the Software Solution/
service as required in this RFE and subsequent Request for Quote (RFQ) to be
floated by the Bank. The interested Bidders who agree to all the terms and
conditions contained in this RFE may submit their Bids with the information desired
in this RFE. Consortium bidding is not permitted under this RFE.
iv. Address for submission of online Bids, contact details including email address for
sending communications are given in Schedule of Events of this RFE.
v. The purpose of SBI behind this RFE is to seek a detailed technical proposal for
empanelment of bidders for the Software Solution/ service desired in this RFE. The
proposed Software Solution/ Services must have the capabilities to integrate with
Bank’s existing infrastructure seamlessly, as and when the Bank desires to avail
these services under RFQs.
vi. This RFE document shall not be transferred, reproduced or otherwise used for
purpose other than for which it is specifically issued.
vii. Interested Bidders are advised to go through the entire RFE before submission of
online Bids to avoid any chance of elimination. The eligible Bidders desirous of
taking up the project for supply of proposed Software Solution/ service for SBI are
invited to submit their proposal in response to this RFE. The criteria and the actual
process of evaluation of the responses to this RFE and subsequent empanelment of
the successful Bidder(s) will be entirely at Bank’s discretion. This RFE seeks
proposal from Bidders who have the necessary experience, capability & expertise
to provide SBI the proposed Software Solution/ service adhering to Bank’s
requirements outlined in this RFE.
Page 6 of 68
RFE for onboarding of Startups, Fintechs and DCPs
viii. The RFE document shall be in two parts viz. Eligibility Evaluation & Category
Specific Technical Evaluation.
ix. A bidder may apply in more than one category provided they fulfill respective
eligibility criteria. If applying for more than one category, separate Category
Specific Technical Evaluation Form should be submitted for each applied
category.
2. DISCLAIMER:
i. The information contained in this RFE, or information provided subsequently to
Bidder(s) whether verbally or in documentary form/email by or on behalf of SBI, is
subject to the terms and conditions set out in this RFE.
ii. This RFE is not an offer by State Bank of India, but an invitation to receive
responses from the eligible Bidders.
iii. The purpose of this RFE is to provide the Bidder(s) with information to assist
preparation of their Bid proposals. This RFE does not claim to contain all the
information each Bidder may require. Each Bidder should conduct its own
investigations and analysis and should check the accuracy, reliability and
completeness of the information contained in this RFE and where necessary obtain
independent advice/clarifications. Bank may in its absolute discretion, but without
being under any obligation to do so, update, amend or supplement the information
in this RFE.
iv. The Bank, its employees and advisors make no representation or warranty and shall
have no liability to any person, including any Bidder under any law, statute, rules
or regulations or tort, principles of restitution or unjust enrichment or otherwise for
any loss, damages, cost or expense which may arise from or be incurred or suffered
on account of anything contained in this RFE or otherwise, including the accuracy,
adequacy, correctness, completeness or reliability of the RFE and any assessment,
assumption, statement or information contained therein or deemed to form or
arising in any way for participation in this bidding process.
v. The Bank also accepts no liability of any nature whether resulting from negligence
or otherwise, howsoever caused arising from reliance of any Bidder upon the
statements contained in this RFE.
Page 7 of 68
RFE for onboarding of Startups, Fintechs and DCPs
vi. The Bidder is expected to examine all instructions, forms, terms and specifications
in this RFE. Failure to furnish all information required under this RFE or to submit
a Bid not substantially responsive to this RFE in all respect will be at the Bidder’s
risk and may result in rejection of the Bid.
vii. The issue of this RFE does not imply that the Bank is bound to select a Bidder or to
empanel Selected Bidder, as the case may be, for the Project and the Bank reserves
the right to reject all or any of the Bids or Bidders without assigning any reason
whatsoever before issuance of purchase order and/or its acceptance thereof by the
successful Bidder as defined in Award Criteria and Award of Contract in this RFE.
viii. Bank reserves the right of discretion to change, modify, add to or alters any or all
of the provisions of this RFE and/or the bidding process at any stage of the process
of bidding/ RFE, without assigning any reasons whatsoever. Such change will be
published on e-tender website (https://etender.sbi/SBI/) and it will become part and
parcel of RFE.
ix. Bank reserves the right to reject any or all the RFEs received in response to this
RFE document at any stage without assigning any reason whatsoever and without
being liable for any loss/injury that Bidder might suffer due to such reason. The
decision of Bank shall be final, conclusive, and binding on all the parties directly or
indirectly connected with the bidding process.
Page 8 of 68
RFE for onboarding of Startups, Fintechs and DCPs
3. DEFINITIONS:
i. “The Bank/ Bank/ SBI” ‘means the State Bank of India (including domestic
branches and foreign offices), Subsidiaries and Joint Ventures, where the Bank
has ownership of more than 50% of voting securities or the power to direct the
management and policies of such Subsidiaries and Joint Ventures.
ii. “Bidder” means an eligible entity/firm submitting the Bid in response to this
RFE.
iii. “Bid” means the written reply or submission of response online to this RFE.
iv. ‘RFE’ means Request for Empanelment published by State Bank of India for
Empanelment of Fintechs companies.
Page 9 of 68
RFE for onboarding of Startups, Fintechs and DCPs
4. Eligibility Criteria
a. The Department for Promotion of Industry and Internal Trade (DPIIT), Ministry of
Commerce and Industry, GOI has issued G.S.R. 127 (E) notification dated the 19th
February 2019, in supersession of the Gazette Notification No. G.S.R. 364 (E) dated
11th April 2018, as modified vide Gazette Notification No. G.S.R. 34 (E) dated 16th
Jan 2019, which states that an entity should be considered a Start-up if it fulfils all
of the following conditions. An entity shall be considered as a Start-up:
An entity shall cease to be a Start-up on completion of ten years from the date of its
incorporation / registration or if its turnover for any previous year exceeds one hundred
crore rupees.
Page 10 of 68
RFE for onboarding of Startups, Fintechs and DCPs
iii. Conversion: Conversion of an entity from one form to another shall not be a
bar for availing recognition subject to the fulfilment of condition provided in
sub-section (3) of section 80-IAC of the Income- tax Act, 1961.
The date of incorporation / registration of the original entity will be considered
for calculation of the age of the entity and the age of the entity to not exceed
ten years from the date of incorporation / registration
Page 11 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Page 12 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Page 13 of 68
RFE for onboarding of Startups, Fintechs and DCPs
5. EVALUATION CRITERIA
The bids received in response to this RFE shall be evaluated by the Bank, as per the
evaluation matrix mentioned in Appendix B.
The bidders are required to score at least 70% of the total score in each criteria (General
and Specific). However, the Bank at its discretion may modify the cut-off scores for
one or both parameters and/ or for one or more categories. The same will be done
through corrigendum.
The bidders need to register themselves on the Bank’s API hub website
(https://apihub.sbi/portal/) to check the feasibility of using the readily available API’s
with the Bank.
Page 14 of 68
RFE for onboarding of Startups, Fintechs and DCPs
6. SCOPE OF WORK:
i. Through this RFE, the Bank is looking to empanel various start
up/FinTechs/Digital Capability Partner. The selection of the bidder will depend
on the Bank's requirements and the availability of relevant experience and
expertise from the bidder.
ii. The broad scope of work for inviting Request for Empanelment (RFE) for
empanelment of Start-ups/ FinTech/ DCPs Companies in various categories is
mentioned below
Page 15 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Note: The detailed Scope of Work for above categories are attached as an Appendix F (i
to viii). Failure to meet the requirements marked as Mandatory under SoW will lead to
disqualification.
Page 16 of 68
RFE for onboarding of Startups, Fintechs and DCPs
7. EMPANELMENT PERIOD:
If selected, the empanelment will be valid for a period of 3 years from the date of
empanelment. Irrespective of the period, the empanelment will deem to be operative
until close of assigned projects, and hence agencies deploying resources will be
required to ensure the availability of resources until completion of the work in hand or
till the extended period as per the respective project terms and conditions, if any project
is awarded to the empaneled vendor pursuant to RFQ or otherwise.
The Bank may conduct review of empaneled vendors at an interval decided by the Bank
and any of the conditions of this empanelment may be revisited during the review.
Based on the review, the Bank may terminate empanelment of any of the vendors. If at
any time it is found that the information provided for empanelment is false or if
irregularities shown by the bidder, Bank shall reserve the right to remove such vendors
from the empaneled list without giving any prior notice to the vendor in advance.
Page 17 of 68
RFE for onboarding of Startups, Fintechs and DCPs
in connection thereto, will be entertained and queries in this regard, therefore will
not be entertained.
v. Queries received after the scheduled date and time will not be responded/acted
upon.
Page 18 of 68
RFE for onboarding of Startups, Fintechs and DCPs
(a) The Bidder should quote for the entire package on a single responsibility basis
for Solutions/services it proposes to be empaneled for.
(b) While submitting the Bid, literature on the Solutions/services should be
segregated and kept together in one section.
(c) Care should be taken that the Bid shall not contain any price information. Such
proposal, if received, will be rejected.
(d) The Bid document shall be complete in accordance with various clauses of the
RFE document or any addenda/corrigenda or clarifications issued in connection
thereto, duly signed by the authorized representative of the Bidder. Board
resolution authorizing representative to Bid and make commitments on behalf
of the Bidder is to be attached.
(e) It is mandatory for all the Bidders to have class-III Digital Signature
Certificate (DSC) (in the name of person who will sign the Bid) from any of
the licensed certifying agency to participate in this RFE. DSC should be in
the name of the authorized signatory. It should be in corporate capacity
(that is in Bidder capacity).
(f) If deemed necessary, the Bank may seek clarifications on any aspect from the
Bidder. However, that would not entitle the Bidder to change or cause any
change in the substances of the Bid already submitted
(g) The Bidder may also be asked to give presentation for the purpose of
clarification of the Bid.
(h) The Bidder must provide specific and factual replies to the points raised in the
RFE.
(i) The Bid shall be typed or written and shall be digitally signed by the Bidder or
a person or persons duly authorized to bind the Bidder to the Contract.
(j) All the enclosures (Bid submission) shall be serially numbered.
(k) Bidder(s) should prepare and submit their online Bids well in advance before
the prescribed date and time to avoid any delay or problem during the bid
submission process. The Bank shall not be held responsible for any sort of delay
or the difficulties faced by the Bidder(s) during the submission of online Bids.
(l) The Bank reserves the right to reject Bids not conforming to above.
Page 19 of 68
RFE for onboarding of Startups, Fintechs and DCPs
iii. Prior to the detailed evaluation, the Bank will determine the responsiveness of each
Bid to the RFE. For purposes of these Clauses, a responsive Bid is one, which
conforms to all the terms and conditions of the RFE as a whole, without any
deviation.
iv. The Bank’s determination of a Bid’s responsiveness will be based on the contents
of the Bid itself, without recourse to extrinsic evidence.
Page 20 of 68
RFE for onboarding of Startups, Fintechs and DCPs
v. After opening of the Bids and preliminary evaluation, some or all the Bidders may
be asked to make presentations on the categories Bid for empanelment.
vi. The Bank can ask for a Proof of Concept (PoC)/ Technical Evaluation (TE). Any
cost incurred by the Bidder for conducting such PoC /TE will not be borne by
the Bank.
vii. If a Bid is not responsive, it will be rejected by the Bank and will not subsequently
be made responsive by the Bidder by correction of the non-conformity.
18. BANK’S RIGHT TO ACCEPT ANY BID AND TO REJECT ANY OR ALL
BIDS:
i. The Bank reserves the right to accept or reject any Bid in part or in full or to cancel
the bidding process and reject all Bids at any time prior to contract award as
specified in Award Criteria and Award of Contract, without incurring any liability
to the affected Bidder or Bidders or any obligation to inform the affected Bidder or
Bidders of the grounds for the Bank’s action.
Page 21 of 68
RFE for onboarding of Startups, Fintechs and DCPs
19. SERVICES:
i. All professional services necessary to successfully implement the proposed
Software Solution will be part of the RFE/Contract.
ii. The Bidder should also submit as part of Bid, an overview of Project Management
approach of the proposed product.
iii. Bidder should ensure that key personnel with relevant skill sets are available to the
Bank.
iv. Bidder should ensure that the quality of methodologies for delivering the services,
adhere to quality standards/timelines stipulated therefor.
v. Bidder shall be willing to transfer skills to relevant personnel from the Bank, by
means of training and documentation.
vi. Bidder shall provide maintenance support for Hardware/ Software/ Operating
System/ Middleware over the entire period of contract.
vii. All product updates, upgrades & patches shall be provided by the Bidder/ Bidder
free of cost during warranty and AMC/ ATS/ S&S period.
viii. Bidder shall provide legally valid Software Solution. The detailed information on
license count and type of license shall also be provided to the Bank.
ix. The Bidder shall keep the Bank explicitly informed the end of support dates on
related products/hardware/firmware and should ensure support during warranty and
AMC/ATS/S&S.
21. SUBCONTRACTING:
As per scope of this RFE if onboarded subsequently, sub-contracting is not
permitted.
Bank may issue RFQ to empanelled vendor as per the actual requirements time to
time. However, please note that empanelment of vendors should not be treated as a
Page 22 of 68
RFE for onboarding of Startups, Fintechs and DCPs
contract for the proposed work and the Bank reserves its right to select any of the
empanelled vendor or otherwise for proposed work at its discretions.
24. CONFIDENTIALITY:
Confidentiality obligation shall be as per Non-disclosure agreement (Appendix –
E).
Page 23 of 68
RFE for onboarding of Startups, Fintechs and DCPs
ii. Bidder is obliged to work closely with the Bank’s staff, act within its own authority
and abide by directives issued by the Bank from time to time and complete
implementation activities.
iii. Bidder will abide by the job safety measures prevalent in India and will free the
Bank from all demands or responsibilities arising from accidents or loss of life, the
cause of which is Bidder’s negligence. Bidder will pay all indemnities arising from
such incidents and will not hold the Bank responsible or obligated.
iv. Bidder is responsible for activities of its personnel or sub-contracted personnel
(where permitted) and will hold itself responsible for any misdemeanors.
v. Bidder shall treat as confidential all data and information about the Bank, obtained
in the process of executing its responsibilities, in strict confidence and will not
reveal such information to any other party without prior written approval of the
Bank as explained under ‘Non-Disclosure Agreement’ in Appendix-E of this RFE.
Page 24 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Page 25 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Page 26 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Without prejudice to the rights of the Bank herein above, if a Bidder is found
by the Bank to have directly or indirectly or through an agent, engaged or
indulged in any corrupt/fraudulent/coercive/undesirable or restrictive
practices during the bidding Process, such Bidder shall not be eligible to
participate in any EOI/RFE issued by the Bank during a period of 2 (two)
years from the date of debarment.
Vendor fails to abide by the terms and conditions or to maintain the required
technical/operational staff/equipment or there is change in its
production/service line affecting its performance adversely, or fails to
cooperate or qualify in the review for empanelment;
Page 27 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Employs a government servant or the Bank’s Officer within two years of his
retirement, who has had business dealings with him in an official capacity
before retirement; or
Any other ground, based on which the Bank considers, that continuation of
Contract is not in public interest.
31. NOTICES:
Any notice given by one party to the other pursuant to this Empanelment shall be sent
to other party in writing and confirmed in writing to other Party’s address. The notice
shall be effective when delivered or on the notice’s effective date whichever is later.
Page 28 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Part-II
Appendix–A
BID FORM – For Empanelment
[On Company’s letter head]
Date: ______________
To:
< Address of tendering office >
Dear Sir,
Ref: RFE No. SBI/CC/DB&T/DB&T-Retail/TI&SP/RFE/2024-25/02 dated 22/07/2024
We have examined the above RFE, the receipt of which is hereby duly acknowledged and
subsequent pre-bid clarifications/ modifications / revisions, if any, furnished by the Bank
and we offer to supply, Install, test, commission and support the desired Software Solution
detailed in this RFE as and when the Bank requests. We shall abide by the terms and
conditions spelt out in the RFE.
Page 29 of 68
RFE for onboarding of Startups, Fintechs and DCPs
any information / data / particulars proving to be incorrect, the Bank will have right to
disqualify us from the RFE without prejudice to any other rights available to the Bank.
vi. We certify that while submitting our Bid document, we have not made any changes in the
contents of the RFE document, read with its amendments/clarifications provided by the
Bank.
vii. We hereby certify that our name does not appear in any “Caution” list of RBI / IBA or
any other regulatory body for outsourcing activity.
viii. We hereby certify that on the date of submission of Bid for this RFE, we do not have any
past/ present litigation which adversely affect our participation in this RFE or we are not
under any debarment/blacklist period for breach of contract/fraud/corrupt practices by
any Scheduled Commercial Bank/ Public Sector Undertaking/ State or Central
Government or their agencies/departments. We also certify that we have not been
disqualified / debarred / terminated on account of poor or unsatisfactory performance
and/or blacklisted by any Scheduled Commercial Bank / Public Sector Undertaking /
State or Central Government or their Agencies / Departments at any time, during the last
3 years.
ix. We hereby certify that we (participating in RFE as OEM)/ our OEM have a support center
and level 3 escalation (highest) located in India.
x. We hereby certify that on the date of submission of Bid, we do not have any Service
Level Agreement pending to be signed with the Bank for more than 6 months from the
date of issue of purchase order.
xi. We hereby certify that we have read the clauses contained in O.M. No. 6/18/2019-PPD,
dated 23.07.2020 order (Public Procurement No. 1), order (Public Procurement No. 2)
dated 23.07.2020 and order (Public Procurement No. 3) dated 24.07.2020 regarding
restrictions on procurement from a bidder of a country which shares a land border with
India. We further certify that we and our OEM are not from such a country or if from a
country, has been registered with competent authority. We certify that we and our OEM
fulfil all the requirements in this regard and are eligible to participate in this RFE.
xii. If our Bid is accepted, we undertake to participate in RFE exercise for empanelment
at our cost, when called upon by the Bank to do so.
xiii. We, further, hereby undertake and agree to abide by all the terms and conditions
stipulated by the Bank in the RFE document.
______________________________________________________________
(Signature) (Name) (In the capacity of)
Page 30 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Appendix-B
EVALUATION CRITERIA
The bid will be evaluated using the evaluation categories mentioned below. Detailed
evaluation parameters with their weightages have been provided in the sections below for
your reference.
Page 31 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Total 70
Page 32 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Appendix-C
Page 33 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Page 34 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Page 35 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Appendix-D
Bidder Details
12. Accreditations
Seal of Company
Page 36 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Appendix-E
NON-DISCLOSURE AGREEMENT
(To be stamped)
2. For purposes of advancing their business relationship, the parties would need to
disclose certain valuable confidential information to each other (the Party receiving the
information being referred to as the “Receiving Party” and the Party disclosing the
information being referred to as the “Disclosing Party. Therefore, in consideration of
covenants and agreements contained herein for the mutual disclosure of confidential
information to each other, and intending to be legally bound, the parties agree to terms and
conditions as set out hereunder.
Page 38 of 68
RFE for onboarding of Startups, Fintechs and DCPs
not restricted by applicable laws) prior to such disclosure and shall comply with any
applicable protective order or equivalent. The intended recipients for this purpose
are:
i. the statutory auditors of the either party and
ii. government or regulatory authorities regulating the affairs of the parties and
inspectors and supervisory bodies thereof
(c) Confidential Information and Confidential Material may be disclosed, reproduced,
summarized or distributed only in pursuance of Receiving Party’s business
relationship with Disclosing Party, and only as otherwise provided hereunder.
Receiving Party agrees to segregate all such Confidential Material from the
confidential material of others in order to prevent mixing.
3. Rights and Remedies
(a) Receiving Party shall notify Disclosing Party immediately upon discovery of any
unauthorized used or disclosure of Confidential Information and/ or Confidential
Materials, or any other breach of this Agreement by Receiving Party, and will
cooperate with Disclosing Party in every reasonable way to help Disclosing Party
regain possession of the Confidential Information and/ or Confidential Materials and
prevent its further unauthorized use.
(b) Receiving Party shall return all originals, copies, reproductions and summaries of
Confidential Information or Confidential Materials at Disclosing Party’s request, or
at Disclosing Party’s option, certify destruction of the same.
(c) Receiving Party acknowledges that monetary damages may not be the only and / or
a sufficient remedy for unauthorized disclosure of Confidential Information and that
disclosing party shall be entitled, without waiving any other rights or remedies
(including but not limited to as listed below), to injunctive or equitable relief as may
be deemed proper by a Court of competent jurisdiction.
i. Suspension of access privileges
ii. Change of personnel assigned to the job
iii. Termination of contract
(d) Disclosing Party may visit Receiving Party’s premises, with reasonable prior notice
and during normal business hours, to review Receiving Party’s compliance with the
term of this Agreement.
4. Miscellaneous
(a) All Confidential Information and Confidential Materials are and shall remain the
sole and of Disclosing Party. By disclosing information to Receiving Party,
Disclosing Party does not grant any expressed or implied right to Receiving Party to
Page 39 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Page 40 of 68
RFE for onboarding of Startups, Fintechs and DCPs
(h) If any provision of this Agreement shall be held by a court of competent jurisdiction
to be illegal, invalid or unenforceable, the remaining provisions shall remain in full
force and effect.
(i) The Agreement shall be effective from _______ ("Effective Date”) and shall be valid
for a period of ________ year(s) thereafter (the "Agreement Term"). The foregoing
obligations as to confidentiality shall survive the term of this Agreement and for a
period of five (5) years thereafter provided confidentiality obligations with respect
to individually identifiable information, customer’s data of Parties or software in
human-readable form (e.g., source code) shall survive in perpetuity.
Name
Designation
Place
Signature
Name
Designation
Place
Signature
Page 41 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Appendix-F
2 Description of Be specific and only list those tangible Deliverables that will
Deliverables be provided to the Bank and list of Documents to be provided
along with Deliverables. Training & Training Plan (if
applicable) everything else should only be described in the
section on Services.
3 Third-Party Should describe all third-party items and materials to be
Components included or provided as part of any Deliverables
4 Term of the Include dates for start and completion of each phase of the
Project - Project Product/Services, and for delivery of each of the Deliverables
Schedule; with delivery locations
Milestones and
delivery
locations
5 Integration / a) Requirements of data conversion.
Migration
Page 42 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Page 43 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Based on the Scope of Work (SoW) for mentioned 8 categories of this RFE, the evaluation will
be carried out as per the below Scoring Matrix:
Absent / Cannot be
Readily Deployable Customizable
customized
2 1 0
Note: For Specific Evaluation criteria, the final score will be converted to weighted average
of 30 out of 100 and rest 70 is defined for General Evaluation Criteria.
Page 44 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Appendix-F(i)
Requirement
Sl No Requirements
Type
Bidder should be able to:
i. Implement a Fraud Risk Management solution to capture usage patterns
associated with the Digital Banking journeys and Transaction Acquiring
infrastructures (e.g., YONO/YONO lite, Internet Banking)
ii. Implement Risk Engine based on:
1 • Usage Parameters, Patterns captured by the proposed solution, Mandatory
• Parameters, Patterns, Profiles, etc., captured by the Bank’s application and
Transaction acquiring infrastructures to identify potential threats. (like
YONO/YONO lite, Internet Banking etc.,)
iii. Facilitate the implementation of Adaptive Authentication
iv. Provide an Integrated Operations Portal
v. Provide an Indicators of Compromise IP Repository
2 Proposed solution should be able to do Fingerprinting of both Device and User. Mandatory
3 Fingerprinted data should as far as possibly be maintained at the User’s device. Mandatory
Proposed solution should have Indicators of Compromise ‘IP Repository’ with
following details
i) Virtual Private Network (VPN) IPs
4 ii) TOR (The Onion Routing) IPs Mandatory
iii) Proxy IPs
iv) Malicious IPs
v) Blacklisted IPs
Proposed solution should be capable of capturing the below details
i. IP of the User
ii. Geolocation (Continent, Country, State/ County, City and ZIP/PIN Code)
iii. Latitude and Longitude coordinates
iv. ISP Details
v. User Device details (Browser, Operating System, etc.,)
5 vi. Keystroke Dynamics Mandatory
vii. Mouse Movement Use Patterns
viii. Touch Interaction Use Patterns
ix. Sensor Use Patterns (Gyroscope, Accelerometer, etc.,) Analytics
x. Malware Presence (If Possible, with limited permission available)
xi. Device Jail Breaking and Roofing
xii. Screen Sharing
Keystroke Dynamics and Touch Interaction Use Patterns should be learnt to
6 Mandatory
determine ‘Form Familiarity’ of the user
All the parameters must be captured & processed only with the consent of the
7 Mandatory
Customer
Page 45 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Page 46 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Page 47 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Comprehensive reporting
Event management including Alerts Configuration and Escalation
matrix
vi. Audit and Compliance:
Audit Trail management (search, filter, view, download)
Audit and Compliance management (search, view, filter, generate,
configure)
vii. Configuration:
Eliminate backend updates through Integrated Operations Portal
Implement ring deployment for all
features/services/functionalities
Bidder should be able to provide Real-time fraud detection and prevention using
34 Mandatory
device intelligence, behavioral analytics, and network validation.
Bidder should be able to detect money mule activities and other fraudulent
35 Mandatory
transactions.
Bidder should be able to provide secure transaction processing with real-time
36 Mandatory
approvals and anomaly detection.
Bidder should be able to ensure adherence to industry regulations and standards
37 Mandatory
like ISO 27001:2013
Bidder should be able to detect mule activities and behaviour for Individuals
using:
i. Identity validation
ii. Employment Details for Employed & Self-employed
38 Desired
iii. Financial Health
iv. Mobile, Email, Address intelligence
v. Identity & Device Intelligence
vi. Digital footprint
Bidder would be responsible to coordinate with Internal & External stakeholders
39 Desired
for development, implementation, operational activities, etc.,
Data Minimization approach by design should be opted across the application.
40 Desired
i.e., Capture data only what is relevant for Decision making.
Apart from reporting, User classification/ Profile information should be stored by
41 Desired
the proposed solution in the way deemed necessary by the Bank.
The parameters used to define the bank's policies and rules should be
customizable according to the bank's needs. If these parameters are not readily
configurable or available as part of the proposed solution, they should be captured
42 Desired
from the customer and/or the bank's applications. This includes transaction
acquiring infrastructures (like YONO/YONO Lite, etc.) and should be made
available for the bank's decision-making at no additional cost to the bank.
Wherever functionalities are not replicable/restricted in non-Production
43 environments, it is Bidder’s responsibility to provide simulation to mimic the Desired
production functionality.
Bidder shall also have the responsibility to upgrade and update the solution in part
44 or full to meet the latest Technology standards in terms of Performance, IT Desired
security and Operationalization of the solution during the Contract period.
Page 48 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Page 49 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Appendix-F(ii)
Requirement
Sl. No Requirement
Type
1 Conduct an environmental impact assessment to identify and mitigate potential Mandatory
risks and impacts on the environment.
2 Measurement of carbon footprint using globally acceptable standards. Mandatory
Build and develop templates to ensure periodic emissions calculations are
3 Mandatory
maintained by the Bank.
4 Track finance emission through a dashboard. Mandatory
Integrate carbon foot-printing and offsetting into the everyday banking
5 Mandatory
experience.
6 Solution to estimate daily carbon footprints based on the spending pattern. Mandatory
Vendor should provide a Green Score to users which gives the user a relative
indication of their carbon footprint. The score should be based on:
• Customer transactional data
7 • Customer non-transactional behaviour (e.g. – visit to branch for a transaction Mandatory
which could have been processed digitally)
• Questionnaire
• Any other basis that the vendor deems fit
Provide summarized and detailed view of per user footprints:
• Instant overview of the carbon footprint offered as part of the mobile banking
8 Mandatory
usage behaviour
• Filter by time period and category/ source
Vendor should show the average Green Score of other users and show insights to
the user on how they fair in their carbon footprint. E.g. – classify users in cohort’s
9 Mandatory
basis various demographic parameters and show to the user “Other users like you
have an average Green Score of 78/100”.
Provide customers with awareness, insight based on their carbon profile:
10 • Nudges and notifications on the carbon impact Mandatory
• Carbon Benchmarking
• Advice on how to spend more sustainably
11 Mandatory
User alternative actions and provides measurable outcomes based on which
special rewards or incentives can be awarded.
Ability to integrate with Bank’s Rewards program to provide the Green rewards
12 Mandatory
to customers.
Page 50 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Vendor should be able to design and run a rewards mechanism through which
points can be awarded to/deducted from a user’s account based on their spending
13 Mandatory
activities (award for spending that has less carbon footprint and deduct for
spending that has high carbon footprint)
The rewards program should include appropriate tiering and the vendor would
be required to manage the tiering program by showing the respective tiers to
14 Mandatory
users, benefits at different tiers, and incentivizing customers to improve their
score to earn more points and upgrade their tier.
The solution should be able to calculate the impact on Green Score of a customer
15 on a continuous basis, based on transaction carried out by the customer and/or Mandatory
any activity undertaken by the user
21 Vendor to take address all concerns related to Privacy and Data Security. Mandatory
The solution should seamlessly integrate with the various user journeys as
25 Mandatory
required by the bank.
The vendor should be able to seamlessly integrate with the bank’s MarTech
26 vendor and share information relevant for analyzing and recommending relevant Mandatory
products/services to customers.
Page 51 of 68
RFE for onboarding of Startups, Fintechs and DCPs
The vendor should be able to integrate with the bank’s OMP vendor to list the
27 Mandatory
sustainable brands on the online marketplace of the bank on its app and web.
Provide detailed action steps w.r.t. Carbon offsetting and green financial products
to improve their score/reduce their carbon footprints
28 Desired
• Carbon offsetting via certified program
• Eco-friendly financial product offers from the Bank
Ensure compliance with relevant laws, regulations, and industry standards in the
Sustainability/ ESG space. Below is a list of agencies/ standards to be followed
(This is not an exhaustive list and is only provided for reference purpose):
UNFFF
Exiobase
European Environment Agency
Greenhouse Gas Protocol
Verra
30 Desired
Ecoinvent
EPA – United States Environmental Protection Agency
Ademe – Agency for Ecological Transition
Global Logistic Emission Council
Smart Freight Centre Accreditation
ISO 14067, ISO 27001
AICPA SOC 2
Classification of Individual Consumption by Purpose (COICOP)
31 Developing and facilitating the use of carbon benchmarks and indexes. Desired
Page 52 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Appendix-F(iii)
Requirement
Sl. No Requirement
Type
Earn the Rewards
1 Generating rewards in form of Coins, vouchers, promocodes & Cashback Mandatory
2 Real time alerts on earning the rewards Mandatory
3 Generation of rewards for Online and Offline transaction / goals. Mandatory
4 Earn rewards via Gamifications (Spin wheels, Scratch Card, Quiz etc.) Mandatory
Ability to offer differentiated rewards as per the categorization of the customer
5 Mandatory
across all trigger points. (Like Premier / wealth customer)
Hyper personalize rewards capability on completing the time bound goal
6 Mandatory
achievement.
7 Rewards through referral programs Mandatory
8 Capability to combine rewards for a family and provide family curated campaigns Desired
Burn the Rewards
9 Real time redemption of rewards Mandatory
10 Redemption of rewards on online and offline transactions Mandatory
11 Capabilities to integrate with PG for redemption in part and full points Mandatory
12 Burn rewards via Gamification Mandatory
13 Should be able to make donation to charitable trust from reward points Mandatory
Portal / Microsite to be introduced to redeem the points accumulated and should
14 Mandatory
be desktop and mobile compatible
Ability to notify customer in advance regarding expiry of points and suggest
15 Mandatory
offers for redemption before expiry.
Miscellaneous
16 Unified accrual of rewards via various platform, INB, YONO & YONO Lite Mandatory
Reward program should provide financial incentive to customer to engage with
17 the bank’s products and services, Joint venture products, and other web/app Mandatory
sections such as updating the complete profile of user (illustrative)
Ability to run cohort based (identified customer segment) campaigns regarding
18 Mandatory
rewards and offers.
The Vendor would be required to propose in their rewards program plan, earn
19 and burn rates, which would be approved by the bank and revised on an ongoing Mandatory
basis as per the performance of the program.
Reporting: Vendor would be required to provide insights to the bank on
20 performance of rewards program, customer preferences, and transaction volumes Mandatory
by products/categories, data related to the tiering program, etc. (illustrative).
Capabilities to integrate through API /file based with Bank’s system as well as
21 Mandatory
with existing rewards program.
Page 53 of 68
RFE for onboarding of Startups, Fintechs and DCPs
22 Tie up with more than one payment gateway will be preferred. Desired
Appendix-F(iv)
Ensure that the aggregator provides a valid RERA registration number for the
3 properties listed. Mandatory
Security
After a pre-determined time of inactivity (for example, 1 minutes) payment session
1 Mandatory
time out period should be put into place
Analytics
Solution should offer real time customer transaction/purchase data, providing
1 insights into customer purchase behavior Mandatory
Compliance
The solution should be compliant with all the latest guidelines of the regulatory
1 authorities. During the contract period, the FinTech partner must make necessary Mandatory
changes in the solution to meet regulatory requirement changes free of cost.
Data Residency: The platform should be entirely hosted in the country ‘India’. All
2 data stored on the platform must always reside within the country ‘India’. Mandatory
Page 54 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Security events, audit trails and logs for administrators and user activity should be
3 enabled to monitor and detect suspicious activity. Mandatory
Solution provider must manage customer consent and appropriately update the
4 consent framework as and when required by regulators’ Mandatory
The proposed solution should comply with the Bank’s Data leakage prevention
measures / policies. In case the proposed solution requires integration with the
5 bank's systems, the solution provider should have data leakage prevention Mandatory
measures in place.
Solution provider must provide, maintain and support its software and subsequent
6 updates, upgrades and bug fixes such that the software is and remains secure from Mandatory
vulnerabilities.
The solution should be portable from cloud model to on-premises / Bank’s cloud
7 service provider, if required by the Bank. Mandatory
Page 55 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Appendix-F(v)
Analytics
1 Solution to offer real time user-behavior and providing insights on the same. Desired
Compliance
The solution should be compliant with all the latest guidelines of the regulatory
authorities. During the contract period, the FinTech partner must make
1 Mandatory
necessary changes in the solution to meet regulatory requirement changes free
of cost.
Data Residency: The platform should be entirely hosted in the country ‘India’.
2 All data stored on the platform must always reside within the country ‘India’. Mandatory
Security events, audit trails and logs for administrators and user activity should
3 be enabled to monitor and detect suspicious activity. Mandatory
Page 56 of 68
RFE for onboarding of Startups, Fintechs and DCPs
The proposed solution should comply with the Bank’s Data leakage prevention
measures / policies. In case the proposed solution requires integration with the
4 Mandatory
bank's systems, the solution provider should have data leakage prevention
measures in place.
Solution provider must provide, maintain, and support its software and
5 subsequent updates, upgrades and bug fixes such that the software is and Mandatory
remains secure from vulnerabilities.
The solution should be portable from cloud model to on-premises / Bank’s cloud
6 service provider, if required by the Bank. Mandatory
Vendor should provide an option to the user for booking test drive at the nearest Desired
12
dealership as per the pin code selected
Vendor should provide information on model/color/variant wise "availability" Desired
13 and "waiting time" of Car chosen by user
Vendor may provide "Challan check" feature Desired
14
Considering the increasing trend of EV Car purchases, Vendor should provide Desired
15 list of nearest EV charging stations as per pin code selected by the user
Page 57 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Appendix-F(vi)
Page 58 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Page 59 of 68
RFE for onboarding of Startups, Fintechs and DCPs
The bidder should be able to build in guardrails on collection outreach, with DRA
21 Mandatory
certified agents and regulatory reporting.
Bidder should be able to provide data security and compliance with regulatory
22 Mandatory
guidelines, and adherence to SBI's data security requirements.
Bidder should be able to provide digital full stack collections platform, digital
23 engagement channels, and managed services for on-the-ground activities like tele Mandatory
calling, CRM and field agent apps and it should be scalable.
The bidder should be able to provide AI based score basis behavioural data for
24 Desired
dynamic view on propensity to pay.
The bidder should be able to integrate with bot using NLP to have human like
25 Desired
engagement powered by speech recognition.
The bidder should be able to provide Humanize borrower relationships by
providing a debtor-centric and personalized debt resolution experience and
26 Desired
improve resolution rates on stressed assets and minimize non-performing loans
(NPLs).
Bidder should be able to enhance customer experience, focusing on providing a
27 frictionless and personalized borrower experience, considering the unique Desired
situation of each borrower, and offering tailored debt resolution options.
Demonstrate strong domain expertise and experience in the Indian banking
28
industry, with a proven track record of successful debt collection and recovery.
Establish a comprehensive debt collection and recovery process, including initial
stage, legal, and post-legal stages. Manage the legal recovery process, including
29 Desired
filing suits, representing the bank in court proceedings, and executing
decrees/orders.
Bidder should be able to optimize cost by optimizing the end-to-end recovery
30 workflow, including communication, tele calling, field collections, and legal Desired
procedures, to reduce operational costs and achieve economies of scale.
The bidder should collaborate with third-party service providers, such as credit
31 bureaus and legal agencies, to facilitate data exchange and streamline recovery Desired
processes.
Page 60 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Appendix-F(vii)
Sl Requirement
Requirements
No Type
The proposed solution must comply with NPCI (National Payments Corporation
1
of India) guidelines for UPI123/feature phone payments, RBI (Reserve Bank of Mandatory
India) payment guidelines and Telecom authority and Regulatory guidelines.
2 The Solution should provide Feature Phone Payments Mandatory
The Solution should handle IVR flow, user interaction and connection with Bank
3 Mandatory
switch.
The Solution should integrate Server-side common library activities and UPI PIN
4 Mandatory
Encryption as per the guidelines of Regulatory/Statutory/NPCI/Bank.
For voice-based payments, the Solution shall be able to support and recognize
5 Mandatory
user’s input and there shall be fallback option incase user’s voice is not captured.
The solution should be able to capture customer's voice/Key inputs during the UPI
6 Mandatory
123-UPI services on feature phone in IVR Solution session.
7 The Solution should have checks in place so that call conferencing while making
Mandatory
the payment is prevented.
The vendor must design & size the hardware required (Including Test /
Development / Training). The vendor should provide complete information on
hardware requirement for end-to-end solution. The vendor should provide the
8 hardware, software and network architecture of the solution offered by means of Mandatory
diagrammatic/pictorial representations, including the project plan for going live.
Vendor should also provide security set-up proposed in the solution and various
layers of risk identification and mitigation measures.
The solution must be enabled to perform post-facto audit of the UPI 123-UPI
9 Mandatory
services on feature phone process (customizable as per the Bank's requirement).
The solution shall ensure that the process is a seamless, real-time, and secured,
end-to-end encrypted audio interaction with the customer and the quality of the
communication adequate to allow identification of the customer beyond doubt
10 Mandatory
(Dependent State Bank of India infrastructure should be explicitly mentioned in
the response). The Solution shall have the user related & user input information
encrypted. End to End secured communication channel.
11 The solution should able to save the communication securely with date/time stamp. Mandatory
The solution should enable the State Bank of India UPI switch to carry out an
12 authenticity check in order to guard against spoofing and such other fraudulent Mandatory
manipulations.
The solution must possess real-time Dashboards capabilities to track UPI 123-UPI
13 Mandatory
services on feature phone activities through IVR Solution.
The solution must have a 3rd party Information Security Audit Report by a CERT-
14 Mandatory
in empaneled agency.
The solution must be capable of providing tracking dashboards & Reports on the
15 Mandatory
initiated UPI 123-UPI services on feature phone in IVR Solution sessions.
Page 61 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Data Residency: The platform should be entirely hosted in the country 'India'. All
16 Mandatory
data stored on the platform must always reside within the country 'India'.
Security logging: Security events, audit trails and logs for administrators and user
17 Mandatory
activity should be enabled to monitor and detect suspicious activity.
Application Security: Solution provider must provide, maintain and support its
18 software and subsequent updates, upgrades and bug fixes such that the software is Mandatory
and remains secure from vulnerabilities.
The solution should be compliant with all the latest guidelines of the regulatory
19 authorities. During the contract period, the successful vendor must make necessary Mandatory
changes in the solution to meet regulatory requirement changes free of cost.
The Bank's environment should not be shared with other clients. Bank should have
20 Mandatory
its own segregated environment.
The solution should have proper Business Continuity Plan.
21 As part of BCP, the solution should have Data Center & Disaster Recovery Center Mandatory
in different seismic zones and both should be hosted in India.
22 MIS Reports need to be customize as per Bank's requirement. Mandatory
The solution should be able to integrate with Bank's Security Operation Centre for
23 Mandatory
monitoring purpose.
The solution should be able to detect if the services are being used by the customer
24 Mandatory
using telecom services.
The solution should be portable from cloud model to on premise / Bank's cloud
25 Mandatory
service provider, if required by the Bank.
The solution should enable customers to avail IVR Solution based UPI services
using feature phone/smart phone. The IVR Solution interaction process should be
26 hassle free for the customer. The IVR Solution interaction request should be Mandatory
initiated by the end customer on the IVR Solution platform being provided for UPI
123-UPI services on feature phone.
IP Whitelisting: The solution provider must have the capability of IP whitelisting
to restrict platform access from a limited number of known locations / IP addresses
27 Mandatory
both for accessing the service as well as for accessing Platform administrative
consoles.
28 The solution should be capable to initiate reconnection in case of call drop. Mandatory
The solution architecture should allow to quickly scale up in case volume surges
29 Mandatory
up. Any limitation to future scalability should be mentioned in the response.
The solution should have the ability to compress the audio file with best possible Mandatory
30
compression technique.
31 The solution must support, rejection reason and drop off if any. Mandatory
32 The data should be stored in encrypted form with the Bank's encryption key. Mandatory
Page 62 of 68
RFE for onboarding of Startups, Fintechs and DCPs
The solution should able to capture/process customer data via API call from Bank's
33 Mandatory
system.
The solution should be able to configure feature phone/voice based UPI journeys
34 and not limited to (Registrations, de-registrations, P2P/P2M Payments, Bill Mandatory
payments, Balance enquiries etc.) separately and capture the response accordingly.
35 Reconciliation System shall be at Par with existing UPI system Mandatory
UPI services flow on IVR Solution should be customizable as per Bank's
36 Mandatory
requirement.
Solution should not store UPI payment data, Personal Information and/or Sensitive
37 Personal Data and Information (as defined under the Information Technology Act, Mandatory
2000), collected or received by them.
Solution shall comply with the laws of India, the rules and regulations
framed/issued thereunder, circulars and notifications issued by RBI (including
Storage of Payment System Data in India dated April 06, 2018), and the procedural
38 Mandatory
guidelines, circulars (including UPI operating circulars no. 115 & 133) and
instructions issued by NPCI, as may be applicable to them and/or issued in relation
to UPI, from time to time.
The solution should be multilingual enabled and support all languages (Assamese,
Bengali, Gujarati, Hindi, Kannada, Kashmiri, Konkani, Malayalam, Manipuri,
Marathi, Nepali, Odia, Punjabi, Sanskrit, Sindhi, Tamil, Telugu, Urdu, Bodo,
39 Mandatory
Santhali, Maithili and Dogri) as per 8th schedule of constitution and should ask
customer for their preferred language and show further instructions in his / her
preferred language.
The solution should support to provide multilevel disclaimers to the user at their
40 Mandatory
preferred language.
Bank should be able to play some product ad to the customer during the waiting
41 Mandatory
time.
The solution should provide connection quality indicator for both end (IVR &
42 Mandatory
Customer).
47 The solution should have ability to generate and record Transcript for conversation. Desired
Page 63 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Appendix-F(viii)
The translation of material must be done using proprietary solutions and personnel
Desired
5 within the selected vendor, not through automatic translation software such as Google
Translate.
Page 64 of 68
RFE for onboarding of Startups, Fintechs and DCPs
6 The Translation Software should support various file types such as Text, PDF,
Mandatory
HTML, and XML, etc.
The vendor should have the capability of extracting/converting the material to be
7
translated from one file format into another and return it in the file format as per the Mandatory
Bank's requirement.
8 Any errors in the deliverables must be corrected by the vendor free of charge Mandatory
immediately and corrected text must be submitted/updated immediately.
The necessary proof reading of the material translated for its authenticity will be the
9
responsibility of the translating vendor. In case of negligence, it will be the Mandatory
responsibility of the translating vendor.
The selected vendor is not permitted to reproduce, reprint, or transmit the content to
10
any third party by any means, including photocopying, photographing, cyclostyling, Mandatory
microfilming, scanning, electronic copying, or any other method.
11 The vendor would be required to translate and transliterate all the static/dynamic
Mandatory
pages of Mobile app/website/intranet etc.
The Translation Software should be capable of converting screens, reports and prints
12
including customer / employee names, designations and addresses from English to Mandatory
Multiple languages in all varieties of deployment viz., Online, batch and on demand.
The Translation Software should be capable of dictionary creation and maintenance
13
of Core Banking Application & any other Applications/screens, reports and prints in Mandatory
Multiple languages.
14 The vendor should be able to deploy software/solution as per the requirement of the Mandatory
bank.
The vendor should have the capability to proofread, verify, and vet the contents in all
15
languages as mentioned in Point.No.2 shared by Bank with 100% accuracy of the Mandatory
translation/content.
The vendor must ensure that all translated content is linguistically and culturally
16 appropriate, free from controversy, and compliant with the current laws of India.
Mandatory
Additionally, vocabulary, grammar, tonality, punctuation, and style should be
contextual and suitable as per the requirements.
17 The vendor shall update security patches, upgrades and resolve bugs if any found in
Mandatory
the provided application throughout the engagement period.
18 The vendor should ensure that the rich library of words and sentences created during Mandatory
the translation process should be shared with SBI.
Page 65 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Appendix -G
Date:
M/s._____________
_________________
Sub: Empanelment by the Bank for Your offer of Software Solution/ Services
RFE ref. No. _____________dated __________ for ________________
1. With reference to your bid for empanelment with the Bank for offering
Solution/Services under the requested category (ies) in pursuant to aforesaid RFE, you
have been shortlisted for empanelment under below mentioned category(ies), in
accordance with the RFE specifications:
Signature _______________________
Name _______________________
Page 66 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Appendix-H
Page 67 of 68
RFE for onboarding of Startups, Fintechs and DCPs
Appendix-I
Client Information
Particulars Details
Client Name (where solution is
implemented)
Client address
Size of Project
Value of Work Order (In Lakh)
(only single work order)
(Bidders to ensure that separate Appendix I is submitted for each reference they are
quoting for evaluation even if it pertains to the same company but for different
projects)
Seal of Company
Page 68 of 68