Guest Post: TradeHarbor on Voice Biometrics
Tuesday, February 9th, 2010This guest post is from Paul Heirendt, co-founder, president and CEO of TradeHarbor and is part of our voice biometrics announcement today. Visit the announcement page to watch a video interview with Paul Heirendt.
In today’s digital world we increasingly interact remotely, this has lead to increased risk and unprecedented growth in Fraud & Identity Theft, as well as convoluted business processes to attempt to manage the risk. Trust is difficult to establish in remote interactions and is extremely fragile. Without some level of trust – nothing meaningful will occur in a business or personal interaction. TradeHarbor’s mission since it’s founding in 1999 has been to “Enable Trusted Interactions”. The Voice Signature ServiceSM (VSS) is a decision support tool for the strong authentication of an individual’s identity in a remote interaction to establish the basis for trust. VSS enables authentication and document signatures over the telephone or web using any device or channel.
Voxeo’s leading edge approach to enabling the mash-up of web services and communications technologies makes them a perfect platform partner for the web service approach of TradeHarbor’s Voice Signature Service. Adopting a platform-agnostic and application-agnostic approach to Voice Authentication delivers a better ROI and more flexibility. This approach enables the rapid implementation of Voice Authentication to legacy applications and platforms that support an organization’s interactions with their customers. It also enables the organization to implement a consistent approach to authentication across disparate business units/product lines, communication modes (Internet & telephone), platforms (Touchtone IVR, Speech-enabled IVR, Live Operator, and Websites/pages) and locations (both owned and outside service providers).
Identity and Authentication are 2 very different things:
- Identity is the data that uniquely represents who you are (Social Security Number, Passport Number, Driver’s License Number, membership number, account number, phone number, email address, etc.)
- Authentication is the assurance that you really are who the data represents that you are.
Identity management without strong authentication is dangerous and has very little business value. The risk in depending on the identity assertion is lowered when biometric voice authentication of an individual provides the required confidence to take action. The confidence level required to take action can vary from interaction to interaction based on many factors – the ability to balance these factors dynamically is a key to lowering risk without impacting user convenience.
TradeHarbor’s Voice Signature Service (VSS) provides the core Voice Biometric functions as a Decision Support Web Service:
Decision Support – business rules can be established and adapted over time to consider such risk factors as: the value of the transaction, the fraudrisk profile of the transaction, the history of that customer, etc.
Ease of integration – application developers can deploy Voice Biometrics as a component of their voice or web application using VSS by invoking a simple Web Service API without having to understand the science, statistics, tuning or professional services required in biometric software deployments.
Interoperability – the VSS Web Service API can be invoked on IVR and Voice Platforms using VoiceXML subdialog calls, an xml interface, or on webpages or web-based applications using server-side scripts. The VSS Web Service API enables a consistent approach to strong authentication and business rules across all of the customer touch points.
Balance Convenience and Security – the VSS returns a “Normalized Confidence Score” enabling a real-time risk decision capability. This allows an application to dynamically select the decision threshold on a transaction-by-transaction basis using the VSS score combined with any other factors available to the application.
Anonymous Authentication – The VSS approach to voice authentication does not use or expose any identity information, personal health information or personal financial information.
Legally-binding Signatures – every VSS interaction constitutes a legally binding signature – meets the American Bar Association guidelines for a Legally-binding signature. The VSS provides: Authentication of the individual using the unique biometric characteristics of the user’s voice; Authorization through a provable cooperative act; and an Audit capability to provide proof for repudiation.
Regulatory Compliance – The VSS provides strong authentication to meet regulatory requirements for financial and health transactions.
Voice Signature Service API Interfaces:
The VSS Service is built with the objective of providing easy access for a broad range of applications via simple XML or VXML interfaces, so that multiple applications can readily share the same registry of enrolled voices without the burden of adding and integrating a unique voice authentication system for each application.
The VSS Web Service only accepts service requests from valid Requesters (Requesters with a current VSS SLA) through XML or VoiceXML sub-dialog calls, through secure communications over the Internet using SSL, TLS/SSL, VPN, or other protocols. Communication can also occur over a dedicated connection between the Requester and VSS, such as ATM, Frame-Relay, dedicated T1 or other methods as specified by the Requester and agreed to by TradeHarbor in the VSS SLA.
The VSS API supports both VoiceXML (VXML) and XML interfaces.
- The Voice Signature ServiceSM system (VSS) supports VXML v2.X. A VSS Session is implemented through a VXML sub-dialog call.
- The VSS also supports XML for implementation as a Web Service or with legacy IVR platforms (that may not be VXML compliant).
- The VSS VXML sub-dialog has been tested with, and is currently supporting transactions on the Voxeo platforms and hosted services.
A VoiceXML integration of the VSS is typically accomplished in less than 1 hour using 3 basic subdialog calls: 1. register_identity_claim.vxml subdialog registers a new identity claim (identity_claim) for use in subsequent enrollment and verification sessions. An identity claim must be registered before a Speaker can enroll his/her voice during an enrollment session. (Note: block registration is available for multiple registrations) 2. create_vss_session.vxml subdialog begins a Voice Signature ServiceSM (VSS) session to either enroll or verify the User. The subdialog will validate the identity_claim and return a VSS session ID = session_id. (An example session ID: 4589-2973-9475-4EA5-9B0B-5306-55CF-76CA.) 3. complete_vss_session.vxml subdialog handles the dialog management for passing the prompts for the platform to play for the user, receiving the recorded user responses from the platform, and when the VSS session is complete, returns the Results Variables and dialog control to the VoiceXML application.
The VoiceSig Express (VSE) API is designed to support webpage or web-application implementations by providing the telephony interface. The VSE API supports two basic telephone interactions – an inbound Call and an Outbound Call invoked through server-side scripts = create_inbound_session, or create_outbound_session and get_session_results . TradeHarbor provides sample scripts in PHP, Perl, Java, Ruby, and others.
The primary development effort in designing and deploying applications that use the VSS for voice authentication or remote Voice Signatures is related to the changes required to the UI (User Interface) or VUI (Voice User Interface) to meet the human factors issues associated with introducing Voice Signatures to new users and properly handling VSS confidence scores that are lower than the threshold required by the specific application in the specific interaction or call context.
Summary:
TradeHarbor offers the VSS as a Web Service (Software as a Service), which makes it simple, quick and inexpensive to implement and which enables interoperability across a business enterprise for all types of Internet, telephone and mobile platforms. While the core VSS interactions remain uniform, the applications supporting various business processes can tailor how the VSS is used: the point in the business process when the VSS is invoked; the “Signature Statement” associated with a document signature or authentication; and balancing the desired security / convenience for an interaction based upon the unique risk and value characteristics of each individual interaction or transaction. The Signature Statement heard in the Voice Signature session can be tailored for each transaction or document type to ensure that the signer is aware of any associated terms and conditions, and is cooperatively agreeing to be subject to them.
Thus, the VSS can enable a uniform approach to authentication and document signatures across all of an enterprises customer touchpoints, and on any of its customer-facing platforms. For example, a customer may enroll their Voice Signature when working with a representative on the phone to open an online account, and be subsequently authenticated in the same or other business units. The VSS is designed to flexibly meet specific business requirements, risk management requirements, technical security, transaction enforceability, and legal/regulatory compliance requirements.
Voxeo’s leading edge approach to enabling the mash-up of web services and communications technologies is a perfect platform partner for the web service approach of TradeHarbor’s Voice Signature Service. TradeHarbor’s partnership with Voxeo enables developers of voice and web applications to add voice biometrics to their solutions quickly and easily through the development, testing, proof of concept and deployment phases of their project.
If you found this post interesting or helpful, please consider either subscribing via RSS, becoming a fan on Facebook, or following us on Twitter.

Why has voice verification historically been so difficult to implement? In an age of identity theft, when companies are looking for additional ways to secure online transactions, why shouldn’t they be able to use voice? In a time when companies are looking for ways to deliver services to customers faster, why shouldn’t they be able to use voice as a way to secure the delivery of those services? 
RSS Feed




