CN111192036A - Account resource updating method and device, computer equipment and storage medium - Google Patents

Account resource updating method and device, computer equipment and storage medium Download PDF

Info

Publication number
CN111192036A
CN111192036A CN201910708647.2A CN201910708647A CN111192036A CN 111192036 A CN111192036 A CN 111192036A CN 201910708647 A CN201910708647 A CN 201910708647A CN 111192036 A CN111192036 A CN 111192036A
Authority
CN
China
Prior art keywords
account
resource
server
user
verification code
Prior art date
Legal status (The legal status 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 status listed.)
Granted
Application number
CN201910708647.2A
Other languages
Chinese (zh)
Other versions
CN111192036B (en
Inventor
郭会东
谢东东
刘瑶
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen Co Ltd
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 Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CN201910708647.2A priority Critical patent/CN111192036B/en
Publication of CN111192036A publication Critical patent/CN111192036A/en
Application granted granted Critical
Publication of CN111192036B publication Critical patent/CN111192036B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

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
    • 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
    • G06Q20/102—Bill distribution or payments
    • 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/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • 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/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4014—Identity check for transactions

Abstract

The application discloses an account resource updating method, and belongs to the technical field of computers. The method is performed by a server of a first resource management system, the method comprising: acquiring a resource transfer record of a second resource management system, extracting remark information from the resource transfer record, and extracting a first user number and a first verification code from the remark information; and updating the second type resource in the third account when the binding relationship between the first user number and the first account exists in the server of the first resource management system and the corresponding relationship between the first user number and the first verification code exists in the server of the first resource management system. According to the method and the device, whether multiple corresponding relations exist in the server is judged, so that whether the second type resources in the third account can be updated or not is determined, information which needs to be checked when the server updates the account resources is increased, and the safety of account resource updating is improved.

Description

Account resource updating method and device, computer equipment and storage medium
Technical Field
The present application relates to the field of computer technologies, and in particular, to an account resource updating method and apparatus, a computer device, and a storage medium.
Background
In daily life, it is more and more common to update account resources in a terminal, for example, a certain amount of money is added to a related Application (APP), so that the amount of money owned by an account registered in the APP changes, and the like.
In the related art, in the aspect of recharging the account logged in the APP, an offline recharging method or an online recharging method may be selected, wherein when a user selects to recharge the account in the offline recharging method, the user often needs to transfer money through a bank account of the user, remittance is performed to a designated bank set by a service provider of the APP, and when the designated bank receives the transfer money of the user, the server of the APP can recharge the account by a corresponding amount in the system. In order to prevent errors in the recharging process, the user can transfer money according to a scheme negotiated by the APP facilitator and the designated bank, for example, when the user transfers money, a character string consisting of certain special characters (such as symbols, Chinese characters, numbers and the like) is selected at a decimal place of the transfer money amount, and when the APP server recharges money, the character string consisting of the special characters can be checked, so that the safety of the recharging process is improved.
In the related art, since the verification process is simple, once the special character is verified incorrectly, the user may receive a loss, so that the security of recharging according to the method is low.
Disclosure of Invention
The embodiment of the application provides an account resource updating method, an account resource updating device, computer equipment and a storage medium, and can improve the safety when the account in an APP is recharged in an offline recharging mode. The technical scheme is as follows:
in one aspect, an embodiment of the present application provides an account resource updating method, where the method is executed by a server of a first resource management system, and the method includes:
acquiring a resource transfer record of a second resource management system, wherein the resource transfer record is a record of transferring a first type of resource from a first account to a second account, the first account is an account of a target user corresponding to the second resource management system, and the second account is an account of a server corresponding to the second resource management system;
extracting remark information from the resource transfer record, wherein the remark information is information filled in a resource transfer triggering interface by the target user, and the resource transfer triggering interface is an interface for triggering the first account to transfer the first type of resource to the second account;
extracting a first user number and a first verification code from the remark information;
when the binding relationship between the first user number and the first account exists in the server and the corresponding relationship between the first user number and the first verification code exists in the server, updating a second type resource in a third account; the third account is an account corresponding to the first user number and registered in the first resource management system.
In one aspect, an embodiment of the present application further provides an account resource updating apparatus, where the apparatus is used in a server of a first resource management system, and the apparatus includes:
a transfer record obtaining module, configured to obtain a resource transfer record of a second resource management system, where the resource transfer record is a record of transferring a first type of resource from a first account to a second account, the first account is an account of a target user in the second resource management system, and the second account is an account of a server in the second resource management system;
a first information extraction module, configured to extract remark information from the resource transfer record, where the remark information is information that the target user fills in a resource transfer trigger interface, and the resource transfer trigger interface is an interface that triggers the first account to transfer the first type of resource to the second account;
the second information extraction module is used for extracting a first user number and a first verification code from the remark information;
an account resource updating module, configured to update a second type resource in a third account when a binding relationship between the first user number and the first account exists in the server and a corresponding relationship between the first user number and the first verification code exists in the server; the third account is an account corresponding to the first user number and registered in the first resource management system.
Optionally, the apparatus further comprises: a binding account inquiry module and a binding relation determination module;
the account number resource updating module is used for updating a first type resource in a first account number, and the account number resource updating module is used for updating a second type resource in a second account number;
and the binding relationship determining module is used for determining that the binding relationship between the user number and the first account exists in the server when the first account exists in the binding accounts.
Optionally, the apparatus further comprises: a reservation recording query module and a corresponding relation determining module;
the reservation record query module is used for querying a target reservation record in the server before the account resource updating module updates the second type of resource in a third account, wherein the target reservation record comprises a corresponding relation between a second verification code and a second user number; the first user number is consistent with the second user number, and the first verification code is consistent with the second verification code;
and the corresponding relation determining module is used for determining that the corresponding relation between the first user number and the first verification code exists in the server when the target reservation record is inquired.
The reservation recording query module comprises: a first record query unit and a first record determination unit;
the first record inquiry unit is used for inquiring a first reservation record according to the first verification code, wherein the first reservation record comprises the corresponding relation between the first verification code and the second user number;
the first record determining unit is configured to determine that the target reservation record is queried when the first user number is consistent with the second user number.
The reservation recording query module comprises: a second record query unit and a second record determination unit;
the second record inquiry unit is used for inquiring a second reservation record according to the first user number, wherein the second reservation record comprises the corresponding relation between the first user number and the second verification code;
the second record determining unit is configured to determine that the target reservation record is queried when the first verification code is consistent with the second verification code.
Optionally, the apparatus further comprises: the system comprises a reservation interface sending module, a verification code generating module, a reservation record establishing module and a verification code sending module;
the reservation interface sending module is configured to send a reservation interface to the user terminal corresponding to the third account before the transfer record obtaining module obtains the resource transfer record of the second resource management system, where the reservation interface includes a reservation control;
the verification code generation module is used for generating the second verification code when receiving a reservation request; the reservation request is a request sent by the user terminal when the user terminal detects the triggering operation of the reservation control;
the reservation record establishing module is used for establishing the target reservation record according to the second verification code;
and the verification code sending module is used for sending the second verification code to the user terminal.
Optionally, the verification code sending module includes: a first transmitting unit or a second transmitting unit;
the first sending unit is used for sending the second verification code to the reservation interface;
the second sending unit is configured to send the second verification code to the user terminal in a message format outside the reserved interface, where the message format outside the reserved interface includes a short message or an instant messaging message.
Optionally, the verification code generating module includes: a first generation unit or a second generation unit;
the first generating unit is used for randomly generating the second verification code when receiving a reservation request;
and the second generating unit is used for generating the second verification code according to a preset coding rule when a reservation request is received.
Optionally, the reservation interface further includes a verification code input box, and the reservation request includes a verification code input by the user in the verification code input box;
the verification code generation module is configured to obtain the verification code included in the reservation request as the second verification code.
Optionally, the first type of resource includes at least two subtypes of resources; the target reservation record also comprises resource information of the first type of resource reserved and transferred; the resource information includes at least one of a number of the first type of resource and a subtype of the first type of resource;
the device further comprises: a resource information acquisition module;
the resource information acquisition module is used for acquiring resource information of the first type of resources transferred from the first account to the second account according to the resource transfer record before the account resource updating module updates the second type of resources in the third account;
the account resource updating module is further configured to execute the step of updating the second type resource in the third account when the resource information of the first type resource reserved for transfer matches the resource information of the first type resource transferred from the first account to the second account.
Optionally, the apparatus further comprises: a recharge record unloading module;
and the recharge record transfer module is used for transferring the target reservation record into the recharge record of the third account after the account resource updating module updates the second type of resource in the third account.
Optionally, the second resource management system is a banking system, and the resource transfer record is a bank transaction flow of the transfer from the first account to the second account.
In one aspect, an embodiment of the present application further provides a computer device, where the computer device includes a processor and a memory, where the memory stores at least one instruction, at least one program, a code set, or a set of instructions, and the at least one instruction, the at least one program, the code set, or the set of instructions is loaded and executed by the processor to implement the account resource updating method described above.
In one aspect, an embodiment of the present application further provides a computer-readable storage medium, where at least one instruction, at least one program, a code set, or a set of instructions is stored in the storage medium, and the at least one instruction, the at least one program, the code set, or the set of instructions is loaded and executed by a processor to implement the account resource updating method described above.
The technical scheme provided by the embodiment of the application at least comprises the following beneficial effects:
when a server of a first resource management system acquires a resource transfer record of a second resource management system, extracting remark information from the resource transfer record, and extracting a first user number and a first verification code from the remark information; and updating the second type resource in the third account when the binding relationship between the first user number and the first account exists in the server of the first resource management system and the corresponding relationship between the first user number and the first verification code exists in the server of the first resource management system. According to the method and the device, whether the corresponding relation exists or not can be judged from the server by extracting the first user number and the first verification code in the remark information in the resource transfer record, so that whether the second type resource in the third account can be updated or not is determined, whether the second type resource in the third account can be updated or not is judged through the corresponding relation of the first user number and the first verification code, information needing to be checked when the account resource is updated by the server is added, and the safety of account resource updating is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic structural diagram of a system for offline recharging provided in an embodiment of the present application;
fig. 2 is a flowchart of a method for updating account resources according to an embodiment of the present disclosure;
FIG. 3 is an interface diagram of a resource triggering interface according to an embodiment of the present application;
fig. 4 is a flowchart of a method for updating account resources according to an embodiment of the present disclosure;
FIG. 5 is a schematic diagram of an interface displayed by a second APP provided in the embodiments of the present application;
FIG. 6 is an interface diagram of an appointment interface according to an embodiment of the present application;
FIG. 7 is an interface schematic diagram of a selection interface relating to FIG. 6 according to an embodiment of the present application;
FIG. 8 is an interface diagram of an appointment interface according to an embodiment of the present application;
FIG. 9 is an interface diagram of an appointment interface according to an embodiment of the present application;
FIG. 10 is an interface diagram of a query interface according to an embodiment of the present application;
FIG. 11 is a schematic diagram of a transfer record interface according to an embodiment of the present application related to FIG. 10;
fig. 12 is a timing diagram illustrating a flow of offline recharge provided by an embodiment of the present application;
FIG. 13 is a system architecture diagram of a first resource management system according to an embodiment of the present application;
fig. 14 is a schematic flowchart of a verification process of a recharge verification module according to an embodiment of the present application;
fig. 15 is a block diagram illustrating a structure of an account resource updating apparatus according to an exemplary embodiment of the present application;
FIG. 16 is a block diagram illustrating a computer device according to an exemplary embodiment of the present application;
fig. 17 is a schematic structural diagram of a computer device according to an exemplary embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The scheme provided by the application can be used in an application scene that a user updates own account resources by recharging under a line, and after the user completes remittance under the line, safety verification is carried out when the account resources are updated, so that errors caused by recharging under a user line are prevented, and user loss and the like are avoided. For ease of understanding, the following first presents a brief summary of some of the terms and application scenarios to which this application relates.
1) Offline recharge
The offline recharging is a mode that a user recharges an account number registered in a third-party payment mechanism or other stored-value mechanisms through offline remittance and other modes.
2) On-line recharge
The online recharging is a mode that a user recharges an account number registered in a payment mechanism or other value-storing mechanisms by means of payment means such as gateway payment and quick payment.
3) Customer reimbursement
Customer reimbursement refers to the actual receipt of the outstanding money funds by the payment institution for the transaction of the customer's committed payment.
4) Bank with reserve payment
The bank of reserve payment is the financial institution which provides the deposit and management service of the reserve payment for the payment institution and needs to sign a cooperative agreement with a plurality of commercial banks and open a deposit and management account number special for the reserve payment for the payment institution to develop the payment business.
5) Spare payment account number
The reserve payment account number refers to a deposit account number special for reserve payment which is set up in a reserve payment bank by a payment mechanism in cooperation with the reserve payment bank.
6) Several offline recharging methods:
(1) recharging in an offline store: the payment mechanism or the value-storing mechanism cooperates with certain offline store mechanisms, a user delivers funds to the offline store mechanisms, the offline store mechanisms inform the payment mechanism or the value-storing mechanism, and the payment mechanism or the value-storing mechanism recharges the account numbers registered in the system of the user according to the notice of the offline store mechanisms.
(2) Offline remittance. The user transfers money from a bank account number of the user or transfers the money to a designated account number of a payment mechanism or a value storage mechanism in a counter remittance mode, the payment mechanism or the value storage mechanism and the user can negotiate to select some special numbers (or specific character strings) in the transfer amount of small digits, and after the payment mechanism or the value storage mechanism confirms that a bank of gold and silver prepared by the user receives the transfer of the user, the payment mechanism or the value storage mechanism supplements the money for the account number registered in the system of the user.
With the development of the field of computers, people have been very common in daily life to use APPs for entertainment or work, users can recharge their accounts in the process of using APPs, so that account resources corresponding to the accounts are changed (for example, account resources become more), and the application scenario related to the application is simply introduced by taking the example that users recharge accounts registered in APPs of certain service providers by recharging under-line.
Please refer to fig. 1, which shows a schematic structural diagram of an offline recharging system according to an embodiment of the present application. As shown in fig. 1, a terminal 110, a first resource management system 120, and a second resource management system 130 are included.
The terminal 110 may have an APP (e.g., application a) of a certain service provider installed therein. Alternatively, the terminal 110 may be a mobile phone, a tablet computer, an e-book reader, smart glasses, a smart watch, a notebook computer, a laptop portable computer, a desktop computer, and the like.
The first resource management system 120 may be a management system of the APP installed in the terminal 110. Optionally, the first resource management system 120 includes a server 140 corresponding to the APP, a database 150 for storing data, and the like. Optionally, the server 140 is a server, or a plurality of servers, or a virtualization platform, a public platform, or a cloud computing service center. Optionally, the user may register an account in the first resource management system 120 through the APP in the terminal 110, and log in the terminal 110, so as to implement interaction with the first resource management system 120. Alternatively, the number of the database 150 may be plural, and the database 150 may be a development database, a payment database, or the like. The user mentioned in the embodiment of the present application may be an enterprise user or an individual user.
Optionally, account resources exist in the first resource management system 120 for the account registered by the user, for example, the account resources may be resources of money, stocks, bonds, funds and the like of the account in the first resource management system 120. The user may interact with the server of the first resource management system 120 through the terminal 110, change account resources of the account, and the like. For example, when the account resource is money, the user may change the account resource by charging or cashing.
Alternatively, the terminal 110 and the first resource management system 120 may be connected through a communication network. Optionally, the communication network is a wired network or a wireless network.
Optionally, the wireless network or wired network described above uses standard communication techniques and/or protocols. The Network is typically the Internet, but may be any Network including, but not limited to, a Local Area Network (LAN), a Metropolitan Area Network (MAN), a Wide Area Network (WAN), a mobile, wireline or wireless Network, a private Network, or any combination of virtual private networks. In some embodiments, data exchanged over a network is represented using techniques and/or formats including Hypertext Mark-up Language (HTML), Extensible markup Language (XML), and the like. All or some of the links may also be encrypted using conventional encryption techniques such as Secure Socket Layer (SSL), Transport Layer Security (TLS), Virtual Private Network (VPN), Internet protocol Security (IPsec). In other embodiments, custom and/or dedicated data communication techniques may also be used in place of, or in addition to, the data communication techniques described above.
Optionally, the second resource management system 130 includes a plurality of servers 160, a plurality of databases 170, and the like. Data interaction can be carried out among a plurality of servers in the second resource management system, and data stored in respective databases can be changed. For example, the second resource management system may be a banking system composed of respective bank systems, the plurality of servers 160 may be respective servers of the respective banks, and the plurality of databases 170 may also be respective databases of the respective banks. Money transfer, remittance and the like can be carried out among the banks, so that the amount of money in the respective databases is changed. Alternatively, the second resource management system may be a single banking system.
Optionally, the server in the second resource management system may also be one server, or several servers, or one virtualization platform, or one cloud computing service center. The database in the second resource management system may also be a development database or a paid database, etc. This is not limited by the examples of the present application. The terminal 110 and the second resource management system 130 may also be connected via the communication network.
Optionally, the facilitator of the first resource management system 120 may register a backup account with a first server in the second resource management system 130, and associate the first resource management system 120 with the first server, so that the first resource management system may interact with the first server, which may be any one of the plurality of servers 160. For example, the first resource management system may send a data query request to the first server, query data of the backup account in a database corresponding to the first server, and the like. That is, the first resource management system 120 and the second resource management system 130 may be connected to each other through the communication network.
Optionally, the user may also register a user account in the second resource management system 130, that is, register a user account on one or more servers of the plurality of servers 160, manage the user account, and the like. For example, when the second resource management system is a union pay system, the user registers his/her own user account in a certain bank server, and the user may perform operations such as money transfer and remittance to the user account. Optionally, the server of the user account registered by the user may be the same as or different from the server of the backup account.
Taking the second resource management system as an example of a unionpay system, when the user selects an offline recharging manner to recharge the account number registered by the user in the first resource system, the user may first transfer money and remit money to a prepaid account number registered by a developer of the first resource management system through the user account number, and when a server of the prepaid account number knows that the user account number transfers money to the server, the server may notify the first resource management system of information of the money (for example, the user account number, the amount of the money, the recharging account number, and the like), and the first resource management system recharges the account number registered by the user in the system, thereby completing the offline recharging. In a possible implementation manner, in the above system structure of adding value offline shown in fig. 1, the user may also transfer the account to the backup payment account by using a manual transfer mode in a physical storefront, which is not limited in this application.
In order to reduce the error rate during offline recharging and improve the security of offline recharging, please refer to fig. 2, which shows a flowchart of a method for updating account resources according to an embodiment of the present application. The method may be applied to the offline recharging system shown in fig. 1, and is executed by a server of a first resource management system in the system, as shown in fig. 2, and the method may include the following steps.
Step 201, acquiring a resource transfer record of the second resource management system.
The resource transfer record is a record of transferring a first type of resource from a first account to a second account, the first account is an account of a target user in a second resource management system, and the second account is an account of a server of the first resource management system in the second resource management system.
The resource transfer record may be a transfer record generated by a server corresponding to the second account after the first account transfers the first type of resource to the second account, for example, the server of the second account may record a resource transfer condition of the second account, record a source account (the first account) of the resource transfer, and record a transfer amount of the resource transfer. In a possible implementation manner, when the transfer-out record generated by the server of the first account includes the transfer-out account, that is, if the server of the first account records the resource transfer condition of the first account, a transfer-out account (a second account) for transferring the resource and a transfer amount of the resource transfer are recorded, the resource transfer record may also be the transfer-out record generated by the server of the first account.
Optionally, if the second resource management system is a unionpay system, the resource may be data of funds, stocks, bonds, and the like, and correspondingly, the first account and the second account may also be bank accounts, stock accounts, bond accounts, and the like.
Optionally, the target user is any user who can register the first account in the second asset management system. For example, when an enterprise registers the first account in the second resource management system, the target user may be the enterprise, and when an individual user registers the first account in the second resource management system, the target user may be the individual user.
Optionally, the second account is an account registered by the server of the first resource management system in the second asset management system, where the second account may be used to receive resources transferred by other accounts, for example, the second account may receive money transferred by the first account, and the like. Optionally, the second account may be a common account registered by the server of the second asset management system for each target user, that is, each target user may transfer resources into the second account.
Optionally, the first resource management system is a platform system developed by a certain service provider and having a payment capability, and accordingly, the server of the first resource management system may be a server of the platform system. For example, the user can make payment, remittance, payment by agency, and the like by using the APP corresponding to the server of the first resource management system.
Step 202, extracting remark information from the resource transfer record.
The remark information is information filled in a resource transfer triggering interface by a target user, and the resource transfer triggering interface is an interface for triggering a first account to transfer a first type of resource to a second account.
The remark information may be an authentication code, a user number, a user name, a telephone number, a mailbox account, and the like, which are filled by the target user. In a possible implementation manner, when a target user transfers a first type of resource from a first account to a second account, a service provider of the first account may provide a first APP of the target user for the target user, and the user may enter a resource transfer triggering interface through the first APP to initiate resource transfer. Please refer to fig. 3, which illustrates an interface diagram of a resource triggering interface according to an embodiment of the present application. As shown in fig. 3, the resource transfer trigger interface 300 includes a first account input box 301, a second account input box 302, a resource type input box 303, a resource quantity input box 304, a remark information input box 305, a confirmation control 306, and a cancel control 307. The user may fill in various information on the resource triggering interface 300 and click the confirmation control 306 to trigger the first account to transfer the resource to the second account.
In one possible implementation, the remark information may also be the remark information that the target user fills when going to the branch bill filled in by the physical storefront. The physical storefront is a storefront opened by a first account's facilitator. Optionally, the bill generated by the resource transfer triggering interface may be referred to as an electronic bill, and the account number filled in the implementation manner may be an entity bill. The embodiments of the present application are not limited.
Optionally, when the second account receives the first type of resource transferred by the first account and generates a resource transfer record, the remark information may also be generated in the resource transfer record as additional information, so that the remark information filled by the target user exists in the resource transfer record, and the server of the first resource management system may obtain the remark information from the resource transfer record.
Step 203, extracting the first user number and the first verification code from the remark information.
Optionally, the first user number may be a user number corresponding to an account registered in a server of the first resource management system and filled by the target user. When a target user registers an account with a server of the first asset management system, the server of the first asset management system may generate a user number for the target user. For example, the target user registers an account in the server of the first resource management system by using a mobile phone number of the target user, at this time, the server of the first resource system may generate a user number (for example, 10001) for the account, the user number may be filled in when the user fills in the remark information, and if the server of the first resource system acquires the user number according to the remark information, the user number may be referred to as the first user number. Similarly, the first verification code may also be a verification code filled in by the target user.
Optionally, when the server of the first resource management system obtains the remark information from the resource transfer record, the remark information may be selectively obtained. For example, when the remark information filled by the user includes an authentication code, a user number, a user name, a telephone number, a mailbox account, and the like, the server of the first resource management system extracts the user number and the authentication code from the remark information according to the scanning identification.
Optionally, when the server of the first resource management system needs to obtain other information in the remark information, the server of the first resource management system may also obtain the other remark information again through scanning identification, for example, the server of the first resource management system also needs to obtain other remark information such as a telephone number of the user, and the server of the first resource management system may also obtain the remark information, which is not limited in this embodiment of the application.
And 204, updating the second-type resource in the third account when the binding relationship between the first user number and the first account exists in the server and the corresponding relationship between the first user number and the first verification code exists in the server.
And the third account is an account corresponding to the first user number and registered in the first resource management system.
Optionally, a database corresponding to the server may store a binding relationship between the first user number and the first account, or store a corresponding relationship between the user number and the verification code, and when the database corresponding to the server has the binding relationship between the first user number and the first account, or has the corresponding relationship between the first user number and the first verification code, the server may update the second type resource in the third account. The user number is a number generated by the server for an account after the user registers the account in the server of the first resource management system, and the server of the first resource management system can store the binding relationship between a plurality of user numbers and a plurality of accounts, that is, each third account corresponds to a unique user number. The first user number may be any one of a plurality of user numbers, and the third account is an account corresponding to the first user number. Optionally, the second type of resource may be the same as or different from the first type of resource.
Optionally, when the binding relationship between the first user number and the first account does not exist in the server, or when the corresponding relationship between the first user number and the first verification code does not exist in the server, the server may further send a feedback of update failure to the target user, so as to remind the user whether to make a mistake when the first type of resource is transferred from the first account to the second account.
To sum up, when the server of the first resource management system acquires the resource transfer record of the second resource management system, the remark information is extracted from the resource transfer record, and the first user number and the first verification code are extracted from the remark information; and updating the second type resource in the third account when the binding relationship between the first user number and the first account exists in the server of the first resource management system and the corresponding relationship between the first user number and the first verification code exists in the server of the first resource management system. According to the method and the device, whether the corresponding relation exists or not can be judged from the server by extracting the first user number and the first verification code in the remark information in the resource transfer record, so that whether the second type resource in the third account can be updated or not is determined, whether the second type resource in the third account can be updated or not is judged through the corresponding relation of the first user number and the first verification code, information needing to be checked when the account resource is updated by the server is added, and the safety of account resource updating is improved.
Taking account resources in the first resource management system as money as an example, please refer to fig. 4, which shows a flowchart of a method for updating account resources according to an embodiment of the present application. The method can be applied to the offline recharging system shown in fig. 1 and executed by the server of the first resource management system in the system, as shown in fig. 4, and the method can include the following steps.
Step 401, a reservation interface is sent to a user terminal corresponding to the third account, and the reservation interface includes a reservation control.
And the third account is the account registered in the first resource management system by the target user. The service provider of the first resource management system can provide a second APP for the target user, the user can register a third account number in the terminal through the second APP, and log in the second APP through the third account number, and initiates a request for displaying the reservation interface, correspondingly, the server of the first resource management system can send the reservation interface to the user terminal after receiving the request for displaying the reservation interface sent by the user terminal, and therefore the user terminal can display the reservation interface.
In a possible implementation manner, the target user may also initiate the request for displaying the reservation interface by logging in the web page client, and similarly, the server of the first resource management system may also send the reservation interface to the user terminal after receiving the request for displaying the reservation interface sent by the user terminal, so that the user terminal displays the reservation interface. This is not limited by the examples of the present application.
Please refer to fig. 5, which illustrates an interface schematic diagram of a second APP display provided in the embodiment of the present application. As shown in fig. 5, a transfer control 501 is included in the interface 500, and a user can click the transfer control to send a request for displaying a reservation interface to a server of the first resource management system. Optionally, when the second APP is an APP that can perform payment, remittance, or payment, the transfer control may be represented by "top-up".
Optionally, a reservation interface returned to the user terminal by the server of the first resource management system includes a reservation control, please refer to fig. 6, which shows an interface schematic diagram of a reservation interface according to an embodiment of the present application. As shown in fig. 6, a reservation interface 600 includes a reservation control 601. The target user may send a reservation request to the server of the first resource management system by clicking the reservation control 601. Optionally, the reservation request includes information such as the first account, the user number, the resource type, and the resource quantity.
The user number may be a user number generated by the server of the first resource management system corresponding to the third account when the target user registers the third account in the server of the first resource management system. Optionally, when the target user registers an account in the server of the first resource management system, the server of the first resource management system may generate a unique corresponding user number for the account, for example, the target user registers an account one, and the server of the first resource management system may generate a number one corresponding to the account one, and use the number one as an identifier of the account one in the first resource management system.
Optionally, the target user may also bind the first account to the account, where the first account is an account of the target user in the second resource management system. That is, the target user may bind the third account in the first resource management system with the first account in the second resource management system. Optionally, the server of the first resource management system is provided with a user binding table, please refer to table 1, which shows a user binding table according to an embodiment of the present application.
Figure BDA0002152975560000141
Figure BDA0002152975560000151
TABLE 1
As can be seen from table 1, when the target user binds the third account and the first account in the server of the first resource management system, the target user can bind according to the information. Please refer to table 2, which illustrates a binding result record table according to an embodiment of the present application.
Uid Uname Currency Bank_account Bank_name Status
100001 Guo Xiaoming First type 621***456 Manufacturer 1 Is effective
100001 Guo Xiaoming Of the second type 621***456 Manufacturer 1 Is effective
100001 Guo Xiaoming First type 142***471 Manufacturer 1 Is effective
100002 Guo Da Ming (Guo) First type 621***474 Manufacturer 2 Is effective
100004 Guo Da Ming (Guo) First type 551***474 Manufacturer 2 Is effective
100003 Guo Xiaoming First type 621***456 Manufacturer 1 Is effective
100003 Guo Xiaoming First type 142***471 Manufacturer 1 Is effective
TABLE 2
As can be seen from table 2, for the binding of the first account and the third account, the server of the first resource management system is bound by the user number corresponding to the third account, that is, the user number may be equivalent to the third account.
Optionally, as shown in table 1, when the target user binds the third account and the first account, the corresponding resource type may also be selected, that is, the second APP may provide a selection control for the target user when the target user binds the first account, and the user may select different resource types to bind through the selection control. For example, the target user selects the first type of resource binding, and the user may also select the second type of resource binding. Alternatively, the server of the first resource management system may record the two binding results in table 2. That is, the target user may establish a binding relationship according to different resource types in the first resource management system for the same first account.
Optionally, when the target user registers multiple third accounts on the server of the first resource management system, the target user may also bind the same first account with the multiple third accounts, and the server of the first resource management system may also generate corresponding binding result records in the table 2 corresponding to the third accounts and the first account. Alternatively, the target user may also bind the same third account with the multiple first accounts in the server of the first resource management system, and the server of the first resource management system may also generate corresponding binding result records in table 2 corresponding to the third account and the multiple first accounts.
Optionally, when the target user binds the same third account with multiple first accounts, after the target user clicks the reservation control shown in fig. 6, the user terminal may further display a selection interface, please refer to fig. 7, which shows an interface schematic diagram of a selection interface related to fig. 6 in an embodiment of the present application. As shown in fig. 7, a plurality of first account fields 701 are included, and a selection control 702 is selected, and a target user can select one of the first accounts to initiate a reservation request by clicking on the selection control. Optionally, the interface shown in fig. 7 may also be converted into a form in which the user inputs the first account, which is not limited in this embodiment of the application.
In a possible implementation manner, the server of the first resource management system is a server of the payment institution a, and the second APP provided by the server of the payment institution a can perform operations such as payment. When a target user registers an account in the second APP, the server of the payment mechanism a may generate a user number internally, the target user may bind a bank card to the account registered in the second APP, such as the user binding table of table 1, in practical applications, the second APP may provide a resource type that the user may select when binding, for example, currencies such as rmb, dollar, euro, japanese yen, and the like, correspondingly, the bank account input when the first account corresponds to the user binding, and the account merchant may also be a bank corresponding to the bank account.
Step 402, generating a second verification code when receiving the reservation request.
The reservation request is a request sent by the user terminal when the triggering operation of the reservation control is detected.
Optionally, the target user triggers the reservation control in the reservation interface, and the server of the first resource management system may generate the second verification code according to the received reservation request. When the user terminal initiates a reservation request to the server based on the second APP logged in with the third account, the server may obtain a user number corresponding to the third account according to the third account, and generate a second verification code for the user number.
In one possible implementation, the server of the first resource management system randomly generates the second verification code upon receiving the reservation request. For example, the server of the first resource management system may randomly generate a corresponding second verification code for each received reservation request, where the second verification code generated each time needs to be different from the second verification code stored in the current server. Optionally, a random string generator may be provided in the server of the first resource management system, and the server may use the string generated by the random string generator as the second verification code generated this time, and optionally, when the random string generator generates a string, the server may further determine the string, determine whether the string exists in the second verification code currently stored by itself, and when the string does not exist in the second verification code currently stored by itself, use the second verification code generated this time by the string.
In a possible implementation manner, when the server of the first resource management system receives the reservation request, the server generates the second verification code according to a preset coding rule. Alternatively, the encoding rule may be sequentially increased according to the order of generating the second verification codes, that is, the second verification code generated each time is increased by a fixed amount relative to the second verification code generated last time. For example, for each reservation request, the number of the generated second verification codes is increased by a fixed amount with respect to the second verification code generated last time, for example, the verification code generated last time is 1234, the verification code generated this time may be 1235, the verification code generated next time may be 1236, and so on.
In a possible implementation manner, the encoding rule of the second verification code may also be generated according to a partial account number of the first account number and a partial account number of the third account number. For example, corresponding to each reservation request, the server of the first resource management system may combine the last 4 digits of the first account and the last 4 digits of the third account to generate the second verification code corresponding to the reservation request. Wherein the encoding rule can be set in the server in advance by a developer.
In a possible implementation manner, the reservation interface displayed in the user terminal further includes a verification code input box, and the reservation request includes a verification code input by the user in the verification code input box; step 402 generates the second verification code according to the reservation request, which may be replaced by acquiring the verification code included in the reservation request as the second verification code. Please refer to fig. 8, which illustrates an interface diagram of an appointment interface according to an embodiment of the present application. As shown in fig. 8, the reservation interface 800 includes a reservation control 801 and a verification code input box 802, where a verification code that a target user can input in the verification code input box in the reservation interface is included, and when the target user clicks the reservation control in the reservation interface, a reservation request sent by a user terminal to a server of a first resource management system may carry the verification code input by the target user, and accordingly, the server of the first resource management system may obtain the verification code included in the reservation request as a second verification code. Optionally, in a possible implementation manner, the server of the first resource management system may also verify a verification code included in the reservation request, determine whether the verification code already exists in the second verification code currently stored by the server, and if the verification code already exists, prompt the user in the reservation interface that the verification code is unavailable, ask the user to reselect or input a verification code.
The embodiment of the present application does not limit the manner of generating the second verification code.
And step 403, establishing a target reservation record according to the second verification code.
The server in the first resource management system may establish the target reservation record in the server according to the obtained second verification code. Alternatively, the target reservation recording may be recorded according to various information contained in the following table 3.
Field(s) Type (B) Means of Examples of the invention
Uid Character string User number 100001
Recharge_code Character string Verification code 20190101000001
Status Enumerated value Status of results Unfinished/finished
TABLE 3
As can be seen from table 3, when the server in the first resource management system establishes the target reservation record according to the second verification code, the server may establish a corresponding relationship between the user number of the third account and the second verification code, and generate the result status of the entry mark reservation record. Wherein the result status is used to indicate whether the resource in the third account has completed the transfer. Referring to table 4, a target reservation recording table according to an embodiment of the present application is shown.
Uid Recharge_code Status
100001 20190101000001 Unfinished
100001 20190101000002 Unfinished
100002 20190101000003 Unfinished
TABLE 4
As can be seen from table 4, in response to the reservation request initiated by the target user, the server in the first resource management system may generate the target reservation record in table 4 in the server corresponding to the user number of the third account and the obtained second verification code, and store the target reservation record in the first resource management system. Optionally, when the server of the first resource management system is the server of the payment mechanism a, the result state may be a recharge state, that is, the recharge state may indicate whether a certain entry mark reservation record corresponding to the third account has been recharged. That is, what is meant by Status in table 3 above may be a charged state, corresponding to an uncharged/charged state in the example description.
Step 404, sending the second verification code to the user terminal.
Optionally, the server of the first resource management system sends the generated second verification code to the user terminal, so that the target user can obtain information of the verification code that needs to be used when transferring the resource from the first account.
In one possible implementation, the server of the first resource management system sends the second verification code to the reservation interface; and the target user knows the second verification code through the reservation interface. Please refer to fig. 9, which illustrates an interface diagram of an appointment interface according to an embodiment of the present application. As shown in fig. 9, the reservation interface 900 includes a second verification code display box 901, and the server of the first resource management system sends the second verification code to the second verification code display box 901 in the reservation interface for display, so that the target user knows the verification code used in resource transfer of the first account here.
In a possible implementation manner, when the server of the first resource management system sends the second verification code to the user terminal, the second verification code may also be sent to the user terminal in a message form other than the reservation interface. Wherein, the message form outside the reservation interface comprises short message or instant communication message. Optionally, the first resource management system stores a mobile phone number of the target user, and in order to prevent the verification code from being leaked to the non-target user, the first resource management system may send a short message to the mobile phone of the target user to notify the second verification code generated by the reservation request. Or, when the first resource management system has an instant messaging program and the third account is an account that the user logs in on the instant messaging program, the first resource management system may also send an instant messaging message to the user through an internal instant messaging program to notify the user of the second verification code.
In a possible implementation manner, a customer service terminal may be provided in the first resource management system, and a customer service corresponding to the customer service terminal may perform telephone communication with the target user, and in the content in the above steps 401 to 403, the customer service may input corresponding required information in the customer terminal through dictation with the target user, so that the server of the first resource management system completes the above steps 401 and 403. Similarly, the second verification code is sent to the user terminal in step 404, or the customer service may inform the target user of the second verification code by speaking. This is not limited by the examples of the present application.
It should be noted that the execution sequence of step 404 and step 403 may be performed simultaneously or may be exchanged, and this is not limited in the embodiment of the present application.
Step 405, obtain the resource transfer record of the second resource management system.
The resource transfer record is a record of transferring a first type of resource from a first account to a second account, the first account is an account of a target user in a second resource management system, and the second account is an account of a server in the second resource management system.
That is, the service provider of the first resource management system registers a second account in the second resource management system, and can receive the resource transferred by the target user through the first account. For example, when the second resource management system is the union pay system, the facilitator of the first resource management system may register a bank account in the union pay system, and the target user may transfer money in the bank account to the bank account registered by the facilitator of the first resource management system.
In a possible implementation manner, the server of the first resource management system may send a request for obtaining the resource transfer record of the second account to a server corresponding to the second account in the second resource management system, and correspondingly, after receiving the request, the server of the second account may return the resource transfer record of the second account to the server of the first resource management system. When the second account is a bank account registered by the facilitator of the first resource management system, the resource transfer record may be a transfer-in record of the bank account. In a possible implementation manner, when the server corresponding to the second account in the second resource management system receives the resource transfer, the server may also actively send the record of the resource transfer to the server of the first resource management system, so that the server of the first resource management system obtains the transfer record of the second account.
Step 406, extracting remark information from the resource transfer record.
The remark information is information filled in a resource transfer triggering interface by a target user, and the resource transfer triggering interface is an interface for triggering a first account to transfer a first type of resource to a second account.
When the second resource management system records the resource transfer condition of the second account, the second resource management system can also record information filled in the resource transfer interface by the target user at the same time. Optionally, when the target user shows the resource transfer triggering interface through the terminal, the user may fill in the first account information, the second account information, the remark information, and the like in the resource transfer interface, so as to request for transferring the resource from the first account to the second account. Optionally, the step 202 may be referred to for the description of the resource transfer triggering interface here, and details are not described here. Optionally, when the second system resource management system is a unionpay system, the resource transfer interface may be an interface of a target user when an electronic transfer bill is filled in by a bank APP, or may be an interface of a bank storefront when a paper transfer bill is filled in, and a bank terminal enters transfer bill data filled by the user.
The server of the first resource management system extracts the remark information from the acquired resource transfer record, that is, the server of the first resource management system acquires information filled in the resource transfer trigger interface by the target user, for example, the target user fills information such as name, gender, home address, mobile phone number, first account, second account, third account, resource type, user number, and verification code in the resource transfer interface, and accordingly, the server of the first resource management system can acquire the remark information.
Step 407, extracting the first user number and the first verification code from the remark information.
The server of the first resource management system may continue to acquire the first user number and the first verification code from the extracted remark information. The server of the first resource management system may use the user number and the verification code in the acquired remark information as the first user number and the first verification code acquired this time, respectively.
In a possible implementation manner, after the server of the first resource management system extracts the first user number and the first verification code from the remark information, the server of the first resource management system may further query a bound account corresponding to the first user number, where the bound account is an account bound with the user number in the server and registered in the second resource management system. That is, the server of the first resource management system may query the binding account corresponding to the first user number from the binding result record table. Optionally, the server of the first resource management system may query the binding result record table according to the first user number, and when a user number that is the same as the first user number is found, obtain the binding account corresponding to the user number.
For example, this time, the server of the first resource management system extracts the first user number 100001 from the remark information, the binding result record table stored by the server of the first resource management system itself is as shown in table 2 above, and the server of the first resource management system may query the user number identical to the first user number from table 2, so as to query two binding accounts, namely 621 × 456 and 142 × 471, according to the user number in table 2.
And when the first account exists in the bound account, determining that the binding relationship between the user number and the first account exists in the server. That is, when the server of the first resource management system has the queried binding account from the first account acquired from the resource transfer record, the server of the first resource management system may determine that the server of the first resource management system has the binding relationship between the first user number and the first account. For example, when the first account obtained by the server of the first resource management system from the resource transfer record is 142 × 471, the first account exists in the set of bound accounts, and at this time, the server of the first resource management system may determine that a binding relationship between 100001 (the first user number) and 142 × 471 (the first account) exists.
In a possible implementation manner, after the server of the first resource management system extracts the first user number and the first verification code from the remark information, the server of the first resource management system may further query a target reservation record in the server, where the target reservation record includes a corresponding relationship between the second verification code and the second user number; the first user number is consistent with the second user number, and the first verification code is consistent with the second verification code. That is, the server of the first resource management system may also query the target reservation record, which may be each reservation record in the target reservation record table, from the target reservation record table.
In a possible implementation manner, the server of the first resource management system may query the first reservation record according to the first verification code, where the first reservation record includes a correspondence between the first verification code and the second user number; and when the first user number is consistent with the second user number, determining that the target reservation record is inquired.
For example, the server of the first resource management system uses the first verification code extracted from the remark information as a query condition, queries a target reservation record identical to the first verification code from a target reservation record table stored in the server, and when a second verification code identical to the first verification code is queried, marks the reservation record of the item corresponding to the second verification code as the first reservation record, wherein in the first reservation record, the user number corresponding to the first verification code is the second user number. For example, when the first verification code obtained by the server is 20190101000002, and the server queries that the second verification code corresponding to the 2 nd entry reservation record in table 4 is the same as the first verification code, the server may use the 2 nd entry reservation record as the first reservation record.
The server may obtain a second user number in the first reservation record, and determine that the target reservation record is queried when the first user number is consistent with the second user number. For example, when the second user number acquired by the server of the first resource management system from the first reservation record is 100001, if the first user number acquired by the server of the first resource management system is also 100001, the server may determine that the target reservation record is currently queried.
In a possible implementation manner, the server of the first resource management system may also query a second reservation record according to the first user number, where the second reservation record includes a correspondence between the first user number and the second verification code; and when the first verification code is consistent with the second verification code, determining that the target reservation record is inquired.
For example, the server of the first resource management system uses the first user number extracted from the remark information as a query condition, queries a target reservation record identical to the first user number from a target reservation record table stored in the server, and when a second user number identical to the first user number is queried, marks the reservation record as a second reservation record corresponding to the second user number, wherein in the second reservation record, the verification code corresponding to the first user number is the second verification code. For example, when the first user number acquired by the server is 100002, if the server queries that the second user number corresponding to the 3 rd entry reservation record in table 4 is the same as the first user number, the server may use the 3 rd entry reservation record as the second reservation record.
The server may obtain a second verification code in the second reservation record, and determine that the target reservation record is queried when the first verification code is consistent with the second verification code. For example, when the second verification code obtained by the server of the first resource management system from the second reservation record is 20190101000003, if the first verification code obtained by the server of the first resource management system is also 20190101000003, the server may determine that the target reservation record is currently queried.
When the target reservation record is inquired, determining that the corresponding relation between the first user number and the first verification code exists in the server. That is, when the server of the first resource management system queries the second target reservation record according to the first user number, or queries the first target reservation record according to the first verification code, the server may determine that the server itself stores the corresponding relationship between the first user number and the first verification code. For example, when the first user number extracted from the remark information by the server of the first resource management system is 100002 and the first verification code is 20190101000003, the server of the first resource management system may acquire the target reservation record in table 4 according to the above manner, and at this time, the server of the first resource management system may determine that a binding relationship between 100002 (the first user number) and 20190101000003 (the first verification code) exists itself.
Step 408, when the binding relationship between the first user number and the first account exists in the server, and the corresponding relationship between the first user number and the first verification code exists in the server, updating the second-type resource in the third account.
And the third account is the account corresponding to the user number and registered in the first resource management system.
Optionally, in step 407, the server may determine that the binding relationship between the first user number and the first account exists in the server, and the server has a corresponding relationship between the first user number and the first verification code, at this time, the second type resource may be updated in the third account.
In one possible implementation, the second type of resource may be the same as the first type of resource. For example, the server of the first resource management system is a server of the payment mechanism a, and the server may open an internal payment account for the target user corresponding to a third account registered by the target user, where the resource type of the internal payment account may be rmb, dollar, euro, yen, and the like, and when the target user transfers a certain amount of first type resources (100 rmb) from the first account to the second account through the above steps, when the server determines that the server itself has a binding relationship between the first user number and the first account and a corresponding relationship between the first user number and the first verification code, the server may update the 100 rmb into the third account.
In one possible implementation, the second type of resource may be different from the first type of resource. For example, the server of the first resource management system is a server of a game facilitator, and corresponds to a third account registered by a target user, the server may open an internal resource account for the target user, where the resource type of the internal resource account may be a virtual gold coin such as a game coin and a gold ingot, and when the target user transfers a certain number of first type resources (100 rmb) from the first account to the second account through the above steps, the server may also update 100 game coins and the like to the third account when determining that the server itself has a binding relationship between the first user number and the first account and a corresponding relationship between the first user number and the first verification code.
Optionally, the server of the first resource management system records various types of resources of the third account in advance, that is, the server of the first resource management system may create an account resource table corresponding to the third account, and store the account resource table in the first resource management system. Optionally, when the server of the first resource management system creates the account resource table of the third account, the server of the first resource management system may be created according to each piece of information shown in table 5.
Figure BDA0002152975560000231
Figure BDA0002152975560000241
TABLE 5
As can be seen from table 5, when the server in the first resource management system creates the account resource table of the third account, the server may establish a corresponding relationship between the user number of the third account and the resource type and the resource quantity, and create the account resource table of the third account according to the established corresponding relationship. Please refer to table 6, which shows an account resource table according to an embodiment of the present application.
Uid Currency Balance
100001 RMB (RMB) 123.00
100001 Dollar 100.00
100001 Euro Yuan 100.00
100002 Japanese yuan 12.00
TABLE 6
As can be seen from table 6, the server of the first resource management system may obtain a plurality of account resource records corresponding to each third account. Optionally, when the target user needs to view a single account resource record of the third account based on currency (for example, item 1 of table 6 above), the second APP may expose a corresponding resource. When the target user needs to view a plurality of account resource records of the third account based on currency (for example, the 1 st to 3 rd entries in table 6 above), the second APP may display the plurality of account resource records corresponding to the third account.
And step 409, transferring the target reservation record into a transfer record of the third account.
After the server of the first resource management system updates the resource of the third account, the server of the first resource management system may also forward the corresponding target reservation record to a recharge record of the third party account. When the target user queries the resource of the third account through the query interface, the resource of the third account and the transfer record can be displayed in the terminal interface.
Referring to fig. 10, an interface schematic diagram of a query interface according to an embodiment of the present application is shown, and as shown in fig. 10, a query interface 1000 includes a third account resource display box 1001 and a query transfer record control 1002. The target user may click on the query transfer record control 1002 to see the resource transfer record for the third account. Please refer to fig. 11, which illustrates a transfer record interface diagram according to an embodiment of the present application related to fig. 10. As shown in fig. 11, each transfer record 1101 is included in an interface 1100. The target user can know the resource surplus and the updating condition of the third account by looking at the transfer record shown in fig. 11.
Optionally, after the server of the first resource management system updates the resource of the third account, the server may further update a target reservation recording table stored inside. For example, please refer to table 7, which shows a target reservation recording table related to fig. 4 according to an embodiment of the present application.
Uid Recharge_code Status
100001 20190101000001 Unfinished
100001 20190101000002 Has been completed
100002 20190101000003 Unfinished
TABLE 7
As shown in table 5, when the server completes updating the resource of a third account, the server may further adjust the result status included in the corresponding target reservation record in the target reservation record table from the incomplete status to the completed status. Optionally, when the server transfers the target reservation record to the transfer record of the third account, the server may obtain the target reservation record of the third account updated in the table 7, and generate a corresponding transfer record according to the target reservation record.
Optionally, when the second resource management system is a unionpay system, the resource transfer record is a bank transaction flow of transferring the first account number to the second account number. For example, after the first account number transfers to the second account number, the collection transaction generated by the second account number is running.
To sum up, when the server of the first resource management system acquires the resource transfer record of the second resource management system, the remark information is extracted from the resource transfer record, and the first user number and the first verification code are extracted from the remark information; and updating the second type resource in the third account when the binding relationship between the first user number and the first account exists in the server of the first resource management system and the corresponding relationship between the first user number and the first verification code exists in the server of the first resource management system. According to the method and the device, whether the corresponding relation exists or not can be judged from the server by extracting the first user number and the first verification code in the remark information in the resource transfer record, so that whether the second type resource in the third account can be updated or not is determined, whether the second type resource in the third account can be updated or not is judged through the corresponding relation of the first user number and the first verification code, information needing to be checked when the account resource is updated by the server is added, and the safety of account resource updating is improved.
In a possible implementation manner, in response to the first-type resource including at least two sub-types of resources, the target reservation record may further include resource information of the first-type resource reserved for transfer; wherein the resource information includes at least one of a number of the first type of resource and a subtype of the first type of resource.
For example, the first type of resource type includes RMB, USD, and Japanese, and the server may add a subtype of the first type of resource in Table 4 when establishing Table 4. Please refer to table 8, which shows a target reservation recording table according to an embodiment of the present application.
Uid Currency Recharge_code Status
100001 RMB (RMB) 20190101000001 Unfinished
100001 Dollar 20190101000002 Unfinished
100002 RMB (RMB) 20190101000003 Unfinished
TABLE 8
Optionally, when the server establishes the table 4, the number of the first type resources and the subtype of the first type resources included in the resource information may also be added to the table 4. Referring to table 9, a target reservation recording table according to an embodiment of the present application is shown.
Uid Currency Recharge_code Status Number of
100001 RMB (RMB) 20190101000001 Unfinished 80
100001 Dollar 20190101000002 Unfinished 100
100002 RMB (RMB) 20190101000003 Unfinished 200
TABLE 9
When the server of the first account or the server of the second account generates the resource transfer record of the own account, the resource information may be added to the resource transfer record. For example, the first account transfers 80-numbered resources of the first resource type to the second account, and the server of the second account may include resource information that the number is 80 and the resource type is the first resource type when generating the resource transfer record of the second account.
Optionally, the server of the first resource management system may further obtain resource information of the first type of resource transferred from the first account to the second account according to the resource transfer record. For example, if the resource information is that the resource type is a first resource type, and the resource quantity of the first resource type is 80, the server of the first resource management system may obtain the corresponding resource information. Before step 408, that is, before the second-type resource is updated in the third account, the server may further determine whether the resource information of the first-type resource matches the resource information of the first-type resource transferred from the first account to the second account, and when the resource information of the first-type resource reserved for transfer matches the resource information of the first-type resource transferred from the first account to the second account, execute the step of updating the second-type resource in the third account.
That is, in the embodiment of the present application, when the binding relationship between the first user number and the first account exists in the server, and the corresponding relationship between the first user number and the first verification code exists in the server, and when the resource information of the first type resource reserved for transfer matches the resource information of the first type resource transferred from the first account to the second account, the second type resource is updated in the third account.
For example, when the server of the first resource management system queries the 2 nd entry reservation record in the table 9 in the step 407, it is determined that the server has a corresponding relationship between the first user number and the first verification code, and also determines that the server has a binding relationship between the user number and the first account number, at this time, the server needs to determine whether the resource information of the first type resource acquired by the server is the same as the resource information of the corresponding 2 nd entry reservation record in the table 9. For example, at this time, the resource information of the first type resource acquired by the server is dollars (subtype of the first type resource), and 100 (number of the first type resource), which is the same as the resource information in the reservation record of item 2 in table 9, at this time, step 409 may be entered, and if the resource information of the first type resource acquired by the server is renminbi (subtype of the first type resource), and 100 (number of the first type resource), at this time, the server finds that the resource information of the first type resource acquired by itself does not match the resource information of the first type resource transferred from the first account to the second account, an error message may be fed back to the target user through the third account, and the target user is prompted.
Taking the first account and the second account as bank accounts in the union pay system, the bank of the first account is bank a, and the bank of the second account is bank B as an example, please refer to fig. 12, which shows a flow sequence diagram of offline recharging provided in the embodiment of the present application. As shown in fig. 12, the system includes a user information management module 1201, a top-up code management module 1202, a pipelining information analysis module 1203, a top-up verification module 1204, an account resource management module 1205, a bank a server 1206, and a bank B server 1207.
The user information management module 1201, the recharge code management module 1202, the pipeline information analysis module 1203, the recharge verification module 1204, and the account resource management module 1205 are all modules in the server of the first resource management system.
The target user may send a request for binding the bank account to the user information management module through the terminal, that is, request for binding a binding relationship between the first account and the third account from the server of the first resource management system, and establish the binding table as shown in fig. 2, where the bank account is equivalent to the first account. Optionally, the user information management module binds the bank account and the third account in the system, and generates a binding table shown in table 2.
When a user initiates a recharging request to the server of the first resource management system through the terminal, the recharging code management module in the server of the first resource management system generates a recharging code, and establishes a target reservation record table (corresponding to the descriptions of generating the second verification code and establishing the target reservation record in the above steps 402 and 403) as shown in the above table 4, table 8 or table 9 for the third account and the generated verification code of the user in the server. The server of the first resource management system may also return the generated top-up code to the target user (corresponding to the description in step 404 above). The sequence step of returning the rechargeable code and the sequence step of recording the rechargeable code shown in fig. 12 may be exchanged with each other or performed simultaneously, which is not limited in the embodiments of the present application.
When a target user transfers from a first account to a second account, the user can send a transfer request to a bank A server, fill a transaction appendix (including a user number and a recharge code) in the transfer request, send the transfer request to the bank A server, and the bank A server executes transfer to a bank B server according to the transfer request, so that the transfer process from the first account to the second account is completed. Correspondingly, the bank B server can also generate the running information of the second account according to the transfer. The bank B server can also send the pipelining information to the pipelining analysis module.
When receiving the flow information of the second account sent by the bank B server, the flow analysis module may analyze the flow information of the second account, obtain verification information such as the user number, the first account, the recharge code, and the like, send the verification information to the recharge verification module, and the recharge verification module verifies the verification information. Which comprises the following steps: the recharge check module determines whether the user number and the transfer bank account number are correct or not by inquiring the stored user number and the transfer bank account number (corresponding to the determination of the binding relationship between the user number and the first account number in the step 407) from the user information module, namely determining whether the binding relationship exists between the user number and the transfer bank account number or not; the recharge check module can also query the recharge code management module for the stored recharge code (corresponding to the correspondence between the user number and the recharge code determined in step 407 above), and determine whether the recharge code is correct, i.e., determine whether there is a correspondence between the user number and the recharge code.
When the recharging verification module passes the verification, a recharging request can be sent to the account resource management module, and the account resource management module updates the account resource of the third account according to the recharging request.
Referring to fig. 13, a system architecture diagram of a first resource management system according to an embodiment of the present application is shown. As shown in fig. 13, the system includes a user information management module 1301, a top-up code management module 1302, a pipeline analysis module 1303, a top-up verification module 1304, an account resource management module 1305, a file server 1306, a user information database 1307, and an account resource database 1308.
The user information module may be configured to manage a third account of the user, and has the following main functions:
the user information module may establish a binding relationship between the third account and the first account. Namely, the third account is bound with the recharging bank account (the first account) of the target user in the first resource management system.
The user information module may query a recharge bank account (third account) bound by the user. Optionally, the user information module may query bank account information (third account) bound by the target user according to the user number as a query condition.
The user information module may also change the user bound top-up bank account (third account). That is, when the target user needs to change the recharging bank account, the bound recharging account can be changed through the user information module, for example, the bound recharging bank account is added, and the bound recharging bank account is deleted.
The main functions of the recharge code management module are as follows:
the recharge code management module can generate and record the recharge code. Wherein, corresponding to each user, each recharging can generate different recharging codes.
The charge code management module can query the charge code. Optionally, the recharge code management module may query and confirm whether a certain recharge code exists according to the input certain recharge code.
The recharge code management module can modify the result state corresponding to the recharge code. That is, the recharge code management module can modify the result state of recording the recharge code.
The main functions of the pipeline analysis module are as follows:
the pipeline analysis module can acquire the pipeline information of the second account and analyze the pipeline information of the second account. Optionally, the format of the pipelining information of the second account obtained by the pipelining analysis module may be a file format agreed between a service provider of the first resource management system and a bank service provider of the second account, for example, the file format of the pipelining information may be an xml (Extensible Markup Language) format or an excel table.
The recharging verification module is responsible for verifying verification information analyzed by the recharging code management module from the flow information of the second account, and has the following main functions:
the recharge verification module can verify the user number. Optionally, the recharge check module performs query check by calling a user query interface of the user information management module.
The recharging verification module can verify the recharging bank account number bound by the user. Optionally, the recharge check module performs the query check by calling a user card binding query interface of the user information management module.
The recharge check module can check the recharge code. Optionally, the recharge check module performs query and check by calling a recharge code query interface of the recharge code management module.
Please refer to fig. 14, which illustrates a schematic flow chart of a verification process of a recharge verification module according to an embodiment of the present application. As shown in fig. 14, the process may include the following steps.
And 1401, reading the check information analyzed by the pipeline analysis module.
Optionally, the recharge and check module may send an acquisition request to the pipeline analysis module, so as to request the pipeline analysis module for check information; or, the running water analysis module can also actively send the verification information obtained by analysis to the recharge verification module. The verification information can comprise a user number, a first account number, a charging code, currency and amount limit.
Step 1402, verify the user number.
The inquiry check is performed by calling the user inquiry interface of the user information management module, if the user number is inquired (i.e. passing the check), step 1403 is entered, otherwise step 1407 is entered.
Step 1403, the first account number is checked.
And performing query and verification by calling a user card binding query interface of the user information management module, and if the first account is queried (namely, the first account passes the verification), entering a step 1404, otherwise, entering a step 1407. Optionally, in this step, reference may be made to part of the description in step 407, that is, the binding relationship between the first account and the user number may be checked, which is not described herein again.
At step 1404, the rechargeable code is verified.
And (4) inquiring and checking by calling a recharging code inquiring interface of the recharging code management module, if the recharging code is inquired (namely, the checking is passed), entering the step 1405, and otherwise, entering the step 1407. Optionally, this step may also refer to the partial description in step 407, that is, the corresponding relationship between the rechargeable code and the user number may be checked, which is not described herein again.
Step 1405, checking currency.
Optionally, the recharge verification module may also call a recharge code query interface of the recharge code management module to perform query and verification, if the currency is queried (i.e. verified), step 1406 is performed, otherwise step 1407 is performed. Optionally, this step may check whether the currency is the same as the currency corresponding to the target reservation record with the same user number or the same recharge code in the target reservation record table.
Step 1406, verify the amount of money.
Optionally, the recharge verification module may also call a recharge code query interface of the recharge code management module to perform query and verification, if the amount limit is queried (i.e. passing the verification), step 1406 is performed, otherwise step 1407 is performed. Optionally, the step may check whether the amount of money is the same as the amount of money corresponding to the target reservation record with the same user number or the same rechargeable code in the target reservation record table.
Step 1407, record the exception.
That is, when the read verification information fails the above verification, recording is performed in the server.
It should be noted that the checking sequence from step 1402 to step 1406 may also be adjusted, which is not limited in the embodiment of the present application.
The account resource management module has the following main functions:
the account resource management module can create account resources for a third account; the account resource management module can inquire account resources for a third account; the account resource management module may update account resources for the third account.
Optionally, the user information database and the account resource database may both adopt an open source database MySQL, or an Oracle DB database or an SQL Server database, and the type of the database is not limited in the embodiment of the present application.
The file server may be configured to store a pipelining file sent by a bank of the second account, and may also be configured to store a pipelining file generated by the first resource management system of the file server for the third account. Optionally, the File server may adopt an FTP (File Transfer Protocol) or an SFTP (Secure File Transfer Protocol) File server, or another File server or storage server capable of meeting the requirement of storing the streaming File.
In summary, the application can judge whether the corresponding relationship of each information exists in the server by extracting each information in the remark information in the resource transfer record, so as to determine whether the second type resource in the third account can be updated, increase the information that needs to be checked when the server updates the account resource, and improve the security of the account resource update.
The following are embodiments of the apparatus of the present application that may be used to perform embodiments of the method of the present application. For details which are not disclosed in the embodiments of the apparatus of the present application, reference is made to the embodiments of the method of the present application.
Fig. 15 is a block diagram illustrating a structure of an account resource updating apparatus according to an exemplary embodiment of the present application. The account resource updating apparatus may be used in a server to perform all or part of the steps performed by the server in the method shown in the corresponding embodiment of fig. 2 or fig. 4, and the account resource updating apparatus may include:
a transfer record obtaining module 1501, configured to obtain a resource transfer record of a second resource management system, where the resource transfer record is a record of transferring a first type of resource from a first account to a second account, the first account is an account of a target user in the second resource management system, and the second account is an account of a server in the second resource management system;
a first information extraction module 1502, configured to extract remark information from the resource transfer record, where the remark information is information that the target user fills in a resource transfer trigger interface, and the resource transfer trigger interface is an interface that triggers the first account to transfer the first type of resource to the second account;
a second information extraction module 1503, configured to extract a first user number and a first verification code from the remark information;
an account resource updating module 1504, configured to update a second type resource in a third account when a binding relationship between the first user number and the first account exists in the server, and a corresponding relationship between the first user number and the first verification code exists in the server; the third account is an account corresponding to the first user number and registered in the first resource management system.
Optionally, the apparatus further comprises: a binding account inquiry module and a binding relation determination module;
the bound account querying module is configured to query a bound account corresponding to the first user number before the account resource updating module 1504 updates the second type resource in a third account, where the bound account is an account bound to the first user number in the server and registered in the second resource management system;
and the binding relationship determining module is used for determining that the binding relationship between the user number and the first account exists in the server when the first account exists in the binding accounts.
Optionally, the apparatus further comprises: a reservation recording query module and a corresponding relation determining module;
the reservation record querying module is configured to query a target reservation record in the server before the account resource updating module 1504 updates the second type of resource in a third account, where the target reservation record includes a correspondence between a second verification code and a second user number; the first user number is consistent with the second user number, and the first verification code is consistent with the second verification code;
and the corresponding relation determining module is used for determining that the corresponding relation between the first user number and the first verification code exists in the server when the target reservation record is inquired.
The reservation recording query module comprises: a first record query unit and a first record determination unit;
the first record inquiry unit is used for inquiring a first reservation record according to the first verification code, wherein the first reservation record comprises the corresponding relation between the first verification code and the second user number;
the first record determining unit is configured to determine that the target reservation record is queried when the first user number is consistent with the second user number.
The reservation recording query module comprises: a second record query unit and a second record determination unit;
the second record inquiry unit is used for inquiring a second reservation record according to the first user number, wherein the second reservation record comprises the corresponding relation between the first user number and the second verification code;
the second record determining unit is configured to determine that the target reservation record is queried when the first verification code is consistent with the second verification code.
Optionally, the apparatus further comprises: the system comprises a reservation interface sending module, a verification code generating module, a reservation record establishing module and a verification code sending module;
the reservation interface sending module is configured to send a reservation interface to a user terminal corresponding to the third account before the transfer record obtaining module 1501 obtains the resource transfer record of the second resource management system, where the reservation interface includes a reservation control;
the verification code generation module is used for generating the second verification code when receiving a reservation request; the reservation request is a request sent by the user terminal when the user terminal detects the triggering operation of the reservation control;
the reservation record establishing module is used for establishing the target reservation record according to the second verification code;
and the verification code sending module is used for sending the second verification code to the user terminal.
Optionally, the verification code sending module includes: a first transmitting unit or a second transmitting unit;
the first sending unit is used for sending the second verification code to the reservation interface;
the second sending unit is configured to send the second verification code to the user terminal in a message format outside the reserved interface, where the message format outside the reserved interface includes a short message or an instant messaging message.
Optionally, the verification code generating module includes: a first generation unit or a second generation unit;
the first generating unit is used for randomly generating the second verification code when receiving a reservation request;
and the second generating unit is used for generating the second verification code according to a preset coding rule when a reservation request is received.
Optionally, the reservation interface further includes a verification code input box, and the reservation request includes a verification code input by the user in the verification code input box;
the verification code generation module is configured to obtain the verification code included in the reservation request as the second verification code.
Optionally, the first type of resource includes at least two subtypes of resources; the target reservation record also comprises resource information of the first type of resource reserved and transferred; the resource information includes at least one of a number of the first type of resource and a subtype of the first type of resource;
the device further comprises: a resource information acquisition module;
the resource information obtaining module is configured to obtain resource information of a first type of resource transferred from the first account to the second account according to the resource transfer record before the account resource updating module 1504 updates a second type of resource in a third account;
the account resource updating module 1504 is further configured to execute the step of updating the second type resource in the third account when the resource information of the first type resource reserved for transfer matches the resource information of the first type resource transferred from the first account to the second account.
Optionally, the apparatus further comprises: a recharge record unloading module;
the recharge record unloading module is configured to unload the target reservation record into the recharge record of the third account after the account resource updating module 1504 updates the second type of resource in the third account.
Optionally, the second resource management system is a banking system, and the resource transfer record is a bank transaction flow of the transfer from the first account to the second account.
To sum up, when the server of the first resource management system acquires the resource transfer record of the second resource management system, the remark information is extracted from the resource transfer record, and the first user number and the first verification code are extracted from the remark information; and updating the second type resource in the third account when the binding relationship between the first user number and the first account exists in the server of the first resource management system and the corresponding relationship between the first user number and the first verification code exists in the server of the first resource management system. According to the method and the device, whether the corresponding relation exists or not can be judged from the server by extracting the first user number and the first verification code in the remark information in the resource transfer record, so that whether the second type resource in the third account can be updated or not is determined, whether the second type resource in the third account can be updated or not is judged through the corresponding relation of the first user number and the first verification code, information needing to be checked when the account resource is updated by the server is added, and the safety of account resource updating is improved.
It should be noted that: in the device provided in the above embodiment, when updating the account resource, only the division of the above functional modules is illustrated, and in practical applications, the above function allocation may be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the above described functions. In addition, the device provided by the above embodiment and the method embodiment of the account resource updating method belong to the same concept, and specific implementation processes thereof are detailed in the method embodiment and are not described herein again.
Fig. 16 is a block diagram illustrating a structure of a computer device 1600 according to an exemplary embodiment of the present application. The computer device 1600 may be a user terminal, such as a smart phone, a tablet computer, an MP3 player (Moving Picture experts Group Audio Layer III, motion video experts compression standard Audio Layer 3), an MP4 player (Moving Picture experts Group Audio Layer IV, motion video experts compression standard Audio Layer 4), a laptop computer, or a desktop computer. Computer device 1600 may also be referred to by other names such as user equipment, portable terminals, laptop terminals, desktop terminals, etc.
Generally, computer device 1600 includes: a processor 1601, and a memory 1602.
Processor 1601 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and so on. The processor 1601 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). Processor 1601 may also include a main processor and a coprocessor, where the main processor is a processor for processing data in an awake state, and is also referred to as a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 1601 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content that the display screen needs to display. In some embodiments, the processor 1601 may further include an AI (Artificial Intelligence) processor for processing computing operations related to machine learning.
Memory 1602 may include one or more computer-readable storage media, which may be non-transitory. The memory 1602 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in the memory 1602 is used to store at least one instruction for execution by the processor 1601 to implement the account resource updating method provided by the method embodiments of the present application.
In some embodiments, computer device 1600 may also optionally include: peripheral interface 1603 and at least one peripheral. Processor 1601, memory 1602 and peripheral interface 1603 may be connected by buses or signal lines. Various peripheral devices may be connected to peripheral interface 1603 via buses, signal lines, or circuit boards. Specifically, the peripheral device includes: at least one of a radio frequency circuit 1604, a touch screen display 1605, a camera 1606, audio circuitry 1607, a positioning component 1608, and a power supply 1609.
Peripheral interface 1603 can be used to connect at least one I/O (Input/Output) related peripheral to processor 1601 and memory 1602. In some embodiments, processor 1601, memory 1602, and peripheral interface 1603 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 1601, the memory 1602 and the peripheral device interface 1603 may be implemented on a separate chip or circuit board, which is not limited by this embodiment.
The Radio Frequency circuit 1604 is used for receiving and transmitting RF (Radio Frequency) signals, also called electromagnetic signals. The radio frequency circuitry 1604 communicates with communication networks and other communication devices via electromagnetic signals. The rf circuit 1604 converts the electrical signal into an electromagnetic signal to be transmitted, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 1604 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a subscriber identity module card, and so forth. The radio frequency circuit 1604 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocols include, but are not limited to: the world wide web, metropolitan area networks, intranets, generations of mobile communication networks (2G, 3G, 4G, and 5G), Wireless local area networks, and/or WiFi (Wireless Fidelity) networks. In some embodiments, the rf circuit 1604 may also include NFC (Near Field Communication) related circuits, which are not limited in this application.
The display 1605 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When the display screen 1605 is a touch display screen, the display screen 1605 also has the ability to capture touch signals on or over the surface of the display screen 1605. The touch signal may be input to the processor 1601 as a control signal for processing. At this point, the display 1605 may also be used to provide virtual buttons and/or a virtual keyboard, also referred to as soft buttons and/or a soft keyboard. In some embodiments, the display 1605 may be one, providing the front panel of the computer device 1600; in other embodiments, the display screens 1605 can be at least two, each disposed on a different surface of the computer device 1600 or in a folded design; in still other embodiments, the display 1605 may be a flexible display disposed on a curved surface or on a folding surface of the computer device 1600. Even further, the display 1605 may be arranged in a non-rectangular irregular pattern, i.e., a shaped screen. The Display 1605 may be made of LCD (Liquid Crystal Display), OLED (organic light-Emitting Diode), or other materials.
The camera assembly 1606 is used to capture images or video. Optionally, camera assembly 1606 includes a front camera and a rear camera. Generally, a front camera is disposed at a front panel of the terminal, and a rear camera is disposed at a rear surface of the terminal. In some embodiments, the number of the rear cameras is at least two, and each rear camera is any one of a main camera, a depth-of-field camera, a wide-angle camera and a telephoto camera, so that the main camera and the depth-of-field camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize panoramic shooting and VR (Virtual Reality) shooting functions or other fusion shooting functions. In some embodiments, camera assembly 1606 can also include a flash. The flash lamp can be a monochrome temperature flash lamp or a bicolor temperature flash lamp. The double-color-temperature flash lamp is a combination of a warm-light flash lamp and a cold-light flash lamp, and can be used for light compensation at different color temperatures.
The audio circuitry 1607 may include a microphone and a speaker. The microphone is used for collecting sound waves of a user and the environment, converting the sound waves into electric signals, and inputting the electric signals to the processor 1601 for processing or inputting the electric signals to the radio frequency circuit 1604 to achieve voice communication. For stereo capture or noise reduction purposes, the microphones may be multiple and located at different locations on the computer device 1600. The microphone may also be an array microphone or an omni-directional pick-up microphone. The speaker is used to convert electrical signals from the processor 1601 or the radio frequency circuit 1604 into sound waves. The loudspeaker can be a traditional film loudspeaker or a piezoelectric ceramic loudspeaker. When the speaker is a piezoelectric ceramic speaker, the speaker can be used for purposes such as converting an electric signal into a sound wave audible to a human being, or converting an electric signal into a sound wave inaudible to a human being to measure a distance. In some embodiments, the audio circuit 1607 may also include a headphone jack.
The Location component 1608 is employed to locate a current geographic Location of the computer device 1600 for purposes of navigation or LBS (Location Based Service). The Positioning component 1608 may be a Positioning component based on the Global Positioning System (GPS) in the united states, the beidou System in china, the Global Navigation Satellite System (GLONASS) in russia, or the galileo System in europe.
Power supply 1609 is used to power the various components within computer device 1600. Power supply 1609 may be alternating current, direct current, disposable or rechargeable. When power supply 1609 includes a rechargeable battery, the rechargeable battery may be a wired rechargeable battery or a wireless rechargeable battery. The wired rechargeable battery is a battery charged through a wired line, and the wireless rechargeable battery is a battery charged through a wireless coil. The rechargeable battery may also be used to support fast charge technology.
In some embodiments, computer device 1600 also includes one or more sensors 1610. The one or more sensors 1610 include, but are not limited to: acceleration sensor 1611, gyro sensor 1612, pressure sensor 1613, fingerprint sensor 1614, optical sensor 1615, and proximity sensor 1616.
The acceleration sensor 1611 may detect acceleration magnitudes on three coordinate axes of a coordinate system established with the computer apparatus 1600. For example, the acceleration sensor 1611 may be used to detect components of the gravitational acceleration in three coordinate axes. The processor 1601 may control the touch display screen 1605 to display the user interface in a landscape view or a portrait view according to the gravitational acceleration signal collected by the acceleration sensor 1611. The acceleration sensor 1611 may also be used for acquisition of motion data of a game or a user.
Gyroscope sensor 1612 can detect the organism direction and turned angle of computer device 1600, and gyroscope sensor 1612 can gather user's 3D action to computer device 1600 in coordination with acceleration sensor 1611. From the data collected by the gyro sensor 1612, the processor 1601 may perform the following functions: motion sensing (such as changing the UI according to a user's tilting operation), image stabilization at the time of photographing, game control, and inertial navigation.
The pressure sensors 1613 may be disposed on the side bezel of the computer device 1600 and/or on the lower layer of the touch display 1605. When the pressure sensor 1613 is disposed on the side frame of the computer device 1600, the holding signal of the user to the computer device 1600 can be detected, and the processor 1601 performs left-right hand recognition or shortcut operation according to the holding signal collected by the pressure sensor 1613. When the pressure sensor 1613 is disposed at the lower layer of the touch display 1605, the processor 1601 controls the operability control on the UI interface according to the pressure operation of the user on the touch display 1605. The operability control comprises at least one of a button control, a scroll bar control, an icon control and a menu control.
The fingerprint sensor 1614 is configured to collect a fingerprint of the user, and the processor 1601 is configured to identify the user based on the fingerprint collected by the fingerprint sensor 1614, or the fingerprint sensor 1614 is configured to identify the user based on the collected fingerprint. Upon recognizing that the user's identity is a trusted identity, the processor 1601 authorizes the user to perform relevant sensitive operations including unlocking a screen, viewing encrypted information, downloading software, paying for and changing settings, etc. The fingerprint sensor 1614 may be disposed on the front, back, or side of the computer device 1600. When a physical button or vendor Logo is provided on the computer device 1600, the fingerprint sensor 1614 may be integrated with the physical button or vendor Logo.
The optical sensor 1615 is used to collect ambient light intensity. In one embodiment, the processor 1601 may control the display brightness of the touch display screen 1605 based on the ambient light intensity collected by the optical sensor 1615. Specifically, when the ambient light intensity is high, the display brightness of the touch display screen 1605 is increased; when the ambient light intensity is low, the display brightness of the touch display 1605 is turned down. In another embodiment, the processor 1601 may also dynamically adjust the shooting parameters of the camera assembly 1606 based on the ambient light intensity collected by the optical sensor 1615.
A proximity sensor 1616, also known as a distance sensor, is typically disposed on the front panel of the computer device 1600. The proximity sensor 1616 is used to capture the distance between the user and the front of the computer device 1600. In one embodiment, the touch display 1605 is controlled by the processor 1601 to switch from a bright screen state to a dark screen state when the proximity sensor 1616 detects that the distance between the user and the front surface of the computer device 1600 is gradually decreasing; when the proximity sensor 1616 detects that the distance between the user and the front surface of the computer device 1600 is gradually increasing, the touch display 1605 is controlled by the processor 1601 to switch from a breath screen state to a light screen state.
Those skilled in the art will appreciate that the configuration shown in FIG. 16 is not intended to be limiting of computer device 1600, and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components may be employed.
Fig. 17 is a schematic structural diagram of a computer device provided in an exemplary embodiment of the present application, and the computer device 1700 may be the server 140 in fig. 1. The computer apparatus 1700 includes a Central Processing Unit (CPU)1701, a system memory 1704 including a Random Access Memory (RAM)1702 and a Read Only Memory (ROM)1703, and a system bus 1705 connecting the system memory 1704 and the central processing unit 1701. The computer device 1700 also includes a basic input/output system (I/O system) 1706 for facilitating the transfer of information between elements within the computer, and a mass storage device 1707 for storing an operating system 1713, application programs 1714, and other program modules 1715.
The basic input/output system 1706 includes a display 1708 for displaying information and an input device 1709 such as a mouse, keyboard, etc. for a user to input information. Wherein the display 1708 and the input device 1709 are connected to the central processing unit 1701 via an input-output controller 1710 connected to the system bus 1705. The basic input/output system 1706 may also include an input/output controller 1710 for receiving and processing input from a number of other devices, such as a keyboard, mouse, or electronic stylus. Similarly, the input-output controller 1710 may also provide output to a display screen, a printer, or other type of output device.
The mass storage device 1707 is connected to the central processing unit 1701 through a mass storage controller (not shown) connected to the system bus 1705. The mass storage device 1707 and its associated computer-readable media provide non-volatile storage for the computer device 1700. That is, the mass storage device 1707 may include a computer-readable medium (not shown), such as a hard disk or CD-ROM drive.
The computer readable media may include computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD-ROM, DVD, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices. Of course, those skilled in the art will appreciate that the computer storage media is not limited to the foregoing. The system memory 1704 and mass storage device 1707 described above may be collectively referred to as memory.
The computer device 1700 may connect to the internet or other network devices through the network interface unit 1711 connected to the system bus 1705.
The memory also includes one or more programs, which are stored in the memory, and the central processor 1701 implements all or part of the steps of the method shown in fig. 2 or 4 or 12 or 14 by executing the one or more programs.
In an exemplary embodiment, a non-transitory computer readable storage medium comprising instructions, such as a memory comprising computer programs (instructions), executable by a processor of a computer device to perform all or part of the steps of the methods shown in the various embodiments of the present application, is also provided. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims (15)

1. An account resource updating method, which is executed by a server of a first resource management system, includes:
acquiring a resource transfer record of a second resource management system, wherein the resource transfer record is a record of transferring a first type of resource from a first account to a second account, the first account is an account of a target user corresponding to the second resource management system, and the second account is an account of a server corresponding to the second resource management system;
extracting remark information from the resource transfer record, wherein the remark information is information filled in a resource transfer triggering interface by the target user, and the resource transfer triggering interface is an interface for triggering the first account to transfer the first type of resource to the second account;
extracting a first user number and a first verification code from the remark information;
when the binding relationship between the first user number and the first account exists in the server and the corresponding relationship between the first user number and the first verification code exists in the server, updating a second type resource in a third account; the third account is an account corresponding to the first user number and registered in the first resource management system.
2. The method of claim 1, wherein before updating the second type of resource in the third account, the method further comprises:
inquiring a binding account corresponding to the first user number, wherein the binding account is an account which is bound with the first user number in the server and is registered in the second resource management system;
and when the first account exists in the bound account, determining that a binding relationship between the first user number and the first account exists in the server.
3. The method of claim 1, wherein before updating the second type of resource in the third account, the method further comprises:
inquiring a target reservation record in the server, wherein the target reservation record comprises a corresponding relation between a second verification code and a second user number; the first user number is consistent with the second user number, and the first verification code is consistent with the second verification code;
and when the target reservation record is inquired, determining that the corresponding relation between the first user number and the first verification code exists in the server.
4. The method of claim 3, wherein querying the server for a target reservation record comprises:
inquiring a first reservation record according to the first verification code, wherein the first reservation record comprises the corresponding relation between the first verification code and the second user number;
and when the first user number is consistent with the second user number, determining to inquire the target reservation record.
5. The method of claim 3, wherein querying the server for a target reservation record comprises:
inquiring a second reservation record according to the first user number, wherein the second reservation record comprises the corresponding relation between the first user number and the second verification code;
and when the first verification code is consistent with the second verification code, determining that the target reservation record is inquired.
6. The method of claim 3, wherein before obtaining the resource transfer record of the second resource management system, further comprising:
sending a reservation interface to a user terminal corresponding to the third account, wherein the reservation interface comprises a reservation control;
when a reservation request is received, generating the second verification code; the reservation request is a request sent by the user terminal when the user terminal detects the triggering operation of the reservation control;
establishing the target reservation record according to the second verification code;
and sending the second verification code to the user terminal.
7. The method of claim 6, wherein the sending the second authentication code to the user terminal comprises:
sending the second verification code to the reservation interface;
alternatively, the first and second electrodes may be,
and sending the second verification code to the user terminal through a message form outside the reserved interface, wherein the message form outside the reserved interface comprises a short message or an instant messaging message.
8. The method of claim 6, wherein generating the second validation code upon receiving a reservation request comprises:
when a reservation request is received, randomly generating the second verification code;
alternatively, the first and second electrodes may be,
and when a reservation request is received, generating the second verification code according to a preset coding rule.
9. The method of claim 6, wherein the reservation interface further comprises a verification code input box, and the reservation request comprises a verification code input by the user in the verification code input box;
the generating the second verification code according to the reservation request includes:
and acquiring the verification code contained in the reservation request as the second verification code.
10. The method of claim 3, wherein the first type of resource comprises at least two subtypes of resources; the target reservation record also comprises resource information of the first type of resource reserved and transferred; the resource information includes at least one of a number of the first type of resource and a subtype of the first type of resource;
before the updating of the second type resource in the third account, the method further includes:
acquiring resource information of a first type of resource transferred from the first account to the second account according to the resource transfer record;
the updating of the second type of resource in the third account includes:
and when the resource information of the reserved and transferred first-type resources is matched with the resource information of the first-type resources transferred from the first account to the second account, executing the step of updating the second-type resources in the third account.
11. The method of claim 3, wherein after updating the second type resource in the third account, further comprising:
and transferring the target reservation record into a transfer record of the third account.
12. The method according to any one of claims 1 to 11,
the second resource management system is a banking system, and the resource transfer record is a bank transaction flow of the transfer of the first account number to the second account number.
13. An account resource updating apparatus, the apparatus being used in a server of a first resource management system, the apparatus comprising:
a transfer record obtaining module, configured to obtain a resource transfer record of a second resource management system, where the resource transfer record is a record of transferring a first type of resource from a first account to a second account, the first account is an account of a target user in the second resource management system, and the second account is an account of a server in the second resource management system;
a first information extraction module, configured to extract remark information from the resource transfer record, where the remark information is information that the target user fills in a resource transfer trigger interface, and the resource transfer trigger interface is an interface that triggers the first account to transfer the first type of resource to the second account;
the second information extraction module is used for extracting a first user number and a first verification code from the remark information;
an account resource updating module, configured to update a second type resource in a third account when a binding relationship between the first user number and the first account exists in the server and a corresponding relationship between the first user number and the first verification code exists in the server; the third account is an account corresponding to the first user number and registered in the first resource management system.
14. A computer device comprising a processor and a memory, the memory having stored therein at least one instruction, at least one program, a set of codes, or a set of instructions, the at least one instruction, the at least one program, the set of codes, or the set of instructions being loaded and executed by the processor to implement the account resource updating method according to any one of claims 1 to 12.
15. A computer readable storage medium having stored therein at least one instruction, at least one program, a set of codes, or a set of instructions, which is loaded and executed by a processor to implement an account resource updating method according to any one of claims 1 to 12.
CN201910708647.2A 2019-08-01 2019-08-01 Account resource updating method and device, computer equipment and storage medium Active CN111192036B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910708647.2A CN111192036B (en) 2019-08-01 2019-08-01 Account resource updating method and device, computer equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910708647.2A CN111192036B (en) 2019-08-01 2019-08-01 Account resource updating method and device, computer equipment and storage medium

Publications (2)

Publication Number Publication Date
CN111192036A true CN111192036A (en) 2020-05-22
CN111192036B CN111192036B (en) 2023-06-20

Family

ID=70708995

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910708647.2A Active CN111192036B (en) 2019-08-01 2019-08-01 Account resource updating method and device, computer equipment and storage medium

Country Status (1)

Country Link
CN (1) CN111192036B (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115116178A (en) * 2022-06-24 2022-09-27 四川海力智能科技股份有限公司 Recharging method of intelligent meter
CN115760459A (en) * 2022-11-22 2023-03-07 广西电网有限责任公司 Method for completing electric charge account cancellation for target number

Citations (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101799901A (en) * 2009-07-15 2010-08-11 姚学民 Method for rapidly registering account, recharging and landing
EP2226771A1 (en) * 2009-03-03 2010-09-08 Alexandre Sam Zormati Money transfer method by prepaid electronic voucher
WO2010130106A1 (en) * 2009-05-13 2010-11-18 Hou Wanchun Method for controlling payment or transfer by a user via a mobile telephone terminal
CN102609835A (en) * 2012-01-16 2012-07-25 中国联合网络通信集团有限公司 Recharging method, system and service platform of telecommunication payment card
CN102915499A (en) * 2011-08-03 2013-02-06 腾讯科技（深圳）有限公司 Method and system for virtual goods order comments
KR101288081B1 (en) * 2012-06-21 2013-07-19 주식회사 하나은행 Fund transfer system and user terminal
US20130262309A1 (en) * 2012-04-02 2013-10-03 Mpayme Ltd. Method and System for Secure Mobile Payment
CN103745349A (en) * 2013-03-01 2014-04-23 王新 Electronic consumer card system
WO2014206659A1 (en) * 2013-06-28 2014-12-31 Bundesdruckerei Gmbh Electronic transaction method and computer system
CN104753892A (en) * 2013-12-31 2015-07-01 腾讯科技（深圳）有限公司 Network resource transmission method, device and system
CN104899732A (en) * 2015-05-05 2015-09-09 深圳市元征科技股份有限公司 Information interaction method and device
CN105681282A (en) * 2015-12-29 2016-06-15 宇龙计算机通信科技(深圳)有限公司 Business numerical value transfer method and device
CN105825376A (en) * 2015-01-26 2016-08-03 国际商业机器公司 Method for processing resource account transaction and wireless electronic device
US20160239834A1 (en) * 2015-02-16 2016-08-18 Xiaomi Inc. Method and apparatus for requesting account transfer
US20160300201A1 (en) * 2013-12-31 2016-10-13 Tencent Technology (Shenzhen) Company Limited Method, device and system for performing transactions
CN106572095A (en) * 2016-11-01 2017-04-19 腾讯科技（深圳）有限公司 Account registration method, device and system
CN106845983A (en) * 2015-12-05 2017-06-13 昆明我行科技有限公司 A kind of hand set paying method using payment mark
CN106845955A (en) * 2017-01-18 2017-06-13 深圳市任网游科技发展有限公司 Internet bar's expenses of surfing in Internet automatic charging method and system
CN107239948A (en) * 2017-05-12 2017-10-10 腾讯科技（深圳）有限公司 Method and device for business processing, computer equipment and storage medium
CN107679844A (en) * 2017-09-30 2018-02-09 北京小米移动软件有限公司 The method, apparatus and storage medium of resource transfers
CN107730261A (en) * 2017-10-18 2018-02-23 维沃移动通信有限公司 A kind of resource transfers method and relevant device
CN108256839A (en) * 2017-07-28 2018-07-06 平安科技（深圳）有限公司 Numerical value resource backing method, device, server and storage medium
CN108322448A (en) * 2018-01-09 2018-07-24 财付通支付科技有限公司 Auth method, device, system, storage medium and computer equipment
CN108985729A (en) * 2018-06-29 2018-12-11 联动优势电子商务有限公司 A kind of method and device of account charging
CN109285000A (en) * 2018-08-13 2019-01-29 唐晓冬 A kind of campus self-help payment method and system
CN109802916A (en) * 2017-11-16 2019-05-24 财付通支付科技有限公司 Resource transfers method, system, server and computer readable storage medium
CN109801051A (en) * 2017-11-16 2019-05-24 财付通支付科技有限公司 Resource transfers method, system, server and computer readable storage medium

Patent Citations (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2226771A1 (en) * 2009-03-03 2010-09-08 Alexandre Sam Zormati Money transfer method by prepaid electronic voucher
WO2010130106A1 (en) * 2009-05-13 2010-11-18 Hou Wanchun Method for controlling payment or transfer by a user via a mobile telephone terminal
CN101799901A (en) * 2009-07-15 2010-08-11 姚学民 Method for rapidly registering account, recharging and landing
CN102915499A (en) * 2011-08-03 2013-02-06 腾讯科技（深圳）有限公司 Method and system for virtual goods order comments
CN102609835A (en) * 2012-01-16 2012-07-25 中国联合网络通信集团有限公司 Recharging method, system and service platform of telecommunication payment card
US20130262309A1 (en) * 2012-04-02 2013-10-03 Mpayme Ltd. Method and System for Secure Mobile Payment
KR101288081B1 (en) * 2012-06-21 2013-07-19 주식회사 하나은행 Fund transfer system and user terminal
CN103745349A (en) * 2013-03-01 2014-04-23 王新 Electronic consumer card system
WO2014206659A1 (en) * 2013-06-28 2014-12-31 Bundesdruckerei Gmbh Electronic transaction method and computer system
CN104753892A (en) * 2013-12-31 2015-07-01 腾讯科技（深圳）有限公司 Network resource transmission method, device and system
US20160300201A1 (en) * 2013-12-31 2016-10-13 Tencent Technology (Shenzhen) Company Limited Method, device and system for performing transactions
CN105825376A (en) * 2015-01-26 2016-08-03 国际商业机器公司 Method for processing resource account transaction and wireless electronic device
US20160239834A1 (en) * 2015-02-16 2016-08-18 Xiaomi Inc. Method and apparatus for requesting account transfer
CN104899732A (en) * 2015-05-05 2015-09-09 深圳市元征科技股份有限公司 Information interaction method and device
CN106845983A (en) * 2015-12-05 2017-06-13 昆明我行科技有限公司 A kind of hand set paying method using payment mark
CN105681282A (en) * 2015-12-29 2016-06-15 宇龙计算机通信科技(深圳)有限公司 Business numerical value transfer method and device
CN106572095A (en) * 2016-11-01 2017-04-19 腾讯科技（深圳）有限公司 Account registration method, device and system
CN106845955A (en) * 2017-01-18 2017-06-13 深圳市任网游科技发展有限公司 Internet bar's expenses of surfing in Internet automatic charging method and system
CN107239948A (en) * 2017-05-12 2017-10-10 腾讯科技（深圳）有限公司 Method and device for business processing, computer equipment and storage medium
CN108256839A (en) * 2017-07-28 2018-07-06 平安科技（深圳）有限公司 Numerical value resource backing method, device, server and storage medium
CN107679844A (en) * 2017-09-30 2018-02-09 北京小米移动软件有限公司 The method, apparatus and storage medium of resource transfers
CN107730261A (en) * 2017-10-18 2018-02-23 维沃移动通信有限公司 A kind of resource transfers method and relevant device
CN109802916A (en) * 2017-11-16 2019-05-24 财付通支付科技有限公司 Resource transfers method, system, server and computer readable storage medium
CN109801051A (en) * 2017-11-16 2019-05-24 财付通支付科技有限公司 Resource transfers method, system, server and computer readable storage medium
CN108322448A (en) * 2018-01-09 2018-07-24 财付通支付科技有限公司 Auth method, device, system, storage medium and computer equipment
CN108985729A (en) * 2018-06-29 2018-12-11 联动优势电子商务有限公司 A kind of method and device of account charging
CN109285000A (en) * 2018-08-13 2019-01-29 唐晓冬 A kind of campus self-help payment method and system

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115116178A (en) * 2022-06-24 2022-09-27 四川海力智能科技股份有限公司 Recharging method of intelligent meter
CN115760459A (en) * 2022-11-22 2023-03-07 广西电网有限责任公司 Method for completing electric charge account cancellation for target number

Also Published As

Publication number Publication date
CN111192036B (en) 2023-06-20

Similar Documents

Publication Publication Date Title
CN110457946B (en) Digital asset generation method and device, electronic equipment and storage medium
CN109615516B (en) Resource transfer method, device, electronic equipment and storage medium
US20160012417A1 (en) System and method for loading and reloading prepaid payment cards from mobile devices
CN111598709B (en) Medical insurance data processing system, method, device, equipment and storage medium
CN111371835A (en) Mobile phone digital currency wallet based payment method and device and mobile terminal
KR20170127854A (en) Electronic apparatus providing electronic payment and operating method thereof
TW200424912A (en) Portable terminal, portable terminal method, portable terminal program, currency information publication server, currency information publishing method and currency information publishing program
CN111260347A (en) Resource processing method, device and equipment based on block chain and storage medium
CN111080371A (en) Method, device and storage medium for issuing resources to user account
CN111192036B (en) Account resource updating method and device, computer equipment and storage medium
CN116670700A (en) System and method for managing electronic transactions
CN111325532A (en) Data processing method and device, electronic equipment and storage medium
CN116917918A (en) Embedded card reader security
CN112036887A (en) Resource transfer method, device, equipment and storage medium
TW202011308A (en) Transaction device, method, and apparatus, server, and storage medium
CN110956469A (en) Payment method, device, equipment and storage medium
CN111158555B (en) Virtual article packet receiving method, virtual article packet sending method, virtual article packet receiving device, virtual article packet sending device and virtual article packet receiving and sending system
JP7038969B2 (en) Electronic money (E-money) payment processing
CN113344617A (en) Resource verification method, device, terminal and storage medium
CN112991069A (en) Resource processing method, device, equipment and storage medium
CN111681098A (en) Resource transfer method, device, server and computer readable storage medium
CN112749959B (en) Resource transfer method, system, device, equipment and storage medium
CN113709721B (en) Resource transfer method, device, terminal and storage medium
CN113378190B (en) Bill online clearing method, system, terminal and storage medium
KR102639361B1 (en) System for providing financial transaction service associated with metaverse environment and method for operation thereof

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant