ZEBRA Pay Enterprise Grade Payment Solution User Guide

June 16, 2024
ZEBRA

ZEBRA Pay Enterprise Grade Payment Solution

Product Information

Specifications

  • Product Name: Zebra Pay
  • Manufacturer: Zebra Technologies
  • Product Type: Mobile Payment Solution
  • Certification: PCI-SPoC Certified
  • Supported Card Brands: Visa, Mastercard, American Express, Discover, Union Pay (varies by acquirer and region)
  • Device Connectivity: USB connection to payment reader
  • Compatibility: Android OS version for COTS device

Introduction to Zebra Pay
Zebra Pay is an enterprise mobile payment solution provided by Zebra Technologies. It is a PCI certified SPoC (Software-based Point of Sale) solution that allows businesses to accept card-based transactions anywhere. With Zebra Pay, you can accept various types of transactions including tap to pay with a digital wallet or NFC-enabled card, insert a chip-based card, accept PIN entry on screen, or swipe an MSR (Magnetic Stripe Reader) card. The solution is EMV certified and supports all major card brands such as Visa, Mastercard, American Express, Discover, and Union Pay.

Product Usage Instructions

Deployment
Zebra Pay is designed for fast, easy, and painless deployment. It is pre- certified for specific markets and includes all the required certifications from acquirers to PCI security compliance.
The solution is also EMV L3 certified for card brands with Global Payments, Worldpay, and Fiserv. As the SPoC solution certification applies to the Android OS version for COTS device, there is no need for per-device certification. Additionally, Zebra Pay provides an easy-integration API for seamless integration with any POS app.

Testing and Integration
Zebra Pay offers a Merchant Sandbox for easy testing. You can easily test your Zebra Pay solution in the sandbox environment before deploying it. The solution also includes certified direct host integration with acquirers, starting with Global Payments in EU, and soon expanding into NA with Worldpay and Fiserv. This eliminates the need for development, integration, and gateway fees. Moreover, unlike other handheld mobile payment solutions, Zebra Pay allows complete device flexibility without requiring device lockdown. You can continue to use any apps on your Zebra mobile devices and install/manage Google Play and other apps via your EMM (Enterprise Mobility Management) system.

Product Applications

Retail
Zebra Pay is suitable for various retail environments including supercenters, discount stores, department stores, specialty stores, and convenience stores. It can be used for line busting, assisted selling, and off-site/outdoor purchasing.

Hospitality
In the hospitality industry, Zebra Pay can be used in amusement parks, restaurants, stadiums, hotels, and airports. Its applications include ticket sales, pop-up sales, table-side payment, concierge sales, line busting, and service upgrades/pay at gate.

Field Services/T &L
In field services and transportation & logistics sectors, Zebra Pay finds applications in service calls, delivery services, courier services, postal services, payment for services and parts, and payment on delivery.

Architecture
Zebra Pay is built on a PCI-SPoC certified architecture. The solution includes the following components:

  • Mobile Payment Solution: Zebra Pay
  • Enterprise Mobile Computing: Zebra Mobile Devices
  • Payment Reader: USB-connected reader for card transactions

Frequently Asked Questions (FAQ)

  • Q: What card brands are supported by Zebra Pay?
    A: Zebra Pay is EMV certified to accept all major card brands including Visa, Mastercard, American Express, Discover, and Union Pay. However, supported card brands may vary depending on the acquirer and region.

  • Q: Can I integrate Zebra Pay with my existing POS app?
    A: Yes, Zebra Pay provides an easy-integration API that allows seamless integration with any POS app. This alleviates the need for you to develop your own integration.

  • Q: How can I test my Zebra Pay solution before deployment?
    A: Zebra Pay offers a Merchant Sandbox where you can easily test your solution. This allows you to ensure everything works as expected before deploying it in a live environment.

  • Q: Can I continue using other apps on my Zebra mobile devices with Zebra Pay?
    A: Yes, unlike other handheld mobile payment solutions, Zebra Pay allows you to continue using any apps on your Zebra mobile devices. You can also install and manage additional apps via your EMM system.

Zebra Pay

  • Miriam T. Ayala
  • Sr. Mgr. SW Engineering, Enterprise Mobile Computing
  • Ian Hatton
  • Pre Sales Consultant Zebra EMEA
  • Daniel Neamtu
  • EMEA Developer Advocate

Introduction to Zebra Pay

  • Enterprise PCI certified SPoC mobile payment solution
    Everything you need to accept any card-based transaction, anywhere

  • Accept any type of transaction
    Tap to pay with a digital wallet or NFC-enabled card, insert a chip-based card, accept PIN entry on screen, swipe an MSR card

  • Accept all major card brands
    EMV certified to accept all major card brands*: Visa, Mastercard, American Express, Discover and Union Pay

  • Single pane of glass
    Complete every payment transaction through the Zebra mobile device screen — including pin entry

  • Fits in one hand
    Provides workers with payment simplicity — no need for a separate keypad for PIN entry or clunky BT connectivity. USB connection to payment reader provides stable connectivity.

*Supported card brands vary by acquirer and region

Easy to deploy
Everything you need for fast, easy and painless deployment

  • Pre-certified for specific markets
    All the required certifications are included, and maintained — from acquirers to PCI security compliance, including EMV L3 certified for card brands with Global Payments, Worldpay and Fiserv. Since SPoC solution certification applies to Android OS version for COTS device, no per-device certification is needed

  • Easy-integration Zebra Pay API
    Easily integrate any POS app with the PCI certified Zebra Pay app, alleviating your need to do so

  • Merchant Sandbox for easy testing
    Easily test your Zebra Pay solution with the Merchant Sandbox, and you’re ready to deploy — no waiting for certifications

  • Host integration included
    Includes certified direct host integration with acquirers, starting with Global Payments in EU, (and soon to expanding into NA with Worldpay and Fiserv), eliminating development, integration and gateway fees

  • Complete device flexibility — no device lockdown required
    Unlike other handheld mobile payment solutions, you can continue to use any apps on your Zebra mobile devices as well as install and manage Google Play and other apps via your EMM

*Zebra Pay for North America, supporting World Pay and Fiserv coming soon

Zebra Pay at work in …

Retail

  • Supercenters
  • Discount stores
  • Department stores
  • Specialty stores
  • Convenience stores

Applications

  • Line busting
  • Assisted selling
  • Off-site/outdoor purchasing
  • Returns
  • Pop-up sales
  • Order online – pay in-store or curbside

Zebra Pay at work in …

Hospitality

  • Amusement parks
  • Restaurants
  • Stadiums
  • Hotels
  • Airports

Applications

  • Ticket sales
  • Pop-up sales
  • Table-side payment
  • Concierge sales
  • Line busting
  • Service upgrades/pay at gate

Zebra Pay at work in …

Field Services/T &L

  • Field Services

  • Transportation & Logistics

    • Service calls Field services
    • Delivery
    • Courier services
    • Postal Services
  • Applications
    Payment for services and parts

  • Applications
    Payment on delivery

Zebra Pay Architecture

Zebra Pay Solution Components
PCI-SPoC Certified Enterprise Mobile Payment Solution

The Zebra Pay solution built for Zebra mobile devices using the Zebra PD20 card reader enables the collection and management of digital/card-based payments. Primary use case target: retail workflows.

  • Software Pin Entry on Zebra Mobile devices (SPoC) with Zebra Pay APK
    Zebra Pay Android Application, expected to be available from Google Play Store, enables Credit and Debit acceptance on the TC52x, TC57x, TC53/TC58 running Android 10, and A11. [ET40/ET45 – coming soon].

  • Zebra Mobile Device Payment back or Payment Battery accessory
    Elegantly connects Mobile Device to PD20 for a comfortable user experience

  • Zebra PD20 PCI-PTS certified Secure Card Reader supports various payment input modalities (insert, tap, and swipe)
    Chip, NFC (Apple Pay, Google Pay, NFC Cards), or MSR

  • Zebra Pay Android API
    Enables quick and easy integration of Zebra Pay with customer or integrator applications.

  • Zebra Pay Portal (Merchant & Admin)
    The Merchant Portal provides tools and visibility to manage mobile devices, reader, user access, and transactions.

  • Zebra Pay Rest API (coming soon)
    The Rest API provides customers with the ability to pull device, reader, and transaction data from the Zebra Pay database in order to support customer cloud applications.

Zebra Pay architecture

Zebra Mobile Device with Zebra Pay

Zebra Pay Merchant Portal

Easily manage all aspects of system usage

Zebra Pay Application Integration

Zebra Pay Android Application
Installation and App Details

  • Zebra Pay production application is only available from Google PlayStore; apk it is not available for sideloading.
  • Devices and OS’s Supported:
    • TC52x, TC52ax,T57x – A11, A10 (LG-June 2022 and later)
    • TC53, TC58 – A11
  • Variants of App for Region (EU vs. NA) and Environment (Sandbox-Test vs. Production)
  • Launching Zebra Pay app from the launcher brings up details UI with device and reader solution details
  • PD20 FW (FW & App) is contained in the Zebra Pay App. upon launch, Zebra Pay will automatically connect to PD20 reader, check FW version, and update FW if required.
  • Attestation checks validate that APK version is current and within acceptable date range. If outside permitted range, an attestation error will occur, and functionality will be blocked. Release notes will indicate if an update is mandatory and timeframe to transition.
    • It is strongly encouraged to validate new releases in Sandbox environment and update production units in a timely fashion.

Zebra Pay Application
Deployment Checks

  • The Zebra PD20 Secure Card Reader may be used/shared across mobile devices (approval required on portal per company)
  • Mobile device may only be registered to one Company (MMK) and one MID/TID at a time.
  • Zebra PD20 Reader contains special HW and SW checks exists to ensure the integrity of the reader to protect against and check for tamper.
  • HW must be registered (via POS API) and Approved (via Portal) before any Payment transactions will be processed
  • Due to strict PCI-SPoC security measures, the following conditions must be met else payment transactions may fail:
    • Zebra Pay UI may not be overlayed
    • Uninterrupted application session
    • ADB debugging and developer settings must be disabled in production
  • Currently USB must be disabled for security purposes for Sandbox release app. We are looking at approaches to allow ADB to be enabled during development.
    • Mobile device integrity ensured (non-rooted device, etc.)
    • Camera must be disabled
    • Screen recording disabled
    • HW has not been tampered

Zebra Pay
High Level Application Flow

Staging:
Company and user set up, Customer & Zebra Pay App deployed to mobiles from Google Playstore, Firewall configuration, mobile device and reader registration and approvals

Transactions:

  • POS Application* Scans Shoppers merchandise, calculates total and fires intent to launch Zebra Pay
  • Zebra Pay presents Payment screen to Shopper requesting presentation of card
  • Shopper presents payment card
  • Zebra Pay UI displays card brand animation with jingle and/or notification screen (configuration settings)
  • Zebra Pay via Intent call, delivers response to Customer Application
  • POS Application generates and presents receipt ****

*”POS Application” refers to the developer’s application that interfaces with Zebra Pay application. See arch slide above.

Zebra Pay Android Library
Android APK and Native Library

  • Customer Android App will use Zebra Pay Android POS API to configure and send Android Intent to Zebra Pay to:
    • Register Mobile Device and PD20 Secure Card Reader
    • Process Payment Transactions (Payment, Refund, or Void)
  • Zebra Pay Android Native SDK: ssmobilethirdpartyintegration-x.xx.x.aar
  • Zebra Pay asynchronously sends and Android call-back Intent to the customer Application with request results
  • Key Configuration parameters include:
    • Transaction Type
    • Transaction Details (e.g. amount, etc)
    • Zebra Pay environment (Region: NA/EU, Test =Sandbox/Production)
    • Name of POS Application’s Call Back Intent (Zebra Pay will send with response data)
    • Merchant Company MMK (aka Developer ID) [obtained from Portal]
  • Alphanumeric string
  • Generated when “Company” is created in Portal and associated with a MID
  • Passed from Mobile device in order to register it with Company

Note: Zebra only supports a native Android SDK. Developers of web-apps can use 3rd party tools to develop android plugins that call the Zebra Pay SDK.

Zebra Pay Android SDK
Straightforward APIs

Available Types

  • Registration – Used to register your reader and get it validated from the Zebra Pay Portal
  • Payment – Used to create a normal payment transaction
  • Void Payment – Used to cancel a referenced transaction only if the approved transaction hasn’t been settled yet
  • Refund Payment – Used to create a refund transaction

ThirdPartyIntegrationRequestVO

  • Various parameters to be populated based on the requested Action Type:
    • setActionType() – registration or payment type Additional parameters (see example with sample fields)
  • ThirdPartyIntegration.requestMPOSIntegration(context, requestObject); ThirdPartyIntegrationResponseVO

Zebra Pay Application UIs
Payment Processing

Zebra Pay Application
Customizations

  • addItemDescription(ThirdPartyDescriptio nVO thirdPartyDescriptionVO)
    • By default, sensory branding is enabled (MC, Visa). To disable, set to true
  • thirdPartyDescriptionVO.setTitle(“disable_sensory_branding”); thirdPartyDescriptionVO.setDescription(“true”);
  • setMerchantData(String merchant data) –can be used for passing small string of data related to transaction that may be useful when reconciling settlement report
  • Portal Driven Configuration of APK:
    • “Store Manager” role user can optionally customize the logo on the Zebra Pay Android App
    • The image will be shown during the Zebra Pay app loading screen
    • Minimum size: 292 x 292 pixels

References

  • References: http://www.zebra.com/zebrapay
    • Zebra Pay API Reference Guide
    • Zebra Pay Solution User Guide – see FAQs
    • ZebraPOSSample Android application source code available for reference to kick start development

Coming soon:

  • Zebra Pay NA – WorldPay, Fiserv (future support for US)
  • Expanding set of supported mobile devices
  • Rest API – enables reading Mobile device, reader status and transaction details. In process of being vetted during customer Pilot. Note: Rest API supports read only functions and does not support any payment processing.

Questions

Thank You

  • ZEBRA and the stylized Zebra head are trademarks of Zebra Technologies Corp., registered in many jurisdictions worldwide. All other trademarks are the property of their respective owners.
  • ©2023 Zebra Technologies Corp. and/or its affiliates. All rights reserved.

Additional Developer Tips

Additional Developer Tips
Common oversights and errors

  • StatusCode responseObject.getStatusCode() ]
    • StatusCode= if not 10 or 100, it’s an error
  • Application/Solution
    • Incorrect MMK (14015), mobile device was not registered (3029) or assigned TID in portal (3040), reader was not registered or approved (3032) invalid/missing parameter (see SDK), 6001=PD20 is not properly seated or insufficiently charged; Network Error on Mobile (-1001—1006) – check firewall settings, connection stability and network time is set on device
    • N o response: ensure your config file has proper Call Back to receive Response intent from Zebra Pay into your app.
  • Attestation
    • USB debugging and/or ADB was enabled, pop up/intervention of non-zebra pay app UI
    • PD20 Reader is tampered – reader was dropped; 1st and 4th LED flashing when power button pressed.
  • Host
    • Card processing issue (e.g., card not supported, payment mode not supported etc.) .
    • Follow guidance provided in error and try again.

Lifecyle from Development to Roll Out

Lifecycle from Development to Production
Onboarding and Development

  • Customer or ISV
    • Engages with Zebra Pay Sales team
    • Obtains Test MID/TID credentials from Acquirer for use within Zebra Pay Sandbox (Test) environment
    • Purchases Zebra Mobile Device, Payment battery/accessory, PD20 Secure Reader (Test sku)
    • Zebra Pay Sales Team works with Zebra Product team to create Parent account in Sandbox Portal
    • Customer creates Company(s) in Sandbox Portal with their Test MIDs and associated TIDs
    • Customer shares Test Company MMK with their Development team
  • Application Development
    • Zebra POS API call to initiate registration of mobile device
    • Upon success Customer’s Company Admin logs into Portal and assigns TID to available mobile device
    • Zebra POS API call to register reader
    • Upon success Customer’s Company Admin Approves the reader in Zebra Pay Portal
    • Zebra POS API calls to process (test) Payment transactions against the Company (MMK and validate application in test environment using Test Credit/Debit cards.
    • Review transactions on the Portal

Lifecycle from Development to Production
Ready for Production (Live transactions)

  • When development and validation is Complete (in Sandbox) and customer is ready for Live Pilot or Production deployment, next steps:
    • Engages with Zebra Pay Sales team
    • Obtains Production MID/TID credentials from their Acquirer for use within Zebra Pay Production environment
    • Purchase Zebra PD20 Secure Reader (Production sku)
    • Zebra Pay Sales Team works with Zebra Product team to create Parent account in Production Portal
    • Customer populates Portal with their Production MID/TIDs and authorized user credentials
    • Customer shares MMK with Development or Deployment team
  • Stage mobile devices deploying Zebra Pay (Production) APK from Google Playstore
  • Customer app registers devices and readers – via Zebra POS API with appropriate MMK for use with the target Store’s Mobile devices using Production MMK credentials
  • Customer Manager/Admin – assigns TID credential to Mobile Devices and Approves Readers via the Merchant Portal
  • Production devices are now ready to process live payment transactions

ZEBRA TECHNOLOGIES

Documents / Resources

| ZEBRA Pay Enterprise Grade Payment Solution [pdf] User Guide
Pay Enterprise Grade Payment Solution, Pay, Enterprise Grade Payment Solution, Grade Payment Solution, Payment Solution, Solution
---|---

References

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>

Related Manuals