OA20072A - Electronic voucher distribution account management. - Google Patents

Abstract

A system and method for managing an electronic voucher distribution account are provided. A method, conducted by a server computer connected to a mobile telephone network in which an agent identifier is linked to an electronic voucher distribution account from which an electronic voucher can be distributed, includes, in response to receiving an event trigger notification, transferring a first amount from a service provider account to the electronic voucher distribution.

Description

FIELD OF THE INVENTION

This invention relates to a System and method for managing an electronic voucher distribution account.

BACKGROUND TO THE INVENTION

Many mobile network operators (MNOs) offer so-caîled prepaid” plans or subscription models by way of which mobile subscribers purchase airtime against which their usage of a mobile téléphoné network on a mobile handset is charged. The airtime must be purchased in advance of any utilisation of the network and once depleted, network utilisation is restricted. To continue to use the network, the subscriber must perform an airtime “top-up” or “recharge” by purchasing and loading more airtime from an airtime vendor.

In an effort to simplify airtime distribution and make airtime more widely available, a number of MNOs use electronic voucher distribution Systems which allow ordinary subscribers to register as “agents” to be able to on-seîl airtime to other subscribers. These electronic voucher distribution Systems allow agents to use their mobile handsets to purchase electronic vouchers which can be provided to and used by a subscriber to perform an airtime top-up or recharge. The electronic voucher distribution Systems may, for example, provide an SMS, USSD, mobile application or web-based interface through which an agent can request an electronic voucher of a spécifie value. The electronic voucher may be returned to the agent via the interface for sharing with the purchasing subscriber or may be sent directly to a handset of the purchasing subscriber. In exchange, the purchasing subscriber transfers a value of currency équivalent to the value of the electronic voucher to the agent, typically by handing over cash, making a mobile money transfer or using a digital wallet, crédit card or the like.

In these electronic voucher distribution Systems, the agent is provided with a voucher distribution account (also termed a “wallet”) which is typically configured to store a value of airtime. The agent purchases airtime for this voucher distribution account, and the value of each electronic voucher purchased by the agent on behalf of a purchasing subscriber is deducted from this voucher distribution account. To remunerate the agent for his or her services, the MNO typically sells the airtime to the agent at a discounted rate to allow the agent to on-sell the airtime at a margin of about 10%. The agents voucher distribution account is separate from and independent of a mobile téléphoné network utilisation account, being an airtime account against which the agents own utilisation of the mobile téléphoné network is charged.

Naturally, if the balance of the agents voucher distribution account is depleted, the agent will be prevented from vending electronic vouchers until the agent performs an airtime topup or recharge in favour of this account. This leads to downtime and lost revenue for both the agent and MNO while the agent has to take time off to purchase more airtime. Often, airtime for a voucher distribution account must be purchased from a spécifie venue or centre and requires the agent to hâve the requisite funds available, which can increase the duration of the agent’s downtime.

There are currently no technical solutions which aid in limiting agent downtime, and there is accordingly scope for improvement.

SUMMARY OF THE INVENTION

In accordance with an aspect of the invention there is provided a computer-impiemented method conducted by a server computer connected to a mobile téléphoné network in which an agent identifier is linked to an electronic voucher distribution account from which an electronic voucher can be distributed, the method comprising: in response to receiving an event trigger notification, transferring a first amount from a service provider account to the electronic voucher distribution account; monitoring the mobile téléphoné network for a second predetermined event; and, upon detecting occurrence of the second predetermined event, automatically transferring a second amount based on the first amount to a service provider account.

The electronic voucher may be an airtime or mobile bundle voucher usable by a subscriber to top-up or recharge an airtime or mobile bundle account.

The service provider account may include a first service provider account and a second service provider account, and transferring the first amount from the service provider account to the electronic voucher distribution account may include transferring the first amount from the first service provider account to the electronic voucher distribution account; and, transferring the second amount based on the first amount to the service provider account may include transferring the second amount to the second service provider account.

The method may include receiving the event trigger notification. Receiving the event trigger notification may include receiving notification of an agent-initiated request message requesting transfer of the first amount. The agent-initiated request message may include a requested value equal to the first amount. The agent-initiated request message may be received from an agent device via one of an SMS, USSD, 1VR, mobile application or webKoccri r'Arrirni rhonnal mujw wi i iii iiui livau νι i vi îc*i ιι iui.

The method may include monitoring the electronic voucher distribution account for a first predetermined event, and receiving the event trigger notification may include detecting occurrence of the first predetermined event. Transferring the first amount from the service provider account to the electronic voucher distribution account may be initiated automatically upon detecting occurrence of the first predetermined event.

The first predetermined event may be a low balance event indicating that a balance of the electronic voucher distribution account has reached a predetermined low level. The second predetermined event may be a top-up event associated with a top-up amount and an instruction to top-up a balance of the electronic voucher distribution account with the topup amount. The electronic voucher distribution account may be a field in a first database maintained by an electronic voucher distribution System providing an electronic voucher distribution service.

The electronic voucher distribution System may be configured for electronic distribution of electronic vouchers by the agent to other subscribers. The vouchers may be airtime vouchers or mobile bundle vouchers and may be associated with an amount of airtime. Monitoring the mobile téléphoné network for the second predetermined event may include monitoring an electronic voucher distribution System of the mobile téléphoné network. The agent identifier may be linked îo a network utilisation account in a second database maintained by a charging System of a mobile network operator. The account may be a network utilisation account against which utilisation of the mobile téléphoné network by a handset associated with the agent identifier îs charged. One or more of the electronic voucher distribution account, network utilisation account, first service provider account and second service provider account may be airtime accounts configured to store a value of airtime.

In accordance with a further aspect of the invention there is provided a System including a server computer connected to a mobile téléphoné network in which an agent identifier is linked to an electronic voucher distribution account from which an electronic voucher can be distributed, the System comprising: a processor and a memory configured to provide computer program instructions to the processor to execute functions of components; an event trigger receiving component for receiving an event trigger notification; a transferring component for, in response to receiving an event trigger notification, transferring a first amount from a service provider account to the electronic voucher distribution account; a network monitoring component for monitoring the mobile téléphoné network for a second predetermined event; wherein the transferring component is further for, upon detecting occurrence of the second predetermined event, automatically transferring a second amount based on the first amount to a service provider account.

In accordance with a further aspect of the invention there is provided a computer program product comprising a computer-readable medium having stored computer-readable program code for performing the steps of: in response to receiving an event trigger notification, transferring a first amount from a service provider account to an electronic voucher distribution account linked to an agent identifier and from which an electronic voucher can be distributed; monitoring a mobile téléphoné network for a second predetermined event; and, upon detecting occurrence of the second predetermined event, automatically transferring a second amount based on the first amount to a service provider account.

Further features provide for the computer-readable medium to be a non-transitory computer-readable medium and for the computer-readable program code to be exécutable by a processing circuit.

Embodiments of the invention will now be described, by way of example only, with reference to the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS in the drawings:

Figure 1 is a schematic diagram which ihustrates an exemplary System for managing an electronic voucher distribution account according to aspectsofthe présent disclosure;

Figure 2 is a schematic diagram which illustrâtes an exemplary data structure which may be maintained by a charging System according to aspects of the présent disclosure;

Figure 3 is a schematic diagram which illustrâtes an exemplary data structure which may be maintained by an electronic voucher distribution System according to aspects ofthe présent disclosure;

Figure 4 is a swim-iane flow diagram in which an example method for managing an electronic voucher distribution account is illustrated according to aspects of the présent disclosure;

Figure 5 is a block diagram which illustrâtes exemplary components of a System for managing an electronic voucher distribution account according to aspects of the présent disclosure;

Figure 6 is a schematic diagram which illustrâtes an example transaction flow according to aspects of the présent disclosure; and,

Figure 7 illustrâtes an example of a computing device in which various aspects of the disclosure may be implemented.

DETAILED DESCRIPTION WITH REFERENCE TO THE DRAWINGS

Aspects of the présent disclosure provide a System and method for managing an electronic voucher distribution account. Aspects of the présent disclosure may provide components for monitoring an electronic voucher distribution account and transferring value to the account in response to detecting a first predetermined event, such as a iow balance event. The value transferred may be an amount of airtime that is provisioned to the account in advance of payment. In other words, the transfer of value may be an airtime advance that is provisioned to the electronic voucher distribution account in advance of received payment. In some scénarios, real-time monitoring of the electronic voucher distribution account and automatic transfer of value in response to detecting the first predetermined event may significantly reduce downtime that would otherwise be experienced by an agent associated with the account due to the low balance event.

The electronic voucher distribution account may be maintained by an electronic voucher distribution system and linked to an agent identifier, such as an MSISDN or dérivative thereof. The electronic voucher distribution account may be separate from a network utilisation account which may be maintained by a charging system (or billing system) of a mobile network operator and which may be linked to the same agent identifier.

Figure 1 is a schematic diagram which illustrâtes an exemplary system (100) for managing an electronic voucher distribution account. The system (100) may include a mobile network operator (MNO) piatform (104) and a server computer (106). The system may further include an agent mobile handset (108) associated with an agent (109) and a subscriber mobile handset (110) associated with a subscriber (111). It should be appreciated that although only one agent mobile handset and one subscriber mobile handset are illustrated, in a practical implémentation there may be a plurality of these for each of a plurality of subscribers and agents.

The MNO piatform may be maintained or operated by an MNO, The agent may be a subscriber who has registered with the MNO to provide airtime vending and optionally other services to othersubscribers (such as the subscriber) on behalf ofthe MNO. Both the agent and subscriber may be “prepaid subscribers” in that they subscribe to a prepaid plan or subscription model offered by the MNO meaning that they hâve to prepay for mobile téléphoné network utilisation, typically by purchasing airtime and/or bundles. Each of the agent mobile handset and subscriber mobile handset (and in turn each of the agent and subscriber) may be associated with a unique identifier, such as an MSISDN, IMSI, dérivatives of one or both of the MSISDN or IMSI, a random number (such as a globallyunique random number) or the like,

The MNO piatform (104) may be provided by one or more suitable computing devices, such as a server computer, server computer cluster, cloud-based server computer or the like. The MNO piatform together with other infrastructure may provide a mobile téléphoné network (105) on which the mobile handsets (108, 110) may communicate with each other, other mobile handsets, the broader public switched téléphoné network (PSTN) as well as the Internet.

The mobile handsets may, for example, be able to make and receive téléphoné calls (including Voice over Internet Protocol (VOIP) téléphoné calls) to and from other mobile handsets connected to the mobile téléphoné network (possibly via the PSTN or Internet).

The mobile téléphoné network (105) may, for example, include one or more base station subsystems (BTSs) while the MNO piatform (104) may provide back-end Systems such as a USSD/GPRS gateway and associated components (MSC, VLR, HLR, etc.).

In the mobile téléphoné network (105), each BTS is given an identity and may be grouped with other BTSs according to location area, which groups may also be given an identity. Each MSC/VLR (Mobile Services Switching Centre/Visitor Location Register) serves the BTSs in a number of location areas. The mobile handsets (108,110) may report to the VLR when they move from a BTS in one location area to a BTS in another location area.

The VLR may keep track of the location area in which each of the mobile handsets (108, 110) is located. The HLR (Home Location Register) may in turn know which MSC/VLR the rnobite handset is at as well. An MSISDN associated with each mobile handset may inform the network ofthe HLR to which the mobile handset belongs.

Téléphoné calls may be routed through the téléphoné network to the closest MSC to the relevant mobile handset associated with the MSISDN to which the call is directed. The MSC may query the HLR for the mobile handset location. Based on this query, the call may be associated with the actual MSC/VLR (Visiting MSC) either directly or through the PSTN. Finally, a request for a mobile call may be transmitted over al! BTSs in the actual location area of the target mobile handset. The mobile handset may recognise its own identity, and the call begins.

Calls initiated from the mobile handset may include sending a call request from the mobile handset via a radio path to a local BTS which is then on-forwarded to the MSC/VLR. The

MSC/VLR may coiiect autnentication data from HLR (if such data has not been coiiected earlier) and the MSC/VLR may request the HLR of the actual location of GSM subscriber, and the call is established as described earlier.

The mobile téléphoné network (105) may be usable by the mobile handsets for initiating téléphoné calls to and receiving téléphoné calls from other handsets. Other téléphonie transactions that may be conducted on the mobile téléphoné network include sending and receiving SMS messages, establishing USSD sessions, exchanging data messages or data packets (e.g., for Internet browsing by mobile software applications, etc.) and the like.

The MNO platform (104) may include an intelligent network (IN) (114) and a charging system (116). The IN (114) may be implemented according to any suitable network architecture (e.g. that specified in the ITU-T Q.1200 sériés recommendations, or the like). The IN (114) may allow the MNO to provide various value-added services, such as network usage advance services, in addition to the standard telecom services such as PSTN, GSM, etc. The IN may include one or more network nodes on the service layer, distinct from the switching layer of the core network, as opposed to solutions based on intelligence in the core switches or equipment. The IN may be supported by the Signalling System #7 (SS7) protocol between network switching centres and other network nodes owned by network operators.

The charging system (116) may be implemented as a node within the IN (114) that is responsible for collecting data on service usage and to generate reports thereon for billing, either on demand or automatiealïy. The charging system (116) may be implemented as a high-throughput database that maintains multiple accounts for each subscriber. The purpose, type and usage of the accounts may be defined by the MNO.

The charging system (116) may maintain a data structure in which each row is associated with a subscriber (identified by way of its unique identifier) and columns are associated with accounts. An exemplary data structure (200) which may be maintained by the charging system (116) is illustrated in Figure 2. In the exemple data structure of Figure 2, each identifier (202, 204), being the identifiers of the agent and subscriber, respectively, may be associated with a network utilisation account (206, 208) against which the agents and subscriber’s respective utilisation of the mobile téléphoné network is charged. In some implémentations each subscriber (including the agent) may be associated with multiple accounts in addition to the network utilisation account, such as one or more mobile bundle accounts, dedicated accounts to which airtime or bundle advances can be provisioned, tracking accounts, etc. In some implémentations, the network utilisation account may include one or more sub accounts, such as a general network utilisation account (e.g. an airtime account) and one or more mobile bundle accounts (such as a voice minute bundle 5 account, an SMS bundle account, a data bundle account, etc-.). In some implémentations, each identifier (202, 204) may be associated with a service class field (210, 212) being provided by a further column of the data structure. Airtime top-ups for the agent or subscriber may be provisioned to the network utilisation account of the agent or subscriber, as may be appropriate, and usage of the mobile téléphoné network (105) by the agent or 10 subscriber may be charged against the relevant network utilisation account.

The accounts of the charging system described herein may be implemented fields of a database, which may be a high-throughput database configured for manipulation and/or accessing of multiple fields per second. The fields may be associated with identifiers and 15 can be updated or modified in real-time in response to network usage or top-up events.

Different fields of the database may represent different accounts associated with a particular subscriber. Other fields may be stored in a subscriber profile associated with the identifier and may for example include: an activation date, an expiration date, a first call flag and the like. The service class may be used by the operator to group the subscribers 20 and assign tariffs, services, etc. In some embodiments, the service class field may be configured to prevent airtime top ups and/or mobile téléphoné network utilisation by agents who hâve outstanding voucher distribution account advances.

The MNO platform (104) may further include or interface with an electronic voucher 25 distribution (EVD) system (130). The EVD System (130) may be configured to provide an electronic voucher distribution service which aïlows the agent to use their associated agent mobile handset or any other suitable computing device to purchase electronic vouchers for distribution to the subscriber to aîlow the subscriber to perform an airtime top-up or recharge (e.g., by redeeming or loading the voucher). An electronic voucher may be an 30 airtime or mobile bundle voucher which can be used by the subscriber to top-up or recharge a network utilisation account (such as an airtime or mobile bundle account).

The electronic voucher distribution system (130) may include an agent interface (132) via which the agent mobile handset (108) can requestan electronic voucher of a spécifie value 35 or amount. The electronic vouener distribution system (130) may include an electronic voucher generating module (134) configured to generate an electronic voucher associated with the spécifie value or amount. The electronic voucher distribution System (130) may also include an electronic voucher provision module (136) configured to provision the electronic voucher to the purchasing subscriber, either directly to the subscriber mobile handset (110) or to the agent mobile handset (108) for the agent to provide to the subscriber.

The electronic voucher distribution System (130) may maintain an electronic voucher distribution account database (138) in which an electronic voucher distribution account associated with the unique identifier of the agent is maintained. The electronic voucher distribution account database (138) may include or be in the form of a data structure in which each row is associated with an entity (such as the agent, identified by way of its unique identifier) and columns are associated with accounts. Figure 3 illustrâtes an exemplary data structure (220) of the electronic voucher distribution account database (138) in which the agent identifier (202) may be associated with an electronic voucher distribution account (222), which may also be termed a “wallet” or “airtime vending wallet”, etc. The value of or amount of airtime associated with each electronic voucher requested by the agent is recorded against (e.g., deducted from) the agent’s electronic voucher distribution account (222). The electronic voucher distribution account (222) may be an airtime account (i.e. an account that stores a value of airtime) and may be required to hâve a value or positive balance being greater than or equal to the spécifie value of or amount of airtime associated with the electronic voucher being requested. In other words, the balance of the electronic voucher distribution account may be required to be greater than the value of the electronic voucher being requested. The agent may be able to top-up or recharge the electronic voucher distribution account through various mechanisms.

In some implémentations each agent identifier may be associated with multiple accounts or fields in the voucher distribution account database (138), such as a loan account, a loan tracking account, a fee account, a service class field and the like. Such accounts may be used to track airtime advances provisioned in faveur of the agent identifier.

The MNO platform (104) may maintain a service provider account database (140) in which one or more service provider accounts associated with a service provider may be maintained. The service provider may provide an electronic voucher distribution account management service to the MNO. In some embodiments, the service provider account database (140) may maintain a first service provider account (e.g. a vending account from which airtime advances are disbursed) and a second service provider account (e.g. a recovery account into which outstanding ioan amounts are recovered), each of which is linked to a unique identifier of the service provider. In some embodiments, the service provider account database (140) may be maintained by the EVD system (130). Although the databases are illustrated in Figure 1 as being separate or discrète databases, in some embodiments the service provider account database (140) and electronic voucher distribution account database (138) may be one and the same database. For example, the service provider accounts may be accounts within the electronic voucher distribution account database (138) associated with a unique identifier of the service provider.

The server computer (106) may be maintained or operated by the service provider. The server computer may be provided by one or more suitable computing devices, such as a server computer cluster, distributed server computer, cloud-based server computer or the like. The physical location of the server computer may be unknown and irrelevant to the parties making use of the service.

The server computer (106) may be configured to provide an electronic voucher distribution account management service to the MNO. It should be appreciated that although embodiments described herein attribute certain functionality to Systems maintained or methods performed by a service provider, it is conceivable that such Systems and methods may be maintained, performed or provided by the MNO itself without reîying on an external and/or third party service provider. Such démarcations are illustrative of an example embodiment only.

The MNO platform (104), server computer (106), agent mobile handset (108) and subscriber mobile handset (110) may be configured to communicate with one another via a suitable communication network (150), which may include the mobile téléphoné network (105), Internet and the like.

The system described above may be configured to implement a method for managing an electronic voucher distribution account. An example method for managing an electronic voucher distribution account is illustrated in the swim-lane flow diagram Figure 4, in which respective swim-lanes delineate steps, operations or procedures performed by respective entities or devices. It should be appreciated that the délinéation as illustrated in Figure 4 is one example délinéation and other embodiments may use other délinéations.

The server computer may receive an event trigger notification. The event trigger notification may be a notification or alert generated by the server computer or may be received from the MNO platform. Receiving the event trigger notification may inciude receiving notification of an agent-initiated request message requesting transfer of an amount of airtime (i.e. an amount of airtime to be advanced). The agent-initiated request message may include a requested value of airtime to be advanced amount (a “first amount” for the purpose of describing this method). The agent-initiated request message may be received from an agent device via one of an SMS, USSD, IVR, mobile application or web-based communication channel.

In some embodiments, the server computer (106) may monitor (302) an electronic voucher distribution account (222) for a first predetermined event. The electronic voucher distribution account (222) may be linked to or associated with an identifier of an agent. The electronic voucher distribution account (222) may be maintained by an EVD system (130). Monitoring (302) the electronic voucher distribution account (222) may include polling or listening to an electronic voucher distribution account database (138) for the first predetermined event, monitoring an events database or log file to which event notifications are posted or the like.

In some implémentations, monitoring (302) the electronic voucher distribution account (222) for the first predetermined event may include a database trigger executing in the electronic voucher distribution account database (138) transmitting (304) and the server computer receiving (306) a trigger alerting the server computer of the occurrence of the first predetermined event. The database trigger may be any suitable procédural code that is automatically executed in response to certain events (such as the first predetermined event) on the electronic voucher distribution account database (138), The first predetermined event may be a low-balance event indicating that a balance of the electronic voucher distribution account has reached a predetermined low level. The predetermined low level may for example be ZAR100, ZAR50, ZA10, ZAR0 or the like.

In such embodiments, receiving the event trigger notification may include detecting (307) occurrence of the first predetermined event.

The server computer may détermine agent eligibility for a transfer of value (or an “advance” or “airtime advance”) and may détermine a maximum amount of value (e.g. an amount of airtime) to be transferred. Determining eligibility may include checking an eïigibie agent list, evaluating an agent score associated with the agent identifier, checking an agent blacklist and the like. Determining the amount of value (i.e. the amount of airtime to be transferred) may include determining the amount based on the agent score and/or other data associated with the agent. In some embodiments, the amount may be tailored to the agent’s 5 particular circumstances, crédit worthiness and/or transacting habits. The amount may therefore be unique to the agent and may differ from amounts advanced to other agents.

The server computer may transfer (308) a first amount from a service provider account to the electronic voucher distribution account (222). If the transfer is in response to detecting 10 the predetermined event, transferring the first amount from the service provider account to the electronic voucher distribution account may be initiated automatically upon detecting occurrence of the first predetermined event. Transferring of the first amount may only be initiated if the agent is eligible for the transfer.

The service provider account may include a first service provider account and a second service provider account and transferring the first amount from the service provider account to the electronic voucher distribution account may include transferring the first amount from the first service provider account to the electronic voucher distribution account. Transferring (308) the first amount may include the server computer (106) instructing the MNO platform 20 (104) to transfer the first amount from the service provider account to the electronic voucher distribution account. In some implémentations, the server computer may instruct the EVD system (130) to transfer the first amount and the EVD system may effect (310) the transfer of the first amount from the service provider account to the electronic voucher distribution account. The EVD system (130) may effect the transfer by adjusting or modifying the values 25 stored in the first service provider account and electronic voucher distribution account, respectiveiy. The value of the first amount may be equai to or less than the maximum amount of value for which the agent is determined to be eligible based on the agent score, etc.

In some embodiments, effecting the transfer may include recording an outstanding advance amount against a record associated with the agent identifier. This may include recording the first amount or an amount based on the first amount against a loan account associated with the agent identifier in the electronic voucher distribution account database (138) or the like in order to indicate the first amount or associated amount as being the 35 value ofthe outstanding loan. In some implémentations, the outstanding loan amount may be determined to be a percentage of the first amount such that a discount is provided to the agent. For exampie, tne first amount may be equai to ZAR1.000 whiie the outstanding loan amount may be determined to be equal to ZAR985 to thus provide a 1.5% discount to the agent on the cost of the airtime.

Transfer of the first amount may therefore be pushed or initiated from the server computer in response to detecting the first predetermined event or pulled or initiated by the agent requesting the transfer by transmitting an agent-initiated request message from the agent mobile handset (108).

ln some embodiments, the server computer (106) may instruct (312) restriction of a network utilisation account (206) associated with the agent identifier. The restriction may be a restriction on the topping-up or recharging of the network utilisation account (or associated accounts) and/or utilisation of the mobile téléphoné network by the agent mobile handset associated with the agent identifier, ln some embodiments, this may be implemented by changing the value of a service class field associated with the agent identifier in the charging system (116) to one which represents or indicates and implements such a restriction. For example, in response to receiving a restriction instruction, the MNO platform may restrict (314) transactions against and/or in favour of a network utilisation account by changing a value of the service class field (210) from a first predetermined value associated with no restriction to a second predetermined value associated with a restriction. The MNO platform and/or charging system may be configured to query the service class field (210) in order to détermine whether any restrictions are in place against the network utilisation account (206) of the agent (109) before allowing any transactions to proceed or continue.

The server computer may monitor (316) the mobile téléphoné network (105) for a second predetermined event. The second predetermined event may be a top-up event associated with an instruction to top-up a balance of the electronic voucher distribution account. The second predetermined event may be associated with a top-up amount. For example, in the case ofthe second predetermined event being a top-up event, the top-up amount may be an amount of airtime associated with the top-up. Monitoring (316) the mobile téléphoné network for the second predetermined event may include monitoring the EVD system (130), the electronic voucher distribution account database (138) and/or the electronic voucher distribution account (222) associated with the agent identifier. In some embodiments, the EVD system (130) may transmit (318), and the server computer may receive (320) a notification in response to receiving a top-up instruction, ln other embodiments, a database trigger executing in the electronic voucher distribution account database (138) may transmit and the server computer may receive a trigger in response to the top-up amount being transferred to the electronic voucher distribution account (222) associated with the agent identifier.

Upon detecting (322) occurrence of the second predetermined event, the server computer (106) may automatically transfer (324) a second amount based on the first amount and/or the top-up amount to a service provider account. The transfer is a redirection ofthe amount, such that it reflects in the service provider account and not in the electronic voucher distribution account to which it was originally destined. Transferring (324) the second 10 amount to the service provider account may include transferring the second amount to the second service provider account.

The second amount may be determined or set to equal the first amount if the top-up amount is equal to or greater than the first amount. In some implémentations, an outstanding loan 15 amount is determined based on the first amount, and the second amount may be determined or set to equal the outstanding loan amount if the top-up amount is equal to or greater than the outstanding loan amount. In either case, the amount associated with the outstanding loan is fully recovered, and the server computer may update the loan account or other record associated with the agent identifier to indicate complété recovery of the 20 outstanding loan.

Otherwise, the second amount may be set to equal the top-up amount if the top-up amount is less than the first amount or the outstanding loan amount, as may be appropriate. In this case, the amount associated with the outstanding loan is partially recovered, and the server 25 computer may update the loan account or other record associated with the agent identifier to indicate partial recovery of the outstanding loan; for example, by subtracting the second amount from the first amount or outstanding loan amount to leave an amount indicating the updated outstanding loan amount,

In some embodiments, transferring (324) the second amount to the service provider account may include redirecting a portion or ail of the top-up amount associated with the top-up event to the service provider account. This may include the server computer instructing (326) and the EVD System (130) converting (32S) the top-up instruction to a recovery instruction in which the top-up amount is associated with the top-up event. In other 35 embodiments, transferring the second amount to the service provider account may include automatically transferring the second amount from the electronic voucher distribution account (222) to the service provider account after the second amount has been provisioned to the electronic voucher distribution account.

In some implémentations, the server computer (106) may instruct the EVD system (130) to transfer the second amount and the EVD system may effect the transfer of the second amount from the electronic voucher distribution account to the service provider account. The EVD system (130) may effect the transfer by adjusting or modifying the values stored in the service provider account and electronic voucher distribution account respectively.

In some embodiments, if (330) the second amount is sufficient to enable full recovery of the outstanding loan amount, the server computer may instruct (332) derestriction of the network utilisation account (206) associated with the agent identifier. In some embodiments, this may be implemented by changing the value of a service class field associated with the agent identifier in the charging system (116) to one which represents or indicates derestriction or no restrictions. For example, in response to receiving a restriction instruction, the MNO piatform may de-restrict (334) the network utilisation account by changing a value ofthe service class field (210) from a second predetermined value associated with restriction to a first predetermined value associated with no restriction.

The operations of transferring value or amounts and recording values as outstanding, as described with reference to Figure 4 above, may be effected by updating fields of the appropriate account databases so as to record the transfer or to log the outstanding amount. Thus the term “transfer” and variants thereof should be inîerpreted to include the updating or manipulating of fields or other records so as to effect and record the transfer of amounts or values.

Various components may be provided for implementing the method described above with reference to Figure 4. Figure 5 is a block diagram which illustrâtes exemplary components, which may be provided by a system (500) for managing an electronic voucher distribution account. The system may include a server computer (106).

The server computer (106) may include a processor (502) for executing the functions of components described below, which may be provided by hardware or by software units executing on the server computer (106). The software units may be stored in a memory component (504) and instructions may be provided to the processor (502) to carry out the functionality of the described component.

The server computer (106) may include an EVD System interface (506) for interfacing with an EVD System (130). The EVD System interface may be provided by way of a suitable application programming interface (API) and may enable the exchange of information, requests and responses between the server computer and the EVD System.

The server computer (106) may include a charging System interface (508) for interfacing with a charging System (116). The charging System interface (508) may be provided by way of a suitable API and may enable the exchange of information, requests and responses between the server computer and the charging System (116).

The server computer (106) may include a network monitoring component (510) for monitoring a mobile téléphoné network (105) for events, such as a first predetermined event and/or a second predetermined event. The network monitoring component may be configured to monitor one or more of a charging System (116), service provider account database (140), EVD System (130) including one or more of an electronic voucher distribution account database (138) and accounts maintained with the electronic voucher distribution account database (138). The network monitoring component (510) may include an account monitoring component (512) for monitoring the electronic voucher distribution account (222) for events, such as a first and/or second predetermined event.

The server computer (106) may include an event trigger receiving component (513) for receiving an event trigger notification. In some embodiments, event trigger receiving component (513) receives event triggers in the form of a notification of an agent-initiated request message requesting transfer of the first amount. The agent-initiated request message may be received at the server computer or the MNO platform from an agent device via one of an SMS, USSD, IVR, mobile application or web-based communication channel. In some embodiments, the event trigger receiving component (513) receives an event trigger notification generated by the network monitoring component (510) in response to detecting occurrence of the first (or another) predetermined event.

The server computer (106) may include a transferring component (514) arranged to transfer, upon detecting occurrence of the first predetermined event, a first amount from a service provider account to the electronic voucher distribution account. The transferring component (514) may further be arranged to transfer, upon detecting occurrence of the second predetermined event, a second amount, based on the first amount and/or a top-up amount, to a service provider account The transféra may be automatic and may be triggered in response to detecting occurrence of the relevant event. The transferring component (514) may interface with the EVD system (130) via the EVD system interface (506) in order to instruct or otherwise effect the transfers.

The server computer (106) may include a network utilisation account configuration component (516) for instrucfing restriction and derestriction of a network utilisation account maintained by a charging system (116) and associated with the agent identifier. The network utilisation account configuration component (516) may interface with the charging system (116) via the charging system interface (508) in order to instruct or otherwise effect the restriction/derestriction.

Figure 6 is a schematic diagram which illustrâtes an example transaction flow according to aspects of the présent disctosure. The service provider may hâve a first service provider account and a second service provider account on the MNO platform (104). The first service provider account may be a vending account and may be provisioned with an amount of airtime (e.g. ZAR1,000). The airtime may be provisioned via a line of crédit (602) from the MNO or other entity and may be provisioned to the service provider at a discount (e.g, 5% discount such that the service provider owes ZAR950), The vending account may thus hâve a balance (604) ofZARI,000 available for Sending while the service provider may owe (606) the MNO ZAR950. At some stage, the agent’s electronic voucher distribution account may reach a predetermined low level in response to which the service provider may provision (607) a loan of an amount of airtime (e.g. ZAR1.000), which loan may be funded from the service provider vending account. The airtime may be provisioned at a discounted rate (e.g. 1.5% discount) such that the agent owes (608) a discounted amount of airtime to the service provider (e.g. ZAR985). The agent may then be able to use the positive balance on loan from the service provider to continue vending airtime (610, 612). At some stage, the agent may top up (614) their electronic voucher distribution account, This may trigger a recollection or recovery in which the top-up amount (up to the amount owed by the agent, i.e. ZAR985) is transferred (616) to the second service provider account, being a recovery account (e.g. as described above with reference to Figure 4). The service provider has thus received ZAR985 for a ZAR1,000 airtime loan that cost the service provider ZAR950, entitiing the service provider to a margin (617) in this example of ZAR35. At some stage the balance of the service provider recovery account may be refunded by the MNO to the service provider at a one-to-one rate, which may be used to fund a further provision of airtime (618) to the service provider vending account for further advancing to agents.

Aspects of the présent disclosure provide a system and method for electronic- voucher distribution account management. Aspects of the présent disclosure provide a server computer which may be operated or maintained by a service provider. The server computer may be configured to instruct/ask an MNO platform to transfer airtime to an agents airtime account (such as the agents electronic voucher distribution account). The server computer 10 may be configured to inform the MNO platform of an outstanding loan amount (e.g. of airtime) as a conséquence of the agents loan, and instruct the MNO platform to record an outstanding loan amount for this agent (e.g. by placing the agent in a négative balance, etc.). In some implémentations, while there is an outstanding loan amount (e.g. négative balance), the agent cannot buy and/or use airtime from the MNO until the agent fuily 15 recovers the loan. In the event of a top-up payment (such as an airtime purchase) by an agent with an outstanding loan amount, the MNO platform may be configured (e.g. in response to an instruction from the server computer) to transfer the purchased airtime (up to the outstanding loan amount) to a service provider account (for full or partial recovery). The service provider and MNO may agréé on a periodical conversion of the collected 20 Airtime into monetary value (e.g. at a one-to-one rate), in order for the service provider vending account to be refunded and the respective service provider revenues to be paid by the MNO.

Figure 7 illustrâtes an example of a computing device (700) in which various aspects of the 25 disclosure may be implemented. The computing device (700) may be embodied as any form of data processing device including a Personal computing device (e.g. laptop or desktop computer), a server computer (which may be self-contained, physically distributed over a number of locations, etc.), a client computer, or a communication device, such as a mobile phone (e.g. cellular téléphoné), satellite phone, tablet computer, personal digital 30 assistant or the like. Different embodiments of the computing device may dictais the inclusion or exclusion of various components or subsystems described below.

The computing device (700) may be suitable for storing and executing computer program code. The various participants and éléments in the previously described system diagrams 35 may use any suitable number of subsystems or components of the computing device (700) to facilitate the functions described herein. The computing device (700) may include subsystems or components interconnected via a communication infrastructure (705) (for example, a communications bus, a network, etc.). The computing device (700) may include one or more processors (710) and at least one memory component in the form of computerreadable media. The one or more processors (710) may include one or more of: CPUs, graphical processing ursits (GPUs), microprocessors, field programmable gâte arrays (FPGAs), application spécifie integrated circuits (ASICs) and the like. In some configurations, a number of processors may be provided and may be arranged to carry out calculations simultaneously. In some implémentations various subsystems or components of the computing device (700) may be distributed over a number of physical locations (e.g. in a distributed, cluster or cloud-based computing configuration) and appropriate software units may be arranged to manage and/or process data on behalf of remote devices,

The memory components may include System memory (715), which may include read only memory (ROM) and random access memory (RAM). A basic input/output System (BIOS) may be stored in ROM. System software may be stored in the System memory (715) including operating System software. The memory components may also include secondary memory (720). The secondary memory (720) may include a fixed disk (721), such as a hard disk drive, and, optionally, one or more storage interfaces (722) for interfacing with storage components (723), such as removable storage components (e.g. magnetic tape, optical disk, flash memory drive, external hard drive, removable memory chip, etc.), network attached storage components (e.g. NAS drives), remote storage components (e.g. cloud-based storage) or the like.

The computing device (700) may include an external communications interface (730) for operation of the computing device (700) in a networked environment enabling transfer of data between multiple computing devices (700) and/or the Internet. Data transferred via the external communications interface (730) may be in the form of signais, which may be eleçtronic, electromagnetiç. optical, radio or other types of signal, The external communications interface (730) may enable communication of data between the computing device (700) and other computing devices including servers and external storage facilities. Web services may be accessible by and/or from the computing device (700) via the communications interface (730).

The external communications interface (730) may be configured for connection to wireless communication channels (e.g., a cellular téléphoné network, wireless local area network (e.g. using Wi-Fi™), satellite-phone network, satellite internet network, etc.) and may include an associated wireless transfer element, such as an antenna and associated circuitry. The external communications interface (730) may include a subscriber identity module (SIM) in the form of an integrated circuit that stores an international mobile subscriber identity and the related key used to identify and authenticate a subscriber using the computing device (700). One or more subscriber identity modules may be removable from or embedded in the computing device (700).

The computer-readabîe media in the form of the various memory components may provide storage of computer-executable instructions, data structures, program modules, software units and other data. A computer program product may be provided by a computerreadabîe medium having stored computer-readabîe program code exécutable by the central procèssor (710). A computer program product may be provided by a non-transient or non-transitory computer-readabîe medium, or may be provided via a signal or other transient or transitory means via the communications interface (730),

Interconnection via the communication infrastructure (705) allows the one or more processors (710) to communicate with each subsystem or component and to control the execution of instructions from the memory components, as well as the exchange of information between subsystems or components. Peripherais (such as printers, scanners, caméras, or the like) and input/output (I/O) devices (such as a mouse, touchpad, keyboard, microphone, touch-sensitive dispiay, input buttons, speakers and the like) may couple to or be integrally formed with the computing device (700) either directly or via an I/O controller (735). One or more displays (745) (which may be touch-sensitive displays) may be coupled to or integrally formed with the computing device (700) via a display or video adapter (740).

The foregoing description has been presented for the purpose of illustration; it is not intended to be exhaustive or to limit the invention to the précisé forms disclosed. Persons skilled in the relevant art can appreciate that many modifications and variations are possible in light of the above disclosure.

Any of the steps, operations, components or processes described herein may be performed or implemented with one or more hardware or software units. atone or in combination with other devices. In one embodiment, a software unit is implemented with a computer program product comprising a non-transient or non-transitory computer-readabîe medium containing computer program code, which can be executed by a processor for performing any or ail of the steps, operations or processes described. Software units or functions described in this application may be implemented as computer program code using any suitable computer language such as, for example, Java™, C++, or Perl™ using, for example, conventional or object-oriented techniques. The computer program code may be stored as a sériés of instructions or commands on a non-transitory computer-readable 5 medium, such as a random access memory (RAM), a read-on!y memory (.ROM), a magnetic medium such as a hard-drive, or an optical medium such as a CD-ROM. Any such computer-readable medium may also résidé on or within a single computational apparatus and may be présent on or within different computational apparatuses within a System or network.

Flowchart illustrations and block diagrams of methods, Systems and computer program products according to embodiments are used herein. Each bïock of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, may provide functions which may be implemented by computer 15 readable program instructions. In some alternative implémentations, the functions identified by the blocks may take place in a different order to that shown in the flowchart illustrations,

Some portions of this description describe the embodiments of the invention in terms of algorithms and symbolic représentations of operations on information. These algorithmic 20 descriptions and représentations, such as accompanying flow diagrams, are commonly used by those skilled in the data processing arts to convey the substance of their work effectively to others skilled in the art. These operations, while described functionally, computationally, or logically, are understood to be implemented by computer programs or équivalent electrical circuits, microcode or the like. The described operations may be 25 embodied in software, firmware, hardware, or any combinations thereof,

The language used in the spécification has been principally selected for readability and instructional purposes, and it may not hâve been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the invention be limited 30 not by this detailed description, but rather by any claims that issue on an application based hereon. Accordingly, the disclosure of the embodiments of the invention is intended to be illustrative, but not limiting, of the scope of the invention set forth in any accompanying claims. Finally, throughout the spécification and any accompanying claims, unless the context requires otherwise, the word 'comprise’ or variations such as 'comprises¹ or 35 ‘comprising’ will be understood to imply the inclusion of a stated integer or group of integers but not the exclusion of any other integer or group of integers.

CLAIMS:

Claims (10)

1. CLAIMS:

   1. A computer-implemented method conducted by a server computer connected to a mobile téléphoné network in which an agent identifier is linked to an electronic voucher distribution account from which an electronic voucher can be distributed, the method comprising:

   in response to receiving an event trigger notification, transferring a first amount from a service provider account to the electronic voucher distribution account;

   monitoring the mobile téléphoné network for a second predetermined event; and, upon detecting occurrence of the second predetermined event, automatically transferring a second amount based on the first amount to a service provider account.
2. 2. The method as claimed in claim 1, wherein the electronic voucher is an airtime or mobile bundle voucher usable by a subscriber to top-up or recharge an airtime or mobile bundle account.
3. 3. The method as claimed in claim 1 or claim 2, wherein the service provider account includes a first service provider account and a second service provider account, and wherein:

   transferring the first amount from the service provider account to the electronic voucher distribution account includes transferring the first amount from the first service provider account to the electronic voucher distribution account; and, transferring the second amount based on the first amount to the service provider account includes transferring the second amount to the second service provider account.
4. 4. The method as claimed in any one of claims 1 to 3, including receiving the event trigger notification.
5. 5. The method as claimed in claim 4, wherein receiving the event trigger notification includes receiving notification of an agent-initiated request message requesting transfer of the first amount, wherein the agent-initiated request message includes a requested value equal to the first amount, wherein the agent-initiated request message is received from an agent device via one of an SMS, USSD, 1VR, mobile application or web-based communication channel.
6. 6. The method as cïaimed in ciaim 4 or daim 5, wherein tne method includes monitoring the electronic voucher distribution account for a first predetermined event, and wherein receiving the event trigger notification includes detecting occurrence of the first predetermined event, wherein transferring the first amount from the service provider account to the electronic voucher distribution account is initiated automatically upon detecting occurrence of the first predetermined event, wherein the first predetermined event is a low balance event indicating that a balance of the electronic voucher distribution account has reached a predetermined low level.
7. 7. The method as cïaimed in any one of the preceding claims, wherein the second predetermined event is a top-up event associated with a top-up amount and an instruction to top-up a balance of the electronic voucher distribution account with the top-up amount, wherein one or more of the electronic voucher distribution account, the service provider account, a network utilisation account, a first service provider account and a second service provider account are airtime accounts configured to store a value of airtime.
8. 8. The method as cïaimed in any one of the preceding claims, wherein the electronic voucher distribution account is a field in a first database maintained by an electronic voucher distribution System providing an electronic voucher distribution service, wherein the electronic voucher distribution System is configured for electronic distribution of electronic vouchers by the agent to other subscribers, wherein the agent identifier is linked to a network utilisation account in a second database maintained by a charging System of a mobile network operator wherein monitoring the mobile téléphoné network for the second predetermined event includes monitoring the electronic voucher distribution System of the mobile téléphoné network.
9. 9. A System including a server computer connected to a mobile téléphoné network in which an agent identifier is linked to an electronic voucher distribution account from which an electronic voucher can be distributed, the System comprising: a processor and a memory configured to provide computer program instructions to the processor to execute functions of components; an event trigger receiving component for receiving an event trigger notification; a transferring component for, in response to receiving an event trigger notification, transferring a first amount from a service provider account to the electronic voucher distribution account; and, a network monitoring component for monitoring the mobile téléphoné network for a second predetermined event; wherein the transferring component is further for, upon detecting occurrence of the second predetermined event, automatically transferring a second amount based on the first amount to a service provider account.
10. 10. A computer program product comprising a computer-readable medium having stored computer-readable program code for performing the steps of:

    in response to receiving an event trigger notification, transferring a first amount from a service provider account to an electronic voucher distribution account linked to an agent ίΗοητίΨίϋΓ αηΗ on οΐοηττηηίη wnt mHor non hû Hcan· tuvl t lli 1X^1 C4I ivi I f V I I i VViilSzlI ail K/i y v WVI tVrl 1 Μ 1 Il i WM LVU , monitoring a mobile téléphoné network for a second predetermined event; and, upon detecting occurrence of the second predetermined event, automatically transferring a second amount based on the first amount to a service provider account.