1.27. Mobile Device Сard Verification

Introduction

Mobile Device Сard Verification allows Consumer to make transfer and sale transactions easier with a single verification process. During the process, the card is being validated by Payneteasy, mapped to reference on Connecting Party’s server. It allows Consumer to avoid entering card data for each transfer or sale transaction. Integration is based on HTTP POST requests/responses with JSON data.

See terms definitions in Glossary.

Mobile Device Сard Verification Flow

@startuml autonumber title Мобильное Устройство - \nВерификация карты 3DS skinparam ParticipantPadding 70 participant "Клиент" as client participant "Мобильное приложение" as mobile participant "Сервер \nПрисоединяющейся Стороны" as party participant "Payneteasy" as company client <-> mobile: Аутентификация mobile -> party: Запрос \nтокена доступа mobile <-- party: Ответ с \nтокеном доступа note right accessToken end note mobile -> party: Запрос \nинициации верификации mobile <-- party: Ответ \nинициации верификации mobile -> company: Обработка \nвалидации запроса mobile <-- company: Обработка \nвалидации ответа note right session token end note party <- company : Проверка \nзапроса верификации party --> company : Проверка \nответа верификации company -> company: Начало обработки mobile -> company: Верификация \nзапроса статуса note left session token end note mobile <-- company: Верификация \nответа со статусом note right state = PROCESSING end note mobile -> mobile: Открытие браузера и \nпредоставлние redirectUrl \nдля перенаправления \nна страницу 3DS activate mobile client <- mobile: Предоставление \nredirectUrl client -> mobile: Предоставлние \nдержателем карты \nданных аутентификации mobile -> company: Обновление статуса 3DS company --> mobile: Запрос на закрытие браузера destroy mobile company -> company: Обработка верификации party <- company: Запрос уведомления \nверификации сравнения \nкарты note right server card id end note party --> company: Ответ уведомления \nверификации сравнения \nкарты mobile -> company: Запрос статуса верификации note left session token end note mobile <-- company: Ответ статуса верификации note right state = APPROVED|DECLINED end note party <- company: Запрос обратного вызова \nс финальным статусом party --> company: Ответ обратного вызова \nс финальным статусом @enduml

(1,2,3) To perform authentication of Consumer in Connecting Party’s app, Connecting Party can use any method which fits best to his needs. As a result, Connecting Party’s server generates {accessToken} and provides it to Connecting Party’s app. This parameter will be used to start and continue session.
(4,5) To initiate card verification, Connecting Party’s app sends {accessToken} with other device parameters to Connecting Party’s server. To implement initiate verification request see Initiate verification.
(6,7) Connecting Party’s app sends cardholder, device, session data and other parameters straight to Payneteasy to check the card for being valid. To implement perform validation request see Perform validation.
(8,9) Check verification is used for security purposes and allows Payneteasy to compare the data sent by Connecting Party’s app with the data stored on Connecting Party’s server. To implement check verification request see Check verification.
(11,12,21,22) Verification status request is made by Connecting Party’s app to Payneteasy to get the status of verification transaction. To implement verification status request see Verification status.
(19,20) Payneteasy sends Verification card mapping notification request to Connecting Party’s server/proxy with created on its side card reference - {serverCardId}. To implement verification card mapping notification request see Verification card mapping notification.
(23,24) If Connecting Party callback URL is specified on endpoint level, Payment Gateway sends message to this callback URL whenever transaction reaches final status, no matter if the result is approved, declined or has other final status. See more in Callbacks.