Page 29 - A2A-interoperability_Online
P. 29
a2a interoperaBility makinG moBile money scHemes interoperate



4.2



Undertaking an




assessment









B y considering each of the above areas for each implementation option identified and applying a simple scoring mechanism for

each of the assessment criteria, a relative assessment can be put together that illustrates the suitability of each option with
regards to the characteristics of a particular market. this is a good way to quickly see which options are of interest, and to screen
out unsuitable options at an early stage allowing a more detailed analysis of a small number of options.

to illustrate how an assessment may be undertaken, and to show that the market context is likely to affect the outcome of the assess-
ment, two worked examples are presented in appendix a. the examples are both for markets where mobile money schemes are mostly
run by a single organisation (in many markets this is a single mno). the first example is a market where the mmos are looking to deploy
a2a interoperability where the retail payments market is concentrated on a small number of banks; while the second example is a mar-
ket where the mmos are looking to build interoperability in a more mature and competitive retail payments and banking market.

these examples illustrate where bilateral agreements between different mmos make sense and where selection of a central processor
to connect many parties may be appropriate. they show that different implementation options are likely to be suitable for different
types of markets, highlighting that the payments landscape within which interoperability is desired is an important influence on the
choice of option.

the framework presented here provides a structured approach that allows an assessment of the strengths and weaknesses of potential
implementation options to be made for any market. this helps to understand the most appropriate deployment approach and be able to
identify key cost elements that will influence the business case for a2a interoperability.








































26
   24   25   26   27   28   29   30   31   32   33   34