OA19720A - Network usage product provisioning via a mobile wallet platform - Google Patents

Network usage product provisioning via a mobile wallet platform Download PDF

Info

Publication number
OA19720A
OA19720A OA1202000271 OA19720A OA 19720 A OA19720 A OA 19720A OA 1202000271 OA1202000271 OA 1202000271 OA 19720 A OA19720 A OA 19720A
Authority
OA
OAPI
Prior art keywords
network usage
subscriber
mobile wallet
product
data
Prior art date
Application number
OA1202000271
Inventor
Antonios CHATZISTAMATIOU
Original Assignee
Channel Technologies Fze
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Channel Technologies Fze filed Critical Channel Technologies Fze
Publication of OA19720A publication Critical patent/OA19720A/en

Links

Abstract

A system and method for network usage product provisioning via a mobile wallet platform is described. In a method, data elements generated based on credit data that is associated with a subscriber identifier which uniquely identifies a mobile subscriber is obtained. A network usage offer based on or including the data elements may be transmitted to a communication device associated with the subscriber identifier via a subscriber channel of a mobile wallet platform in which the subscriber identifier is associated with a mobile wallet. Acceptance of the network usage offer may be received from the communication device by means of the subscriber channel. The acceptance received from the communication device may be associated with a selected network usage product. An instruction transmitted to cause the network usage product to be provisioned to an account which is maintained by an intelligent network and associated with the subscriber identifier.

Description

NETWORK USAGE PRODUCT PROVIS1ONING VIA A MOBILE WALLET PLATFORM
CROSS-REFERENCE(S) TO RELATED APPLICATIONS
This application claims priority from South African provisional patent application number 2020/04132 filed on 7 July 2020, which is incorporated by reference herein.
FIELD OF THE INVENTION
This invention relates to a system and method for network usage product provisioning via a mobile wallet platform.
BACKGROUND TO THE INVENTION
Some mobile network operator (MNO) platforms include a mobile wallet (also termed “mobile money”) platform for managing mobile wallets on behalf of subscribers and via which individual subscribers can store, transfer and withdraw money, pay merchants, utility providers and the like as well as use and access other financial services.
Some such mobile wallet platforms include features by way of which subscribers can purchase network usage products, such as airtime, voice minute bundles, data bundles, SMS bundles or the like. This can be convenient for subscribers who hâve sufficient funds in their mobile wallet to fund the purchase of the network usage product.
For subscribers having insufficient funds, some mobile wallet platforms include features by way of which cash loans can be obtained and disbursed into the subscriber’s mobile wallet and then used to purchase the relevant network usage product. However, this is a tedious process for the subscriber and amounts to an inefficient use of the MNO platform and network infrastructure. There is accordingly scope for improvement.
The preceding discussion of the background to the invention is intended only to facilitate an understanding of the présent invention. It should be appreciated that the discussion is not an acknowledgment or admission that any of the material referred to was part of the common general knowledge in the art as at the priority date of the application.
SUMMARY OF THE INVENTION
In accordance with an aspect of the invention there is provided a computer-implemented method comprising: obtaining data éléments generated based on crédit data associated with a subscriber identifier which uniquely identifies a mobile subscriber; transmitting a network usage offer based on or including the data éléments to a communication device associated with the subscriber identifier via a subscriber channel of a mobile wallet platform in which the subscriber identifier is associated with a mobile wallet; receiving an acceptance of the network usage offer from the communication device via the subscriber channel, the acceptance being associated with a network usage product; and, transmitting an instruction to cause provisioning of the network usage product to an account maintained by an intelligent network and associated with the subscriber identifier.
The method may include receiving a request for a network usage product in advance of received payment from the communication device via the subscriber channel of the mobile wallet platform; the data éléments may include one or more network usage products available in advance of received payment for acceptance by the mobile subscriber; transmitting the network usage offer includes transmitting the one or more network usage products available in advance of received payment; and receiving an acceptance of the network usage advance offer includes receiving a selected network usage advance product.
The method may include detecting a transaction failure associated with an attempt to purchase a network usage product against the mobile wallet, the transaction failure being triggered due to an insufficient balance of the mobile wallet; the data éléments may include a crédit limit value, and if the crédit limit value and the balance of the mobile wallet together are sufficient, transmitting the network usage offer may include transmitting an offer to advance the différence between the value of the network usage product and the balance of the mobile wallet.
The method may include determining the différence between the value of the network usage product and the balance of the mobile wallet; and comparing the différence to the crédit limit value to détermine whether the différence can be advanced.
The method may include recording a value associated with the accepted network usage offer as outstanding against one or both of the mobile wallet and the account, wherein the value is either a value of the network usage product provisioned in advance of received payment or a différence between the value of the network usage product and a balance of the mobile wallet. The method may include waiting a predefined time period before recording the value as outstanding. The method may include recording a lien configured for automatic recovery of at least part of the value, wherein automatic recovery is in response to a top-up event being detected at the mobile wallet or the account.
The method may be conducted at the mobile wallet platform, wherein obtaining the data éléments includes requesting and receiving the data éléments from a service provider platform; and, transmitting the instruction includes transmitting the instruction to the service provider platform.
The method may be conducted at a service provider platform, wherein the method includes receiving a request for data éléments associated with the subscriber identifier from the mobile wallet platform; transmitting the data éléments to the mobile wallet platform; and, receiving and forwarding the instruction from the mobile wallet platform to the intelligent network.
In accordance with a further aspect of the invention there is provided a computer implemented method conducted at a mobile wallet platform in which a subscriber identifier which uniquely identifies a mobile subscriber is associated with a mobile wallet, the method comprising: obtaining data éléments generated based on crédit data associated with the subscriber identifier; identifying a network usage product associated with the data éléments; and, transmitting an instruction to cause provisioning of the network usage product to an account maintained by an intelligent network and associated with the subscriber identifier.
In accordance with a further aspect of the invention there is provided a system including a memory for storing computer-readable program code and a processor for executing the computer-readable program code, the system comprising: a data element obtaining component for obtaining data éléments generated based on crédit data associated with a subscriber identifier which uniquely identifies a mobile subscriber; an offer transmitting component for transmitting a network usage offer based on or including the data éléments to a communication device associated with the subscriber identifier via a subscriber channel of a mobile wallet platform in which the subscriber identifier is associated with a mobile wallet; an acceptance receiving component for receiving an acceptance of the network usage offer from the communication device via the subscriber channel, the acceptance being associated with a network usage product; and, a transmitting component for transmitting an instruction to cause provisioning of the network usage product to an account maintained by an intelligent network and associated with the subscriber identifier.
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: obtaining data éléments generated based on crédit data associated with a subscriber identifier which uniquely identifies a mobile subscriber; transmitting a network usage offer based on or including the data éléments to a communication device associated with the subscriber identifier via a subscriber channel of a mobile wallet platform in which the subscriber identifier is associated with a mobile wallet; receiving an acceptance of the network usage offer from the communication device via the subscriber channel, the acceptance being associated with a network usage product; and, transmitting an instruction to cause provisioning of the network usage product to an account maintained by an intelligent network and associated with the subscriber identifier.
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 shows a schematic diagram which illustrâtes a system for network usage product provisioning via a mobile wallet platform according to aspects of the présent disclosure;
Figure 2 is a swim-lane flow diagram which illustrâtes an example method for network usage product provisioning via a mobile wallet platform, where a subscriber requests a network usage product in advance of making payment;
L
Figure 3 is a schematic diagram which illustrâtes an example user expérience where a subscriber requests a network usage product in advance of making payment;
Figure 4 is swim-lane flow diagram which illustrâtes an example method for network usage product provisioning via a mobile wallet platform, where a transaction failure associated with an attempt to purchase a network usage product against the mobile wallet is detected;
Figure 5 is a schematic diagram which illustrâtes an example user expérience where a transaction failure associated with an attempt to purchase a network usage product against the mobile wallet is detected;
Figure 6 is a block diagram which illustrâtes exemplary components which may be provided by a System for network usage product provisioning via a mobile wallet platform 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 ofthe présent disclosure relate to a system and method for network usage product provisioning via a mobile wallet platform. Aspects of the présent disclosure provide a mobile wallet platform that obtains data éléments generated based on crédit data associated with a subscriber identifier, identifies a network usage product associated with the data éléments, and transmits an instruction to cause provisioning of the network usage product to an account maintained by an intelligent network and associated with the subscriber identifier. The data éléments may include a crédit limit value or one or more network usage products available in advance of received payment. In some cases, identifying the network usage product may include receiving a subscriberis sélection of one of the network usage products available for provision in advance of received payment. In other cases, identifying the network usage product may include determining or even generating a suitable network usage product to be provisioned in advance of received payment based on the crédit limit value and optionally other data (such as a balance of a mobile wallet associated with the subscriber identifier).
An example System for network usage product provisioning via a mobile wallet platform is illustrated in Figure 1. The system (100) may include a service provider platform (102) and an MNO platform (104).
The service provider platform (102) may be provided by a third-party service provider which provides services to the MNO and its subscribers. In other implémentations, the funçtionality of the service provider platform may be incorporated into the MNO platform. The MNO platform (104) may be provided by a mobile network operator (MNO) which provides access to a mobile network (110) by mobile subscribers. The system (100) may further include communication devices (106), such as mobile handsets, associated with mobile subscribers who subscribe to the MNO and make use of the mobile network (110).
The MNO platform (104) and mobile network (110) may collectively provide the infrastructure by way of which communication devices can communicate with each other and the broader public switched téléphoné network (PSTN) and the Internet. The mobile network (11Q) may for example include one or more base station subsystems while the MNO platform (104) may provide back-end Systems such as a USSD/GPRS gateway, SMSC and associated components (VLR, HLR, etc.).
The MNO platform (104) may include a mobile wallet platform (112), a prepaid gateway (113), an intelligent network (IN) (114) and a charging system (116).
The mobile wallet platform (112) may be configured to manage mobile wallets on behalf of subscribers and provide funçtionality by way of which individual subscribers can transact against their wallets, for example by storing, transferring and withdrawing money, paying merchants, utility providers and other beneficiaries and optionally use and access other financial services.
The mobile wallet platform (112) may include a subscriber channel (112A) via which the mobile wallet platform interfaces with the mobile network (110) and in turn the communication devices (106) of individual subscribers. The subscriber channel (112A) may provide access to the mobile wallet platform via SMS, IVR, USSD, software application or web channels. The mobile wallet platform (112) may transmit and receive data and/or messages to and from the respective communication devices (106) via the subscriber channel (112A) and the mobile network (110). The mobile wallet platform (112) may for example be configured to receive requests and/or instructions from the communication devices (106) via the subscriber channel (112A) and to transmit offers and/or notifications to the communication devices via the subscriber channel.
The mobile wallet platform (112) may hâve access to and/or maintain a wallet database (112B) in which individual mobile wallets (112C) are stored. Each mobile wallet (112C) may be associated with a subscriber identifier and may store balance and/or transaction information. Each mobile wallet (112C) may be configured for transacting against by its associated subscriber via the subscriber channel (112A) so as to enable the mobile wallet platform functionality. The mobile wallet platform (112) may include a lien component (112D) configured to record and monitor liens against individual accounts associated with subscriber identifiers. The lien component (112D) may be configured to redirect the inflow of funds to a mobile wallet (112C) against which a lien is recorded towards partial or full recovery of an outstanding amount associated with the subscriber identifier.
The prepaid gateway (113) may be configured, amongst other things, to deteçt requested usage ofthe mobile network (110) by a subscriber associated with a subscriber identifier, to capture information associated with the requested usage, such as the subscriber identifier, to transmit the captured information to the charging System (116), to receive permitted usage information from the charging system, to permit and monitor usage of the mobile network in accordance with the permitted usage information and to report actual usage information to the charging system.
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 (114) 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, l
either on demand or automatically. In some implémentations, the charging system may be an online charging system (OCS). The charging system (116) may be configured to authenticate and authorize network usage requests associated with subscriber identifiers received from the prepaid gateway (113), détermine and transmit permitted usage information (such as a maximum call duration, etc.) to the prepaid gateway and to receive and charge the subscriber in accordance with actual usage information from the prepaid gateway (113). The charging system (116) may be implemented as or hâve access to a high-throughput database that maintains multiple accounts for each subscriber. The purpose, type and usage ofthe accounts may be defined by the MNO, in some cases upon request by the service provider.
Each subscriber may be associated with one or more of: a main account, a dedicated account, a loan tracking account (also referred to as a principal tracking account) and a fee tracking account. These accounts may be airtime accounts in that their value is denominated in airtime (which is typically équivalent to a value of currency, such as ZAR, USD, NGN, etc.). Each subscriber may further be associated with one or more data bundle, SMS bundle and voice minute bundle accounts which accounts may hâve their values denominated in bytes, a number of SMS messages and a number of minutes and seconds, respectively.
Airtime top-ups, recharges or purchases may be provisioned to the main account and usage ofthe mobile network (110) (such as making phone calls, sending SMS messages, transmitting and receiving data packets) by the subscriber may typically be charged against the main account. Network usage advances (such as airtime advances) may be provisioned to the main account or the dedicated account. Once the network usage advance has been provisioned, further use of the mobile network (110) may be charged against the account to which the network usage advance was provisioned until the balance thereof has been depleted.
Data bundles purchased by the subscriber may be provisioned to a main data bundle account after which the transmission and réception of data packets by the subscriber’s communication device (106) via the mobile network (110) may be recorded (or deducted from) the main data bundle account. Data bundle advances may be provisioned either to the main data bundle account or, in some implémentations, to a dedicated data bundle account. Once provisioned, further transmission/reception of data packets may be recorded against the main data bundle account or the dedicated data bundle account, as the case may be, until the balance thereof has been depleted to zéro. The same may apply, mutatis mutandis, for the SMS and voice minute bundle accounts.
The tracking accounts may be used to keep track of amounts owed by subscribers in respect of advances (or loans) that the subscribers hâve requested and received. A nonzero balance of any one of the tracking accounts (be it loan tracking or fee tracking) may indicate an outstanding advance or an outstanding amount. The value or amount of balance may indicate the amount owed by the subscriber.
The accounts described herein may be implemented as fields of a high-throughput database. The fields may be associated with a subscriber identifier and 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.
In some implémentations, the charging system (116) may include or be embodied by a data structure, such as a table maintained by relational database management system (RDBMS), having rows which are associated with subscribers (identified by way of a subscriber identifier, such as an MSISDN or other suitable identifier) and columns which are associated with account identifiers which identify and correspond to different types of accounts, such as each ofthe respective accounts described in the foregoing.
The System (100) may include a provisioning and recovery node (120), which may be provided by a node of the IN (114). The provisioning and recovery node (120) may be configured to provision network usage products to appropriate accounts of subscribers pursuant to associated events, such as network usage product purchases, network usage product advances, top-up events and the like. The provisioning and recovery node (120) may be configured to manipulate or adjust (e.g. access, change and/or update) fields of the charging system (116) so as to effect the provisioning of airtime and/or mobile bundles. In some implémentations, the provisioning and recovery node (120) may be configured to query one or both of the loan tracking account and fee tracking account upon a subscriber top-up event or other inflow of funds and to divert some or ail of the amount associated with the top-up or inflow in order to effect partial or complété recovery of the outstanding amount represented by these accounts.
The MNO platform (104) may include or more front-end APIs (126) by way of which the service provider platform may interface with components or nodes of the MNO platform, such as the mobile wallet platform (112), the intelligent network (114), the charging system (116), the provisioning and recovery node (120) and the like. The front-end API (126) may interface with or provide access to an IN-integration component for aspects of the interface.
The service provider platform (102) may be provided by any suitable computing device or devices and may for example include a server computer (121). The service provider platform (102) and/or the server computer (121) may be configured to interface and/or integrate with the MNO platform (104), for example the mobile wallet platform (112) and the intelligent network (114). For example, the server computer may be configured to interface with the mobile wallet platform, intelligent network (IN) and/or charging system of the MNO platform via an appropriate front-end API, an appropriate IN intégration component or the like. The service provider platform (102) and/or the server computer (121) may for example be able to transact against mobile wallets maintained by the mobile wallet platform and adjust account balances of accounts stored in the charging system.
The service provider platform (102) and/or the server computer (121) may utilise IN intégration for: receiving MNO (or ‘telco’) related subscriber data; provisioning network usage (or ‘telco’) products; setting/updating/removing liens against accounts maintained by the IN (or ‘telco accounts’); and, receiving loan payments. The service provider platform (102) and/or the server computer (121) may utilise mobile wallet platform intégration for: receiving mobile wallet related subscriber data; crediting loan amounts; setting/updating/removing a lien against the mobile wallets; and, receiving loan payments.
The service provider platform (102) may hâve access to a subscriber database (122) in which a record (124) associated with each subscriber is stored. Each subscriber record (124) may include and be associated with a subscriber identifier. In some implémentations, each subscriber record includes one or more sets of crédit data, such as a crédit score, an outstanding network usage advance status, a network usage advance eligibility, a total crédit limit and the like. The crédit score may be an indication of crédit worthiness or an indication of the risk associated with the subscriber. A high crédit score may indicate low risk while a low crédit score may indicate a high-risk subscriber. The total crédit limit may be a total crédit limit value denominated in a value of airtime. The crédit limit value represents a value of a network usage advance for which a subscriber associated with the subscriber identifier is eligible in advance of payment.
The service provider platform (102) may be configured to perform crédit scoring and risk management operations using data received from the MNO platform and/or other sources and to maintain and update crédit data and/or risk data stored in subscriber records accordingly. For crédit scoring and risk management, the service provider platform may for example be configured to utilize/process available MNO and mobile wallet service data available from the mobile money service provider.
The system (100) may be configured to obtain data éléments generated based on crédit data associated with a subscriber identifier which uniquely identifies a mobile subscriber; transmit a network usage offer based on or including the data éléments to a communication device associated with the subscriber identifier via the subscriber channel of the mobile wallet platform in which the subscriber identifier is associated with a mobile wallet; receive an acceptance of the network usage offer from the communication device via the subscriber channel, the acceptance being associated with a network usage product; and, transmit an instruction to cause provisioning of the network usage product to an account maintained by the intelligent network and associated with the subscriber identifier.
The system (100) may be configured to receive a request for a network usage product in advance of received payment from the communication device via the subscriber channel of the mobile wallet platform. In such a scénario, the data éléments may include one or more network usage products available in advance of received payment for acceptance by the mobile subscriber. The system may be configured to transmit the one or more network usage products available in advance of received payment; and to receive sélection of a network usage advance product.
The system (100) may also be configured to detect a transaction failure associated with an attempt to purchase a network usage product against the mobile wallet of a particular subscriber, the transaction failure being triggered due to an insufficient balance of the mobile wallet. In such a scénario, the data éléments may include a crédit limit value, and if the crédit limit value and the balance of the mobile wallet together are sufficient, the System may be configured to transmit an offer to advance the différence between the value of the network usage product and the balance of the mobile wallet.
The system (100) described above may implement a method for network usage product provisioning via the mobile wallet platform (112). An exemplary method for network usage product provisioning via a mobile wallet platform (112) is illustrated in the swim-lane flow diagram of Figure 2 in which respective swim-lanes delineate steps, operations or k
procedures performed by respective entities or devices. The délinéation illustrâtes one example embodiment and in other embodiments other délinéations may be applied. Figure is described with reference to an example scénario in which a subscriber requests a network usage product in advance of making payment. An example user expérience corresponding to the method of Figure 2 is illustrated in Figure 3.
The subscriber may use his or her communication device (106) to access (200) the mobile wallet platform (112) via the subscriber channel (112A). The access may be via USSD, SMS messaging, IVR, a website, or a mobile wallet application installed on the communication device (106). The communication device (106), and hence the subscriber, may be identifiable to the mobile wallet platform (112) via the subscriber channel, such that communications between the communication device and mobile wallet platform are associated with a subscriber identifier. The subscriber may access (202), for example, a ‘Borrow Network Usage Product’ option via the subscriber channel. Accessing the Borrow Network Usage Product option may cause the communication device (106) to transmit (203) a request for a network usage product to the mobile money platform (112) via the subscriber channel.
The mobile wallet platform (112) may receive (204) the request for the network usage product in advance of received payment from the communication device (106) via the subscriber channel (112A). The request may be associated with the subscriber identifier, which uniquely identifies a mobile subscriber.
The mobile wallet platform (112) may obtain (216) data éléments generated based on crédit data associated with the subscriber identifier. This may include transmitting a data element request message to a service provider platform (102). The data element request may include the subscriber identifier and particulars associated with the request (e.g., in the illustrated embodiment, that the subscriber has selected a borrow network usage product option via the subscriber channel).
The service provider platform (102) may receive the request and may obtain or détermine (218) the data éléments associated with the request. Determining the data éléments may include checking if the subscriber associated with the subscriber identifier is eligible and/or checking a crédit profile associated with the subscriber identifier. The service provider platform (102) may for example use the subscriber identifier to query a subscriber database (122) and access and evaluate relevant data stored in a corresponding subscriber record (124). In the scénario illustrated with reference to Figures 2 and 3, determining the data éléments (218) includes determining or identifying network usage products for which the subscriber is eligible in advance of received payment based on crédit data stored in the subscriber record. For example, based on the crédit data and/or risk profile, the subscriber may be allowed to borrow multiple products up to his/her crédit limit value at the same time.
The service provider platform (102) may return (220) the data éléments to the mobile wallet platform (112). The data éléments may constitute an offer by the service provider platform for acceptance by the subscriber via the subscriber channel. In the scénario illustrated with reference to Figures 2 and 3, the data éléments include one or more network usage products which are available to the subscriber in advance of received payment. The products may be unique to the particular subscriber based on his/her crédit data.
In the illustrated implémentation, the mobile wallet platform (112) transmits (222) a network usage offer based on or including the data éléments to the communication device (106) associated with the subscriber identifier. The transmission may be via the subscriber channel (112A). In the scénario illustrated with reference to Figures 2 and 3, the offer includes a list ofthe one or more network usage products. The communication device (106) may receive and display (223) the network usage offer, which in the illustrated scénario includes a list of network usage products available for sélection by the subscriber. The offer may be presented to the subscriber along with the product and loan terms. Product terms may include bundle details and expiry. Loan terms may include fee, duration/ term, etc. The subscriber may input his or her sélection into the communication device, which receives (225) the input and transmits an acceptance of the network usage offer to the mobile wallet platform (112) via the subscriber channel (112A). The acceptance is associated with a network usage product, in this scénario being the product selected by the subscriber. The mobile wallet platform (112) receives (227) acceptance of the network usage offer and requests (228) provision of the relevant network usage product. In this scénario, receiving acceptance of the network usage advance offer includes receiving a sélection of a network usage advance product from the list of one or more network usage advance products.
It should be appreciated that in other implémentations, the method mobile wallet platform may identify a suitable network usage product based on the data éléments without reaching out to the subscriber. This may enable so called auto-refill functionality.
In the illustrated embodiment, requesting (228) provision of the network usage product may include the mobile wallet platform (112) transmitting an instruction to the service provider platform (102) to cause provisioning of the network usage product to an account maintained by an intelligent network and associated with the subscriber identifier. In other embodiments, requesting provision of the network usage product may include the service provider platform instructing the IN to provision the network usage product.
In the illustrated embodiment, the service provider platform (102) receives the instruction and provisions (230) the network usage product. The service provider platform (102) may also register the loan, including for example updating the subscriber record and/or associated data points (e.g. the total crédit limit value) to reflect the value advanced in respect of the network usage offer, in this scénario being the value of the network usage product provisioned in advance of received payment. Provisioning the network usage product may include instructing the intelligent network (114) to provision the network usage product to an account associated with the subscriber identifier in the charging system. The intelligent network (114) may for example adjust (232), e.g. using a provisioning and recovery node, balances of one or more accounts associated with the subscriber identifier in the charging System so as to provision the network usage product.
In the illustrated embodiment, the service provider platform (102) records (234A, 234B) a value associated with the accepted network usage offer as outstanding against one or both of the mobile wallet (112C) and the account associated with the subscriber identifier in the IN. Recording the value may record the value as an amount due to be repaid by the subscriber. The value associated with the network usage product may include a fee portion and a principal portion corresponding to the value loaned to the subscriber. In the illustrated scénario, for example, the value associated with the accepted network usage product includes a fee of USD1 and the value of the network usage product provisioned in advance of received payment, being USD10.
Recording the value as outstanding may include recording a lien configured for automatic recovery of the or part of the value, wherein automatic recovery is in response to a top-up event being detected at the mobile wallet or the account. For example, the service provider platform (102) may instruct the intelligent network (114) to adjust one or more account balances in order to record the value as outstanding, for example by recording a principal amount against a loan tracking account associated with the subscriber identifier in charging system and recording a fee amount against a fee tracking account associated with the subscriber identifier in the charging system. In other embodiments, the intelligent network may record the outstanding value in other ways, for example using a négative balance feature or the like. The service provider platform may for example instruct a lien component (112D) of the mobile wallet platform to record a lien against the mobile wallet (112C) associated with the subscriber identifier such that any inflow of funds into the mobile wallet can be redirected towards recovery of the outstanding value. The service provider platform (102) may wait a predefined time period before recording the value as outstanding. The time period may be configurable on a per-subscriber basis and may vary from hours to days or even weeks.
In the scénario described above with reference to Figures 2 and 3, a subscriber is able to request a network usage product in advance of received payment via a subscriber channel Of a mobile wallet platform. The subscriber can follow these steps for borrowing a product from the mobile wallet service menu: Select the Product, Borrow Product offers will be presented based on subscriber’s eligibility and crédit data; Accept Loan Terms, A summary of application (Fees, Repayment term / duration) and other T&C’s are shown; Submit Request, Borrow Product request submitted for processing. Once the subscriber accepts the offer and the terms, via the mobile wallet platform, the service provider platform will receive the product loan request and then it will provision the product and registerthe loan. Once the product is provisioned, a lien may be activated on one or both of the mobile wallet and an account associated with the subscriber in the IN. This can be done immediately or after a maturity period of a few days.
Another example method for network usage product provisioning via a mobile wallet platform is illustrated in the swim-lane flow diagram of Figure 4, which is described with reference to an example scénario in which a transaction failure associated with an attempt to purchase a network usage product against the mobile wallet is detected. Figure 5 illustrâtes a corresponding example user expérience. The scénario illustrated with reference to Figures 4 and 5 differs primarily in the loan product that is offered to the subscriber (e.g. purchase completion versus advance product). The flow of data and/or messages between devices and operations performed by the respective devices remains substantially the same as the scénario described above with reference to Figures 2 and 3. The same reference numerals are used for corresponding operations in Figures 2 and 4 to reflect this similarity, although the exact operations or content of the messages may differ slightly in the different scénarios.
The subscriber may use his or her communication device (106) to access (200) the mobile wallet platform (112) via the subscriber channel. In this example scénario, the subscriber accesses (201) a ‘Purchase Network Usage Product’ option via the subscriber channel and selects (205) the network usage product that he/she wants to purchase. In response to the subscriber selecting the network usage product for purchase, the communication device transmits (206) a request to purchase a network usage product to the mobile money platform (112) via the subscriber channel.
The mobile money platform (112) receives the request to purchase the network usage product associated with the subscriber identifier and checks the balance of the mobile wallet associated with the subscriber identifier. If the balance is sufficient to fund the purchase, the purchase may be allowed to continue. If not, the mobile wallet platform may detect (208) a transaction failure associated with an attempt to purchase a network usage product against the mobile wallet, the transaction failure being triggered due to an insufficient balance of the mobile wallet associated with the subscriber identifier.
The mobile wallet platform (112) may obtain (216) data éléments generated based on crédit data associated with the subscriber identifier. This may include transmitting a data element request message to a service provider platform (102). The data element request may include the subscriber identifier and particulars associated with the request (e.g., in the illustrated scénario, that a transaction failure is detected against a mobile wallet associated with the subscriber identifier).
The service provider platform (102) may receive the request and may détermine (218) the data éléments associated with the request. Determining (218) the data éléments may include checking if the subscriber associated with the subscriber identifier is eligible and/or checking a crédit profile associated with the subscriber identifier. The service provider platform (102) may for example use the subscriber identifier to query a subscriber database (122) and access and evaluate relevant data stored in a corresponding subscriber record (124). In the scénario illustrated with reference to Figures 4 and 5, determining the data éléments includes determining a crédit limit value associated with the subscriber identifier which corresponds to a maximum value which may be loaned to the subscriber associated with the subscriber identifier.
The service provider platform (102) may return (220) the data éléments to the mobile wallet platform (112). In the scénario illustrated with reference to Figures 4 and 5, the data éléments include the crédit limit value or maximum loan value associated with the subscriber identifier. The service provider platform may therefore return the maximum loan offer up to subscriber’s crédit limit based on the risk profile and/or crédit data associated with the subscriber identifier.
The mobile wallet platform (112) may détermine the différence between the value of the network usage product and the balance of the mobile wallet and compare the différence to the crédit limit value to détermine whether the différence can be advanced to the subscriber (e.g. whether a loan can be registered in favour of the subscriber in respect of the différence). If the crédit limit value and the balance of the mobile wallet together are sufficient, the mobile wallet platform (112) transmits (222) a network usage offer based on or including the data éléments to the communication device (106) via the subscriber channel. In this scénario, the network usage offer is based on the data éléments (e.g. the crédit limit value) and is an offerto advancethe différence between the value ofthe network usage product and the balance of the mobile wallet so that the subscriber can complété the purchase of the selected network usage product despite the insufficient balance of the mobile wallet.
The communication device (106) may receive and display (224) the network usage offer, which in the illustrated scénario includes an offerte advance the différence (e.g. provide a loan in respect of the différence) such that the purchase of the selected network usage product can continue. The offer may be presented to the subscriber along with the product and loan terms. Product terms may include bundle details and expiry. Loan terms may include fee, duration/term, etc. The subscriber may input his or her acceptance into the communication device, which receives (226) the input and transmits the acceptance of the network usage offer to the mobile wallet platform (112) via the subscriber channel (112A). The acceptance is associated with a network usage product, in this scénario being the product selected for purchase by the subscriber. The mobile wallet platform (112) receives (227) acceptance of the network usage offer and requests (228) provision of the relevant network usage product.
In the illustrated embodiment, requesting (228) provision ofthe networkusage product may include the mobile wallet platform (112) transmitting an instruction to the service provider platform to cause provisioning of the network usage product to an account maintained by an intelligent network and associated with the subscriber identifier. In other embodiments, requesting provision of the network usage product may include the service provider platform instructing the IN to provision the network usage product.
In the illustrated embodiment, the service provider platform (102) receives the instruction and provisions (230) the network usage product. The service provider platform may collect the balance of the mobile wallet, for example by requesting the mobile wallet platform to transfer the remaining balance of the mobile wallet associated with the subscriber identifier to an account associated with the service provider. The service provider platform may also register the loan, including for example updating the subscriber record and/or associated data points (e.g. the total crédit limit value) to reflect the value advanced in respect of the network usage offer, in this scénario being the value of the différence between the balance of the mobile wallet and the network usage product purchased by the subscriber. Provisioning the network usage product may include instructing the intelligent network (114) to provision the network usage product to an account associated with the subscriber identifier in the charging system. The intelligent network (114) may for example adjust (232) balances of one or more accounts associated with the subscriber identifier in the charging system so as to provision the network usage product.
In the illustrated embodiment, the service provider platform (102) records (234A, 234B) a value associated with the accepted network usage offer as outstanding against one or both of the mobile wallet (112C) and the account associated with the subscriber identifier. Recording the value may record the value as an amount due to be repaid by the subscriber. The value associated with the network usage product may include a fee portion and a principal portion corresponding to the value loaned to the subscriber. In the illustrated scénario, for example, the value associated with the accepted network usage product includes a fee of USD2 and the value of the différence between the balance of the mobile wallet and the value of the network usage product selected for purchase by the subscriber (e.g. USD20).
As described above with reference to Figures 2 and 3, recording the value as outstanding may include recording a lien configured for automatic recovery of the or part of the value, wherein automatic recovery is in response to a top-up event being detected at the mobile wallet or the account. The service provider platform may wait a predefined time period before recording the value as outstanding. The time period may be configurable on a persubscriber basis and may vary from hours to days or even weeks.
In the example scénario described above with reference to Figures 4 and 5, the subscriber wants to purchase a network usage (or ‘telco’) product (e.g. a Bundle or Airtime) but the mobile wallet balance is insufficient to complété the purchase. A loan will be offered during the checkout process to complété the purchase. The subscriber will access the ‘Purchase Network Usage Product’ option via any of the existing access channels offered by the mobile wallet menu and select his product of preference. On checkout, if purchase is identified to be short of balance (this is the mobile wallet balance), the mobile wallet platform checks with the service provider loan service of the maximum loan offer. The combination of mobile wallet balance and loan offer is checked for sufficiency to complété the product purchase and présent the offer to the subscriber. Once the subscriber accepts the offer and the terms, the service provider platform providing the loan service will receive the product loan request and then it will provision the product and register the loan. Once the product is provisioned, a lien needs to be activated on both the mobile wallet and an account associated with the subscriber identifier in the intelligent network. This can be done immediately or after a maturity period of, e.g., a few days.
Various components may be provided for implementing the methods described above with reference to Figures 2 to 5. Figure 6 is a block diagram which illustrâtes exemplary components which may be provided by a system for network usage product provisioning via a mobile wallet platform. The system includes a server computer (121), which may form part of a service provider platform or an MNO platform, depending on the implémentation.
The server computer (121) 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 (121). 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 components. In some cases, for example in a cloud computing implémentation, software units arranged to manage and/or process data on behalf of the server computer (121) may be provided remotely.
The server computer (121) may include a data element obtaining component (506) arranged to obtain data éléments generated based on crédit data associated with a subscriber identifier which uniquely identifies a mobile subscriber. In embodiments where the server computer (121) forms part of a service provider platform, the data element obtaining component may obtain the data éléments by determining the data éléments based on data stored in a subscriber record. In embodiments in which the server computer forms part of the MNO platform, the data éléments obtaining component may obtain the data éléments from a service provider platform.
The server computer (121) may include an offer transmitting component (508) arranged to transmit a network usage offer based on or including the data éléments to a communication device associated with the subscriber identifier. The offer may be transmitted via a subscriber channel of a mobile wallet platform in which the subscriber identifier is associated with a mobile wallet.
The server computer (121) may include an acceptance receiving component (510) arranged to receive an acceptance of the network usage offer from the communication device via the subscriber channel. The acceptance may be associated with a network usage product.
The server computer (121) may include a transmitting component (512) arranged to transmit an instruction to cause provisioning of the network usage product to an account maintained by an intelligent network and associated with the subscriber identifier.
The Systems and methods described herein enable network usage product provisioning via a mobile wallet platform. The Systems and methods described herein may reduce the steps required to purchase network usage products via a subscriber channel of a mobile wallet platform, which may in turn lead to improved efficiency of MNO resources in that, for example, fewer messages or instructions need to be relayed between the subscriber and the relevant platforms. Recovery options and/or efficiency may also be improved as the loan value can be recovered from the mobile wallet or an account in the IN.
Instead of offering a generic cash loan to cover purchases of airtime, bundles and, in general, télécommunication services from mobile wallet, the Systems and methods described herein provide a telco loan service for mobile wallets. This is a spécial purpose loan service that only covers télécommunication product purchases. It is a new type of loan that empowers the subscribers of the mobile money wallet to purchase telco, or network usage, products (like airtime, bundles, etc.) when his/her wallet does not hâve enough balance. The main characteristics of the telco loan are:
very short term in duration;
very simple fee structure; and, the ability to be repaid from both the mobile wallet and the main telco account.
The “Telco Loan Service” described herein allows mobile money or mobile wallet service providers to offer the optimal solution to their customers for buying Télécommunication services including airtime, data and bundles on crédit. The service provides:
• short duration loans • which can be used only for the purchase of télécommunication (or ‘network usage’) products, and • which can be repaid from the mobile money wallet and/or the Telco’s Airtime account.
The service can be delivered via: a new menu option in the existing mobile wallet menu; or, a payment option during purchase of a telco product. These options can be captured in the following use cases: borrowing a Telco product on request; or, completion of purchase of a telco product (loan on checkout).
Use cases Description Notes
Borrow on request A mobile wallet subscriber accesses the new “Borrow Telco Product” menu to purchase a Telco product on crédit. This new menu will offer spécifie Telco products to be purchased only on crédit.
Completion of purchase (loan on checkout) A mobile wallet subscriber will access the existing “Purchase Telco Product” option of the mobile wallet menu and select a product to purchase. If the wallet balance is insufficient, the subscriber will hâve the option to complété the purchase with a loan. This use case allows the purchase of a telco product, using both mobile wallet balance and eligible loan crédit to purchase the product.
The value of the loan may include:
• the principal amount which typically matches the value of the telco service to be purchased. It is a dynamic value to cover any price of telco service; and, • the fee which is the charge for the crédit facility. It can be either a percentage of the principal amount (with or without cap) or, fixed per loan (regardless of the principal amount or in buckets of principal amount).
The amount due is the sum of the principal amount and the fee. The lifecycle of the Telco Loan product is divided in the two (2) main phases: maturity phase; and, collection phase. The Loan date is the date that loan was provisioned, and it is considered as the O-day (day zéro) of the loan. Due date is the last date of the maturity phase and marks the date when the subscriber should fully repay the loan. The proposed service accepts partial payments.
Phases Period Descriptions
Maturity It can be any period of time, even 0 seconds, which essentially means that loan is due immediately. It is the loan phase in which the full loan repayment is not expected, and the end of the phase marks the date where the full repayment of the loan is expected.
Collection Until repayment. It is the loan phase that follows the maturity phase and it lasts until the loan is fully repaid. During the collection phase the customer will be regularly notified of the outstanding amount.
The Telco Loan can be repaid from either of the following channels: the subscriber’s Mobile 10 wallet; the subscribers Telco Airtime account (e.g. maintained by the IN). To collateralize the loan, on the due date a lien will be applied to both accounts. When a repayment is received, the liens on both mobile wallet and airtime accounts we will be either updated, if it is a partial repayment or removed, if it is a full repayment. The bellow table shows example balance adjustments of the Mobile wallet and Telco’s Main Account, when a 15 subscriber gets a Telco Product as a loan and when the loan is repaid.
Mobile wallet Platform Intelligent network Service provider platform
Wallet Lien Main Account (MA) Lien Outstanding
Initial State 0 0 0 0 0
Subscriber requests for Airtime loan of $10 with $1 fee 0 11 10 11 11
Subscriber recharges his MA with $5 (partial repayment) 0 11-5 = 6 10 11-5 = 6 11-5 = 6
Making call (use of airtime) 0 6 10-3 = 7 6 6
Subscriber adds $50 to mobile wallet (full repayment) 0 + 50 — 6 =44 6-6 =0 7 6-6=0 6-6 =0
Subscribers with outstanding loans in collection phase may receive regular reminders of their loan until the loan is fully repaid.
Figure 7 illustrâtes an example of a computing device (700) in which various aspects of the 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), a client computer, or a communication device, such as a mobile phone (e.g. cellular téléphoné), satellite phone, tablet computer, personal digital assistant or the like. Different embodiments of the computing device may dictate 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 may use any suitable numberof subsystems or components ofthe 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 units (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, externat 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 electronic, electromagnetic, 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-readable 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 computerreadable medium having stored computer-readable program code exécutable by the central processor (710). A computer program product may be provided by a non-transient or non-transitory computer-readable 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. Peripherals (such as printers, scanners, caméras, or the like) and input/output (I/O) devices (such as a mouse, touchpad, keyboard, microphone, touch-sensitive display, 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, alone 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-readable 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 medium, such as a random access memory (RAM), a read-only 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 block 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 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 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 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 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 ‘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 (10)

  1. CLAIMS:
    1. A computer-implemented method comprising:
    obtaining data eiements generated based on crédit data associated with a subscriber identifier which uniquely identifies a mobile subscriber;
    transmitting a network usage offer based on or including the data éléments to a communication device associated with the subscriber identifier via a subscriber channel of a mobile wallet platform in which the subscriber identifier is associated with a mobile wallet;
    receiving an acceptance ofthe network usage offer from the communication device via the subscriber channel, the acceptance being associated with a network usage product; and, transmitting an instruction to cause provisioning of the network usage product to an account maintained by an intelligent network and associated with the subscriber identifier.
  2. 2. The method as claimed in claim 1, including receiving a request for a network usage product in advance of received payment from the communication device via the subscriber channel of the mobile wallet platform, wherein the data éléments include one or more network usage products available in advance of received payment for acceptance by the mobile subscriber.
  3. 3. The method as claimed in claim 2, wherein transmitting the network usage offer includes transmitting the one or more network usage products available in advance of received payment, and wherein receiving an acceptance of the network usage advance offer includes receiving a selected network usage advance product.
  4. 4. The method as claimed in any one of claim 1 to 3, including detecting a transaction failure associated with an attempt to purchase a network usage product against the mobile wallet, wherein the transaction failure is triggered due to an insufficient balance of the mobile wallet.
  5. 5. The method as claimed in claim 4, wherein the data éléments include a crédit limit value, and if the crédit limit value and the balance of the mobile wallet together are sufficient, transmitting the network usage offer includes transmitting an offer to advance the différence between the value of the network usage product and the balance of the mobile wallet.
  6. 6. The method as claimed in any one of the preceding claims, including recording a value associated with the accepted network usage offer as outstanding against one or both of the mobile wallet and the account, wherein the value is either a value of the network usage product provisioned in advance of received payment or a différence between the 5 value of the network usage product and a balance of the mobile wallet.
  7. 7. The method as claimed in claim 6, including recording a lien configured for automatic recovery of at least part of the value.
    10
  8. 8. The method as claimed in claim 7, wherein automatic recovery is in response to a top-up event being detected at the mobile wallet or the account.
  9. 9. A computer-implemented method conducted at a mobile wallet platform in which a subscriber identifier which uniquely identifies a mobile subscriber is associated with a 15 mobile wallet, the method comprising:
    obtaining data éléments generated based on crédit data associated with the subscriber identifier;
    identifying a network usage product associated with the data éléments; and, transmitting an instruction to cause provisioning of the network usage product to an 20 account maintained by an intelligent network and associated with the subscriber identifier.
  10. 10. A system including a memory for storing computer-readable program code and a processor for executing the computer-readable program code, the system comprising:
    a data element obtaining component for obtaining data éléments generated based 25 on crédit data associated with a subscriber identifier which uniquely identifies a mobile subscriber;
    an offer transmitting component for transmitting a network usage offer based on or including the data éléments to a communication device associated with the subscriber identifier via a subscriber channel of a mobile wallet platform in which the subscriber 30 identifier is associated with a mobile wallet;
    an acceptance receiving component for receiving an acceptance of the network usage offer from the communication device via the subscriber channel, the acceptance being associated with a network usage product; and, a transmitting component for transmitting an instruction to cause provisioning of the 35 network usage product to an account maintained by an intelligent network and associated with the subscriber identifier.
OA1202000271 2020-07-07 2020-07-30 Network usage product provisioning via a mobile wallet platform OA19720A (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
ZA2020/04132 2020-07-07

Publications (1)

Publication Number Publication Date
OA19720A true OA19720A (en) 2021-02-26

Family

ID=

Similar Documents

Publication Publication Date Title
US11568375B2 (en) Decentralized systems and methods for transferring information between subsystems of communication networks
US20180197167A1 (en) System and method for person-to-person payments
US9911103B2 (en) Payment gateway for processing payment requests associated with a wireless users account
RU2706180C2 (en) Processing of financial transactions
US8799092B2 (en) Methods, apparatus, and systems for supporting purchases of goods and services via prepaid telecommunication accounts
US20140089188A1 (en) System for funds transfer using source atm and delivering atm
US20140201070A1 (en) Monetary transaction system
US20120173396A1 (en) Bill division and group payment systems and methods
US20090106152A1 (en) Money transfers utilizing unique receiver identifier
US20140095383A1 (en) System for anonymous funds transfer using adhoc staging accounts
US20140279388A1 (en) Method, apparatus, and computer-readable medium for advancing prepaid credit
US20080270279A1 (en) Method and system for automated skip tracing
KR20110089295A (en) Money transfer using cellular networks
WO2019229655A1 (en) Credit limit-based provisioning of network usage advances
US9003079B2 (en) API methods for phone-on-file opt-in at a merchant server
OA19720A (en) Network usage product provisioning via a mobile wallet platform
WO2022038455A1 (en) System and method for network usage product provisioning
WO2022008967A1 (en) Network usage product provisioning via a mobile wallet platform
WO2019229650A1 (en) Systems and methods for mobile subscriber provisioning and recovery
US9558480B2 (en) Phone-on-file opt-in at a merchant server
US10310712B2 (en) Multicomputer processing of client device request data with centralized event orchestration
OA21014A (en) Integrated cross-platform account management.
WO2022200881A1 (en) Integrated cross-platform account management
OA19727A (en) Type classification-based provisioning of network usage advances in a mobile network
OA20072A (en) Electronic voucher distribution account management.