Determining the best way to operate teller cash recyclers (TCR) in your branch environment can be difficult. Understanding the available options is an elemental part of making an informed decision. Today, I’d like to discuss deploying TCRs in a direct integration format.
Direct integration is frequently touted as the best option for deploying TCRs in retail branch environments. When successfully directly integrated, use of TCRs no longer requires double-key entries during transactions or balancing. Additionally, direct integration eliminates the need to support an additional application independent of the teller application. Unfortunately, direct integrations are often costly, proprietary to a manufacturer or application platform, and limited in terms of supported device functionality.
Pros
- Eliminate double keying – no intermediary between teller and device
- Supported by core – device supported / certified by teller app provider
- Enterprise rollout – often lower cost (licenses, fees) for larger rollouts
- Ease of use – limited adjustment to current teller workflow
Cons
- Universal API – often limits device performance and capabilities
- Hard coded / direct – costly and subject to long lead times
- Costly for core – app provider has limited incentive to “certify” devices
- Support – can create confusion relative to root cause – hardware or software issue?
Direct integration is widely considered the future of TCR integration. Taking into account the size and scope of your implementation plan in addition to identifying required device functionality will help you estimate the return on direct integration investment.