TruService interface features summary for a technical and marketing audience

= Not supported
= Supported

Interface Version 2.0.0 2.1.0 2.2.0 2.3.0
Local deployment
Cloud deployment
HTTP connections 1 1 1 1
HTTPS connections 2 2 2 2
MAC'ing
Load balancing 2 2 2 2
Static question trigger
Dynamic question trigger 3 3 3 3
Hashed card data
Multiple tenders per transaction
Multilingual support
Real-time rating exchange
Scheduled rating exchange
Prizes/Rewards
Question regulation
Question sequencing
Merchant multi-tenancy 2 2 2 2
Real-time basket data ingest
Batched basket data ingest
Merchant Led Activation
Terminal Led Activation
Activation Query
1 Only available when deployed locally
2 Only available when deployed in the cloud
3 Only available when real time basket data is ingested

Features Summary

Load balancing

Technical

Multiple TruService instances can accept incoming connections with instances geographically located to maximise performance and response times.

Marketing

Load balancing allows for graceful service level degradation in the event TruService instances become unavailable. Load balancing increases performance and availability by spreading load amongst a set of TruService instances.

HTTP & HTTPS connections

Technical

Allows TruModule to send serialized TSI messages wrapped in HTTP messages to TruService. Reduces development effort using the HTTP application layer protocol. HTTPS connection can be used if TruService is local to TruModule. HTTPS must be used when TruService is remote from TruModule.

Marketing

Vastly simplifies the effort to establish communication with TruService for developers using Java or .NET or C/C++ with open source framework. It delegates socket management responsibility to operating system components. It allows TruModule instances to seamlessly communicate between local and cloud deployments of TruService.

MAC’ing

Technical

MAC’ing is used by TruService to support authentication of inbound connections from TruModule. Is a process or technology in which the TruService side of the communications link authenticates the other party. MAC’ing is mandated in all situations where TruService is deployed in the cloud or on a different secure network from TruModule.

Marketing

Identifies and ensures the identity of a TruModule talking to TruService. Encrypts all data and reduces the man in the middle attack vector.

Cloud deployment

Technical

Provides a scalable, monitored SaaS TruService farm. Removes the need for local installation.

Marketing

Cloud deployments provide a reduction in complexity for merchant and partner deployment, communication with the cloud in a production environment is secure with mutual authentication ensuring the safety of the data exchanged between TruModule and TruService. Load balancing in the cloud allows for rapid changes in traffic scale.

Question triggers

Technical

Questions can be asked at a variable time during a transaction based on configuration in TruModule, currently Card insertion, Dwell time and dwell time extend are supported.

Marketing

Merchants can configure questions to be triggered at a custom time to ensure that the customer experience is unaffected by the TruRating question. Questions can be triggered either at card insertion, dwell time or dwell time extend based on the implementation.

Product basket data

Technical

Exposes a message type that can be populated by the POS/Payment Application/Proxy to provide basket data item by item

Marketing

Capturing basket level and product item level data allows customer sentiment to be measured around the actual purchase. This allows value performance to be measured against individual items, their discounts or overall discounts.

TruTrace

Technical

The TruTrace algorithm applies specifically to card present payment transactions using Payment Cards. The solution proposed may not apply to payment transactions made by customers through other channels (e.g. Web, Phone, NFC, etc.).

Marketing

By collecting a anonymous card hash, TruRating is able to give an additional dimension to data by building up a customer’s repeat visit behavior. Sentiment can be tracked over time to measure performance.

Multiple tenders per transaction

Technical

Allows for split tenders per transaction, i.e. Cash + Card + Voucher as part of a Transaction.

Marketing

Point of sale systems typically accept part or complete payments other than card payments, allowing for multiple tenders ensures the additional detail of vouchers or coupons are captured as part of the rating data.

Product specific questions

Technical

Where POS events are received in real-time, allow for questions to be enqueued based on specific items being scanned on the POS.

Marketing

Allows the merchant to target questions at specific products as they are scanned through the POS.

Dynamic Question Trigger

Technical

TruService returns a question event with a specified trigger point. TruModule must ask for a question at the indicated trigger point.

Marketing

Gives full control of the customer experience by TruService. By allowing dynamic movement of the point the question is asked, TruService can cater for busy/quiet periods and split test the point the question is asked to give more data insight.

Static Question Trigger

Technical

TruModule is configured to ask the question at a pre-configured point.

Marketing

Questions are presented at a pre-determined point.

Batched basket data

Technical

TruService may receive basket data in a single transmission from TruModule to save on bandwidth, or because the POS is unable to send individual events.

Marketing

TruService can receive all basket and product data in a single event, if there are restrictions in the POS software. Product specific questions or prizes will not be available.

Real-time basket data

Technical

TruService may receive basket data from TruModule or the POS in real-time to support product specific questions and other events.

Marketing

TruService can receive POST events such as basket and product data in real-time. Product specific question events can be asked.

Batched rating exchange

Technical

TruService uploads all ratings from all terminals in a single transmission.

Marketing

TruService saves on bandwidth by sending all data to the PED API in a single call. Data analysis is delayed between each exchange.

Real-time rating exchange

Technical

TruService uploads ratings on a rating-by-rating basis.

Marketing

Ratings are uploaded to the PED API immediately after collection. This allows TruRating to process the data more quickly and give the merchant more up-to date analytics and alerts.

Scheduled rating exchange

Technical

TruService uploads ratings on a schedule.

Marketing

To save on bandwidth, TruService uploads data to the PED API on a schedule. Data analysis is delayed between each scheduled exchange.

Concurrent transactions

Technical

TruService allows for multiple transactions to occur simultaneously on the same terminal.

Marketing

In bars, filling stations and other service industry sectors - till operators may sign-on or sign-off midway through a transaction. To ensure rating data is not lost in a partially complete transaction, TruService can temporarily save a part complete rating session.

Support more than 2 languages

Technical

TruService allows for unlimited languages to be asked by TruModule.

Marketing

In some territories, bi-lingual support is a legal requirement - TruService supports two languages by default. There are some sectors, such as airports and filling stations where up-to four or more languages can be selected during the transaction - changing the language of the payment device in real-time.

Prizes / Rewards

Technical

TruService allocates prizes/rewards to customers at random on a territorial basis.

Marketing

TruService allocates prizes/rewards to customers at random on a territorial basis.

Multi tenancy

Technical

TruService deployed as a single instance or as part of a farm can accept connections from multiple partners, merchants and terminals.

Marketing

TruService can be deployed either in the TruRating cloud or in a partner’s data center, allowing connectivity to be shared between multiple merchants or partners - this lowers deployment and operational complexity.

Question sequencing

Technical

TruService controls the sequence of questions.

Marketing

To ensure an even spread of questions is asked, TruService controls the sequencing of the questions - weighting can be controlled via the merchant portal.

Question regulation

Technical

TruService issues a question once per sliding window period.

Marketing

For some extremely high transaction volume merchants, the number of questions asked during a given time window can be regulated to ensure that the total transaction time and therefore transaction rate is unaffected.

Efficient XML Interchange

Technical

Efficient XML Interchange (EXI) is a binary XML format which was adopted as a Recommendation by the World Wide Web Consortium (W3C) on 10 March 2011. It was developed by the W3C’s Efficient XML Interchange Working Group and is one of the most prominent binary XML efforts to encode XML documents in a binary data format, rather than plain text.

Marketing

TruService can save on bandwidth by compressing the data stream.

Merchant Led Activation

Technical

Mechanism provided by TruService that allows TruModule to check the current activation status of the merchants outlet and provide the merchant with a number of screens on their terminals to activate their account.

Marketing

Merchant activation process that’s performed through the merchants terminals.

Terminal Led Activation

Technical

Mechanism provided by TruService that allows TruModule to check the current activation status of the merchants outlet and provide the merchant with information and guidance on activation via the TruRating web site.

Marketing

Simple merchant activation process that’s performed primarily through the TruRating website, in-conjunction with the merchants terminals.

Activation Query

Technical

TruModule is able to query the activation status for a given outlet (MID) and sales position or device (TID). TruModule uses the information to drive the Terminal Led Activation process and to be able to provide status to the merchant. TruModule can make use of the Query command to reduce frequency of communications with TruService when a merchant or outlet has not yet been activated or suspended.

Marketing

Increases the efficiency of communication between TruModule and TruService and provides TruModule with information for reporting and logging purposes.

Feedback