.. _account-verification-form:

Account Verification Form
##################################################

.. toctree::
    :maxdepth: 1

.. contents::
    :local:

.. role:: ex

.. role:: code

Introduction
------------------------------------

| Account verification is a non-financial transaction, which allows to validate Payer's card account information. This verification procedure helps to prevent potential fraudulent activity and meet industry-specific compliance obligations. Account Verification Form integration allows Connecting Party to exclude itself from storing, processing, or transmitting Payer’s cardholder data or other sensitive payment details. Such data is submitted by Payer on Payneteasy hosted payment form in PCI DSS certified environment.
|
| See terms definitions in :ref:`Glossary<glossary>`.

.. _account-verification-form-flow:

Account Verification Form Flow
------------------------------------------------------

.. uml::
  :align: center

    skinparam roundcorner 20
    skinparam sequenceArrowThickness 2
    skinparam ParticipantPadding 30
    actor Payer as Customer
    participant "Connecting Party\nwebsite" as Merchant
    participant "Payment Gateway" as g
    autonumber
    Customer -> Merchant: Checkout
    activate Merchant
    == Account Verification Request ==
    Merchant -> g: api/v2/account-verification-form
    activate g
    g --> Merchant: Redirect-url, orderId
    deactivate g
    Merchant -> Customer: Provide redirect-url \nto payer’s browser
    deactivate Merchant
    activate Customer
    Customer -> g: GET redirect-url
    deactivate Customer
    activate g
    g --> Customer: Account Verification Form
    deactivate g
    activate Customer
    Customer -> g: Submit form
    deactivate Customer
    activate g
    g --> g: Process Account Vetification transaction
    == Final redirect of customer ==
    g -> Customer: Redirect to Connecting Party website
    activate Customer
    Customer -> Merchant: POST redirect_url\nstatus, orderid
    deactivate Customer
    activate Merchant
    group Get Final Status
    == Receive Connecting Party Callback ==
    Merchant <- g: Сallback with final status
    g <-- Merchant: HTTP 200
    deactivate g
    == Order Status Request ==
    Merchant -> g: api/v2/status
    activate g
    g --> Merchant: Response \nstatus, order-stage
    deactivate g
    end
    Merchant --> Customer: Show result
    deactivate Merchant

| (2) To implement Account Verification Form request see :ref:`/api/v2/account-verification-form/<api_v2_account-verification-form>`.
| (9) To implement final redirect see :ref:`Final Redirect<final_redirect>`.
| (11,12) To implement order status request see :ref:`/api/v2/status/</api/v2/status/>`. Status should be requested multiple times with 3-5 seconds interval until final status will be received in response.
| (13) To implement callback with final status handling see :ref:`Connecting Party Callbacks<merchant_callbacks>`.