{"title":"Understand the iOS Mobile solutions","category":"default","creationDate":1776961627,"content":"

This page explains various concepts that our Mobile solutions are based on. The focus is on how the Adyen Mobile SDK interacts with the plataforma de pagamentos da Adyen and with your POS app.<\/p>\n

Communication session<\/h2>\n

When you integrate the Mobile SDK into your POS app, the SDK has to communicate in a secure way with the plataforma de pagamentos da Adyen. To enable this, you must integrate a server-to-server POST \/checkout\/possdk\/v68\/sessions<\/a> request to create a session. Your POS app needs to call your backend to trigger this request and get the session data.<\/p>\n

The SDK uses the session data from the response to authenticate with our payments platform. Because the session expires after some time, the SDK checks regularly if it needs to establish a new session.<\/p>\n

\n

\"\"<\/p>\n<\/div>\n

SDK transaction flow<\/h2>\n

If you use or build a Mobile solution where our iOS Mobile SDK is integrated into your POS app, transactions take place as follows:<\/p>\n

    \n
  1. \n

    Optional but recommended: your POS app calls a warm-up function to speed up initiating transactions. <\/p>\n<\/li>\n

  2. \n

    Your POS app creates a Terminal API request that is serialized to JSON, or receives the Terminal API payment request from your backend.<\/p>\n

  3. \n

    The POS app passes the Terminal API request to the Mobile SDK.<\/p>\n<\/li>\n

  4. \n

    The SDK checks if the communication session is still valid, and if necessary establishes a new session.<\/p>\n<\/li>\n

  5. \n

    The transaction starts on the mobile device.<\/p>\n<\/li>\n

  6. \n

    The SDK passes the Terminal API response to your POS app.<\/p>\n<\/li>\n<\/ol>\n

    \n

    \"\"<\/p>\n<\/div>\n

    PIN transactions<\/h2>\n

    It is possible to make PIN transactions in your Tap to Pay and card reader solution. Unlike traditional payment terminals with physical keypads, PIN entry on a mobile device requires specialized security measures to protect the shopper's data. To comply with PCI MPoC compliance requirements<\/a>, the PIN entry pad is not always centered on the mobile device screen. Instead, it appears in a random position as shown in the following examples. <\/p>\n\n\n\n\n\n
    <\/th>\n<\/th>\n<\/tr>\n<\/thead>\n
    Bottom-left
    \"\"<\/td>\n    		Top-right
    \"\"<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    PIN transaction with a card reader in the US<\/h3>\n

    You need an NYC1 card reader with PIN support for secure PIN transactions<\/a>.<\/p>\n

    \n

    NYC1 card readers with PIN support require Mobile SDK version 3.8.0 or later.<\/p>\n<\/div>\n

    In the US, not all NYC1 card readers support PIN. You can check if your card reader supports PIN transactions in the following ways:<\/p>\n