Multi-Currency Exchange Kiosk Sourcing: 9-Point Checklist

Answer first: the nine specs that decide your FX kiosk quote

A multi-currency exchange kiosk quote only becomes comparable once nine items are frozen in writing: (1) the currency-pair matrix, (2) the cassette and denomination plan sized against your cash-in-transit cycle, (3) note-validation scope per series and orientation, (4) recycling vs dispensing-only vs accept-only architecture, (5) rate-display, rounding and stale-rate behaviour, (6) reconciliation and audit fields, (7) identity, AML and data-protection touchpoints, (8) environmental and serviceability requirements, and (9) MOQ, lead time and the change-order boundary. Items 1–7 change the bill of materials, the software scope and the support obligation — which is why a bid that looks cheaper before they are fixed usually is not cheaper after.

This page is deliberately not another "self-service FX kiosks are faster and more convenient" article. Vendor blogs and market-research landing pages already cover queue times, touchscreen usability and generic cybersecurity risk. What they do not give you is a pre-RFQ specification list: they rarely explain denomination-level cassette planning against a CIT cycle, almost never ask for a note-recognition dataset version, and typically say nothing about what the terminal does when the rate feed drops. Those three gaps are where FX projects actually lose money, so that is where this checklist sits.

Evidence note: no market-size, uptime, transaction-volume or ROI figure appears on this page, because no independently verifiable figure was available for this draft. Where a supplier quotes you a growth percentage or an availability target, ask for the source, the measurement period and the reference sites behind it before it enters your business case.

1. Freeze the currency-pair matrix before anything else

List every currency the machine must dispense , every currency it must accept , and which pairs are one-way versus two-way. A two-way pair multiplies the acceptor, cassette and reconciliation work; a one-way pair does not. Most cost overruns on this project type start with a matrix that was written in prose instead of as a table.

• Separate "accepts but does not dispense" currencies (tourist leftovers, low-volume notes) from full trading pairs. Many operators over-specify and then pay for cassettes they will never fill.
• Decide whether cross-rate display is required — for example showing a EUR→THB rate while the customer pays in USD. This is a software-scope item, and it usually surfaces late as a change order.
• Ask each supplier to state the maximum number of simultaneously supported currencies at controller and note-acceptor firmware level , not just what the enclosure can physically hold.

2. Size the cassette and denomination plan against your CIT cycle

Work backwards from peak-hour transaction count and average payout per transaction to a cassette capacity per denomination. Cassette count drives cabinet size, footprint and unit price more than the screen or the fascia ever will.

• Balance high-denomination cassettes (fewer refills, wide payout coverage) against low-denomination cassettes (better change accuracy, more refills).
• Model your cash-in-transit frequency explicitly. Recycling can reduce refill trips, but it adds note-fitness sorting and counterfeit handling that a dispensing-only build avoids. Do not accept a recycling recommendation that is not tied to your CIT schedule.
• Ask for the cassette removal and loading procedure, and whether cassettes are keyed, serialised and individually reported in the audit log. A cassette that cannot be identified in the log cannot be reconciled.

3. Specify note validation per series and per orientation — not "accepts local currency"

This is the item most often missing from a comparable quote. Note validation is not a yes/no feature; it is a dataset, a sensor set and an update obligation.

• Require the supplier to name the note-recognition dataset version and the series it covers, and to state in writing how updates are delivered when a central bank introduces or retires a series — remote push, service visit, or on-site USB upload.
• Cover mixed circulation: old and new series of the same denomination in the same cassette, plus heavily soiled notes. Ask what the acceptance threshold is, who configures it, and whether you can change it.
• Define the counterfeit-rejection policy: reject-and-return versus retain, what the machine logs, and what your operator is legally permitted to do with a retained note in that jurisdiction.
• Note validation involves both optical and magnetic sensing and is orientation-sensitive — a note fed upside down or backwards is a different test case. Build a physical note sample set covering more than one series and both orientations into the acceptance test.

4. Choose recycling, dispensing-only or accept-only — and price all three

Architecture determines cassette count, maintenance interval and reconciliation complexity, so it must be decided before quotes are compared rather than negotiated afterwards.

Ask every bidder to quote all three against the same currency matrix. A bidder who quotes only the architecture they prefer has removed your ability to compare.

5. Lock rate-display, rounding and stale-rate behaviour

Screen brightness does not protect margin; the rate-failure rule does.

• Specify the rate source, the refresh interval, and exactly what the screen shows when the feed fails — block transactions, apply the last known rate with a visible timestamp, or fall back to a manual rate. Choose one and write it into the acceptance criteria.
• Define rounding and payout rules per currency: smallest dispensable unit, rounding direction, and who absorbs the remainder.
• Confirm that the receipt carries the applied rate, its timestamp and its source.
• Decide whether rates are pushed from a central system or held locally — an integration-scope question that decides your middleware cost, not a UI question.

6. Define reconciliation and audit fields before software scoping

List the fields your back office needs per transaction: applied rate and source, currency pair, denominations dispensed, cassette IDs, note-validation result codes, operator ID, timestamp. Then require per-cassette reconciliation — opening count, dispensed, deposited, rejected, remaining — so a variance is traceable to a cassette rather than to a whole site.

Also ask how the kiosk behaves on a mid-transaction fault: what is reversed, what is retained, and what the audit event looks like. Finally, confirm export format and frequency. An audit log that cannot be machine-ingested is a recurring manual cost you will pay every month for the life of the estate.

7. Map identity, AML and data-protection touchpoints to each deployment market

Multi-currency exchange infrastructure carries inherent compliance exposure. The IMF working paper on a multi-currency exchange and contracting platform explicitly flags AML/CFT compliance risk and data-protection obligations — including GDPR-type national data protection law — as risks borne by operators of such systems ( IMF Working Paper 2022/217 ; a related PDF version is hosted by MIT Economics ). That paper describes platform-level infrastructure, not kiosk hardware rules — treat it as a risk framing, not as a specification.

• Translate it into kiosk specs: whether ID capture or document scanning is required, where data is stored, the retention period, and whether data stays on-device or goes to a host.
• Confirm with your own legal and compliance function which thresholds and reporting duties apply in each country. A supplier's assertion about local law is not your compliance basis.
• If card or contactless payment is in scope, require the payment module's PCI DSS scope statement in writing and confirm which party owns which part of that scope.

8. Set the environmental, physical and serviceability spec

• State indoor, semi-outdoor or curb placement, the ambient temperature and humidity range, and the required ingress protection for both cabinet and note path. Airport landside, corridor and curb positions are different builds.
• Specify screen size, brightness and — where the terminal sits in a queue line — a privacy filter so neighbouring customers cannot read the rate screen.
• Require a service access plan: which modules are field-replaceable, the target swap time, and whether the acceptor or recycler can be exchanged without removing the cabinet.
• Ask for the preventive-maintenance interval per module and the daily transaction volume that interval assumes.

9. Nail MOQ, lead time and the change-order boundary

• Get MOQ stated separately for the base platform and for custom items — custom cabinet, bespoke fascia, additional cassette positions. Custom tooling usually sets a much higher floor than the standard build.
• Ask for a lead-time ladder by quantity band and customisation depth, and identify long-lead modules (acceptors, recyclers, payment units).
• Define what counts as a change after design freeze and how it is priced. This is where FX budgets leak faster than on standard kiosk builds.
• Request warranty terms per module and a spare-parts availability commitment in years, and put both straight into the comparison table.

How to compare the quotes you get back

Build one table with identical rows for every bidder: cassette count and denominations, currency pairs, note dataset version and update mechanism, recycling architecture, rate-source integration, stale-rate behaviour, reconciliation export, payment scope, MOQ, lead time, warranty. Treat any bidder who cannot state a note-recognition dataset version or a rate-failure behaviour as incomplete , not as cheaper.

Then substitute procedure for statistics, because published reliability figures for this equipment class are scarce and difficult to verify. Ask each shortlisted bidder for a factory acceptance test plan covering a mixed-series note feed run, repeated cassette swap cycles and a deliberate rate-update interruption test — and witness it or request the signed report. Where possible, visit a reference site at a comparable deployment and ask the operator about refill frequency and fault response, not about satisfaction. Score on total cost across the cassette refill cycle, not on unit price.

Questions buyers ask before the RFQ goes out

How many cassettes does a multi-currency kiosk need?

There is no universal number: it follows from your denomination plan, the number of dispensing currencies and your CIT frequency. Derive it from peak-hour volume and payout per transaction, then confirm the controller's supported currency count before you approve the layout.

Can one kiosk accept and dispense several currencies at once?

Yes, subject to controller and firmware limits. Get that limit stated in writing alongside the currency matrix, and separate accepted-only currencies from full trading pairs so you are not paying for unused cassettes.

How does an FX kiosk handle old and new series of the same note?

Through the recognition dataset and its configuration. Ask for the dataset version, the series covered, the acceptance threshold, and the documented route for a central-bank series change.

What happens when the rate feed goes down?

Whatever you specified. Decide between blocking transactions, applying the last known rate with a visible timestamp, or a manual fallback — and make it an acceptance-test item rather than an assumption.

Next step: get the configuration sheet before the quote

Send this checklist back with your currency matrix and volume assumptions filled in. A configuration sheet answers items 1–7 in one pass and makes the first quote comparable instead of decorative.

Request a multi-currency configuration sheet and sample quote — and in the same reply ask specifically for the note-recognition dataset version, the verified rate-failure behaviour, and, if card payment is in scope, the payment-module PCI DSS scope statement. Those three answers will tell you more about the supplier than the enclosure render ever will.