Apriva Payment Engine
Your Name
Email
Phone

Technical Overview

The Apriva Payment Engine allows Windows Mobile, WIndows CE and Win32/Windows developers to quickly and securely implement credit, debit, loyalty and gift card payment processing functionality in their applications. In simple terms, think of it like a traditional credit card terminal embedded right into your own solution.

Before looking at the individual steps involved in integrating and deploying payment processing with Apriva, let's take a quick look at the overall system.

 

 
 

 

Where your application runs today - a Windows Mobile, Windows CE or Win32/Windows device or computer. Apriva Payment Engine installs a Windows Service on the device and your application communicates with this Service via the Apriva Payment Engine API.






 

 
WWAN networks from carriers such as AT&T, Verizon, T-Mobile and Sprint, Wi-Fi networks, or Ethernet.





 

 
The Payment Engine Windows Service, running on your device, communicates with the Apriva Intelligent Gateway over a wired or wireless network, providing secure, fast and reliable access to 37 payment processing processing networks.
 







Step One: Integrate Using the Apriva Payment Engine SDK

The Apriva Payment Engine SDK consists of two components:

1. Apriva Payment Engine Windows Service

  • Windows Service running on each device that handles all the "heavy lifting" involved with payment processing
  • Secure local storage of payment and transaction data
  • Secure communication with the PCI-compliant Apriva Intelligent Gateway
  • Secure pairing with Bluetooth peripherals handling cardholder information

2. Apriva Payment Engine API

  • Communication interface between your application and the local Payment Engine Windows Service
  • Supports popular Windows development technologies such as .NET, C#, VB.NET, VB6 and COM

Apriva provides a test environment for running simulated transactions and debugging your application during development. When development and testing is completed, the final solution needs to be certified.

Step Two: Certify Your Solution

Once you've integrated and tested the Apriva Payment Engine with your application, the complete solution needs to be certified by Apriva and, in some cases, outside labs to satisfy payment industry regulations. Certifications can include:

Apriva Certified Secure
Comprehensive testing required to make sure your payment solution is production ready for deployment on the Apriva architecture.

PA-DSS
Payment Application Data Security Standard (PA-DSS) aims to help software vendors and others develop secure payment applications that do not store prohibited data, such as full magnetic stripe, CVV2 or PIN data, and ensure their payment applications support compliance with the PCI DSS. Apriva and its partners can help you quickly and cost-effectively gain PA-DSS certification.

PTS
Mastercard PTS certification ensures the necessary level of protection for transaction and cardholder data for merchants that use equipment supporting the TCP/IP protocol suite. The security evaluation verifies that POS devices meet the relevant MasterCard requirements in terms of confidentiality, integrity and communicating parties’ authentication. Apriva and its partners can help you quickly and cost-effectively gain PTS certification.

Step Three: Go to Market

Working with Apriva enables you to receive expert guidance in finding the best channel, credit card acquiring, credit card processing and technology partners to help make your product successful.

 

Getting Started
To learn more about the Apriva Secure Payment Engine solutions call 480-421-1240, send an email to PE@apriva.com or click here to request a white paper overview.