Device role first
Separate cash dispenser, cash recycler, STM / VTM, banking kiosk and broader branch self-service scope before comparing machines.
Banking Terminal Infrastructure RFQ Guide
ATM and CRS Replacement Scope Clarification What Banks Should Define before RFQ
Clarify ATM, CRS, cash recycler and smart branch self-service scope before supplier quotation. The machine category is only the first line of the RFQ; the real scope sits behind cash workflow, software stack, host / switch / CBS integration, lifecycle operations and local support.
Executive orientation
An ATM / CRS RFQ is not quotation-ready until responsibility boundaries are named.
A bank should not force suppliers to guess whether the request is hardware-only, hardware plus software, middleware integration, host / switch / CBS support, commissioning, local service or full lifecycle operations. Clear scope makes quotations comparable.
Cash workflow changes scope
Dispense, deposit, recycle, cassette logic, reject / retract handling and reconciliation affect both software and operations.
Software ownership is a commercial boundary
OEM ecosystem, multivendor middleware or existing bank software paths create different RFQ responsibilities.
Local support must be scoped
Warranty, SLA, spare parts, first-line support, Tier-2 escalation and issue evidence should be clarified before award.
Key takeaway
The machine category is only the first line of the RFQ.
The real scope sits behind cash workflow, software stack, host / switch / CBS integration, lifecycle operations and local support model. Treat PCI, EMV, XFS and cash recycling as evidence-request topics, not standards tutorials.
Responsibility boundary
Who should own what before ATM or CRS quotation?
The RFQ should assign responsibility across bank / buyer, software owner, middleware or system integrator, OEM / hardware supplier and local service partner before pricing.
Bank / buyer
Own the service role and acceptance criteria
The bank defines the business role, cash workflow, acceptance criteria, SLA expectations and approval path.
01
Device role
Cash dispenser, CRS, STM / VTM or banking kiosk scope.
→
02
Cash operations
Reconciliation, cash logistics and local requirements.
→
03
Acceptance
UAT, go-live criteria and evidence required before sign-off.
Software / middleware
Own the integration path only if scoped
ATM application, service providers, middleware, host / switch / CBS integration and monitoring are not automatically included in hardware pricing.
01
Software model
OEM ecosystem, multivendor middleware or existing bank software path.
→
02
XFS boundary
Service providers, device behavior, tests and defects need named owners.
→
03
Host integration
Switch, CBS and bank-side test access need scoped ownership.
OEM / local service
Own hardware, evidence and field support where contracted
Hardware configuration, module evidence, warranty, spare parts and local service must be priced explicitly.
01
Hardware modules
EPP, reader, dispenser, recycler, printer, safe and cassettes.
→
02
Evidence
PCI / POI, EMV or tender evidence should be layer-specific.
→
03
Local support
First-line support, spare parts, repair and escalation.
TermBridge framing
ATM / CRS replacement should be scoped as a responsibility map, not only a device list. Clear owner boundaries reduce supplier quotation ambiguity and post-award disputes.
RFQ scope checklist
Clarify these ten areas before requesting supplier pricing
Use these groups to turn an ATM / CRS replacement inquiry into a supplier-facing scope brief.
01
Device role
Define ATM, CDM, CRS, cash dispenser, cash recycler, STM, VTM or banking kiosk scope.
01
Is this replacement, expansion or new deployment?
02
Is the goal cash continuity or branch service migration?
03
Which functions are mandatory and which are optional?
02
Installation and access
Confirm physical model, access model and site readiness ownership.
01
Through-the-wall, lobby or freestanding?
02
Front access, rear access or back-loading?
03
Who owns site survey, power, network and commissioning prerequisites?
03
Cash handling
Clarify dispense, deposit, recycle, cassette logic and reconciliation.
01
What cash functions are required?
02
Who owns reconciliation and cash logistics?
03
What local cash handling requirements must be confirmed?
04
Software and integration
Separate hardware quotation from software, middleware and host responsibility.
01
Is the quotation hardware-only or hardware plus software?
02
Who owns XFS / middleware and ATM application?
03
Is host / switch / CBS integration in scope?
Project scoping handoff
Before final quotation, prepare the RFQ extract, target device role, installation model, cash handling assumptions, software and host integration owner, certification evidence, local support and SLA expectation.
Device-family boundary
Merchant payment terminal RFQ methodology →
This is a banking terminal infrastructure guide.
It is about ATM, CRS, cash dispenser, cash recycler, STM, VTM, banking kiosk and broader assisted-service banking terminal scope. It is not a POS, Android POS, PSP or merchant payment terminal RFQ guide.
Replacement scope path
Clarify cash workflow, integration and support before comparing ATM / CRS quotations.
A banking terminal replacement scope should connect device role, software ownership, host integration and local service responsibility before the RFQ becomes a price exercise.
01
Define the cash role
Separate cash dispense, cash deposit, cash recycling, reconciliation and branch service migration before requesting device pricing.
02
Map the software stack
Clarify OEM software, XFS or middleware ownership, host / switch / CBS connection, UAT and acceptance responsibility.
03
Assign operations ownership
Name the bank, vendor, integrator and local service partner responsibilities for commissioning, support and escalation.
04
Request evidence before price
Ask for applicable security, certification, service, warranty and spare-parts evidence before comparing supplier quotations.
ATM, CRS and cash operations
Device role, cassette logic, reject / retract handling, reconciliation and cash logistics.
XFS, middleware and host path
Service providers, controller software, middleware ownership, host testing and interface evidence.
SLA, warranty and field service
Installation, local support, spare parts, uptime measurement and escalation responsibility.
RFQ readiness signals
Why ATM / CRS replacement is not a quotation-ready phrase
If these boundaries are open, one supplier may price hardware only while another includes software, integration and support. The unit prices may look comparable but represent different scopes.
Device role is still unclear
The RFQ should say whether the bank needs a cash dispenser, cash recycler, cash deposit function, STM, VTM, banking kiosk or mixed self-service estate.
Installation model is not defined
Through-the-wall, lobby, freestanding, front access and rear-access models create different site, service and commissioning responsibilities.
Cash handling scope is incomplete
Dispense, deposit, recycle, cassette mix, reject / retract handling, reconciliation and cash logistics should be defined before quotation.
Software ownership is not assigned
The RFQ should define who owns the OS environment, service providers, XFS layer, middleware, ATM controller, host integration and UAT support.
Certification evidence is not scoped
PCI / POI and EMV evidence should identify the applicable component, software layer, approval reference and intended project scope where applicable.
Support responsibility is not operational
Warranty language alone does not define field operation, spare parts, escalation, remote diagnosis, uptime reporting or issue evidence.
Device role
Cash dispenser, cash recycler, STM, VTM or banking kiosk?
The first scope decision is the role of the banking terminal. A replacement inquiry should not treat every self-service banking device as the same RFQ.
Cash dispenser
Best scoped around cash-out service continuity, availability, card / PIN flow, receipt handling, security, monitoring and local support.
Cash recycler
Adds deposit, recycle, cassette logic, reject / retract handling, reconciliation, cash logistics and local cash-operation controls.
STM / VTM
Usually a service workflow project involving assisted service, remote teller support, onboarding, document capture or branch service migration.
Banking kiosk
May involve enclosure design, customized peripherals, application ownership, queue integration, authentication and field maintenance.
Banking device family
Banking self-service equipment families
Cash dispenser, CRS, STM / VTM and banking kiosk scopes should not be priced as the same machine category.
Cash dispenser / ATM
Cash-out service continuity, card / PIN flow, receipt handling, security and local support.
Cash recycler / CRS
Deposit, recycle, cassette mix, reject / retract handling, reconciliation and cash logistics.
STM / VTM assisted service
Remote teller, onboarding, document capture, authentication and branch service migration scope.
Banking kiosk
Modular enclosure, peripheral slots, document handling, QR / NFC and local field maintenance.
Installation and cash operations
Physical access and cash handling change price and responsibility
Installation and access model
A through-the-wall device can involve wall opening, fascia, secure area access, service space, cash loading process and site preparation. Lobby or freestanding devices may create different power, network, anchoring, visibility, security and staff-access assumptions.
The RFQ should state which model is required, whether site survey is included and who owns civil works, service access and site readiness.
Cash handling and reconciliation
CRS projects should define cash withdrawal, cash deposit, cash recycling, mixed denomination handling, cassette configuration, reject / retract handling, transaction journal requirements and reconciliation ownership.
Local cash-operation requirements may differ. The RFQ should require confirmation rather than importing another market's rule set.
Hardware modules
Do not rely on vague standard configuration language
The bank does not need an engineering bill of materials, but it should identify required modules, optional modules and evidence required for critical components.
Cash modules
Cash dispenserCash recyclerDeposit moduleCassettesSafe
Security / evidence modules
EPP / PIN padCard readerContactless readerAnti-skimming controlsNFCQR / barcode reader
Service / operations modules
Receipt printerElectronic journalCameraUPSSensors and alarms
Software stack and host integration
OEM ecosystem, multivendor middleware or existing bank software?
Hardware similarity does not define software compatibility. A hardware quotation may not include ATM application software, middleware, monitoring, licensing, device profiles, service provider validation, regression testing, host / switch / CBS integration, UAT or lifecycle support unless those items are explicitly scoped.
OEM ecosystem
The ATM supplier may provide hardware, service providers, application components or supporting software only if the RFQ names that scope.
Multivendor middleware
A software or middleware provider may own device access, service behavior, integration tests and defects where contracted.
Existing bank software
The bank may already own the application, switch connection, monitoring stack and production support model.
Integration boundary
ATM / CRS software stack and integration boundary
Hardware similarity does not define software compatibility.
cash dispenserrecyclerEPP / PIN padcard readerprintercamerasensors
XFS SPdriversdevice interface
middlewareATMCAPtransaction flowmonitoring adapter
host / switchCBScard managementmonitoring / TMS
UATgo-liveSLAspare partslocal supportremote support
Responsibility matrix
Who Should Own What Before ATM Or CRS Quotation?
This is not a legal contract. It is a scope clarification map for procurement, technology, integration, hardware and local service teams.
Responsibility Boundary Matrix Scroll horizontally on smaller screens to review every owner column.
| Scope area | Bank / buyer | ATM software or application provider | System integrator / middleware provider | OEM / hardware supplier | Local service partner | Clarification before RFQ |
|---|---|---|---|---|---|---|
| Device role and configuration | Defines service role, site type and mandatory functions | Confirms software fit for selected role | Reviews integration impact | Confirms model, modules and options | Confirms site service practicality | Is this cash dispense, CRS, STM / VTM or kiosk scope? |
| Cash handling and cassette logic | Defines cash workflow, reconciliation and controls | Supports transaction and journal logic | Maps reports or interfaces if needed | Confirms cassette, recycler and reject / retract capability | Supports loading or service process if in scope | What cash functions and reconciliation evidence are required? |
| Software stack model | Chooses OEM ecosystem, multivendor middleware or existing software path | Confirms application, licensing and feature scope | Confirms middleware and integration responsibility | Confirms OEM software, service provider and hardware compatibility scope | Confirms local support capability for the chosen software stack | Is the quotation based on OEM software, multivendor middleware or bank-owned / existing software? |
| XFS / service provider / device access layer | Requires evidence and owner clarity | Consumes device services in application flow | Owns middleware / SP behavior if contracted | Provides device SP / driver evidence where applicable | Reports field device behavior | Who owns SP versions, behavior, defects and test evidence? |
| ATM application / ATMC | Defines business flow and approval needs | Owns application / controller scope | Integrates with middleware or host paths | Confirms hardware compatibility | Supports field deployment if required | Is ATMC / AP included, existing or third-party? |
| Host / switch / CBS integration | Owns bank-side access, approval and test window | Supports message flow required by application | Owns interface mapping if contracted | Provides hardware / SP support only unless scoped | Usually not owner | Who connects to the host, switch and CBS test environment? |
| EMV / PCI / security evidence | States tender evidence requirements | Provides software / kernel evidence where applicable | Provides integration evidence if applicable | Provides component evidence for EPP / POI / reader where applicable | Maintains evidence handoff records if required | Which component or software layer does each evidence item cover? |
| UAT / commissioning / go-live | Owns acceptance criteria and sign-off | Supports application defects and test scripts | Supports integration defects and cutover | Supports device commissioning and hardware defects | Supports local installation and first visits | Who is present during UAT, commissioning and go-live? |
| SLA / warranty / spare parts | Defines SLA, uptime and warranty expectations | Defines software support scope | Defines middleware escalation scope | Defines warranty, OEM support and parts terms | Defines local spares, repair and response | What support is included after delivery? |
| Local first-line support | Defines branch / channel support model | Provides escalation path for software issues | Provides escalation path for integration issues | Provides hardware escalation path | Owns local inspection, swap or repair if contracted | Who handles first call, evidence capture and escalation? |
XFS and evidence scope
XFS support does not solve integration by itself
XFS and XFS4IoT should be treated as integration-scope topics, not proof that an ATM or CRS project is already integrated. The bank still needs ownership, testing and acceptance boundaries.
XFS / middleware questions
- Which service providers and peripheral devices are included?
- Who owns middleware, ATM controller or application behavior?
- Who connects to the host switch and prepares test cases?
- Who supports UAT, go-live and defects after commissioning?
Certification evidence checklist
- Ask for PCI PTS / POI evidence for the applicable EPP, PIN pad or other POI component where applicable.
- Ask what EMV evidence applies, and to which component or software layer.
- Confirm tender-specific and local evidence without implying country-specific legal advice.
Lifecycle operations
Delivery is not readiness
ATM / CRS replacement does not end at shipment. The RFQ should define support ownership across pilot, commissioning and live operation.
Warranty
Define what is covered, what is excluded, when warranty begins, who handles claims and whether local labor, remote support or component replacement is included.
SLA and uptime
Define service hours, response times, repair times, escalation process, remote diagnosis, reporting rhythm and how uptime is measured.
Commissioning and UAT
Define delivery, installation, site acceptance, UAT support, test case preparation, host / switch / CBS testing, go-live support and handover documents.
Smart branch expansion
Review Digital Branch scope → When ATM / CRS scope expands into Digital Branch
When the project includes STM workflows, VTM or remote teller service, QMS, account onboarding, document capture, instant card issuance, authentication, branch staff workflow or AI-assisted triage, treat the RFQ as a banking service workflow project rather than a narrow hardware replacement.
RFQ scope checklist
Use this checklist before asking suppliers for final pricing
Device role
- Is the project ATM, CDM, CRS, cash dispenser, cash recycler, STM, VTM or banking kiosk?
- Is this replacement, expansion or new deployment?
- Is the goal cash service continuity or broader branch service migration?
- Which functions are mandatory and which are optional?
Installation and access
- Is the device through-the-wall, lobby, freestanding or another model?
- Is front access, rear access or back-loading required?
- Who owns site survey and site readiness?
- Who owns installation, anchoring, power, network and commissioning prerequisites?
Cash handling
- Does the device dispense, deposit, recycle or only perform one cash function?
- What cassette mix is expected?
- How should reject and retract events be handled?
- Who owns reconciliation and cash logistics?
- What local cash handling and regulatory requirements must be confirmed?
Hardware modules
- Which EPP / PIN pad, card reader and contactless reader are required?
- Which cash dispenser, recycler or deposit module is required?
- Are receipt printer, journal, camera, safe, cassettes, NFC, QR / barcode, UPS or anti-fraud modules required?
- Which modules require evidence or approval documentation?
Software and integration
- Is the quotation hardware-only or hardware plus software?
- Who owns OS environment, service providers, XFS / middleware, ATMC or application software?
- Is NDC / DDC, ISO8583 or host / switch / CBS integration in scope?
- Who owns UAT and go-live support?
XFS / middleware responsibility
- What XFS support evidence is provided?
- Which service providers and peripherals are included?
- Who owns middleware behavior, test cases and integration defects?
- Is XFS4IoT or a newer service architecture relevant to the lifecycle plan?
Certification evidence
- What PCI PTS / POI evidence applies to the EPP, PIN pad or other POI component where applicable?
- What approval number, listing reference, version and validity period apply where applicable?
- What EMV evidence applies, and to which component or software layer?
- What tender-specific or local evidence must be supplied?
SLA, warranty and spare parts
- What warranty, local support and Tier-2 or OEM support are included?
- What spare parts pool is required?
- What response time, repair time, preventive maintenance and corrective maintenance are expected?
- How is uptime measured, and what end-of-life support is expected?
Delivery, commissioning and UAT
- Who delivers, installs and commissions the machines?
- Who supports UAT and host / switch / CBS testing?
- Who supports go-live and resolves open defects?
- What handover documents are required?
Project scoping handoff
- Prepare the current RFQ or tender extract.
- Name the target device role, installation model and cash handling assumptions.
- Name the software, host integration and XFS / middleware owner.
- List evidence, local support, SLA, UAT and go-live expectations.
Supplier assumptions
What suppliers should not be forced to guess
If these items are left unclear, the quotation may be cheaper but less useful. RFQ clarification prevents later disputes over what was included.
cash dispense only or cash recyclinghardware-only supply or software integration supportfront access or rear accesslocal first-line supportspare parts stockingcertification evidence for specific componentshost / switch / CBS integrationUAT support and commissioningcash reconciliation supportpreventive maintenance and uptime reporting
Project scoping handoff
Preparing an ATM / CRS RFQ before supplier quotation?
Share the device role, cash handling assumptions, software stack, host / switch / CBS integration boundary, evidence requirements, local support model and current RFQ extract. TermBridge can help turn the inquiry into a clearer supplier-facing scope.