Order pickup

Roughly divided, one can say that order pickup is done in three different ways:

• A NOD Client retrieves first and best OrderGroup on the card number (PDO Scenario)

• A NOD Client retrieves a specific OrderGroup that has just been sold by the same application (TVM Scenario)

• A NOD Client obtains a Static Order to implement a specific alternative scenario.

• A NOD client retrieves all orders assigned to the client's ID (POS).

Ruters Mobile APP today is the TVM scenario. That is, the client sells a ticket through an internal sales solution and picks it up immediately. In this case, the sales solution must tell the NOD Client which order group it should pick up.

In the future one can imagine a solution where parents can buy a ticket in a WEB-based sales solution that is then retrieved on the mobile phone of a child. This can then follow the PDO scenario, where a NOD client searches for tickets that are posted via other channels.

A Static Order Group is an Order Group with a unique name that a NOD Client can retrieve on their own initiative to perform special actions. A Static Order is not an order placed by a sales system in advance, but a predefined order that is always available in NOD.

The following Static Orders are currently supported on the NOD Platform

• staticDesfireContents - Reads by Image on Travel Card and returns a Logical representation

• staticNothingToDo - Returns a custom message that there is no OrderGroup to retrieve

• staticDesfireIndependentImg - Returns the media's independent content

• staticDesfireInspection - Performs inspection on a Desfire card

• staticDesfireValidation - Performs validation on a Desfire card

• staticQRIndependentImg - Returns the media's independent content

• staticQRInspection - Performs inspection on QR ticket

• staticULIndependentImg - Returns the media's independent content

• staticULInspection - Performs inspection on the UL card

• staticULValidation - Performs validation on the UL card