Overview

Market Pay's Tap to Pay solution enables seamless integration with third-party applications such as Electronic Cash Registers (ECR) and Point of Sale (POS) systems.

In an integrated setup, the client application manages user interactions while Tap to Pay handles payment-specific functions.

Core Capabilities

• Read contactless payment instruments (cards and mobile devices)
• Handle PIN entry when required
• Display transaction results

Integration Methods

Available integration methods depend on the target mobile platform.

Note: iOS SDK integration follows Apple's guidelines for payment solutions.

Integration Architecture

The Tap to Pay solution uses Single Sign-On (SSO) for secure authentication. Two integration points must be implemented by client developers.

Mobile Integration

Implement communication between your application and the Tap to Pay solution via app-to-app calls (Android Intents) or by embedding the SDK directly.

Backend Integration

Your backend must handle outbound API requests from the Market Pay platform for SSO permission requests and refund approvals.

Prerequisites

Organisation Account Setup

Your Market Pay Implementation Manager will configure your organisation account and create test merchant accounts on the Market Pay platform.

Credentials Provided by Market Pay

• Documentation access credentials for app and SDK documentation
• SDK API Key for retrieving SDK configuration
• Client ID for routing SSO permission requests

Information You Must Provide

• SSO API Endpoint — HTTPS endpoint for receiving SSO permission requests
• App Package Name / App ID — Android package name or iOS App ID
• Certificate Fingerprint — SHA-256 fingerprint (Android app-to-app only)

Staging Environment

For initial testing, use these pre-configured default values:

Mobile Integration

App-to-App Integration (Android)

In this configuration, both your application and the Tap to Pay app must be installed on the device. Communication is handled via Android Intents.

Your application responsibilities: User authentication, receipt generation, post-transaction flows, and business logic.

Tap to Pay responsibilities: Payment transaction processing and display of transaction screens.

SDK Integration (Android & iOS)

The SDK approach embeds the Tap to Pay library directly into your application, eliminating the need for a separate app installation and providing a seamless user experience.

Client ID Configuration

The Client ID ensures SSO permission requests are routed correctly to your API endpoint. It must be passed in the operationMetadata field during initialisation and refund operations.

Format

operationMetadata = "{\"ClientID\":\"your-client-id-here\"}"

Backend Integration

Your backend must expose an HTTPS endpoint to handle SSO permission requests from the Market Pay platform. This enables user access control and transaction type control.

SSO Request Flow

1. Client app initiates an operation (initialisation or refund)
2. Market Pay platform sends a POST request to your SSO endpoint
3. Your backend validates the user and operation type
4. Your backend responds with approval or denial

Documentation Access

Detailed SDK documentation is available at:

https://integration.readytotap.fr/documentation/rtt-cbp-saas/softpos/sdk/latest/

Access credentials will be provided by your Market Pay Implementation Manager during onboarding.

Support

For technical assistance or questions about integration, contact your assigned Market Pay Implementation Manager.