“The last set was also some of the most inter­est­ing. Here sev­eral organ­iz­a­tions wanted to offer new pay­ments sys­tems that would provide a range of new ser­vices to sev­eral tar­get demo­graph­ics, These ser­vices were ‘new’ and aimed to attempt to move both banked and unbanked users out of the cash mar­ket and into a cash­less sys­tem. Here they faces a vari­ety of con­flict­ing issues, such as –

• Need to dis­trib­ute small and medium value pay­ments to new cus­tom­ers who may or may not be bankable
• Users of the ser­vice may be illiterate
• Busi­ness mod­els can­not sup­port exist­ing pay­ments sys­tems and so new archi­tec­tures are required
• Oper­ator could not use its exist­ing archi­tec­ture, and does not want to risk modi­fy­ing that archi­tec­ture, but that archi­tec­ture can­not sup­port the pro­posed pay­ment system
• Pay­ments sys­tem needed to sup­port social secur­ity distribution
• Pay­ments sys­tem needed to offer money man­age­ment services
• Pay­ments sys­tem needed to inter­face to ATMs
• Pay­ments sys­tem needed to offer loy­alty points and tar­geted marketing
• Pay­ments sys­tem also needed to sup­port even­tual move to digital currency
• One organ­iz­a­tion wanted to turn an exist­ing loy­alty scheme into an integ­rated mobile and card pay­ments system
• One wanted to sup­port mul­tiple pay­ment sys­tems on a single card and app
• Exist­ing mobile money solu­tions con­flic­ted with the exist­ing cent­ral bank reg­u­la­tions and required strin­gent con­trols on the funds to elim­in­ate redemp­tion liquid­ity risks. How­ever, the mobile money solu­tions provided no tech­nical way of enfor­cing those regulations…”