01
Problem first
We score the operating need, not the product page.
CashPrime Operations Advisor/Product fit check
Five operating signals separate the visible symptom from the real requirement. The result may confirm this product, connect it to another layer, or tell you not to buy yet.
Product fit check
We will test whether this product addresses the root requirement or only the visible symptom.
We score the operating need, not the product page.
A result can confirm, qualify, or reject the current route.
Hardware, controls, data, service, and workflow stay connected.
Continue the equipment journey
Compare fit, test capacity assumptions, then bring the shortlist into a deployment conversation.
Equipment fit
Equipment fit
Your operating scope travels with you
Explore and save equipment, ARKASH modules, and operating touchpoints to build a live decision brief.
A staffed cash room or customer deposit point needing receipts and controlled identity.
A 500-note feeder and 200-note escrow support batch deposits into a bag with nominal capacity up to 20,000 notes. A 10-inch touchscreen, receipt printer and camera options support supervised or self-service workflows. Specify the safe, identification components and bank-host application for your deployment.
A 500-note input and 200-note escrow separate presentation from acceptance. Test actual currencies, note condition, rejects and operator time before sizing the deployment.
Face and cash-slot camera configurations can associate deposit events with the transaction record. Define recording consent, retention and access permissions.
EMV card-reader and encrypted PIN-pad options support an agreed authentication workflow. PCI and EMV approvals apply to the selected components, not every part of the machine.
Manufacturer literature lists UL291 safe configurations. Confirm the delivered safe grade, locks, anchoring and component certificates against the insurer and bank requirements. A safe standard does not certify the cash bag or the complete software environment.
A staffed cash room or customer deposit point needing receipts and controlled identity.
Link deposits to bag or cassette custody and downstream reconciliation.
Configure the complete service, bank and software workflow before rollout.
Manufactured in China by
Shandong New Beiyang Information Technology Co., Ltd. (SNBC)
BDM-100
Official two-page CashPrime edition
Bring your note mix, peak workload and operating constraints. CashPrime will define the configuration, integration scope and acceptance test with you.
BDM-100 operating fit
BDM-100 combines a 500-note feeder, 200-note escrow, 20,000-note bag, cameras and NDC support for bank-lobby or high-control deposit journeys.
Acceptance checkpoint
Treat the machine, host, safe procedure and cash-removal process as one acceptance scope.
Best fit
Use it when the depositor, transaction, captured cash and receipt must be tied to a bank-controlled session rather than a stand-alone bag drop.
Integration test
Test timeout, partial acceptance, escrow return, communication loss, receipt failure and camera evidence with the target host before rollout.
Choose another model when
A smaller assisted-deposit machine can reduce footprint and complexity when card, PIN, camera and ATM-style session controls are unnecessary.
Turn the page into a testable decision.
Capture the workload, constraint and required evidence, then review the fit with an operations specialist.
Engineer the solution, not just the machine
UL291 and CEN safe requirements concern the approved enclosure, grade and configuration. Request the certificate reference, protection grade, locks and anchoring for each model. Plate thickness alone is not certification; a safe approval does not cover the bag.
Verify PCI approval for the exact encrypted PIN pad and EMV approval for the selected card reader, including version and validity. These do not automatically make the site, software or every device PCI DSS compliant. Options vary by model.
CEN/XFS is a software device interface, not a safe rating. Specify the service-provider version, device functions, operating system and host tests. NDC support or an available API does not prove bank or ARKASH integration is ready without implementation and testing.
Start the integration scope with device, transaction and storage-unit identity. Then connect deposits to collection, counting, differences and bank posting. Agree offline operation, replay without duplicate posting, approval permissions and data retention. Manufacturer software is not ARKASH; the project defines what is connected and tested.
Nominal specifications follow manufacturer literature; confirm the revision and delivered configuration in your quotation. Manufacturer reference · Complete solution