Page 33 - Methodology for inter-operator and cross-border P2P money transfers

• The Discard button is permanently enabled. Different implementations may make other choic-
The Submit button is enabled after T3 has been es in actual user interface aspects such as screen
pushed. For handling of time-outs in early stages layout, button-locking logic colorization. It is howev-
of the transaction, see the next section. er assumed that the functional core is the same, so
• The T7 button is permanently enabled. Button T1 the descriptions in subsequent sections of this meth-
enables T2, T2 enables T3. T3 enables T4 to T6. odology refer to the generic functional elements as
This follows the sequence prescribed by the use defined in from above list.
case modelling and shall reduce the risk of submit-
ting erroneous data. As T4, T6 and T7 can appear 14�2 Practical Application
in any order, sequence-forcing after T3 or auto- The following applies for the synchronous testing
matic submission of data cannot be supported. mode as described in section 13. The Figure below
symbolizes the action flow. For asynchronous test-
If a specific implementation uses a different set of ing, the B-Party activities are omitted.
button logic, adjustments to the practical hints as
given in the next section have be required.

Figure 12 – Symbolized flow of action (synchronous testing mode). For the asynchronous testing mode, B-Par-
ty activities are omitted.

• A-Party Situations, normal testing workflow • B-Party Situations, normal testing workflow

• Normal flow of actions: Successively tap T1, • Getting ready to expect incoming notifica-
T2 etc. To conclude and record/upload the tion: tap T1 (optional). When notification
data set, tap Submit. comes, tap T7, then Submit.
• No response (timeout) after activating the • No notification after agreed time-out peri-
service by USSD command (T1 has been od: Enter “B Timeout” in the Comment field,
recorded): Enter “A Timeout” in the Comment then tap Discard.
field, then tap Discard.
• Handling erroneous actions:

Methodology for inter-operator and cross-border P2P money transfers 31