Page 241 - The Digital Financial Services (DFS) Ecosystem
P. 241

ITU-T Focus Group Digital Financial Services
                                                         Ecosystem



               4.   Paying large institutions with eMoney: While payments to MNOs, schools, governments, and other
                    institutions are a small part of BoP obligations, they may be a meaningful factor in driving eMoney
                    adoption since many individuals use these services. Because these institutions can be quasi-monopolies,
                    government-controlled entities, or otherwise influential organizations, they can mandate eMoney.
                    Examples include registration payments for public schools in The Ivory Coast and tuition payments to the
                    Bridge Academy, an independent school system in Kenya. The often remote nature of these institutions
                    provides an additional catalyst for eMoney adoption.

               Figure 10 – Example eMoney use cases




































               4      Agricultural Use Cases

               Although not a silver bullet, agricultural use cases play a role in a holistic approach to achieving digital liquidity.
               Example use cases for tight value chains include:
               •    bulk payments to farmers;

               •    multi-party agriculture payments;
               •    input subsidy programs;

               •    trader credit (agriculture items);
               •    informal store credit;
               •    savings-based line of credit (LoC).

               This section discusses these use cases with the intention of:
               •    Highlighting the range of benefits eMoney can provide to SHFs, and whether digital liquidity is one of
                    them.
               •    Illustrating the importance of tailoring solutions to specific use cases. The user experience, value
                    proposition, backend processes, pricing, rollout strategies, and other components must be tailored to
                    each use case.






                                                                                                       213
   236   237   238   239   240   241   242   243   244   245   246