.. _orders_manager:

Orders
######

.. toctree::
  :maxdepth: 1

.. contents::
  :local:

.. role:: ex

.. role:: code

.. _orders_search_manager:

Orders Search
=============

The “Orders search” screen displays information on all transactions processed by Payneteasy. This screen is located in the “Orders” – “Orders search” section. Related transactions are grouped in Orders. Each Order has ID assigned by Payneteasy, ID assigned by Merchant or Connecting Party which represents Merchant and ID assigned by external processor (if transaction was processed in it). For example, sale transaction and subsequent refund on this sale transaction will have the same Order ID in Payment Gateway and will be searchable by both transaction types. Orders can also be accessed from Dashboard via Quick actions.

Find Orders
-----------

Basic search is performed by date and exact criteria:

.. image:: ./_static/images/7/pic25.png
  :width: 680
  :align: center
  :alt: pic25 manager faq

|

Exact criteria can be used to assist in locating a specific transaction:

.. list-table::
   :widths: 50, 50
   :header-rows: 0
   :class: longtable
   :width: 500px

   * - ``Main``
     - | • merchant invoice id
       | • order id in Payneteasy
       | • processor order id
       | • purpose
       | • amount
       | • session token
   * - ``Customer``
     - | • phone
       | • email
       | • IP address
       | • IP address country
       | • billing country
   * - ``Source Card``
     - | • bank name
       | • country
       | • card from order id
       | • BIN
       | • BIN range from order
       | • last 4
       | • 6+4
       | • approval code
       | • ARN
       | • RRN
       | • card holder
       | • card ref id
   * - ``Destination Card``
     - | • bank name
       | • country
       | • card from order id
       | • BIN
       | • BIN range from order
       | • last 4
       | • 6+4
       | • approval code
       | • ARN
       | • RRN
       | • card ref id
   * - ``Wire``
     - | • account number
       | • routing number.
   * - ``Card Present API``
     - | • reader ID
       | • reader key serial number
       | • reader device serial number
   * - ``Mobile API``
     - | • device serial number
       | • phone serial number
       | • phone IMEI

The most convenient criteria to find an exact transaction are:

* 6+4 digits, which allows to most accurately search for a specific card;
* approval code and RRN (can be obtained from a bank statement or from a transfer receipt);
* transaction ID.

| Additional search criteria are used to help with the selection of relevant orders list.
| The following criteria are available:

.. list-table::
   :widths: 30, 70
   :header-rows: 0
   :class: longtable

   * - ``Card types``
     - allows to view transactions with a specific type of cards and payment methods;
   * - ``Currency``
     - allows to select one or more currencies;
   * - ``Transaction types``
     - allows to view only the specified transaction types;
   * - ``Transaction statuses``
     - allows to view transactions with the specified status;
   * - ``Order status``
     - when the transaction can’t be found, this criterion allows to track the order on all stages of its processing;
   * - ``Endpoint``
     - allows to view all transactions on selected endpoints;
   * - ``Project``
     - allows to view all transactions for a specific project or several projects;
   * - ``Gate``
     - allows you to display all transactions on selected payment gateways
   * - ``Processor``
     - allows you to display all transactions for a specific processor or multiple processors
   * - ``Company``
     - allows you to display all transactions for selected companies
   * - ``Merchant``
     - allows you to display all transactions for a specific Merchant or multiple Merchants
   * - ``Reseller``
     - allows you to display all transactions for a specific reseller or multiple resellers
   * - ``Error code``
     - allows to view all transactions with a specific error.

| After selecting one or more search criteria, click :ex:`Search`.


Orders View
-----------

.. |e| image:: ./_static/images/7/pic30.jpg
.. |f| image:: ./_static/images/7/pic31.jpg

| By default, orders in Payment Gateway are displayed as follows:
|

.. image:: ./_static/images/7/pic26.png
  :width: 925
  :align: center
  :alt: pic27 manager faq

|
| Orders can be presented in a brief :ex:`Brief` or :ex:`Detailed` view. This can be switched with the following button:
|

.. figure:: ./_static/images/7/pic27.png
  :scale: 70 %
  :align: center
  :alt: pic28 manager faq

|
| In detailed form, the orders will be displayed as follows:
|

.. image:: ./_static/images/7/pic28.png
  :width: 860
  :align: center
  :alt: pic29 manager faq

|
| The number of orders displayed on one page can be changed with the buttons in the “Rows” column:
|

.. figure:: ./_static/images/7/pic29.png
  :scale: 70 %
  :align: center
  :alt: pic30 manager faq

|
| The :ex:`Date` button performs sorting by date. By default the latest transactions will be displayed on top.

Download Of Selected Transactions Report
----------------------------------------

| To download the sorted transactions, click one of the following buttons:
| |e| - download to Excel format
| |f| - download to CSV format.
| An additional menu can be used to manage export fields:
|

.. image:: ./_static/images/7/pic32.png
  :width: 300
  :align: center
  :alt: pic33 manager faq

|
| In the pop-up window, select necessary data and save the list:
|

.. image:: ./_static/images/7/pic33.png
  :width: 450
  :align: center
  :alt: pic34 manager faq

.. _orders_details_manager:

Order Details Screen
--------------------

| Order details screen is opened by сlicking on the order ID from the search screen.
| Order details, such as IDs and order creartion time, are displayed on the left side of this screen:
|

.. image:: ./_static/images/7/pic50.png
  :width: 515
  :align: center
  :alt: pic36 manager faq

|
| First six and the last four digits of the card number, card expiration date and cardholder name are displayed on the card. There is also information about country, bank, card type and the payment system of the card.
|

.. figure:: ./_static/images/7/pic35.jpg
  :scale: 80 %
  :align: center
  :alt: pic36 manager faq

|
| Next to the sender and receiver cards are buttons to add card details to Black, white and loyalty lists.
|

.. image:: ./_static/images/7/pic36.jpg
  :width: 490
  :align: center
  :alt: pic37 manager faq

|
| Additional customer data sent by the Merchant or submitted by customer on the form is displayed under the card or other payment method indicator. Clicking on cardholder or customer data parameter (for example, e-mail address) initiates a search for all transactions with a selected parameter.

.. figure:: ./_static/images/7/search.png
  :scale: 80 %
  :align: center
  :alt: search merchant faq


| Click on one of the plus signs near the customer data parameter (highlighted in red on the picture) adds this parameter to black, white or loyalty list. Additional click on this sign removes the parameter from respective list:
|

.. image:: ./_static/images/7/pic37.png
  :width: 530
  :align: center
  :alt: pic38 manager faq

| If Merchant is added to :code:`Customer Management` module - new CMS customer can be created manually:
|

.. image:: ./_static/images/7/CMSadd.png
  :width: 530
  :align: center
  :alt: pic38 manager faq

|
| After pressing :code:`Create CMS customer` - fill in needed fields, assign new :ex:`"Merchant customer ID"` and press :code:`Create` button. New customer will not be created if :ex:`"Merchant customer ID"` is not unique.
|

.. image:: ./_static/images/7/CMSadd3.png
  :width: 700
  :align: center
  :alt: pic38 manager faq


|
| All transactions within the order are grouped and the commission for each operation is calculated:
|

.. image:: ./_static/images/7/pic39.png
  :width: 890
  :align: center
  :alt: pic40 manager faq

|
| This screen has the functionality to leave notes. For example, notes for transaction documents, customer contacts, or any other information related to this order.
|

.. figure:: ./_static/images/7/pic40.png
  :scale: 70 %
  :align: center
  :alt: pic41 manager faq

|
| Current transaction status can be seen in the upper right part of order screen:
|

.. figure:: ./_static/images/7/pic41.jpg
  :scale: 70 %
  :align: center
  :alt: pic42 manager faq

|
| General information on all transactions associated with provided customer data is displayed in the top panel.
| The total amount of all transactions made by the specified cardholder and the number of approved/declined/filtered/etc transactions:
|

.. figure:: ./_static/images/7/pic42.png
  :scale: 80 %
  :align: center
  :alt: pic43 manager faq

|
| The total amount of transactions and the number of approved/declined/filtered/etc transactions with the specified E-mail:
|

.. figure:: ./_static/images/7/pic43.png
  :scale: 80 %
  :align: center
  :alt: pic44 manager faq

|
| The total amount of transactions and the number of approved/declined/filtered/etc transactions with the specified IP address:
|

.. figure:: ./_static/images/7/pic44.png
  :scale: 80 %
  :align: center
  :alt: pic45 manager faq

|
| The total amount of transactions and the number of approved/declined/filtered/etc transactions with the specified card number (PAN):
|

.. figure:: ./_static/images/7/pic45.png
  :scale: 80 %
  :align: center
  :alt: pic46 manager faq


.. _manager_order_captures_cancels:

Captures And Cancels From Back Office
-------------------------------------

If Preauth has final successful status, the Merchant can initiate cancel which cancels the deduction and returns locked amount back to customer’s card or the Merchant can initiate capture which deducts the locked amount from customer’s card.
To start a cancellation or capturing (deduction) of the transaction, go to the details of the relevant order.
On the order details page, click the :ex:`Cancel order` button for cancellation of deducting and :ex:`Capture order` for deducting the locked amount.

.. figure:: ./_static/images/7/pic51.png
  :scale: 70 %
  :align: center
  :alt: pic47 Manager faq

.. _manager_order_refunds:

Refunds From Back Office
------------------------

If the order has final successful status, the Manager can return the money to the customer, on their request, for instance.
To start a refund (reversal) transaction to the customer card, go to the details of the relevant order.
On the order details page, click the :ex:`Reverse order` button.

.. figure:: ./_static/images/7/pic46.jpg
  :scale: 70 %
  :align: center
  :alt: pic47 Manager faq

|

The dialog box will open like presented below:

.. image:: ./_static/images/7/pic47.jpg
  :width: 490
  :align: center
  :alt: pic48 Manager faq

|

In this dialog box specify the amount of reversal. It can be the entire amount of the order, or only a part of it for cases where the Merchant refunds payment for certain goods that are part of one order.
In the :ex:`Comment` field a description of this refund can be added.

.. Warning:: Merchants must be extremely careful when making a refund on the order! Refund requests are immediately sent to the bank and it will not be possible to cancel this transaction from the Payneteasy system afterwards.

.. _manager_order_callbacks:

Callbacks From Back Office
---------------------------------

If the order has final status and had :ex:`server_callback_url` in the initial request, the Merchant can re-send the final callback.
To send a callback to the Connecting Party, go to the details of the relevant order.
On the order details page, click the :code:`Callbacks` button.

.. figure:: ./_static/images/7/pic52.png
  :scale: 70 %
  :align: center
  :alt: pic52 Manager faq

The dialog box will open like presented below:

.. image:: ./_static/images/7/pic53.png
  :width: 700
  :align: center
  :alt: pic53 Manager faq

|

In this dialog box click :code:`Send` to sent callback to the Connecting Party.

|

.. list-table::
   :widths: 30 70
   :header-rows: 1
   :class: longtable

   * - Callback Fields
     - Description
   * - Jevt ID
     - Callback event identifier
   * - Callback URL
     - Callback receiver URL
   * - Transaction type
     - Type of the transaction
   * - Transaction status
     - Transaction status
   * - Last fire date
     - Time of the last callback attempt
   * - Next fire date
     - Time of the next callback attempt
   * - Retry count current
     - Remaining automatic retry attempts
   * - Job processed
     - Callback job processing status

|

Callback Sending Logic

.. list-table::
   :widths: 30 70
   :header-rows: 0

   * - ``Job processed = N``
     - | • callback sending is active
       | • automatic retries will occur
       | • :code:`Cancel` button is available
   * - ``Job processed = Y``
     - | • callback sending is stopped
       | • automatic retries will not occur
       | • :code:`Cancel` button is not available

When the :code:`Send` button is pressed, a single manual callback is sent and the ``Retry count current`` will decrease by 1.
The status will change from: Y → N if the callback attempt fails.

You can stop callbacks by pressing :code:`Cancel`.

When the :code:`Cancel` is pressed:
The status will change from: N → Y, callback will stop and no further automatic attempts will occur.

.. note:: Cancelling a callback prevents any further automatic retry attempts until the callback is manually triggered again.

.. _manager_order_change_status:

Change Status From Back Office
-----------------------------------

If the order has final status, the Manager can change the status from :ex:`declined` to :ex:`approved` (and other way round).
To change the order's status, go to the details of the relevant order.
On the order details page, click the :ex:`Change Transaction Status` button.

.. figure:: ./_static/images/7/pic54.png
  :scale: 70 %
  :align: center
  :alt: pic54 Manager faq

The dialog box will open like presented below:

.. image:: ./_static/images/7/pic55.png
  :width: 550
  :align: center
  :alt: pic55 Manager faq

In the :ex:`Amount` field the order's amount can be changed.
In the :ex:`Result Status` field a order's status (:ex:`DECLINED`/:ex:`APPROVED`) should be choosed.
In the :ex:`External ID` field External Order ID can be changed.
In the :ex:`RRN` field a retrieval reference number of the transaction can be added.


Recurring Payments
==================

| The screen is located in the “Orders” section.
| This screen displays recurring payments (for example, subscriptions).
| Basic search is performed by date and exact criteria:
|

.. image:: ./_static/images/7/pic49.png
  :width: 910
  :align: center
  :alt: pic50 manager faq

|
| The :ex:`Criteria` button contains additional search parameters:
|

.. list-table::
   :widths: 30, 70
   :header-rows: 0
   :class: longtable

   * - ``Recurrence status``
     - | Allows to select the specified repetition status of the recurring transaction:
       | :ex:`Failed` – unsuccessful attempt;
       | :ex:`Scheduled` – planned attempt;
       | :ex:`Stopped` – currently paused or finished attempt.
   * - ``Recurrence type``
     - | Allows to select the specified repetition type of the recurring transaction:
       | :ex:`Manual` – recurring payments are initiated manually;
       | :ex:`Auto` – recurring payments are initiated automatically in accordance with the set schedule;
       | :ex:`Native`- recurring payments use special integration with the acquiring bank.
   * - ``Endpoint``
     - Allows to select the specific endpoint if there are several endpoints available.
   * - ``Project``
     - | Allows to select the specified project if there are several projects available.
       | Select one or more search criteria and click :ex:`Search` to find the needed transactions.

Ethoca Alerts
=============

This section allows to see alerts from Ethoca which helps in preventing chargebacks:

.. image:: /_static/images/Ethoca/Ethoca.png
  :width: 840
  :align: center
  :alt: pic48 Manager faq

ChargebackHelp
==============

This section allows to see alerts from Verifi which helps in preventing chargebacks:

.. image:: /_static/images/Ethoca/Verifi.png
  :width: 840
  :align: center
  :alt: pic48 Manager faq