VeriFone Universal API Concepts Helpdesk Training.

Slides:



Advertisements
Similar presentations
Learning Objectives Understand the shifts that are occurring with regard to online payments. Discuss the players and processes involved in using credit.
Advertisements

M-PAYMENT SYSTEM (e–WALLET ).
XHTML Basics.
The Client-Server Model for the Web 1. A Web Client (usually in the form of a web browser) makes an HTTP request to a specific web server. 2. The Web Server.
Tele’Ware Software Application. Helping you manage your clients….
A New Computing Paradigm. Overview of Web Services Over 66 percent of respondents to a 2001 InfoWorld magazine poll agreed that "Web services are likely.
MIT iCampus iLabs Software Architecture Workshop June , 2006.
15 Chapter 15 Web Database Development Database Systems: Design, Implementation, and Management, Fifth Edition, Rob and Coronel.
Guide To UNIX Using Linux Third Edition
Chapter 7 Managing Data Sources. ASP.NET 2.0, Third Edition2.
Sharif University of Technology Session # 7.  Contents  Systems Analysis and Design  Planning the approach  Asking questions and collecting data 
1 Visa Acceptance and Enablement Bank of America Merchant Services - Supplier Strategy April 2009.
Member Portal. Improved Member Experience Platform transformation improves the capabilities of the member portal and offers new self-service tools that.
Mgt 240 Lecture Website Construction: Software and Language Alternatives March 29, 2005.
Welcome to the Manage Quality Assurance module of the “MIP Release 3 Study Workflow Training” course! This module guides you through the process of managing.
Training Presentation This presentation is meant for end users of the ZERO Plan program. The Training will include: Overview of the ZERO Plan process and.
Cougar Mountain Services and Companion Products PDF-eXPLODE® e-DOCS.
Electronic Payment Systems University of Palestine University of Palestine Eng. Wisam Zaqoot Eng. Wisam Zaqoot March 2010 March 2010 ITSS 4201 Internet.
1 Google Checkout API Jingsong Wang Arpril 2, 2007.
Advanced Shell Programming. 2 Objectives Use techniques to ensure a script is employing the correct shell Set the default shell Configure Bash login and.
May 28, 2002Mårten Trolin1 Protocols for e-commerce Traditional credit cards SET SPA/UCAF 3D-Secure Temporary card numbers Direct Payments.
MobeSys Technologies MobeSys – helping you overcome mobile technology challenges.
Britannia/NET1 Web Seminar 2007 Presented By: NET1 Payment Solutions Presenter: Brian Morabito.
Jaeki Song ISQS6337 JAVA Lecture 16 Other Issues in Java.
11/16/2012ISC329 Isabelle Bichindaritz1 Web Database Application Development.
Introduction to XML. XML - Connectivity is Key Need for customized page layout – e.g. filter to display only recent data Downloadable product comparisons.
Lecture 23 Internet Authentication Applications modified from slides of Lawrie Brown.
| imodules.com Summer 2013 Release Review Presented by Mark Werner Director of Product Management.
James Holladay, Mario Sweeney, Vu Tran. Web Services Presentation Web Services Theory James Holladay Tools – Visual Studio Vu Tran Tools – Net Beans Mario.
XP New Perspectives on Microsoft Office FrontPage 2003 Tutorial 6 1 Microsoft Office FrontPage 2003 Tutorial 6 – Publishing a Web Site.
Web Server Administration Web Services XML SOAP. Overview What are web services and what do they do? What is XML? What is SOAP? How are they all connected?
COMP3121 E-Commerce Technologies Richard Henson University of Worcester November 2011.
Security Protocols and E-commerce University of Palestine Eng. Wisam Zaqoot April 2010 ITSS 4201 Internet Insurance and Information Hiding.
 A look at mobile payments past  Mobile payments today  Utility Mobile Apps  Payments Tomorrow.
Access Online Cardholder Transaction Approval Training 1 Client Logo.
WEB BASED DATA TRANSFORMATION USING XML, JAVA Group members: Darius Balarashti & Matt Smith.
Learning Objectives Understand the shifts that are occurring with regard to online payments. Discuss the players and processes involved in using credit.
Chapter 11 Working with Credit Card Methods of Processing Credit Cards Preparing for Cyber Cash Authoring a Credit card Transaction.
Mentoring and SHARE. The Mentoring Concept The functionality is very flexible in its design. Currently the model can handle the following one – on one.
PAYPAL PRESENTED TO:SIR ADNAN PRESENTED BY:SAIMA ASGHAR
8 Chapter Eight Server-side Scripts. 8 Chapter Objectives Create dynamic Web pages that retrieve and display database data using Active Server Pages Process.
Cougar Mountain Services and Companion Products PC Charge.
PAYWARE MOBILE API – APP TO APP INTEGRATION. PAYWARE MOBILE API OVERVIEW VeriFone’s PAYware Mobile API provides iPhone developers the ability to easily.
Introduction to eTIM. Introduction to eTIM eTIM Overview   eTIM (eTIM) is a server designed and developed by VeriFone, Inc. to work between PAYware.
VeriFone Virtual Terminal Web-Hosted Hosted Payment Gateway
ASP-2-1 SERVER AND CLIENT SIDE SCRITPING Colorado Technical University IT420 Tim Peterson.
Review of XML Concepts Helpdesk Training. Review of XML Concepts What is an XML declaration? What is an XML Element What is Nesting? What is a Document.
Introduction to Softpay CP 105 Tier 1 Training Education and Support Technical Series : Tier 1 Core Software Technical Developer: Christopher Wallis –
Groupon Training June 2011.
Intro to Web Services Dr. John P. Abraham UTPA. What are Web Services? Applications execute across multiple computers on a network.  The machine on which.
INTRODUCTION TO SIM.DLL AGENDA SIM.DLL Overview and Features SIM.DLL Requirements Supported Terminals Transaction Flow Benefits.
PAYWARE SIM Secure Integration Method. WHY PAYWARE SIM? PAYware SIM provides a single interface to simply and securely integrate Windows-based POS systems.
An Enterprise Clinical Data Search Solution. is Designed for: Informatics professionals, clinicians, statisticians, data managers and process/quality.
SECURE INTEGRATION METHOD (SIM) Device Control SIM DEVICE CONTROL The SIM controls the flow of all sensitive cardholder data (card, track, exp. date,
8 th Semester, Batch 2009 Department Of Computer Science SSUET.
PAYWARE TRANSACT TIM TROUBLESHOOTING TERMINAL INTERFACE DIAGNOSTIC TOOL The diagnostic tool can be used to check connections with TIM, PAYware Transact.
Connecting to External Data. Financial data can be obtained from a number of different data sources.
Authored by Frank Hamelly, Microsoft MVP Regional Chapters.
KFS DEPOSITS Fiscal Services Office Rev March 17, 2016.
Trusted source for all your payment processing needs.
Emdeon Office Batch Management Services This document provides detailed information on Batch Import Services and other Batch features.
1 Terminal Management System Usage Overview Document Version 1.1.
XHTML Basics.
XHTML Basics.
Web Server Administration
XHTML Basics.
Introduction of Week 11 Return assignment 9-1 Collect assignment 10-1
XHTML Basics.
XHTML Basics.
Presentation transcript:

VeriFone Universal API Concepts Helpdesk Training

VeriFone Universal API Concepts What are advantages of VeriFone having a unified standard? What is the VeriFone Universal API? Which VeriFone products use the VeriFone Universal API? What is the structure of the VeriFone Universal API? What does the Response XML Element typically contain? What does the Request XML Element typically contain?

What is the VeriFone Universal API? The VeriFone Universal API is a standardized format to send and receive information from VeriFone products. One of the earliest products to employ this structure was the Rapid Internet Transit Authority (RiTa), a product VeriFone gained from the GOSoftware acquisition. That product is now known officially as PAYware Transact. Today, several of VeriFone's most popular software based card acceptance products are built on top of PAYware Transact. These products have inherited the VeriFone Universal API as their method of organizing data.

What are advantages to VeriFone having a unified standard?  Ease of Troubleshooting – Helpdesk/First-Line Support can debug field issues on multiple products with little difference in training between products.  Ease of Migration – integrators and partners can easily migrate from one VeriFone product to another making few, if any, code changes.  Ease of Development – VeriFone can reuse their code base across several platforms with confidence that it will function in the expected manner. This saves VeriFone time and money.  Ease of Quality Assurance – Quality Assurance can test multiple platforms using the same tests and tools

Products that utilize the VeriFone Universal API Softpay Connect PAYware Connect PAYware Merchant PAYware Mobile PAYware PC PAYware Report Viewer PAYware Settlement Manager PAYware SIM PAYware STS PAYware TIM PAYware Transact

Structure of the VeriFone Universal API The VeriFone Universal API uses XML 1.0 as its document structure. Each request has TRANSACTION as the Document Element, whereas, each response has RESPONSE as the Document Element. The request uses TRANSACTION as its tag because a “transaction” is occurring between the sending application and the VeriFone product. This “transaction” is not necessarily going to be an actual monetary transaction. Strictly speaking, the word transaction does not mean a monetary transaction. It can also refer to an exchange of data. In other words, a request can contain an administrative command or a reporting command, and the tag will still be TRANSACTION. The response should contain less information than the request, and the returned fields will be more predictable.

Structure of the VeriFone Universal API (Continued) Each RESPONSE or TRANSACTION should contain an element for each field that is being passed or returned. Typically, the XML Element name is the parameter or field being passed; whereas, the XML Text Content between the starting and ending tags is the value being passed for that field or parameter. In some cases, mostly with reporting, some elements have nested children elements. This is typically used for specifying search fields and fields that you would like to be returned in the report. The other exception to the VeriFone Universal API is also in reporting. Some responses for instance a PDF formatted report, are returned in the format specified and don't return as XML.

Structure Example 1 (PAYware Connect Settlement) Request: BATCH SETTLE APITest1 ******* ********** Response: Settlement Scheduled 21 SUCCESS

Structure Example 2 (Reporting API Exception in Request) Request: TRANSEARCH *********** REPORT 8000 delimited,

Structure Example 3 (Reporting API Exception in Response) Response: ,14:44:56,6,400555******0019,, ,SALE,0.00,1.00,TAS ,14:03:50,7,545454******5454,, ,SALE,0.00,1.00,TAS ,13:18:39,8,400555******0019,123456, ,SALE,0.00,1.00,TAS ,13:19:02,8,400555******0019,123456, ,SALE,0.00,1.00, ,13:20:15,8,371449******8431,123456, ,SALE,0.00,1.00, ,13:21:03,-10003,371449******8431,123456, ,SALE,0.00,1.00,AXS ,13:21:20,8,371449******8431,123456, ,SALE,0.00,1.00, ,15:54:53,8,545454******5454,, ,SALE,0.00,1.00,TAS ,14:23:02,9,401200******0026,, ,SALE,0.00,1.00,TAS ,15:05:44,9,401200******0026,, ,SALE,0.00,1.00, ,15:06:21,9,401200******0026,, ,CREDIT,0.00,1.00,

Typical Types of Data contained in a TRANSACTION element  Required Functional Data – elements that are necessary for every transaction type in order for the VeriFone product to understand what type of function is being accessed  Required Account Data – elements used to locate a specific account, site, or terminal in the VeriFone product, as well as, the information required to authenticate to the product.  Conditionally Required Data – elements specific to each command that are required in order to process the transaction  Conditionally Optional Data – elements that are specific to each command but not necessary at minimum to execute the command requested

Types of TRANSACTION Data Example 1

Types of TRANSACTION Data Example 2

Elements you should almost always see in a RESPONSE  TERMINATION_STATUS – If this is SUCCESS, the operation requested has been completed successfully. This does not denote that the transaction had a positive response  RESULT – The VeriFone product's interpretation of the response being sent out. An example is APPROVED for a payment transaction.  RESULT_TEXT – normally this is unabridged from whatever application or operation succeeded or failed during the course of processing the request  RESULT_CODE – a numeric code that represents the state of the response. Normally, the number matches a specific RESULT

Example of a RESPONSE 1

Quick Quiz (to make sure you were paying attention) What are 3 products that use the VeriFone Universal API? True or False? All requests that have TRANSACTION as the Document element are payment transactions. Where would you most likely find an exception to the VeriFone Universal API in VeriFone Products? What are 3 of the elements that you typically see in a RESPONSE tag?

End of Presentation Created by: Christopher Wallis