Page 176 - The Digital Financial Services (DFS) Ecosystem

ITU-T Focus Group Digital Financial Services
Ecosystem

3.6.3 Economics/cost sensitivity

• Much less cost-sensitive than small sellers
• May be willing to pay to receive payments (at minimum, unlikely to surcharge sender)

3.6.4 Appetite for risk and need to manage risk

• Many transactions with senders with ongoing relationships – unlikely to have meaningful levels of disputes

3.6.5 Operational Assumptions

• Payments may be taken over the phone, face-to-face, or remotely
• Need interfaces to billing/receivables systems

3.7 M6: Transit

This segment includes both large mass-transit systems and small operators providing taxi or mini-van services.

3.7.1 Technology

• Technology required to collect fares on a ride-by-ride basis from feature phone users would likely require
displaying a QR code on the phone (one time rides, monthly passes, etc.) that could be read and validated
by the fare collector; smart phones with NFC be viable technology solutions

3.7.2 Key function and feature requirements

• Transaction processing speeds
• Auto-top up (but may not be relevant in all cases for BoP)

3.7.3 Economics/cost sensitivity
• May be willing to pay to be paid assuming eMoney solution could reduce shrinkage and cash handling
costs, and increase fares collected
• Payors (riders) unlikely to shoulder transaction costs

3.7.4 Appetite for risk and need to manage risk
• Considered low risk transactions

3.7.5 Operational Assumptions

• Real time or near real time processing may be required to prevent double use
• EMoney procedures could be slower then cash and paper tickets

3.8 M7: Large/Top Tier Merchants

3.8.1 Technology

• Less willing to keep dedicated phones at each till

• More likely to have card-accepting terminals/ECRs
• PCs and/or store servers

148