For the complete documentation index, see llms.txt. This page is also available as Markdown.

App Initialization

Objective

This section defines the minimum requirements for the application startup flow, ensuring that the device environment is suitable and secure to process proximity-based payments (Tap to Pay).

Insights

  • Using friendly illustrations is recommended to reduce friction during verification.

  • The “Continue” button must be visually and functionally linked to a successful security validation.

  • This step is mandatory to ensure compliance with proximity payment security best practices (e.g., PCI MPoC).


Welcome Screen

01 - Illustrative icon

Must represent the store context. Custom branding is allowed, as long as it maintains legibility and proper contrast.

02 - Welcome message

Must include the store name and a short message guiding the user through the app.

03 - “Enter” button

Must be clearly highlighted as the main action. Triggers the mandatory security check before granting access to the app.


Security Checklist

04 - Magnifying glass illustration

Optional visual element. Recommended to indicate inspection or safety check.

05 - Verification checklist

Must include all items that are checked during the security scan.


Environment Ready

06 - All items marked as checked

All conditions must be positively validated.

07 - “Continue” button (enabled)

Must be displayed as the main action and only enabled when all conditions are fulfilled.


Environment with Restrictions

08 - Invalid item highlighted in red

Example: NFC deactivated. The item must be visually emphasized with a red icon and clear explanatory label.

09 - “Continue” button (disabled)

The button must be clearly inactive (greyed out) and non-clickable while any item in the checklist is not satisfied.

Recommended:

Display contextual guidance for the user, such as “Activate NFC to continue.”


Expected Behaviors

  • The checklist must run automatically after pressing “Enter”.

  • Immediate visual feedback must be provided (green or red icon) for each checklist item.

  • If any requirement fails, the interface must clearly inform the user in non-technical language.

  • The “Continue” button must only be available once all validations return.

Mandatory Messages

  • When NFC is deactivated:

    NFC is deactivated. Please activate NFC to continue using Tap to Pay.

  • When the app is running in a suspicious environment:

    Unsecure environment detected. Please check your device's integrity.

Last updated