An overview of the Xiippy platform

Xiippy is the world’s first and only privacy-preserving in-person and online data-rich payments provider.

Xiippy’s transactions naturally include extra data within them (e.g. a detailed statement object) that are delivered to the payer’s personal device on an end-to-end-encrypted fashion without Xiippy maintaining knowledge of the contents of the object, hence facilitating enriching payments with data while removing adoption barriers around privacy, information security and information protection.

Xiippy’s response of a payment processing also include extra data for merchants (e.g. a privatized unique-per-franchise card identifier or customer identifier) that remain the same for the same card (or customer), helping marry and connect online and in-person transactions made by the same card (or customer), helping run effective rewards programs without requiring rewards cards.

In a normal integration scenario, Xiippy’s Core SDK is directly used by a POS or e-commerce system developer, however, the developer would need to perform certain operations like key management, configuration management as well as implementing a UI for registration of the POS or e-commerce server instance, which is necessary to facilitate end-to-end encrypted data transfer and merchant-centric privatization of data. This can expand the scope of the integration work.

To make the integration easier, and as can be seen in the diagram above, the SDKBridge abstracts most of the operations of Xiippy’s Core SDK, including configuration and key management and also providing a UI for configuration management that should be normally implemented by the POS or e-commerce developer.

In return, now the SDKBridge comes as a cross-platform compatible executable service itself that exposes the following 3 components for a POS or e-commerce system developer:

  1. Config UI, helping avoid the necessity of building UI for POS or e-commerce instance registration

  2. A checkout page for online and on-computer payments that can be rendered in an iframe to facilitate PCI compliance and manage the end to end online payment processes (including simple credit card entry form as well as single-step QR based payments). On-computer payments can be useful for cases where a customer’s card details are entered by an operator on a computer to process payments without interacting with a terminal.

  3. Unified locally-available APIs that can be used by a POS or e-commerce system to interact with the SDK to initiate payments or transfer data to payers.

This document provides insights on how to interact with the lightweight Xiippy SDK, process payments and receive insights from the platform.

Last updated