Skip to main content

Introduction

Fiuu ToP (Tap on Phone) SDK enables merchants to accept contactless card payments without any external hardware — no Electronic Data Capture (EDC), PIN Entry Device (PED), or Secure Card Reader (SCR) required.

It uses the device's Near Field Communication (NFC) channel to transact with the end user's payment card. The SDK also handles connectivity with Fiuu and third-party back-end services to perform mandatory security checks on the device and app before a transaction is allowed to proceed. Once integrated, your app can accept contactless payments directly through its own NFC interface.

Minimum Requirements​

To integrate and use the Fiuu ToP SDK, the following must be met to comply with the security standard the SDK is certified against:

Component / EnvironmentRequirements
PlatformAndroid only. Devices running an uncertified (non-Google-certified) Android build are not supported.
Supported OSMinimum Android 10.0 (API 29). Optimum: the latest 2 major versions.
Device SpecsMust have NFC hardware, online (network) connectivity, and Google Mobile Services with CTS certification.
Development RequirementsEnable and obtain a Google Android Device Verification API key via the Google Play Console. Register your app with Fiuu by sharing the official Application ID together with the public key of the keystore used to sign the release build.
Correlatable DataPhone numbers, email addresses, and other end-user PII must not be stored by the app or the payment service. Any memory buffer holding correlatable data must be cleared immediately after use, and that buffer-clearing code must survive compiler optimization.

What's Included​

  • Android ToP SDK library (topnewroute-debug.aar, topnewroute-release.aar)
  • Tap-On-Phone Testing App — a reference app for exercising the SDK end-to-end before wiring it into your own app; see the flow described in Flow Overview.

Where to Go Next​

  • Haven't set up Google Play Integrity credentials yet? Start at Credential Setup.
  • Already have credentials and just need to wire up the SDK? Skip straight to Getting Started.

Revision History​

Document VersionDescriptionDateDRI
1.0.0Initial versionMay 27, 2025Nik Mohd Faris
2.0.0Second versionAugust 4, 2025Nik Mohd Faris
2.0.4Update opt-in valueJune 19, 2026Nik Mohd Faris
2.0.5Update Response CodeJuly 23, 2026Ahmad Hafiz
2.1.0Update Required Params for cancelPurchaseSeptember 17, 2026Haziq Ruslan