Presentation is loading. Please wait.

Presentation is loading. Please wait.

Syniverse Solutions - ABC-BANK

Similar presentations


Presentation on theme: "Syniverse Solutions - ABC-BANK"— Presentation transcript:

1 Syniverse Solutions - ABC-BANK
SyntraPoint Pre Production Launch Proposal

2 Agenda (pls update accordingly)
Summary of Ask Scope of the Pre Production Launch Syniverse Proposal on Key Components of the Pre Production Launch Recap SyntraPoint Card Control Solution SyntraPoint Card Controls System Architecture Onsite Hardware Controls Integration via e.g. ABC-BANK’s Enterprise Gateway/other options The Mobile APP SyntraPoint Card Control Use Cases

3 Summary of Ask (pls update accordingly)
ABC-BANK is developing a digital transformation road map and is looking for card controls functionalities as well as additional value added capability beyond controls such as offers and rewards. Scope of the Pre Production Launch The scope will focus on card control solution via stand alone mobile APP provided by Syniverse The aim is to evaluate and experience the solution functionalities. The design and UI of the stand alone APP will be for future discussions. ISO8583 integration via e.g. the bank’s Enterprise Gateway/other options ABC-BANK wants minimum adaptation on their back end to facilitate quick deployment of the Pre Production Launch Syniverse Proposal on Key Components of the Pre Production Launch Card Controls Card on /off Merchant category Spend limit Effective alert and messaging Soft and hard caps Transaction history Recurrent payment controls Scheme agnostic

4 Recap SyntraPoint Card Control Solution

5 ABC-BANK Priorities and Challenges (pls update accordingly)
Digital transformation: acquire, retain and service customers adapt to the digital consumer enable digital self service to reduce costs Customer focus and engagement Omni channel delivery and experience Single customer view Cost reduction: lowering cost per transaction increasing  sales (cross-selling, up-selling, acquisition) Customer Self-service Compliance: industry mandates regulatory requirements Develop new offerings adapted to evolving customer needs Personalization and Context to create differentiators Analytics and ways to combine all interactions, information and predominantly unstructured – data Mitigate Fraud

6 SyntraPoint brings a combination of Real-time Consumer Spend + Context + Mobile Moments to create highly personalized and contextual Cross-channel engagement touch points with customers.

7 Transforming the Customers Experience
Two-Way Messages/Alerts User Driven Controls Real-Time Consumer + Context Appropriate Engagement on Customer Relevant Channels Customer Engagement Dynamic Rewards and Incentives Card Transactions Opti-Channel Two-Way Engagement

8 Amplify the Customer Experience with…
July 2, 2015 Amplify the Customer Experience with… Next Generation Technology! Don’t just check-off the ‘box’ for alerts… Transform your cardholders experience! Dynamic Real-time Controls Real-time Alerts Self Service Cross Channel Mobile Engagement Mobile Context (Location, Mobile Identity) Consumer Driven Analytics Customer demands are growing, Alerts are not enough Fraud continues to increase: 2015 Card Not Present fraud has increased by over 30% in the US, Alerts/controls drastically improve consumer confidence and boosts card use Geolocation Enhancement Technology Layering

9 SyntraPoint Card Controls System Architecture: Onsite Hardware

10 Onsite Implementation – Hardware Considerations
The SyntraPoint systems are typically operated on the same physical server running a virtual environment such as VMware comprised of 4 x virtual machines. Server Hardware Specifications will be provided based on card count and TPS rates. Logger API Listener Decision Engine Encoder Gateway

11 Onsite Implementation – Hardware Considerations VM Functionality Breakdown
Encoder Gateway (EG) The EG is responsible for receiving messages from the authorization system, replacing the PAN Decision Engine (DE) The DE is responsible for making decisions on transactions, based on the customized card settings set by the end-user, and communicates those to the app, by way of Central (Central hosted by Syniverse). API Listener (API) This accepts changes to card settings from Central and stores them in the same database that the DE uses to decision transactions. The API Listener is a separate instance in order to not impact the DE’s performance, as well as allowing better network segregation. Management/Logging (Logging) This server allows storage, search, and visualization of logs as well as providing access to the other servers for management purposes via SSH, Salt/Chef/Puppet/Ansible, or other configuration tools. Encoder Gateway Decision Engine API Listener Logger

12 Onsite Implementation – Hardware Considerations
GogoNogo Encoder Gateway GogoNogo Decision Engine GogoNogo API Listener GogoNogo Logger GogoNogo Encoder Gateway GogoNogo Decision Engine GogoNogo API Listener GogoNogo Logger GogoNogo Encoder Gateway GogoNogo Decision Engine GogoNogo API Listener GogoNogo Logger Stage 1: Dev Stage 2: QA Stage 3: Production In any deployment, it is advised that the following environments are made available: Dev, QA and Production. Initial work will be done within the Dev Environment, and then on completion moved to QA pre-production. On success of QA, the system is moved to Production.

13 Onsite Implementation – Hardware Considerations
Virtual Machine 1: (Virtual Machine Name: Logger System) 2 vCPU 2 GB RAM 1 Gb NIC 10GB Hard Drive (preferably based on SSD, can be thin provisioned) 120GB Hard Drive (or SAN/NAS, etc, can be thin provisioned) Can be: Linux CentOS, Redhat Enterprise Linux, or Microsoft Windows Virtual Machine 3: (Virtual Machine Name: Decision Engine) 2 vCPU 2 GB RAM 1 Gb NIC 10GB Hard Drive (preferably based on SSD, can be thin provisioned) Can be: Linux CentOS, Redhat Enterprise Linux, or Microsoft Windows Logger Decision Engine Virtual Machine 2: (Virtual Machine Name: Encoder Gateway) 2 vCPU 2 GB RAM 1 Gb NIC 10GB Hard Drive (preferably based on SSD, can be thin provisioned) Can be: Linux CentOS, Redhat Enterprise Linux, or Microsoft Windows Virtual Machine 4: (Virtual Machine Name: API Listener) 2 vCPU 2 GB RAM 1 Gb NIC 10GB Hard Drive (preferably based on SSD, can be thin provisioned) Can be: Linux CentOS, Redhat Enterprise Linux, or Microsoft Windows Encoder Gateway API Listener Minimum server specifications are described above. Take note that these are simply recommendations, and SyntraPoint will provide ABC-BANK with a suitable specification custom for the environment. This is based on the following two factors: 1. Cards on File and 2. TPS (Transactions per Second) rates during average and peak times.

14 Onsite Implementation – Hardware Considerations
Decision Engine Options: PostgreSQL MySQL Microsoft SQL Server Oracle… The Decision Engine will need to connect to a database system provisioned by ABC-BANK. SyntraPoint will provide ABC-BANK with the database schema to implement onto a ABC-BANK database instance at the time of deployment. Supported databases include: PostgreSQL, MySQL, Microsoft SQL Server and Oracle.

15 Scheme Agnostic Supports ALL card brands: MasterCard VISA
China Union Pay American Express JCB ELO Discover Diners Club Rupay BC Cards And more… Supports ALL card types Credit Debit Prepaid Closed Loop Private Label Custom Cards Supports current cards in circulation and new cards issued

16 SyntraPoint Card Controls System Architecture: Controls Integration

17 Controls Integration The Fastest Financial Processing Platform in the World Scalable for hundreds-of-millions of cardholders ++ Restful API driven frontend and backend systems (everything is API based) Zero association between card information and user Token based (SHA256 + Salted Hash, or other as defined by Issuer) Rules and preferences assigned and securely stored per Token IPSEC & TLS 1.2 host-to-host interconnectivity, AES­256 encrypted ZeroMQ connections for host management Elastic Auto-scale Architecture based on throughput Has no upper TPS limit due to architectural design (Auto scale) 10,000 TPS per instance, prior to auto scale Tested to over 100,000 TPS at < 5ms per transaction, consistent under load An end-to-end real-time system (authorization processing through to user interaction) Supports ALL card brands (MC/Visa/etc.) & card types (Credit, Debit, Prepaid, Closed Loop, Private Label) Supports current cards in circulation and new cards issued

18 ISO8583 / ISO20022 Real-time Analysis of ISO8583 / ISO20022
Use of Dynamic Adapters Ability to tailor incoming authorization message format Authorization Messages (0100/0200) Response or Advice (0110/0120/0210/0220) Reversals (400) Ability to tailor authorization message response back to host (or onward to next in-line host) Support for multiple adapters (single message, dual message, various brands, custom formats, etc.) Support for authorization protocol conversions (from a custom format to standardized format, etc.) Support for multiple connection types (socket, MQ, https) Ability to perform deep authorization analysis in real-time Every DE within the bitmap is computationally processed against a rule (if a rule is applicable) Example: DE36 (Track 3 data) can be exploded to take the Individual Account Identifier (IAI) into consideration for common PAN’s Capability to modify authorization message in real-time Convert data in-flight, as required by Issuer or host system

19 SDK/API Integration Every component of the technology is API driven
JSON based, RESTful API PAN tokenized SHA Salted Hash, or… GetCardHash API over HTTPS + TLS (typically only done once) Responsive Website Provided out-of-the-box Customized by SyntraPoint team to client specifications Authentication, as required Look and feel Control based Features / Options

20 Typical Payment Process, as it is today…
Payment Networks ABC-BANK VAP / MIP / Other Enterprise Gateway Merchant Acquirer Check 1 CMS / Authorizing Host Check 2 Merchant Check ‘ n ’ Final Auth Decision

21 Option B (Direct Switch Connection)
Payment Networks ABC-BANK API Listener VAP / MIP / Other Encoder Gateway Decision Engine Enterprise Gateway Merchant Acquirer Rules Database SyntraPoint Central CMS / Authorizing Host Check 1 Real Time Messages User Defined Rules Updates Merchant Check 2 Final Auth Decision Benefits to Direct Switch Connection Option: Quick Installation Process, connection through Enterprise Gateway

22 User Defined Rules Updates
Option E (Fully Hosted, Encoder Gateway) Payment Networks ABC-BANK VAP / MIP / Other Encoder Gateway Enterprise Gateway Merchant Acquirer SyntraPoint Central CMS / Authorizing Host Check 1 Real Time Messages User Defined Rules Updates Merchant Check 2 Final Auth Decision Benefits to Fully Hosted Encoder Gateway Option: Quick Installation Process, Low cost point

23 Option E (Fully Hosted, Encoder Gateway)
Admin Portal Customer Service SyntraPoint Central Environment History DB Public Web Interface Portal / API Decision Engine (Optional) Analytics Mobile Engagement Platform Geo Location Logic Engine (MNO Based) Central SyntraPoint Central Tokenized Data Secure VPN / Leased Line Real Time Messages to Cardholder User Defined Updates to Cardholder Rules Encoder Gateway Benefits to SyntraPoint Central, Hybrid model: Less to deploy & manage, infrastructure/support cost savings Faster time to market

24 Option F (Fully Hosted, Encrypted Connection)
Payment Networks ABC-BANK VAP / MIP / Other Enterprise Gateway Hardware Encryption Device Hardware Encryption Device Merchant Acquirer SyntraPoint Central CMS / Authorizing Host Check 1 Real Time Messages User Defined Rules Updates Merchant Check 2 Final Auth Decision Benefits to Fully Hosted Encrypted Connection Option: Quick Installation Process, Low cost point Fully PCI compliant

25 The Mobile APP

26 SyntraPoint Stand Alone Mobile APP
The Stand Alone Mobile APP The Pre Production Launch will utilize the stand alone mobile APP provided by Syniverse The focus is to evaluate and experience the card control functionalities The design and UI will be for future discussions Customer Onboarding The APP will include cardholders adding the card(s) to enable control ABC-BANK ABC-BANK

27 SyntraPoint Card Controls Solution : Controls

28 Channel Independent Card Controls
Can be integrated via API or SDK into all ABC-BANK’s existing digital channels Can be delivered through while-labelled Mobile App and Controls Website Integration options for: ABC-BANK Online Banking Site ABC-BANK Mobile Banking App ABC-BANK SMS Banking ABC-BANK USSD Banking ABC-BANK Physical Branches ABC-BANK ATM Consoles Any other digital channel

29 App Based Card Controls
Card OFF Card ON Channel Controls Travel Controls Recurring Controls Limit Controls Alerts & History Incentives and Rewards

30 Web Based Card Controls
Web Based Controls Responsive White Labeled Website Branded for ABC-BANK Single Sign on Capabilities Full Functionality

31 SMS Based Card Controls
Amount Threshold Example: Payment Channel Method: A charge exceeding $100 on your card ending in 5065 was just Approved at Publix ($204.22). If this was not you, reply HELP An Online Shopping charge on your card ending in 5065 was just Approved at Apple iTunes ($6.50). If this was not you, reply HELP Merchant Category Types: Single Transaction Notifications: A charge on your card ending in 5065 was just Approved at Delta Airlines ($1,067.99). If this was not you, reply HELP A charge at 2:40am on your card ending in 5065 was just Approved at Sophie's ($24.95). If this was not you, reply HELP Geographies: Amount Threshold Example: Your charge at Toys-R-Us was declined (Insufficient Funds). Reply EXTEND to extend your credit limit. A charge out of your home State (CA) on your card ending in 5065 was just Approved at Starbucks ($16.00). If this was not you, reply HELP Combined Alerting Triggers: A charge exceeding $100 at 2:40am on your card ending in 5065 was just Approved at Delta Airlines ($ ). If this was not you, reply HELP

32 Card Controls Use Cases

33 ON/OFF We’re much more than just ON/OFF, and here’s why: ABC-BANK
Card On/Off Control The Card On/Off feature is designed to disable a card so that it cannot be used. If a card is turned off, a transaction will not be processed - regardless of location or channel. When the lock icon is green and open, the card is ON. When the lock icon is red and closed, the card is OFF. For example, when the user turns the card OFF, transactions taking place in a grocery store, online or at an ATM will all be blocked (Declined) and no money will be transferred from the cardholder’s account. Channel On/Off Control Cardholders that would like more control of how their card can be used will have the ability to turn off certain channels. A payment channel is defined as how you use your card. For example, the four channels used within the platform’s mobile app include In Store, ATM, MOTO and Online. ABC-BANK

34 Channel ON/OFF ABC-BANK In Store (POS) ATM
The first channel that can be configured is In Store. In Store represents transactions that take place at a physical location, such as for example a retail establishment, retailer or restaurant. When the In Store icon is green, it means that In Store is ON for your card and any transaction taking place in person at a POS will be allowed. When In Store is transparent, it means that In Store is OFF for your card and any transactions at a retail store will be declined. ATM The cardholder may also control if their card can be used at an ATM. This includes balance inquiries as well as withdrawals. Similar to In Store, when the ATM button is transparent it means that the channel is OFF. Any transactions attempted while ATM channel is OFF will be blocked. Conversely, ATM is ON when the ATM button is green and any transactions attempted will be allowed. ABC-BANK

35 Channel ON/OFF ABC-BANK Online Mail Order / Telephone Order (MOTO)
The next channel is Online. The Online channel includes transactions that occur over the internet. As is the case with ATM and In Store, when the Online button is transparent, it indicates that this channel is OFF and no transactions will be allowed via the internet. When the button is green, all transactions will be allowed for purchases made online. Online does not take geographic location into account. For example, if the cardholder has all travel controls set to OFF, but the Online button is green, the transaction will be allowed. Mail Order / Telephone Order (MOTO) Finally, the last channel is Mail Order / Telephone Order (MOTO). This particular channel encompasses all transactions that occur over the phone or mail order, such as purchases made over the phone from a catalogue/magazine or for ordering food from your favorite pizza delivery service. Similar to the previous channels, when the Phone button is transparent, all transactions attempted through this channel will be declined. When the Phone button is green, it means that button is on and all transactions will be allowed. Similar to Online, Phone does not block transactions based on geographic location. ABC-BANK

36 Geography Travel Control
Through the Travel settings, the user can adjust where their card can be used. Tapping on the Travel icon will take the user to a list of countries, with their home country anchored to the top of the list. To the right of each country name is a switch that will allow the user to turn certain countries ON and OFF. For example, if a user is planning a trip to Spain, they would simply scroll down the list until Spain appeared and then tap the switch to turn that country ON. If a user does not travel frequently, they may choose to leave every country OFF except their home country. For the US, cardholders have the ability to fine-tune where their card can be used by state. Tapping the more icon located to the right of United States provides access to the list of states with each accompanying switch. For processors or banks with existing fraud prevention systems in place, the Platform offers options that guarantee seamless integration based on the configurations of the existing fraud prevention platform.

37 Spend Limits / Merchant Category and Budgeting Tool
The Limits feature provides the cardholder with a guide for budgeting. The user can delineate how much they would like to spend daily, monthly, per channel or per merchant type. Limits set by merchant type are based on merchant category code (MCC), which is found within the transaction data. In order to set a limit, the user can tap the text field and type in the amount that they would like to budget. Limits can either decline a transaction or notify the cardholder (and permit the transaction) should a limit be reached or exceeded – and this is defineable. Real-Time Messaging Notifications via Push, SMS and OTT in the future phases can be sent for allowed, approved, blocked and/or declined transactions, rewards and system notifications. This allows the card member to opt for notification associated with different types of transactions and thresholds. Further messages related to Reward, offers and cashback can also be configured.

38 Recurring Payments and Replacement Cards
Ability to control Recurring and flexibility to update card for recurring payments after a stolen or lost card is replaced By identifying the “Recurring” Field within the ISO8583 / ISO20022 / similar message, we can present a recurring payment to the cardholder. The cardholder can either elect to allow the recurring transaction to be sent for approval irrespective of the state of their card (ON/OFF/etc) or choose to block all future transactions from that recurring merchant. Should the “Recurring” flag NOT be set, we use big data analysis to determine if a payment is of a recurring nature of not through the following bid-data logic analysis: Identify any like/similar payments within the history database Across the cardholder base (All BIN ranges) For specific cards Identify any transactions that take place on a similar frequency Identify any transactions that take place for a similar value This process allows us to permit the first recurring payment without necessarily blocking the transaction, and then querying the cardholder as to the nature of subsequent transactions This is complaint with the rules as set by the card associations and card brands

39 Balance and Transaction History
In addition to real-time transaction data within the History view, the user can also access their real-time balance for their account. By tapping the Balance icon, the user can see their current balance. This involves integration into the bank to obtain this information, and any type of balance data can be presented. The most basic form of Balance can be augmented, depending on the availability of web services provided by the processor or bank, to provide the user with more detailed information regarding their real-time credit limit, amount spent towards this limit, next payment due date, minimum payment etc.

40 Sophisticated On/Off Controls
On for One Occasionally the cardholder may not realize which settings are blocking their attempted transactions. On for One is a unique feature that allows the cardholder to make the purchase with just one tap once the transaction is blocked. The user can enact the On for One feature within the detail transaction view by tapping the On for One icon. Whitelist & Blacklist (exception to simple On/Off) Certain transactions are habitual, such as a morning coffee at Starbucks, or lunch at your favorite bistro. Whitelist helps cardholders ensure that these transactions are never blocked for a particular merchant, even if they forgot to turn their card on. Conversely, the Blacklist feature will guarantee that particular merchants are never approved, giving your cardholders true peace of mind. The user can enable Whitelist/Blacklist by visiting the detail transaction view within History.

41 Frictionless Controls
Automated Frictionless Controls – Adding VALUE to the Cardholder Geolocation based Automatic enablement of geography based on mobile phone location (domestic and international) Not reliant and independent of any data, smartphone or any App based capabilities! Domestic: based on GSM network triangulation International: based on network handover in roaming negotiation process Additional automatic application of controls: Automatic enablement or disablement of transaction based on: Currency used and geolocation data Transaction velocity ISO8583 based transaction velocity with DE43 (Data Element) location analysis, not based on external geographic input (example: Spend $X in New York at a POS, then 10 minutes later spend $Y at a POS in California)

42 Expense Management History Upload Photo Receipt (History Value Add)
Within the History view, the user has the ability to see real-time and all historic transactions. The history view offers details related to the transaction such as the amount, merchant name, date and time of the transaction, the channel through which the transaction occurred and if it was blocked, declined or approved. In order to access this view, simply tap the History icon. To review more details related to the transaction, tap the transaction in question. Upload Photo Receipt (History Value Add) Maintaining records of payment receipts for business consumers and spend conscious consumers is exceptionally important. With the upload receipt function, cardholders can keep their receipts in one location for later reference. In order to upload a receipt, tap the Upload Receipt button found in the detail transaction view and take a photograph of your printed POS receipt. This data is centrally and securely stored on our servers so that you can never loose it. To review the uploaded receipt, simply tap the View Receipt button. Export Transaction Details (History Value Add) The Export Transaction Details feature allows cardholders to send the details found in the History view of their purchase via . The export icon can be found at the top right of the detail transaction view within History.

43 Shared Card Share Cards
Tapping the share icon takes the user to a menu that offers the perfect solution for managing and sharing cards. Cardholders can simply send an invitation to share a card to a recipient and manage if the recipient will have full or limited access of the card. Neither Limited nor Full Access offer the shared user the ability to share the card with an additional party. Limited Access will give the shared user the ability to set channels and Card On/Off. Full Access offers the user the ability to do everything that the owner of the card can do with the exception of Share card and Edit card. The Select from Contacts button is a simple means of reviewing the user’s address book on their mobile device to send the Share request. At any point in time the owner of the card can remove a shared user from a card by swiping left on their name within the Share view. The cardholder can also convert a shared user from Full Access to Limited Access and vice versa by swiping left on the shared user. Use cases supported by shared card function: Corporate cards – the administrator can set controls for employee cards Government issue payroll and food cards Parent/Child cards Remittance

44 Virtual Cards A Dynamic Solution for VCN’s
Ability to generate VCN’s on the go A Generic VCN with the full capabilities of a real payment instrument Can be restricted to: Specific Merchant Specific Value Only valid for X transactions Only valid until Y date Full Card Controls applicable to VCN’s Can be generated as and when required, or based on a “proxy” to real PAN/Account

45 SyntraPoint Omni-Channel Personalized Alerts

46 Customizable Real-Time Transactional Alerts
Transaction Based Notifications Amount Threshold When a transaction is greater than $X When a transaction is equal to $Y When a transaction is less than $Z Merchant Category Types and Thresholds When a transaction takes place as a specific MCC When the transaction at a defined MCC exceeds a preset $ value Geographies When a transaction takes place within X State When a transaction takes place anywhere outside of Y State When there is an International transaction (outside of the US) When there is an International transaction from a specific country (as per user defined list) When a transaction takes place within a user defined geo-fence When a transaction takes place outside of a user defined geo-fence When a transaction takes place that is not in the same country as the users mobile handset (phone)

47 Customizable Real-Time Transactional Alerts
Transaction Based Notifications Payment Channel Method When a transaction takes place Online When a transaction takes place at an ATM When a transaction takes place at a POS When a transaction takes place based on MOTO When the transaction at a defined Payment Channel (as above) exceeds a preset $ value Single Transaction Notifications When a transaction takes place between a particular timeframe (e.g.: Between 11pm and 6am) When a transaction happens over a Public Holiday When a transaction happens over a Weekend When a transaction happens over a Weekday When the transaction at a defined timeframe (as above) exceeds a preset $ value

48 Customizable Real-Time Transactional Alerts
Account Based Notifications Spend Thresholds Alert when spend threshold is Greater than $X Alert when spend threshold is Equal to $Y Alert when spend threshold is Less than $Z When my daily spend exceeds $A When my weekly spend exceeds $B When my monthly spend exceeds $C Value Added When a user lands / arrives in a new country – informing him that his card can be used in that country When a payment channel is ON for X timeframe and not used (timeframe is definable) When a card reissue takes place When a lost & stolen ticket has been issued When merchant credit is received (reversals) When my card exceeds a transaction velocity threshold (velocity is definable)

49 Customizable Real-Time Transactional Alerts
Transaction Outcome, Do Not Disturb, Delivery Methods Transaction Outcome When a transaction is Declined (by Host – including decline reason in English, based on Authorization Decline Codes) When a transaction is Blocked (by card controls) When a transaction is Approved Do Not Disturb When a transaction takes place between a particular timeframe (e.g.: Between 11pm and 6am) Conditional rules can apply (e.g.: unless the transaction exceeds $X) Delivery Method Push Message (data) SMS Outbound Phone Call A combination of the above / Automatic selection based on receipt via Syniverse

50 Personalized Alerts Transaction Outcome, Do Not Disturb, Delivery Methods Transaction Outcome When a transaction is Declined (by Host – including decline reason in English, based on Authorization Decline Codes) When a transaction is Blocked (by card controls) When a transaction is Approved Do Not Disturb When a transaction takes place between a particular timeframe (e.g.: Between 11pm and 6am) Conditional rules can apply (e.g.: unless the transaction exceeds $X) Delivery Method Push Message (data) SMS Outbound Phone Call A combination of the above / Automatic selection based on receipt via Syniverse

51 SyntraPoint Card Control Solution - Transaction History

52 Transaction History Cardholder History Database
Every transaction is centrally recorded in a secure fashion (SHA-256 Salted Hash or Pan) Transaction history has no limitation to age Cardholders can view all transactions, Approved, Blocked and Declined, and understand: Outcome of transaction Merchant Name Monetary Value of Transaction Currency Date and Timestamp Payment Channel Decline Reason (if transaction was declined, example: Insufficient Funds) Cardholders can assign an image through the mobile phone’s camera capabilities to a transaction for: Keeping transaction receipts No data is stored on the phone – everything is stored centrally

53 Transaction History ABC-BANK History Database and Analytics
Centralized view of all ABC-BANK operations, or drill down into: Specific Card Specific Cards (CSV List Upload) Cards that have: Done transactions at a particular merchant Cards that have spend less than or more than $X within timeframe Y Cards declined, blocked or approved (including per reason) Cards that have done transactions between a particular timeframe X and Y More… Specific ABC-BANK operations, BIN’s or card programs Ability to assess the following Analytics through Historical Data Analysis Transaction Usage Call Center NOTE: Transaction, Usage and Call Center are described at next page

54 Transaction History Backend Analytics Platform (Transactions / Usage / Call Center) Transactions Multiple Data Filters Date Range Issuer or Card Program BIN Range Transaction Details Transactions Analysis Payment Channel MCC Merchant(s) Approved / Blocked / Issuer Declined Financial Throughput Analysis

55 Transaction History Backend Analytics Platform (Transactions / Usage / Call Center) Usage (via External API Interface – Mobile Apps / Online Banking, etc.....) Multiple Data Filters Date Range Issuer or Card Program User / Account Data Number of Enrolled Users Making Configurations to Cards Number of Enrolled Users Making Configurations to Cards for the First Time Average Number of Enrolled Users Making Configurations Total Number of Existing Accounts Total Number of Accounts Created Push Message Data Messages by platform (iOS / Android / other) Opened Messages Unopened Messages

56 SyntraPoint: Integration with Call Center

57 Call Center Integration
Hosted within AWS or Syniverse Private Cloud Integration Options: A Full ‘Out of the Box’ Call Center Application for SyntraPoint services API Integration into Existing Call Center Applications An iframe based Integration into Existing Web based Call Center Applications Full Feature Call Center Modules (every application function can be managed in real-time) Deployment of automated Bots to resolve issues without a human operator (text, other) Cost savings on call center process – automated processes Tracking Support Tickets, Resolution Actions and Calls Managing Call Center Agents and Resolution Times + Full Manager Reporting

58 Transaction History Backend Analytics Platform (Transactions / Usage / Call Center) Call Center Multiple Data Filters Date Range Issuer or Card Program Reason Code (reason for the call) Operator ID Call Center Details Total Number of Sessions per Reason Code Percentage for Each Reason Code Average Session Time per Operator

59 SyntraPoint Omni-Channel: Offers, Rewards and Cashback Module

60 Rewards : Adding Single Purchase Reward

61 Rewards : Adding Multi Purchase Rewards

62 Rewards : Cash Back Plan (Flat Rate)

63 Rewards : Cash Back Plan (Variable Rate)

64 Rewards : Targets (Merchants / Cardholders)

65 Instant Card Member Gratification
Event triggers defined by Issuing institution or Participating Merchants Based on real-time ‘in-the-moment’ spend activity Administered at the time of purchase Value redemption managed by 3rd party offering institution Simple easy-to-use Consoles Frictionless Management Online Management Interfaces Multiple Delivery Channels In-App Messaging SMS Delivery (2 -way SMS) Other, as applicable Special In-App Offer You just purchased an airline ticket from Would you like to purchase discounted travel insurance from ABC-Bank? YES | NO ABC-BANK


Download ppt "Syniverse Solutions - ABC-BANK"

Similar presentations


Ads by Google