WO2022200881A1 - Gestion intégrée de comptes multiplateformes - Google Patents

Gestion intégrée de comptes multiplateformes Download PDF

Info

Publication number
WO2022200881A1
WO2022200881A1 PCT/IB2022/051868 IB2022051868W WO2022200881A1 WO 2022200881 A1 WO2022200881 A1 WO 2022200881A1 IB 2022051868 W IB2022051868 W IB 2022051868W WO 2022200881 A1 WO2022200881 A1 WO 2022200881A1
Authority
WO
WIPO (PCT)
Prior art keywords
repayment
source
account
amount
subscriber
Prior art date
Application number
PCT/IB2022/051868
Other languages
English (en)
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
Priority to MX2023007900A priority Critical patent/MX2023007900A/es
Publication of WO2022200881A1 publication Critical patent/WO2022200881A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02—Banking, e.g. interest calculation or account maintenance
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/03—Credit; Loans; Processing thereof

Definitions

  • This invention relates to a system and method for integrated cross-platform account management.
  • the invention relates to a system and method for integrated cross-platform account management for mobile wallet cash loan repayment.
  • MNO mobile network operator
  • mobile wallet also termed “mobile money”
  • mobile wallets for managing mobile wallets on behalf of subscribers and via which individual subscribers can store, transfer, borrow and withdraw money, pay beneficiaries and access other financial services.
  • mobile wallets have gained popularity, especially across emerging economies, for accessing digital credit or cash loans.
  • These loans may be so-called “microloans”, which are very small loans made to impoverished borrowers who typically lack collateral, steady employment, or a verifiable credit history.
  • Loans accessed via a mobile wallet platform typically exhibit characteristics such as a maturity period, setup fee, interest, instalment and repayment methods.
  • a computer-implemented method comprising: generating one or more repayment instructions, wherein the or each repayment instruction instructs repayment of at least part of an outstanding amount associated with a cash loan, the or each repayment instruction including a source amount and a repayment source indicator indicating either a subscriber wallet account maintained by a mobile wallet platform or a subscriber network usage account maintained by an intelligent network (IN) of a mobile network operator (MNO) as a source account for repayment; and, initiating a transfer of funds from the one or more source accounts to a recovery account for an amount being a sum of the one or more source amounts to effect repayment of at least part of the outstanding amount, including: if the one or more source accounts include the subscriber wallet account, initiating a transfer of funds from the subscriber wallet account to the recovery account, including interacting with the mobile wallet platform via a mobile wallet platform interface to adjust values of respective accounts maintained therein; and, if the one or more source accounts include the subscriber network usage account, initiating a transfer of funds from
  • the method may include receiving a request message requesting repayment of at least part of the outstanding amount.
  • the request message may include one or more repayment source indicators and either or both the one or more source amounts and a repayment amount. Generating the one or more repayment instructions may be in response to receiving the request message.
  • the request message may be received from a communication device of a subscriber associated with the cash loan via a subscriber channel of the mobile wallet platform.
  • the subscriber channel may provide access to the mobile wallet platform via SMS, IVR, USSD, software application or web channels.
  • the method may include monitoring for occurrence of a predefined condition.
  • the predefined condition may include one or more of: loan repayment due date passed; and, inflow of funds detected at one of the one or more source accounts.
  • the method may include detecting occurrence of a predefined condition. Detecting occurrence of the predefined condition may trigger generating the one or more repayment instructions.
  • the number of repayment instructions generated and the source amount of the or each repayment instruction may be determined based on an available balance of one or both of the subscriber wallet account and the subscriber network usage account such that a sum of the one or more source amounts is less than or equal to the outstanding amount associated with the cash loan.
  • the method may include determining one or more of: an available balance of the one or more source accounts; the number of repayment instructions to be generated; the source amount of the or each repayment instruction; the source account to be indicated by the repayment source indicator of the or each payment instruction; and, a repayment amount.
  • the method may further include determining, based on an available balance of one or more source accounts, one or more of: the number of repayment instructions to be generated; the source amount of the or each repayment instruction; the source account to be indicated by the repayment source indicator of the or each payment instruction; and, a repayment amount.
  • Determining based on the available balance of one or more source accounts may include determining an inequality or equality of the available balance of one or more source accounts relative to the repayment amount or the outstanding amount.
  • the repayment amount may be determined such that the repayment amount is less than or equal to the outstanding amount.
  • the source amount of the or each repayment instruction may be less than the available balance of the source account with which it is associated.
  • the method may include: determining whether a balance of a first source account is greater than or equal to the repayment amount; and, if the balance of the first source account of the one or more source accounts is greater than or equal to the repayment amount, generating a repayment instruction including a repayment source indicator indicating the first source account and including a source amount being equal to the repayment amount.
  • the method may include, if the balance of the first source account is less than the repayment amount, determining whether a balance of a second source account is greater than or equal to the repayment amount; and, if the balance of the second source account is greater than or equal to the repayment amount, generating a repayment instruction including a repayment source indicator indicating the second source account and a source amount being equal to the repayment amount.
  • the method may further include if the balance of the second source account is less than the repayment amount: determining a second source amount which is less than the balance of the second source account; generating a repayment instruction including a repayment source indicator indicating the second source account and including the second source amount.
  • the method may include: determining whether a difference between the repayment amount and the second source amount is less than the balance of the first source account; generating a repayment instruction including a repayment source indicator indicating the first source account and including a first source amount equal to the difference.
  • a system including a server computer comprising: a generating component for generating one or more repayment instructions, wherein the or each repayment instruction instructs repayment of at least part of an outstanding amount associated with a cash loan, the or each repayment instruction including a source amount and a repayment source indicator indicating either a subscriber wallet account maintained by a mobile wallet platform or a subscriber network usage account maintained by an intelligent network (IN) of a mobile network operator (MNO) as a source account for repayment; an initiating component for initiating a transfer of funds from the one or more source accounts to a recovery account for an amount being a sum of the one or more source amounts to effect repayment of at least part of the outstanding amount, wherein the initiating component is configured: to initiate, if the one or more source accounts include the subscriber wallet account, a transfer of funds from the subscriber wallet account to the recovery account, and, to initiate, if the one or more source accounts include the subscriber network usage account, a transfer of funds from the subscriber network usage
  • the system may include a mobile wallet platform configured to manage the wallet account on behalf of a subscriber and to provide functionality by way of which the subscriber can transact against the mobile wallet, including by storing, transferring and withdrawing money and paying beneficiaries.
  • the system may include a subscriber channel configured to provide access to the mobile wallet platform by a communication device via SMS, IVR, USSD, software application or web channels, wherein the mobile wallet platform is configured to transmit and receive data to and from the communication device via the subscriber channel and a mobile network.
  • the system may include an intelligent network (IN) and a charging system implemented as a node within the IN.
  • the charging system may be implemented as or have access to a high- throughput database that maintains multiple network usage accounts for each subscriber.
  • the server computer may include a message receiving component configured to receive a request message requesting repayment of at least part of the outstanding amount.
  • the request message may include one or more repayment source indicators and either or both the source amount and the repayment amount.
  • the server computer may be configured to generate the one or more repayment instructions in response to receiving the request message.
  • the server computer may include a monitoring component configured to monitor for occurrence of a predefined condition.
  • the predefined condition may include one or more of: loan repayment due date passed; and, inflow of funds detected at one or more source accounts.
  • the server computer may include a detecting component configured to detect occurrence of a predefined condition.
  • the server computer may be further configured to generate one or more repayment instructions in response to detecting occurrence of the predefined condition.
  • the server computer may include a determining component configured to determine one or more of: an available balance of the one or more source accounts; the number of repayment instructions to be generated; the source amount of the or each repayment instruction; the source account to be indicated by the repayment source indicator of the or each payment instruction; and, the repayment amount.
  • the determining component may be configured to determine, based on the available balance of one or more source accounts, one or more of: the number of repayment instructions to be generated; the source amount of the or each repayment instruction; the source account to be indicated by the repayment source indicator of the or each payment instruction; and, the repayment amount.
  • the determining component may be configured to determine an inequality or equality of the available balance of one or more source accounts relative to the repayment amount or the outstanding amount.
  • the determining component may be configured to determine the repayment amount such that the repayment amount is less than or equal to the outstanding amount, and, wherein the source amount of the or each repayment instruction is less than the available balance of the source account with which it is associated.
  • the server computer may be configured: to determine whether a balance of a first source account is greater than or equal to the repayment amount or the outstanding amount; and, if the balance of the first source account of the one or more source accounts is greater than or equal to the repayment amount or the outstanding amount, to generate a repayment instruction including a repayment source indicator indicating the first source account and including a source amount being equal to the repayment amount.
  • the server computer may be configured, if the balance of the first source account is less than the repayment amount or the outstanding amount, to determine whether a balance of a second source account is greater than or equal to the repayment amount or the outstanding amount; and, if the balance of the second source account is greater than or equal to the repayment amount or the outstanding amount, to generate a repayment instruction including a repayment source indicator indicating the second source account and a source amount being equal to the repayment amount.
  • the server computer may be configured: if the balance of the second source account is less than the repayment amount or the outstanding amount: to determine a second source amount which is less than the balance of the second source account; and, to generate a repayment instruction including a repayment source indicator indicating the second source account and including the second source amount.
  • the server computer may be configured: to determine whether a difference between the repayment amount or the outstanding amount and the second source amount is an amount less than the balance of the first source account; and, to generate a repayment instruction including a repayment source indicator indicating the first source account and including a first source amount equal to the difference.
  • a computer program product comprising a computer-readable medium having stored computer-readable program code for performing the steps of: generating one or more repayment instructions, wherein the or each repayment instruction instructs repayment of at least part of an outstanding amount associated with a cash loan, the or each repayment instruction including a source amount and a repayment source indicator indicating either a subscriber wallet account maintained by a mobile wallet platform or a subscriber network usage account maintained by an intelligent network (IN) of a mobile network operator (MNO) as a source account for repayment; and, initiating a transfer of funds from the one or more source accounts to a recovery account for an amount being a sum of the one or more source amounts to effect repayment of at least part of the outstanding amount, including: if the one or more source accounts include the subscriber wallet account, initiating a transfer of funds from the subscriber wallet account to the recovery account, including interacting with the mobile wallet platform via a mobile wallet platform interface to adjust values of respective accounts maintained therein; and, if the one or more source
  • computer-readable medium to be a non-transitory computer- readable medium and for the computer-readable program code to be executable by a processing circuit.
  • a system comprising: a server computer configured to interface with a mobile wallet platform and an intelligent network (IN) of a mobile network operator (MNO), the server computer being configured to: receive a request message requesting repayment of at least part of a cash loan, wherein the request message includes a repayment amount and a repayment source indicator indicating a repayment source being one of a subscriber wallet account maintained by the mobile wallet platform or a subscriber network usage account maintained by the IN of the MNO; and, initiate a transfer of funds from the repayment source to a recovery account for the repayment amount to effect repayment of at least part of the cash loan.
  • a server computer configured to interface with a mobile wallet platform and an intelligent network (IN) of a mobile network operator (MNO)
  • the server computer being configured to: receive a request message requesting repayment of at least part of a cash loan, wherein the request message includes a repayment amount and a repayment source indicator indicating a repayment source being one of a subscriber wallet account maintained by the mobile wallet platform or a subscriber network usage account maintained by
  • Figure 1 is a schematic diagram which illustrates a loan lifecycle according to aspects of the present disclosure
  • Figure 2 is a schematic diagram which illustrates an example system for integrated cross-platform account management according to aspects of the present disclosure
  • FIGS. 3A to 3C are flow diagrams which illustrate example methods for integrated cross-platform account management according to aspects of the present disclosure
  • Figure 3D is a swim-lane flow diagram which illustrates an example method for initiating a transfer of funds from a repayment source to a recovery account in an integrated cross-platform account management system according to aspects of the present disclosure
  • Figure 4 is a schematic diagram which illustrates a user interface flow according to aspects of the present disclosure
  • Figure 5 is a swim-lane flow diagram which illustrates example operations of a method for cash loan provisioning in an integrated cross-platform account management system according to aspects of the present disclosure
  • Figure 6 is a swim-lane flow diagram which illustrates example operations of a method for loan repayment initiated by a subscriber in an integrated cross-platform account management system according to aspects of the present disclosure
  • Figure 7 is a swim-lane flow diagram which illustrates example operations of a method for time triggered payment process in an integrated cross platform account management system according to aspects of the present disclosure
  • Figure 8 is a swim-lane flow diagram which illustrates example operations of a method for lien triggered loan repayment in an integrated cross platform account management system according to aspects of the present disclosure
  • Figure 9 is a block diagram which illustrates exemplary components which may be provided by a system for integrated cross-platform account management according to aspects of the present disclosure.
  • Figure 10 illustrates an example of a computing device in which various aspects of the disclosure may be implemented.
  • aspects of the present disclosure provide a system and method for integrated cross-platform account management.
  • the integrated cross-platform account management system and method may be provided for cash loan repayment.
  • aspects of the present disclosure provide for generating one or more repayment instructions.
  • Each repayment instruction instructs repayment of at least part of an outstanding amount.
  • the outstanding amount is the total amount owed by a subscriber for receiving a cash loan.
  • Each repayment instruction may include a repayment source indicator and a source amount.
  • the repayment source indicator indicates a source account from which funds will be transferred for repayment of the or part of the outstanding amount.
  • the source account for repayment may be a subscriber wallet account maintained by a mobile wallet platform or a subscriber network usage account maintained by an intelligent network (IN) of a mobile network operator (MNO).
  • the source amount is the amount to be withdrawn from the source account.
  • the repayment may be for a repayment amount, which may be set by a subscriber or a repayment plan, or which may be determined based on a sum of the one or more source amounts.
  • Generating repayment instructions may be in response to receiving a request message or in response to detecting a predefined condition.
  • the request message may include an indication of one or more of: an available balance of the one or more source accounts; the number of repayment instructions to be generated; the source amount of the or each repayment instruction; the source account to be indicated by the repayment source indicator of the or each payment instruction; and, the repayment amount.
  • the aforementioned parameters may need to be determined. Determining may for example include analysing the available balances of one or more source accounts and determining the aforementioned based on the available balances.
  • Repayment instructions may cause funds to be transferred from the one or more source accounts to a recovery account for the repayment amount to effect repayment of at least part of the outstanding amount.
  • initiating a transfer of funds from the subscriber wallet account to the recovery account may include interacting with the mobile wallet platform via a mobile wallet platform interface to adjust values of respective accounts maintained therein. If the one or more source accounts include the subscriber network usage account, initiating a transfer of funds from the subscriber network usage account to the recovery account, may include interacting with the IN via an IN interface to adjust values of respective accounts maintained therein.
  • aspects of the present disclosure therefore may provide the infrastructure for integrated cross platform account management for using mobile airtime for the repayment of an outstanding mobile wallet cash loan amount. This may offer more flexibility to the loan recipients and may enable them to avoid additional fees/penalties by paying the outstanding amount on time.
  • a subscriber will access the cash loan service from the mobile money service menu accessible to the subscriber via his or her communication device. The subscriber can apply for a cash loan digitally via the cash loan service. Upon the approval of the cash loan application, the cash equivalent of the approved loan amount will be disbursed into the mobile wallet of the subscriber (or otherwise paid out to the subscriber). The subscriber will be informed about the available repayment methods, which may, according to aspects of the present disclosure, include a “Repayment via Airtime” option. As illustrated in Figure 1 , the lifecycle of a cash loan product is typically divided into two main phases: maturity phase (3); and collection phase (5)
  • loan date (7) The date on which the loan was taken is referred to as a loan date (7), and it is considered as the 0-day (day zero) of the loan.
  • the last date of the maturity phase is termed the loan repayment due date (9) and marks the date when the subscriber should fully repay the loan.
  • the proposed service may accept partial payments.
  • Figure 1 is further described by Table 1 below:
  • the system (100) may include a service provider platform (102), a mobile wallet platform (112) and a mobile network operator (MNO) platform (104).
  • a service provider platform 102
  • a mobile wallet platform (112)
  • MNO mobile network operator
  • 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 implementations, the functionality 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) to make and receive calls, send and receive SMS messages, transmit and receive data packets (e.g. for Internet browsing, etc.) and the like.
  • the MNO platform (104) and mobile network (110) may collectively provide the infrastructure by which communication devices (106) can communicate with each other and the broader public switched telephone network (PSTN) and the Internet.
  • the mobile network (110) 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 prepaid gateway (113), an intelligent network (IN) (114) and a charging system (116).
  • the MNO platform (104) may include or maintain the mobile wallet platform (112).
  • the mobile wallet platform (112) may be independent of the MNO platform (104).
  • the mobile wallet platform (112) may be configured to manage mobile wallets (112C) on behalf of subscribers and provide functionality by 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 such as requesting and repaying cash loans.
  • 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 (112) via SMS, IVR, USSD, software application or web channels.
  • the mobile wallet platform (112) may transmit and receive data, instructions 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 (106) via the subscriber channel (112A).
  • the mobile wallet platform (112) may have access to and/or maintain a wallet database (112B) in which individual mobile wallets (112C) (which may also be termed “wallet accounts”) 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. In some implementations, each mobile wallet (112C) includes or is associated with a loan account against which cash loans and their associated outstanding balance information may be recorded.
  • the mobile wallet platform (112) may include a lien component (112D) configured to record and monitor liens against individual wallet accounts associated with subscriber identifiers.
  • the lien component (112D) may be configured to redirect an 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 outstanding amount may for example be stored in a loan account maintained by the mobile wallet platform
  • the prepaid gateway (113) may be configured, amongst other things, to detect requested usage of the 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 (116), to permit and monitor usage of the mobile network in accordance with the permitted usage information and/or to report actual usage information to the charging system (116).
  • the IN (114), which may also be termed a “Telco IN,” may be implemented according to any suitable network architecture (e.g. that specified in the ITU-T Q.1200 series 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.
  • SS7 Signalling System #7
  • 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 automatically.
  • the charging system may be an online charging system (OCS).
  • OCS online charging system
  • the charging system (116) may be configured to authenticate and authorize network usage requests associated with subscriber identifiers received from the prepaid gateway
  • the charging system (116) may be implemented as or have access to a high-throughput database that maintains multiple network usage accounts for each subscriber.
  • the purpose, type and usage of the network usage accounts may be defined by the MNO, in some cases upon request by the service provider.
  • the network usage accounts may include one or more of: a main account, a dedicated account, a loan tracking account (also referred to as a principal tracking account), a fee tracking account and a lien. These accounts may be airtime accounts in that their value is denominated in airtime (which is typically equivalent to a value of currency, such as ZAR, USD, NGN, etc.).
  • the network usage accounts may further include one or more data bundle, SMS bundle and voice minute bundle accounts which accounts may for example have 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 of the 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 reception 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 implementations, 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 zero. The same may apply, mutatis mutandis, for the SMS and voice minute bundle accounts.
  • the network usage 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 network usage accounts associated with a particular subscriber.
  • 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 network usage account identifiers which identify and correspond to different types of network usage accounts, such as each of the respective network usage accounts described in the foregoing.
  • RDBMS relational database management system
  • 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 network usage 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 or the recovery of loans.
  • the provisioning and recovery node (120) may be configured to query a lien associated with the subscriber identifier upon a subscriber top-up event or other inflow of funds and to divert some or all of the amount associated with the top-up or inflow to a recovery account in order to effect partial or complete recovery of the outstanding amount represented by the lien.
  • the system (100) may include one or more front-end APIs (126) by which the service provider platform (102) may interface with mobile wallet platform (112) and/or components or nodes of the MNO platform (104) such as 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 server computer (121) may be configured to interface and/or integrate with the MNO platform (104); for example the server computer (121) may be configured to interface and/or integrate with the intelligent network (114) and/or the charging system (116) via an appropriate front-end API (126), an appropriate IN integration component or the like.
  • the server computer (121) may be configured to interface with the mobile wallet platform (112).
  • the server computer (121) may be able to transact against mobile wallets (112C) maintained by the mobile wallet platform (112) and adjust account balances of network usage accounts stored in the charging system (116).
  • the server computer (121 ) may utilise IN integration for: receiving MNO (or ‘telco’) related subscriber data; setting/updating/removing liens against accounts maintained by the IN (or ‘telco accounts’); and, receiving loan payments.
  • the server computer (121) may utilise mobile wallet platform integration for: receiving mobile wallet related subscriber data; crediting loan amounts (disbursed into subscriber wallet); setting/updating/removing a lien against a mobile wallet; and, receiving loan payments.
  • the server computer (121) may have 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.
  • each subscriber record (124) includes one or more sets of credit data, such as a credit score, an outstanding network usage advance status, a network usage advance eligibility, a total credit limit and the like.
  • the credit score may be an indication of credit worthiness, or an indication of the risk associated with the subscriber.
  • a high credit score may indicate low risk while a low credit score may indicate a high- risk subscriber.
  • the total credit limit may be a total credit limit value denominated in a value of airtime.
  • the credit 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.
  • Each subscriber record (124) may also include information relating to outstanding loans (e.g. outstanding cash loans), such as due dates, amounts outstanding, information relating to liens and the like.
  • the server computer (121) may be configured to perform credit scoring and risk management operations using data received from the MNO platform and/or other sources and to maintain and update credit data and/or risk data stored in subscriber records accordingly.
  • the server computer (121 ) 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) described above may implement a method for loan provisioning and repayment.
  • An exemplary method for loan repayment is illustrated in the flow diagrams of Figures 3A to 3C.
  • the method may be conducted by one or more computing devices, such as one or more server computers forming part of a service provider platform, MNO platform, mobile wallet platform or the like.
  • the method may include monitoring (201) for occurrence of one or more predefined conditions, such as a loan repayment due date (9), associated with a cash loan.
  • the loan repayment due date may only be monitored while the loan is outstanding.
  • the method may include receiving (202) a request message requesting repayment of at least part of a cash loan recorded against a loan account.
  • the request message may be associated with a subscriber identifier associated with a subscriber.
  • the request message may include the subscriber identifier, or the request message may be received from a communication device associated with the subscriber identifier.
  • the request message may be received from a communication device of a subscriber associated with a cash loan via a subscriber channel of the mobile wallet platform.
  • the communication device, and hence the subscriber may be identifiable via the communication channel via which the request message is received.
  • the loan account may be maintained by the mobile wallet platform (112) and may for example be a sub-account of the subscriber’s mobile wallet (112C).
  • the subscriber channel may provide access to the mobile wallet platform via SMS, IVR, USSD, software application or web channels.
  • the request message requests repayment of at least part of the outstanding amount.
  • the request message may include a repayment amount and a repayment source indicator.
  • the repayment amount indicates the amount to be repaid (which may be equal to or less than an outstanding amount associated with the loan).
  • the repayment source indicator indicates a repayment source, which may be one of a subscriber wallet account (i.e. the subscriber’s mobile wallet (112C)) maintained by the mobile wallet platform, or a subscriber network usage account maintained by the IN or the charging system of the MNO.
  • the subscriber network usage account may be an airtime account or a mobile bundle account associated with the subscriber identifier.
  • the subscriber network usage account may be maintained by an intelligent network (IN) forming part of a mobile telephone network.
  • the request message may be comprised of one or more separate messages which together constitute a request message.
  • the method may include generating one or more repayment instructions in response to receiving a request message. This may include determining a source amount from the repayment amount and an available balance of the source account (e.g. checking to see if the balance of the source account is greater than or equal to the repayment account such that the repayment can be funded from the source account).
  • the request message may not include the repayment amount and/or repayment source indicator.
  • the method may for example include determining one or more of: an available balance of the one or more source accounts; the number of repayment instructions to be generated; the source amount of the or each repayment instruction; the source account to be indicated by the repayment source indicator of the or each payment instruction; an available balance of the one or more source accounts, and the repayment amount. Determining may take into account or be based on the available balance of one or more source accounts. Determining based on the available balance of one or more repayment sources may include determining an inequality or equality of the available balance of one or more source accounts relative to the repayment amount or the outstanding amount. For example, the method may include determining (204) whether the balance of the source account is greater than or equal to the desired repayment amount. This may include querying the status of the subscriber wallet account or subscriber network usage account via a mobile wallet platform interface or intelligent network interface, as the case may be.
  • the method may include generating (207) a repayment instruction indicating a source amount equal to the repayment amount, and associated a repayment source indicator indicating the source account.
  • the method may include identifying from the repayment instruction the repayment source indicator and determining the source account for repayment (208).
  • the method may include identifying the one or more repayment source indicators and determining the one or more source accounts for repayment. Identifying the repayment source indicator and determining the source account may be used for routing to the appropriate interface for initiating the transfer of funds.
  • the method may include initiating (209) a transfer of funds from the repayment source to a recovery account for the repayment amount to effect repayment of at least part of the loan according to the repayment instruction or instructions. This may include adjusting the balance of the repayment source and the recovery account to reflect the transfer of funds. This may include interacting with a first source account and/or a second source account, as the case may be, via a mobile wallet platform interface or intelligent network interface, as the case may be. Otherwise (206), the repayment may fail (207), and the subscriber may be notified accordingly.
  • the request message may be received from a mobile communication device associated with the subscriber identifier.
  • the subscriber may initiate full or partial repayment by accessing a user interface on his/her communication device.
  • the subscriber may choose between their mobile wallet account, network usage (e.g. airtime) account and other available methods for repaying the outstanding loan amount.
  • network usage e.g. airtime
  • the subscriber may select whether he/she wants to repay the full outstanding amount or any amount (partial payment).
  • the system may check availability of an equivalent airtime amount in the network usage account (or telco main account) within the IN, and accordingly process the transaction.
  • the transaction will be unsuccessful, and the subscriber may be notified accordingly.
  • An example user interface flow for subscriber-initiated repayment is illustrated in Figure 4.
  • the subscriber may input only the repayment amount and the method may dynamically determine one or more source amounts from one or more available source accounts and generate one or more repayment instructions based on the determination.
  • the repayment instruction may be auto-generated in response to the method monitoring (201) for and detecting (221) occurrence of one or more predefined conditions.
  • the predefined conditions may include one or more of: loan repayment due date passed (9); and, inflow of funds detected at first or second account for which lien has been applied after loan repayment due date (9).
  • the method may include determining (222) an outstanding value associated with the loan. This may include querying a loan account associated with the subscriber identifier maintained by the mobile wallet platform to determine the outstanding value associated with the loan.
  • the method may include determining one or more of: an available balance of the one or more source accounts; the number of repayment instructions to be generated; the source amount of the or each repayment instruction; the source account to be indicated by the repayment source indicator of the or each payment instruction; an available balance of the one or more source accounts, and the repayment amount as previously described. Determining may take into account or be based on the available balance of one or more source accounts. Determining based on the available balance of one or more repayment sources may include determining an inequality or equality of the available balance of one or more source accounts relative to the repayment amount or the outstanding amount.
  • the method may include determining (226) whether the balance of a first source account is greater than or equal to the repayment amount.
  • the repayment amount may be determined such that the repayment amount is less than or equal to the outstanding amount.
  • the method may include generating (229) a repayment instruction including a repayment source indicator indicating the first source account and including a source amount being the repayment amount.
  • the method may further include initiating (230) the transfer of funds from the first source account to a recovery account for the repayment amount.
  • the method may include determining (236) whether the balance of a second source account is greater than or equal to the repayment amount.
  • the method may include generating (239) a repayment instruction including a repayment source indicator indicating the second source account and including a source amount being the repayment amount.
  • the method may further include initiating (240) a transfer of funds from the second source account to a recovery account for a second source amount equal to the repayment amount.
  • the method may first try to obtain recovery from the subscriber wallet account and then, if that fails, from the subscriber network usage account, or vice versa.
  • the source amount of the or each repayment instruction may be less than the available balance of the source account with which it is associated.
  • the repayment may fail (242).
  • Repayment failing may be the full repayment of the repayment amount failing.
  • the method may include initiating partial repayment (243) of the repayment amount.
  • Initiating partial repayment may include generating one or more payment instructions and initiating a transfer of funds for the amount or amounts of one or both of the balance of the first account or second account if either or both have a positive value to as to effect recovery.
  • Each repayment instruction may for example include a source amount which is equal to or less than an available balance of an associated source account and a repayment source indicator indicating the source account as the repayment source.
  • the source account may be one of a subscriber wallet account maintained by the mobile wallet platform or a subscriber network usage account maintained by the IN or the charging system of the MNO.
  • Effecting recovery may therefore include initiating (244) a transfer of funds from the subscriber network usage account maintained by the IN of the MNO for a value equal to the positive balance (if any) of the subscriber network usage account; and initiating (246) a transfer of funds from the subscriber wallet account maintained by the mobile wallet platform for a value equal to the positive balance (if any) of the subscriber wallet account.
  • the available balance of each of the subscriber wallet account and the subscriber network usage account may be used for recovery of the outstanding value of the loan.
  • the method may include determining an updated second source amount which is less than the balance of the second source account, and, if the difference between the repayment amount and the updated second source amount is an amount less than the balance of the first source account, generating a repayment instruction including an updated first source amount equal to the difference and initiating a transfer of funds from the first source account to a recovery account for the updated first source amount. In this way partial payment from multiple accounts may be effected.
  • the method may include effecting repayment from a first source account, and if unable to do so, effecting repayment from a second source account. If repayment cannot be effected from the second source account, the method may include effecting partial repayment from either or both the first and second accounts. If repayment is to be effected from both accounts, the server computer (121) may be configured to determine the source amounts such that the repayment amount is less than or equal to the outstanding amount and each source amount is less than or equal to the available balance of the respective source accounts.
  • the first source account may be a network usage account
  • the second source account may be a wallet account, or vice versa.
  • the auto-generation of payment instructions described in the foregoing may be termed “auto-debit.”
  • a mobile wallet of the subscriber may be auto-debited for recovering the outstanding installment amount.
  • a telco main account network usage or airtime account
  • Transaction status (successful / unsuccessful) may be communicated to the subscriber.
  • Table 2 The balances within the respective accounts after an exemplary transactional scenario are shown in Table 2 below.
  • Table 2 Exemplary account balances after transactions
  • the method may include setting (250) a lien against one or both of the subscriber wallet account and the subscriber network usage account associated with the subscriber identifier.
  • the method may include detecting (252) an inflow of funds into one or both of the subscriber wallet account and the subscriber network usage account.
  • the method may include generating (254) one or more repayment instructions, each of which instructs repayment of at least part of the loan.
  • Each request message includes a repayment amount which is equal to the balance of the subscriber wallet account or the subscriber network usage account, as the case may be, and a repayment source indicator indicating either the subscriber wallet account or subscriber network usage account as the source account for the repayment.
  • the method includes method includes initiating (256) a transfer of funds from the one or more repayment sources to a recovery account for the one or more repayment amounts to effect repayment of at least part of the loan. This may include adjusting the balance of the repayment source and the recovery account to reflect the transfer of funds.
  • the liens may be removed from the first account and/or second account.
  • a lien on each account could be implemented in the following way: the Telco IN/Mobile Money platform may hold the value of the outstanding balance (the value may be set/cleared/updated by service provider platform). Based on this value, the Telco IN/Mobile Money platform may proceed with the collection whenever new airtime/cash is credited by the subscriber to the Telco IN/Mobile Money platform. Or, the Telco IN/Mobile Money platform may notify in real time the service provider platform for new airtime/cash. Based on this notification and its private ledger, the service provider platform may trigger a debit operation toward the Telco IN/Mobile Money platform to recover partially or fully the outstanding amount.
  • a lien may be applied to both accounts.
  • the lien may be updated, if it is a partial repayment or the lien may be removed, if it is a full repayment.
  • the recovery account referred to herein may be a service provider wallet account maintained by the mobile wallet platform or a service provider network usage account maintained by the IN of the MNO.
  • initiating the transfer of funds from the repayment source to the recovery account may include interacting with one or both of the mobile wallet platform and the IN to adjust values of respective accounts maintained therein.
  • Initiating the transfer of funds may include the server computer (121) determining (302) whether the repayment source is an account maintained by the IN (114) or the mobile wallet platform (112) or the like. This may include the server computer (121) parsing or otherwise evaluating the repayment source indicator included in the request message to determine if the repayment source is an account maintained by the IN, the mobile wallet platform or the like.
  • the server computer may interact (306) with the IN via the IN interface (126A) and adjust or cause adjustment of values of the subscriber network usage account (114A) and the service provider network usage account (114B) in order to effect the transfer of funds. This may include using the subscriber identifier (and/or a subscriber network usage account identifier) and a service provider identifier (and/or a service provider network usage account identifier) to adjust the values of the appropriate accounts.
  • the server computer (121) may then receive (307) a response from the IN via the IN interface (126A). If successful, the response may confirm the adjustment of the values. If unsuccessful, the response may be a notification of failure or other error message.
  • Initiating the transfer of funds from the repayment source to the recovery account may therefore include initiating a transfer of funds from the repayment source to a service provider network usage account if the repayment source is the subscriber network usage account.
  • the server computer may interact (308) with the wallet database via the mobile wallet platform interface (126B) and adjust or cause adjustment of the values of the subscriber wallet account (112C) (or subscriber mobile wallet) and the service provider wallet account (112D) in order to effect the transfer of funds. This may include using the subscriber identifier (and/or a subscriber wallet account identifier) and a service provider identifier (and/or a service provider wallet account identifier) to adjust the values of the appropriate accounts. If successful, the server computer (121) may then receive (309) a response from the mobile wallet platform via the mobile wallet platform interface (126B) confirming adjustment of the values. If unsuccessful, the response may be a notification of failure or other error message.
  • Initiating the transfer of funds from the repayment source to the recovery account may therefore include initiating a transfer of funds from the repayment source to a service provider wallet account if the repayment source is the subscriber wallet account.
  • initiating the transfer of funds from the repayment source to the recovery account may include initiating a transfer of funds from the repayment source to a service provider wallet account if the repayment source is the subscriber network usage account.
  • the transfer may include interacting with the IN to adjust values of the subscriber network usage account and an intermediate network usage account and then interacting with the mobile wallet platform to adjust values of an intermediate wallet account the service provider wallet account.
  • the intermediate accounts may be dispensed with.
  • Tables 3 and 4 show example balance adjustments of a subscriber’s mobile wallet and network usage accounts for provisioning and recovery of a cash loan according to aspects of the present disclosure.
  • Table 4 Exemplary recovery by lien-triggered loan repayment from both the subscriber's airtime and wallet accounts ; j i .
  • the method may include identifying the one or more source accounts for repayment from the repayment source indicator or indicators in order to initiate a transfer of funds from the one or more source accounts.
  • Figures 5 to 8 are swim-lane flow diagrams which illustrate the methods described above in greater detail.
  • FIG 5 illustrates an exemplary method for loan provisioning.
  • the subscriber may firstly use a communication device (106) to request a cash loan from the service provider's server computer (121), and the server computer (121) may then run eligibility checks. If the subscriber is found to be eligible, the server computer (121) may then credit the loan amount to the subscriber's wallet (112C), and the mobile wallet platform (112) may send a response to the server computer (121). If the cash loan is outstanding after the maturity date of the loan, the server computer (121) may set the outstanding amount flag or value in the wallet platform (112), and the wallet platform (112) may return a response. The server computer (121) may also set the outstanding amount flag or value in the IN (114), after which the IN (114) may send a response to the server (121).
  • Figures 6 to 8 illustrate example operations of methods for loan repayment.
  • Figure 6 illustrates an example method where repayment is initiated by the subscriber;
  • Figure 7 illustrates a time triggered payment process; and
  • Figure 8 illustrates lien triggered loan repayment.
  • the subscriber may use a communication device (106) to request full or partial payment of a loan from the service provider's server computer (121 ).
  • the server computer (121) may then debit the amount from the subscriber's mobile wallet (112C), and the wallet platform (112) may send a response to the server computer (121). If the payment is after the maturity date, the server computer (121) may update the outstanding amount flag or value in the mobile money wallet platform (112), and the wallet platform (112) may send a response to the server computer (121).
  • the server computer (121 ) may also update the outstanding amount flag or value in the IN (114), after which the IN (114) may send a response to the server computer (121).
  • the server computer (121) may firstly debit the amount from the mobile money wallet (112C), and the wallet platform (112) may send a response. If the payment is after the maturity date, the server computer (121 ) may update the outstanding amount flag or value in the mobile money wallet platform (112), and the wallet platform (112) may send a response to the server computer (121). The server computer (121 ) may also set the outstanding amount flag or value in the IN (114), after which the IN (114) may send a response to the server computer (121). The server computer (121) may then send a notification of the payment process outcome to the subscriber's communication device (106).
  • the subscriber may use a communication device (106) either to deposit cash into the mobile money wallet (112C) or to recharge the IN (114) account.
  • the wallet platform (112) may notify the service provider's server computer (121) that new money has landed in the account (112C), and the server computer (121) may debit the amount from the wallet (112C) (the lien triggered loan payment).
  • the wallet platform (112) may then send a response to the server computer (121).
  • the IN (114) may notify the server computer (121) that new money has landed in the account, and the server computer (121) may debit the amount from the IN (114) account (the lien triggered loan payment).
  • the IN (114) account may then send a response to the server computer (121).
  • the server computer (121) may update the outstanding amount flag or value in both the mobile money wallet platform (112) and the IN (114), and the wallet platform (112) and the IN (114) may send responses to the server computer (121).
  • the server (121 ) may then send a notification of the outcome of the lien triggered payment to the subscriber's communication device (106).
  • FIG. 9 is a block diagram which illustrates exemplary components which may be provided by a system for integrated cross-platform account management according to aspects of the present disclosure.
  • the system includes a server computer (121), which may form part of a service provider platform, a mobile wallet platform or an MNO platform, depending on the implementation.
  • the server computer (121) may include a processor (901 ) 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 (902) and instructions may be provided to the processor (901) to carry out the functionality of the described components.
  • 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 generating component (903) arranged to generate one or more repayment instructions.
  • the or each repayment instruction may instruct repayment of at least part of an outstanding amount, the outstanding amount equalling the amount owed by a subscriber for receiving a cash loan.
  • the repayment instruction may include a source amount and a repayment source indicator indicating either a subscriber wallet account maintained by a mobile wallet platform or a subscriber network usage account maintained by an intelligent network (IN) of a mobile network operator (MNO) as a source account for repayment.
  • the server computer (121) may include an identifying component (904) for identifying the one or more source accounts for repayment from the repayment source indicator or indicators.
  • the server computer (121 ) may include an initiating component (905) for initiating a transfer of funds from the one or more source accounts to a recovery account for a repayment amount being a sum of the one or more source amounts to effect repayment of at least part of the outstanding amount.
  • the initiating component (905) may be configured to initiate, if the one or more source accounts include the subscriber wallet account, a transfer of funds from the subscriber wallet account to the recovery account.
  • the initiating component (905) may further be configured to initiate, if the one or more source accounts include the subscriber network usage account, a transfer of funds from the subscriber network usage account to the recovery account.
  • the initiating component (905) may include an interacting component (906) which interacts with the mobile wallet platform and the IN.
  • the interacting component (906) may include a mobile wallet platform integration component (906B) configured to interact with the mobile wallet platform via a mobile wallet platform interface.
  • the interacting component may further include an IN integration component (906A) configured to interact with the IN via an IN interface.
  • the server computer (121) may include a message receiving component (903) arranged to receive a request message requesting repayment of at least part of the outstanding amount.
  • the request message may include one or more repayment source indicators and either or both the source amount and the repayment amount.
  • the server computer may be configured to generate the one or more repayment instructions in response to receiving the request message.
  • the initiating component (904) may be arranged to initiate a transfer of funds from the repayment source to the recovery account by initiating a transfer of funds from the repayment source to a service provider wallet account if the repayment source is the subscriber wallet account or the subscriber network usage account.
  • the initiating component (904) may be arranged to initiate the transfer of funds from the repayment source to the recovery account by initiating a transfer of funds from the repayment source to a service provider network usage account if the repayment source is the subscriber network usage account.
  • the initiating component (904) may further include an adjustment component (907) arranged to interact with one or both of the mobile wallet platform and the IN, via the interacting component 906), to adjust values of respective accounts maintained therein.
  • the server computer (121 ) may include a monitoring component (908) arranged to monitor for occurrence of a predefined condition.
  • the predefined condition may include one or more of: loan repayment due date passed; and, inflow of funds detected at one or more source accounts
  • the server computer (121 ) may include a detecting component (910) configured to detect occurrence of the predefined condition.
  • the server computer may be further configured to generate one or more repayment instructions in response to detecting occurrence of the predefined condition.
  • the generating component (909) may be arranged to auto-generate the request message in response to the server computer (121 ) detecting a predefined condition.
  • the server computer (121 ) may include a determining component (911 ) configured to determine an available balance of the one or more source accounts.
  • the determining component may be configured to determine one or more of: the number of repayment instructions to be generated; the source amount of the or each repayment instruction; the source account to be indicated by the repayment source indicator of the or each payment instruction; and, the repayment amount. Determining of the aforementioned parameters may be based on the available balance of one or more source accounts.
  • the determining component (911) may be arranged to determine an inequality or equality of the available balance of one or more source accounts relative to the repayment amount or the outstanding amount.
  • the determining component (911) may be configured to determine the repayment amount such that the repayment amount is less than or equal to the outstanding amount.
  • the server computer (121 ) may be configured to effect repayment from a first source account, and if unable to do so, effect repayment from a second source account.
  • the server computer (121 ) may further be configured to effect partial repayment from either or both the first and second accounts. If repayment is to be effected from both accounts, the server computer (121) may be configured to determine the source amounts such that the repayment amount is less than or equal to the outstanding amount and each source amount is less than or equal to the available balance of the respective source accounts.
  • the first source account may be a network usage account
  • the second source account may be a wallet account, or vice versa.
  • aspects of the present disclosure therefore provide a system and method for airtime as payment method for repayment of a cash loan.
  • FIG. 10 illustrates an example of a computing device (900) in which various aspects of the disclosure may be implemented.
  • the computing device (900) 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 telephone), satellite phone, tablet computer, personal digital assistant or the like.
  • a mobile phone e.g. cellular telephone
  • satellite phone e.g. cellular telephone
  • tablet computer e.g. cellular telephone
  • personal digital assistant e.g. cellular telephone
  • the computing device (900) may be suitable for storing and executing computer program code.
  • the various participants and elements in the previously described system diagrams may use any suitable number of subsystems or components of the computing device (900) to facilitate the functions described herein.
  • the computing device (900) may include subsystems or components interconnected via a communication infrastructure (905) (for example, a communications bus, a network, etc.).
  • the computing device (900) may include one or more processors (910) and at least one memory component in the form of computer-readable media.
  • the one or more processors (910) may include one or more of: CPUs, graphical processing units (GPUs), microprocessors, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs) and the like.
  • a number of processors may be provided and may be arranged to carry out calculations simultaneously.
  • various subsystems or components of the computing device (900) 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 (915), which may include read only memory (ROM) and random access memory (RAM).
  • ROM read only memory
  • RAM random access memory
  • BIOS basic input/output system
  • System software may be stored in the system memory (915) including operating system software.
  • the memory components may also include secondary memory (920).
  • the secondary memory (920) may include a fixed disk (921 ), such as a hard disk drive, and, optionally, one or more storage interfaces (922) for interfacing with storage components (923), 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 (900) may include an external communications interface (930) for operation of the computing device (900) in a networked environment enabling transfer of data between multiple computing devices (900) and/or the Internet.
  • Data transferred via the external communications interface (930) may be in the form of signals, which may be electronic, electromagnetic, optical, radio, or other types of signal.
  • the external communications interface (930) may enable communication of data between the computing device (900) and other computing devices including servers and external storage facilities. Web services may be accessible by and/or from the computing device (900) via the communications interface (930).
  • the external communications interface (930) may be configured for connection to wireless communication channels (e.g., a cellular telephone network, wireless local area network (e.g. using Wi-FiTM), satellite-phone network, Satellite Internet Network, etc.) and may include an associated wireless transfer element, such as an antenna and associated circuitry.
  • wireless communication channels e.g., a cellular telephone network, wireless local area network (e.g. using Wi-FiTM), satellite-phone network, Satellite Internet Network, etc.
  • wireless transfer element such as an antenna and associated circuitry.
  • 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 computer-readable medium having stored computer-readable program code executable by the central processor (910).
  • 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 (930).
  • Interconnection via the communication infrastructure (905) allows the one or more processors (910) 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, cameras, or the like
  • input/output (I/O) devices such as a mouse, touchpad, keyboard, microphone, touch-sensitive display, input buttons, speakers and the like
  • I/O input/output
  • One or more displays (945) (which may be touch-sensitive displays) may be coupled to or integrally formed with the computing device (900) via a display or video adapter (940).
  • 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.
  • Components or devices configured or arranged to perform described functions or operations may be so arranged or configured through computer-implemented instructions which implement or carry out the described functions, algorithms, or methods.
  • the computer- implemented instructions may be provided by hardware or software units.
  • 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 all 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, JavaTM, C++, or PerlTM using, for example, conventional or object-oriented techniques.
  • the computer program code may be stored as a series 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 reside on or within a single computational apparatus, and may be present on or within different computational apparatuses within a system or network.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Economics (AREA)
  • Strategic Management (AREA)
  • Development Economics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Marketing (AREA)
  • Technology Law (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

L'invention concerne un système et un procédé de gestion intégrée de comptes multiplateformes. Un procédé consiste à créer une ou plusieurs instructions de remboursement qui ordonnent le remboursement d'au moins une partie d'un prêt en espèces. Chaque instruction comprend un montant source et un indicateur de source de remboursement indiquant soit un compte portefeuille d'abonné géré par une plateforme de portefeuille mobile, soit un compte d'utilisation de réseau d'abonné géré par un réseau intelligent (IN) d'un opérateur de réseau mobile (MNO) en tant que compte source destiné au remboursement. Le procédé consiste en outre à activer un transfert de fonds du ou des comptes sources à un compte de recouvrement pour un montant de remboursement égal à la somme du ou des montants sources pour effectuer un remboursement d'au moins une partie du prêt en espèces.
PCT/IB2022/051868 2021-03-23 2022-03-03 Gestion intégrée de comptes multiplateformes WO2022200881A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
MX2023007900A MX2023007900A (es) 2021-03-23 2022-03-03 Gestion integrada de cuentas multiplataforma.

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
ZA2021/01908 2021-03-23
ZA202101908 2021-03-23
ZA2021/04686 2021-07-06
ZA202104686 2021-07-06

Publications (1)

Publication Number Publication Date
WO2022200881A1 true WO2022200881A1 (fr) 2022-09-29

Family

ID=83395101

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2022/051868 WO2022200881A1 (fr) 2021-03-23 2022-03-03 Gestion intégrée de comptes multiplateformes

Country Status (2)

Country Link
MX (1) MX2023007900A (fr)
WO (1) WO2022200881A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080114676A1 (en) * 2003-11-12 2008-05-15 Burton David M Method for providing a prepaid debit card for debt recovery
US20090006205A1 (en) * 2007-06-26 2009-01-01 The Western Union Company Consolidated Payment Options
KR101128060B1 (ko) * 2009-12-18 2012-03-29 중소기업은행 대출금 상환 업무 처리를 개선한 대출금 자동상환 관리 시스템 및 그 동작방법
US20140279388A1 (en) * 2013-03-15 2014-09-18 Mobile Decisioning Holdings Limited Method, apparatus, and computer-readable medium for advancing prepaid credit
US20160042448A1 (en) * 2013-05-02 2016-02-11 Broadway Financial Technology Limited System, method, and apparatus for scoring and depositing short term credit

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080114676A1 (en) * 2003-11-12 2008-05-15 Burton David M Method for providing a prepaid debit card for debt recovery
US20090006205A1 (en) * 2007-06-26 2009-01-01 The Western Union Company Consolidated Payment Options
KR101128060B1 (ko) * 2009-12-18 2012-03-29 중소기업은행 대출금 상환 업무 처리를 개선한 대출금 자동상환 관리 시스템 및 그 동작방법
US20140279388A1 (en) * 2013-03-15 2014-09-18 Mobile Decisioning Holdings Limited Method, apparatus, and computer-readable medium for advancing prepaid credit
US20160042448A1 (en) * 2013-05-02 2016-02-11 Broadway Financial Technology Limited System, method, and apparatus for scoring and depositing short term credit

Also Published As

Publication number Publication date
MX2023007900A (es) 2023-07-11

Similar Documents

Publication Publication Date Title
US20220147969A1 (en) Monetary transaction system
US20200175488A1 (en) Interoperable financial transactions via mobile devices
US20230133708A1 (en) Decentralized systems and methods for transferring information between subsystems of communication networks
US9911103B2 (en) Payment gateway for processing payment requests associated with a wireless users account
US20120173396A1 (en) Bill division and group payment systems and methods
EP2974258A1 (fr) Procédé, appareil et support lisible par ordinateur pour une avance de crédit prépayé
US20140195427A1 (en) Mobile transactions
WO2020008384A1 (fr) Provision et recouvrement d'avances sur une utilisation de réseau
KR20110089295A (ko) 이동통신 네트워크를 이용한 송금 방법, 홈 위치 레지스터 및 서비스 제어 포인트
GB2517994A (en) Electronic transaction method
BR102019015628A2 (pt) Provisão de uso de rede antecipado para um assinante de celular pré-pago
WO2022200881A1 (fr) Gestion intégrée de comptes multiplateformes
WO2022038455A1 (fr) Système et procédé de fourniture de produit d'utilisation de réseau
OA21014A (en) Integrated cross-platform account management.
WO2019229652A1 (fr) Système et procédé de fourniture et de recouvrement d'une avance d'utilisation de réseau
WO2022008967A1 (fr) Fourniture de produit d'utilisation de réseau par le biais d'une plate-forme de portefeuille mobile
OA19720A (en) Network usage product provisioning via a mobile wallet platform
OA19727A (en) Type classification-based provisioning of network usage advances in a mobile network
OA20072A (en) Electronic voucher distribution account management.
WO2021240253A1 (fr) Provisionnement, en fonction de la classification de type, d'avances d'utilisation du réseau dans un réseau mobile
OA21159A (en) System and method for remote provision, disbursement and collection of secured loans.
WO2022038431A1 (fr) Système et procédé d'approvisionnement, de versement et de recouvrement à distance de prêts garantis
WO2022008988A1 (fr) Fourniture de différents services d'avance d'utilisation de réseau pour différentes catégories d'abonnés
EP4414921A1 (fr) Gestion de risque en libre-service
OA18625A (en) Systems and methods for mobile subscriber provisioning

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22774412

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: MX/A/2023/007900

Country of ref document: MX

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22774412

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 12.02.2024)