CN118052639A - Addressing transaction processing method, addressing transaction processing device, electronic equipment and computer readable medium - Google Patents

Addressing transaction processing method, addressing transaction processing device, electronic equipment and computer readable medium Download PDF

Info

Publication number
CN118052639A
CN118052639A CN202410375184.3A CN202410375184A CN118052639A CN 118052639 A CN118052639 A CN 118052639A CN 202410375184 A CN202410375184 A CN 202410375184A CN 118052639 A CN118052639 A CN 118052639A
Authority
CN
China
Prior art keywords
currency
addressing
identifier
channel
quick payment
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.)
Pending
Application number
CN202410375184.3A
Other languages
Chinese (zh)
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.)
China Construction Bank Corp
CCB Finetech Co Ltd
Original Assignee
China Construction Bank Corp
CCB Finetech 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 China Construction Bank Corp, CCB Finetech Co Ltd filed Critical China Construction Bank Corp
Priority to CN202410375184.3A priority Critical patent/CN118052639A/en
Publication of CN118052639A publication Critical patent/CN118052639A/en
Pending legal-status Critical Current

Links

Landscapes

  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

The application discloses an addressing transaction processing method, an addressing transaction processing device, electronic equipment and a computer readable medium, which relate to the technical field of data processing, and a specific implementation mode comprises the steps of responding to an addressing transaction request and acquiring corresponding channel identification and currency data; based on the channel identification and the currency data, performing registration verification, and acquiring a user identification in response to a registration verification failure; determining a currency number in response to the currency data corresponding to the plurality of currencies, generating respective registered currency identifications based on the currency number and the currency data; generating each quick payment identifier based on the user identifier, the channel identifier and each registered currency identifier; in response to successful insertion of each quick payment identification into the registration information table, the account status of the account corresponding to each quick payment identification is modified as available, and the addressing transaction is performed based on the account. Thereby improving the efficiency and accuracy of addressing transaction processing involving multiple currencies.

Description

Addressing transaction processing method, addressing transaction processing device, electronic equipment and computer readable medium
Technical Field
The present application relates to the field of data processing technologies, and in particular, to an addressing transaction processing method, an addressing transaction processing device, an electronic device, and a computer readable medium.
Background
In recent years, hongkong dollar has been in continuous increase in channel usage, and a number of transactions have been completed by Hongkong dollar. FPS: refers to a rapid payment system of the bureau of gold, also known as a fast revolution (FASTER PAYMENT SYSTEM). At present, FPS does not support Hongkong dollar, which results in failure of part of online transactions due to inconsistent currencies, FPS faces challenges of incomplete currencies support, and addressing transactions involving multiple currencies are inefficient and have low accuracy.
Disclosure of Invention
In view of the above, embodiments of the present application provide an addressing transaction processing method, apparatus, electronic device, and computer readable medium, which can solve the problem of low efficiency and accuracy of the existing addressing transaction processing involving multiple currencies.
To achieve the above object, according to an aspect of an embodiment of the present application, there is provided an addressing transaction processing method including:
responding to the addressing transaction request, and acquiring corresponding channel identification and currency data;
based on the channel identification and the currency data, performing registration verification, and acquiring a user identification in response to a registration verification failure;
determining a currency number in response to the currency data corresponding to the plurality of currencies, generating respective registered currency identifications based on the currency number and the currency data;
generating each quick payment identifier based on the user identifier, the channel identifier and each registered currency identifier;
in response to successful insertion of each quick payment identification into the registration information table, the account status of the account corresponding to each quick payment identification is modified as available, and the addressing transaction is performed based on the account.
Optionally, performing a registration check includes:
Inquiring whether a quick payment identifier simultaneously corresponding to the channel identifier and the currency data exists in the registration information table, if not, determining that the registration check fails, and if so, determining that the registration check is successful.
Optionally, generating each registration currency identifier includes:
the currency type corresponding to the currency data is determined, and each registered currency identifier corresponding to the currency number is generated based on the currency type.
Optionally, performing the addressing transaction based on the account includes:
Acquiring a type identifier corresponding to an addressing transaction request;
Responding to the type identifier to initiate addressing modification corresponding to the channel, and acquiring an uploading field;
Inquiring a local registration information table according to the uploading field, and initiating an addressing modification request to a target node based on a corresponding quick payment identifier after verifying that addressing information corresponding to the uploading field is registered;
and in response to receiving the modification result data returned by the target node, modifying the registration information table according to the modification result data.
Optionally, performing the addressing transaction based on the account includes:
Acquiring a type identifier corresponding to an addressing transaction request;
Responding to the type identifier to initiate addressing revocation corresponding to the channel, and acquiring an uploading field;
Inquiring a local registration information table according to the uploading field, and initiating an addressing revocation request to a target node based on a corresponding quick payment identifier after verifying that addressing information corresponding to the uploading field is registered;
In response to receiving revocation result data returned by the target node, the registration information table is modified and the account status is modified as unavailable in accordance with the revocation result data.
Optionally, performing the addressing transaction based on the account includes:
Acquiring a type identifier corresponding to an addressing transaction request;
Responding to the type identifier corresponding to the channel to initiate addressing inquiry, acquiring a corresponding quick payment identifier, and initiating an addressing inquiry request to a target node based on the quick payment identifier;
And in response to receiving the query result data returned by the target node, initiating transfer service based on the quick payment identification after the query result data is verified to be successful.
Optionally, the target node corresponds to the currency corresponding to the corresponding quick payment identifier one by one.
In addition, the application also provides an addressing transaction processing device, which comprises:
An acquisition unit configured to acquire corresponding channel identification and currency data in response to an addressing transaction request;
A registration verification unit configured to perform registration verification based on the channel identification and the currency data, and acquire a user identification in response to a failure of the registration verification;
a registered-currency-identification generating unit configured to determine a currency number in response to the currency data corresponding to the plurality of currencies, and generate respective registered-currency identifications based on the currency number and the currency data;
a quick payment identification generation unit configured to generate respective quick payment identifications based on the user identification, the channel identification, and the respective registered currency identifications;
And the execution unit is configured to respond to the successful insertion of each quick payment identifier into the registration information table, modify the account state of the account corresponding to each quick payment identifier to be available, and further execute the addressing transaction based on the account.
Optionally, the registration verification unit is further configured to:
Inquiring whether a quick payment identifier simultaneously corresponding to the channel identifier and the currency data exists in the registration information table, if not, determining that the registration check fails, and if so, determining that the registration check is successful.
Optionally, the registration currency identifier generating unit is further configured to:
the currency type corresponding to the currency data is determined, and each registered currency identifier corresponding to the currency number is generated based on the currency type.
Optionally, the execution unit is further configured to:
Acquiring a type identifier corresponding to an addressing transaction request;
Responding to the type identifier to initiate addressing modification corresponding to the channel, and acquiring an uploading field;
Inquiring a local registration information table according to the uploading field, and initiating an addressing modification request to a target node based on a corresponding quick payment identifier after verifying that addressing information corresponding to the uploading field is registered;
and in response to receiving the modification result data returned by the target node, modifying the registration information table according to the modification result data.
Optionally, the execution unit is further configured to:
Acquiring a type identifier corresponding to an addressing transaction request;
Responding to the type identifier to initiate addressing revocation corresponding to the channel, and acquiring an uploading field;
Inquiring a local registration information table according to the uploading field, and initiating an addressing revocation request to a target node based on a corresponding quick payment identifier after verifying that addressing information corresponding to the uploading field is registered;
In response to receiving revocation result data returned by the target node, the registration information table is modified and the account status is modified as unavailable in accordance with the revocation result data.
Optionally, the execution unit is further configured to:
Acquiring a type identifier corresponding to an addressing transaction request;
Responding to the type identifier corresponding to the channel to initiate addressing inquiry, acquiring a corresponding quick payment identifier, and initiating an addressing inquiry request to a target node based on the quick payment identifier;
And in response to receiving the query result data returned by the target node, initiating transfer service based on the quick payment identification after the query result data is verified to be successful.
Optionally, the target node corresponds to the currency corresponding to the corresponding quick payment identifier one by one.
In addition, the application also provides an addressing transaction processing electronic device, which comprises: one or more processors; and a storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the addressing transaction processing method as described above.
In addition, the application also provides a computer readable medium, on which a computer program is stored, which when executed by a processor implements the addressing transaction processing method as described above.
To achieve the above object, according to still another aspect of an embodiment of the present application, there is provided a computer program product.
A computer program product of an embodiment of the present application includes a computer program, which when executed by a processor implements an addressing transaction processing method provided by the embodiment of the present application.
One embodiment of the above application has the following advantages or benefits: the application obtains the corresponding channel identification and currency data by responding to the addressing transaction request; based on the channel identification and the currency data, performing registration verification, and acquiring a user identification in response to a registration verification failure; determining a currency number in response to the currency data corresponding to the plurality of currencies, generating respective registered currency identifications based on the currency number and the currency data; generating each quick payment identifier based on the user identifier, the channel identifier and each registered currency identifier; in response to successful insertion of each quick payment identification into the registration information table, the account status of the account corresponding to each quick payment identification is modified as available, and the addressing transaction is performed based on the account. Thereby improving the efficiency and accuracy of addressing transaction processing involving multiple currencies.
Further effects of the above-described non-conventional alternatives are described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the application and are not to be construed as unduly limiting the application. Wherein:
FIG. 1 is a schematic diagram of the main flow of an addressing transaction processing method according to one embodiment of the application;
FIG. 2 is a schematic diagram of the main flow of an addressing transaction processing method according to one embodiment of the application;
FIG. 3 is an addressing registration flow diagram of an addressing transaction processing method according to one embodiment of the present application;
FIG. 4 is a schematic diagram of an addressing inquiry flow of an addressing transaction processing method according to one embodiment of the present application;
FIG. 5 is a schematic diagram of the main units of an addressing transaction processing device according to an embodiment of the application;
FIG. 6 is an exemplary system architecture diagram in which embodiments of the present application may be applied;
Fig. 7 is a schematic diagram of a computer system suitable for use in implementing an embodiment of the application.
Detailed Description
Exemplary embodiments of the present application will now be described with reference to the accompanying drawings, in which various details of the embodiments of the present application are included to facilitate understanding, and are to be considered merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness. It should be noted that, in the technical scheme of the application, the acquisition, transmission, storage, use, processing and the like of the data all conform to the relevant regulations of national laws and regulations. It should be noted that, in the embodiments of the present application, some existing solutions in the industry such as software, components, models, etc. may be mentioned, and they should be regarded as exemplary, only for illustrating the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or must not use the solution. In the technical scheme of the application, the related aspects of acquisition, analysis, use, transmission, storage and the like of the personal information of the user accord with the regulations of related laws and regulations, are used for legal and reasonable purposes, are not shared, leaked or sold outside the legal use aspects and the like, and are subjected to supervision and management of a supervision department. Necessary measures should be taken for the personal information of the user to prevent illegal access to such personal information data, ensure that personnel having access to the personal information data comply with the regulations of the relevant laws and regulations, and ensure the personal information of the user. Once these user personal information data are no longer needed, the risk should be minimized by limiting or even prohibiting the data collection and/or deletion.
User privacy is protected by de-identifying data when used, including in some related applications, such as by removing a particular identifier, controlling the amount or specificity of stored data, controlling how data is stored, and/or other methods.
FIG. 1 is a schematic diagram of the main flow of an addressing transaction processing method according to one embodiment of the application, as shown in FIG. 1, the addressing transaction processing method includes:
step S101, in response to the addressing transaction request, obtaining the corresponding channel identifier and currency data.
In this embodiment, the execution body (for example, may be a server) of the addressing transaction processing method may receive the addressing transaction request through a wired connection or a wireless connection. After receiving the addressing transaction request, the executing body can acquire channel identification and currency data carried in the request. The channel identifier is used to characterize the channel from which the addressing transaction was initiated, such as an applet or payment mechanism, and embodiments of the application are not particularly limited to the channel characterized by the channel identifier. The currency data may include currency and associated merchant information, and the embodiment of the present application does not specifically limit the currency data.
Step S102, based on the channel identification and the currency data, registration verification is performed, and the user identification is acquired in response to the failure of the registration verification.
And the executive body rechecks whether the addressing is the registered currency according to the currency data, namely the currency and merchant information, sent by the channel corresponding to the channel identification, if not, the registration verification fails, and the user identification initiating the transaction addressing request is obtained.
Step S103, in response to the currency data corresponding to the multi-currencies, determining the currency number, and generating respective registered-currency identifications based on the currency number and the currency data.
Since the same identifier can only register one currency, the multi-currency account generates different identification numbers (namely, each registered currency identifier) according to the currency, and the identification numbers are used for being inserted into a registration information table and then sent to a quick payment system corresponding to the channel identifier for registration.
Step S104, generating each quick payment identifier based on the user identifier, the channel identifier and each registered currency identifier.
FPS: is a fast payment system, also known as fast revolution (FASTER PAYMENT SYSTEM). A fast payment identifier, such as an FPS identifier. For example, since the uniqueness of the FPS identifier is guaranteed, payment settlement may be based on the type of proxy account number of the payer (i.e. may correspond to the registered currency identifier), the bank number of the proxy bank, the channel identifier sent up, and the additional number of the payer (i.e. may correspond to the user identifier). It is ensured that one FPS identification (i.e. the fast payment identification) corresponds to only one currency of one payment account of one customer (i.e. corresponds to the channel identification). The quick payment identification is implemented to correspond to only one currency of one payment account of one user. The uniqueness of the quick payment identification is guaranteed, and the security of the addressing transaction based on the quick payment identification is guaranteed.
Address transaction processing: the payee enjoys the instant account transfer payment, and address registration must be performed in the FPS system first, the newly registered address information will be immediately validated, and only one currency can be registered for the same identifier. The address is divided into functions of registration, revocation, modification, inquiry and the like. After each quick payment identifier is generated, the channel can initiate address registration, and payment settlement verifies the client information. The executive body rechecks the addressing registration currency according to the currency sent by the channel and the merchant information, and rechecks the registration currency through subsequent registration. Since the same identifier can register only one currency, the multi-currency accounts generate different identifier numbers according to the currencies, and insert the identifier numbers into an address registration table and an address account information table (in the embodiment of the application, the address registration table and the address account information table are called as a registration information table together), and the FPS of the corresponding currency of the delivery channel is registered. And after the channel FPS addressing information is put in storage, returning to P8 payment settlement, and subsequently notifying the client of the registration result. And modifying the address registration table and the address account information table according to the result returned by the channel FPS, setting the account to be in a usable state, and ending the service.
In step S105, in response to the successful insertion of each quick payment identifier into the registration information table, the account status of the account corresponding to each quick payment identifier is modified to be available, and then the addressing transaction is executed based on the account.
After each quick payment identifier is successfully inserted into the registration information table, the fact that the currency corresponding to each quick payment identifier is successfully registered in the quick payment system addressing service is indicated, and the quick payment transaction can be normally carried out.
Specifically, performing an addressing transaction based on an account includes: acquiring a type identifier corresponding to an addressing transaction request; responding to the type identifier to initiate addressing modification corresponding to the channel, and acquiring an uploading field; inquiring a local registration information table according to the uploading field, and initiating an addressing modification request to a target node based on a corresponding quick payment identifier after verifying that addressing information corresponding to the uploading field is registered; and in response to receiving the modification result data returned by the target node, modifying the registration information table according to the modification result data.
Address refers to an addressing service whereby a payer can make a transfer payment by phone number or FPS identification. For example, the channel initiates address modification, pays for settlement verification of customer information, and processes the address modification request after verification. Payment settlement (which may be an executing entity of an embodiment of the present application) queries a local database table (i.e., a local registration information table) according to the upload field, verifies that the addressing information is registered, and then initiates an addressing modification request to the channel FPS (which may be a target node), and the channel FPS verifies and feeds back modification result data to the participating institution. The payment settlement modifies the address registry and the address account information table (in the embodiment of the present application, the address registry and the address account information table are collectively referred to as a registration information table) according to the modification result data returned by the channel FPS, and the service ends.
Specifically, performing an addressing transaction based on an account includes: acquiring a type identifier corresponding to an addressing transaction request; responding to the type identifier corresponding to the channel to initiate addressing inquiry, acquiring a corresponding quick payment identifier, and initiating an addressing inquiry request to a target node based on the quick payment identifier; and in response to receiving the query result data returned by the target node, initiating transfer service based on the quick payment identification after the query result data is verified to be successful.
Illustratively, the channel initiates an address query and the payer enters the payee's phone number or FPS identifier through the participating institution to perform the transfer service. The participating institution initiates a query request to the channel FPS, including information such as the payee's phone number or FPS identification. The channel FPS responds to the request initiated by the participating institution, and the response information (i.e., the query result data) includes the participating institution code, the customer name, and the customer FPS identification. After the information is obtained, the transfer service can be initiated, and the online transaction service with multiple currencies can be performed.
Specifically, the target nodes are in one-to-one correspondence with the currencies corresponding to the corresponding quick payment identifiers.
The target node may be, for example, a server that handles transaction requests of different currencies.
Exemplary, reconciliation document processing: channel FPS may support transactions of two currencies, the transaction requests of which need to be sent to different servers for processing. Payment settlement can therefore be distinguished by currency from the server sent in daily reconciliation files. And storing the transaction information in the account checking file into an account checking temporary table in combination with the corresponding currency, respectively checking accounts by taking the currency as a key field when checking accounts, reserving account checking results and supplying the account checking results to a data warehouse for storage.
Payment settlement processing (addressing) method: multiple channels can initiate address registration service, and different identifications are given to each channel, wherein the first place is currency. And checking the account initiating address according to the currency field and the first identification bit of the channel. The address information is divided into two tables, namely an address registration table and an address account information table (in the embodiment of the present application, the address registration table and the address account information table are collectively referred to as a registration information table) and stored. The address registration table stores account information, address state information, FPS identification information, creation time information and the like, and the address account information table stores more comprehensive address information, wherein the address information comprises key information such as names, FPS identifications, channel identifications and the like of the applicant. Because the uniqueness of the FPS identification is ensured, the payment settlement forms the FPS identification according to the type of the proxy account number of the payer, the number of the proxy bank, the uploaded channel identification and the additional number of the payer. It is ensured that one FPS identification (i.e. the fast payment identification) corresponds to only one currency of one payment account of one customer (i.e. corresponds to the channel identification). When the address is cancelled, the address status field is added in the database design because the cancelled FPS identifier is guaranteed to be unusable. When the undo operation is completed, the address status field is changed, and the unique constraint of the database is used to ensure that the same FPS identification record is not inserted into the table.
In the embodiment, corresponding channel identification and currency data are acquired by responding to an addressing transaction request; based on the channel identification and the currency data, performing registration verification, and acquiring a user identification in response to a registration verification failure; determining a currency number in response to the currency data corresponding to the plurality of currencies, generating respective registered currency identifications based on the currency number and the currency data; generating each quick payment identifier based on the user identifier, the channel identifier and each registered currency identifier; in response to successful insertion of each quick payment identification into the registration information table, the account status of the account corresponding to each quick payment identification is modified as available, and the addressing transaction is performed based on the account. Thereby improving the efficiency and accuracy of addressing transaction processing involving multiple currencies.
Fig. 2 is a schematic flow chart of a method for processing an addressing transaction according to one embodiment of the application, as shown in fig. 2, the method for processing an addressing transaction includes:
Step S201, in response to the addressing transaction request, the corresponding channel identifier and currency data are acquired.
The addressing transaction request may be an addressing transaction request involving multiple currencies. After receiving the addressing transaction request, the executing body can acquire channel identification and currency data carried in the request. The channel identifier is used to characterize the channel from which the addressing transaction was initiated, such as an applet or payment mechanism, and embodiments of the application are not particularly limited to the channel characterized by the channel identifier. The currency data may include currency and associated merchant information, and the embodiment of the present application does not specifically limit the currency data.
Step S202, inquiring whether a quick payment identifier corresponding to the channel identifier and the currency data exists in the registration information table or not based on the channel identifier and the currency data, if not, determining that the registration check fails, and if so, determining that the registration check is successful.
By using the channel identifier and the currency data together as check data to perform registration check, a more accurate registration check result can be obtained.
Step S203, responding to the failure of the registration verification, and acquiring the user identification.
When the registration verification fails, the fact that the related channel and currency are not registered in the registration information table is indicated, quick payment cannot be performed at the moment, and the user identification needs to be acquired to serve as necessary data for subsequent registration.
Step S204, determining the number of currencies in response to the currency data corresponding to the multi-currencies.
And acquiring the currency identifications corresponding to the currency data, when the currency identifications are different from each other and not only one is available, determining that the currency data corresponds to multiple currencies, and determining the quantity of the currency identifications different from each other to determine the quantity of the currencies corresponding to the multiple currencies.
Step S205, a currency type corresponding to the currency data is determined, and each registered currency identifier corresponding to the currency number is generated based on the currency type.
The same identifier can only register one currency, and different registration currency identifiers are required to be randomly generated according to different currency types or generated according to preset rules. The mode of generating different registration currency identifiers is not particularly limited in the embodiment of the present application.
Step S206, generating each quick payment identifier based on the user identifier, the channel identifier and each registered currency identifier.
And assembling the user identifier, the channel identifier and each registered currency identifier according to a preset assembly form to obtain each quick payment identifier.
The executing body may further obtain each quick payment identifier based on the user identifier, the channel identifier, and a part of each registered currency identifier, for example, the executing body may extract a first target identifier of the user identifier, a second target identifier of the channel identifier, and a third target identifier of each registered currency identifier, and assemble the first target identifier and the second target identifier, and the third target identifier, so as to quickly and simply obtain each quick payment identifier. By way of example, the first target identifier, the second target identifier, and the third target identifier may be numbers or letters or other symbols, and embodiments of the present application are not limited in detail.
In step S207, in response to the successful insertion of each quick payment identifier into the registration information table, the account status of the account corresponding to each quick payment identifier is modified to be available, and the addressing transaction is further executed based on the account.
Specifically, performing an addressing transaction based on an account includes: acquiring a type identifier corresponding to an addressing transaction request; responding to the type identifier to initiate addressing revocation corresponding to the channel, and acquiring an uploading field; inquiring a local registration information table according to the uploading field, and initiating an addressing revocation request to a target node based on a corresponding quick payment identifier after verifying that addressing information corresponding to the uploading field is registered; in response to receiving revocation result data returned by the target node, the registration information table is modified and the account status is modified as unavailable in accordance with the revocation result data.
Illustratively, the channel initiates an address revocation, and the payment settlement process addresses the revocation request. The payment settlement inquires a local database table (namely a local registration information table) according to the uploading field, the addressing information is verified to be registered, an addressing revocation request is initiated to the channel FPS, the original FPS identification is invalidated and cannot be reused, and revocation result data is fed back to the participating mechanism after the channel FPS verification is passed. The payment settlement modifies the address registration table and the address account information table (in the embodiment of the present application, the address registration table and the address account information table are collectively referred to as a registration information table) according to the revocation result data returned by the channel FPS, sets the account state to an unavailable state, and ends the service.
Fig. 3 is an addressing registration flow diagram of an addressing transaction processing method according to one embodiment of the application. As shown in fig. 3, the FPS: is a fast payment system, also known as fast revolution (FASTER PAYMENT SYSTEM). The addressing registration process involves the payee, the collection institution, the FPS, the associated collection institution. Specifically, ① the payee sends an addressing registration application to the payee institution through the internet banking or the mobile phone bank, and the payee institution verifies the client information; ② The collection mechanism sends a short message to the receiver for verification; ③ The payee performs short message verification and confirmation; ④ The cashier addresses the registration request fps.adrs.001; ⑤ The FPS (gold bureau) performs validity check; ⑥ a, passing the validity check, and storing and processing addressing registration information; ⑦ Returning an addressing registration result fps.adrs.004 to the cash register; ⑧ The cash register mechanism receives an addressing registration result fps.adrs.004; ⑨ The payee receives the registration success message; ⑩ The FPS (gold bureau) sends a status update notification fps.adrs.005 to the relevant collection facility, which receives the status update notification fps.adrs.005; ⑥ b, if the validity check is not passed, sending a failure receipt fps.adrs.004 to the collection mechanism, and receiving the failure receipt fps.adrs.004 by the collection mechanism.
Fig. 4 is a schematic diagram of an addressing inquiry flow of an addressing transaction processing method according to an embodiment of the present application. As shown in fig. 4, the FPS: is a fast payment system, also known as fast revolution (FASTER PAYMENT SYSTEM). Addressing queries involve the payer, the payment institution, and the FPS. Illustratively, ① the payer sends a payment request to the payment mechanism via the bank of internet or cell phone, which addresses the query request fps.adrs.008; ② The FPS (gold bureau) performs validity check, ③ a passes the validity check, and returns an addressing inquiry response fps.adrs.009 to the payment mechanism; ④ The payment mechanism receives an addressing query result fps.adrs.009; ⑤ The payment mechanism presents the addressing inquiry response to the payer; ③ b pass the validity check and send a failure receipt admi.002, fps.adrs.009 to the payment institution.
The embodiment of the application can realize the addressing transaction by using multiple currencies, and the bank is used as a participant of the channel FPS system, and only needs to simply modify the service interface when expanding the service. The function of the second currency transaction is integrated on the basis of not affecting the existing transaction, the automatic account checking function of the double currencies is realized, and the competitiveness of the system is greatly expanded. On the basis of keeping the existing business logic, the address transaction of the new currency can be supported by only modifying the channel identifier sent by the channel, so that the online transaction of more currencies can be supported without repeatedly developing a new payment system. The transaction of the two currencies does not affect the transaction reconciliation of the respective currencies.
Fig. 5 is a schematic diagram of the main units of an addressing transaction processing device according to an embodiment of the application. As shown in fig. 5, the addressing transaction processing apparatus 500 includes an acquisition unit 501, a registration verification unit 502, a registration currency identification generation unit 503, a quick payment identification generation unit 504, and an execution unit 505.
An obtaining unit 501 configured to obtain corresponding channel identification and currency data in response to an addressing transaction request;
A registration verification unit 502 configured to perform registration verification based on the channel identification and the currency data, and acquire a user identification in response to a registration verification failure;
A registered-currency-identification generating unit 503 configured to determine a currency number in response to the currency data corresponding to the multi-currencies, and generate respective registered-currency identifications based on the currency number and the currency data;
A quick payment identification generation unit 504 configured to generate respective quick payment identifications based on the user identification, the channel identification, and the respective registered currency identifications;
An execution unit 505 is configured to, in response to a successful insertion of each quick payment identifier into the registration information table, modify an account status of an account corresponding to each quick payment identifier as available, and further execute an addressing transaction based on the account.
In some embodiments, the registration verification unit 502 is further configured to: inquiring whether a quick payment identifier simultaneously corresponding to the channel identifier and the currency data exists in the registration information table, if not, determining that the registration check fails, and if so, determining that the registration check is successful.
In some embodiments, the registration currency identification generating unit 503 is further configured to: the currency type corresponding to the currency data is determined, and each registered currency identifier corresponding to the currency number is generated based on the currency type.
In some embodiments, the execution unit 505 is further configured to: acquiring a type identifier corresponding to an addressing transaction request; responding to the type identifier to initiate addressing modification corresponding to the channel, and acquiring an uploading field; inquiring a local registration information table according to the uploading field, and initiating an addressing modification request to a target node based on a corresponding quick payment identifier after verifying that addressing information corresponding to the uploading field is registered; and in response to receiving the modification result data returned by the target node, modifying the registration information table according to the modification result data.
In some embodiments, the execution unit 505 is further configured to: acquiring a type identifier corresponding to an addressing transaction request; responding to the type identifier to initiate addressing revocation corresponding to the channel, and acquiring an uploading field; inquiring a local registration information table according to the uploading field, and initiating an addressing revocation request to a target node based on a corresponding quick payment identifier after verifying that addressing information corresponding to the uploading field is registered; in response to receiving revocation result data returned by the target node, the registration information table is modified and the account status is modified as unavailable in accordance with the revocation result data.
In some embodiments, the execution unit 505 is further configured to: acquiring a type identifier corresponding to an addressing transaction request; responding to the type identifier corresponding to the channel to initiate addressing inquiry, acquiring a corresponding quick payment identifier, and initiating an addressing inquiry request to a target node based on the quick payment identifier; and in response to receiving the query result data returned by the target node, initiating transfer service based on the quick payment identification after the query result data is verified to be successful.
In some embodiments, the destination node corresponds one-to-one to the currency corresponding to the corresponding quick payment identity.
It should be noted that, the addressing transaction processing method and the addressing transaction processing apparatus of the present application have a corresponding relationship in terms of implementation content, so the description of the repetition content is not repeated.
Fig. 6 illustrates an exemplary system architecture 600 to which the addressing transaction processing method or addressing transaction processing device of embodiments of the present application may be applied.
As shown in fig. 6, the system architecture 600 may include terminal devices 601, 602, 603, a network 604, and a server 605. The network 604 is used as a medium to provide communication links between the terminal devices 601, 602, 603 and the server 605. The network 604 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
A user may interact with the server 605 via the network 604 using the terminal devices 601, 602, 603 to receive or send messages, etc. Various communication client applications such as shopping class applications, web browser applications, search class applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only) may be installed on the terminal devices 601, 602, 603.
The terminal devices 601, 602, 603 may be a variety of electronic devices having an addressing transaction processing screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.
The server 605 may be a server providing various services, such as a background management server (by way of example only) providing support for addressing transaction requests submitted by users using terminal devices 601, 602, 603. The background management server can respond to the addressing transaction request and acquire corresponding channel identification and currency data; based on the channel identification and the currency data, performing registration verification, and acquiring a user identification in response to a registration verification failure; determining a currency number in response to the currency data corresponding to the plurality of currencies, generating respective registered currency identifications based on the currency number and the currency data; generating each quick payment identifier based on the user identifier, the channel identifier and each registered currency identifier; in response to successful insertion of each quick payment identification into the registration information table, the account status of the account corresponding to each quick payment identification is modified as available, and the addressing transaction is performed based on the account. Thereby improving the efficiency and accuracy of addressing transaction processing involving multiple currencies.
It should be noted that, the addressing transaction processing method provided in the embodiment of the present application is generally executed by the server 605, and accordingly, the addressing transaction processing apparatus is generally disposed in the server 605.
It should be understood that the number of terminal devices, networks and servers in fig. 6 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 7, there is illustrated a schematic diagram of a computer system 700 suitable for use in implementing an embodiment of the present application. The terminal device shown in fig. 7 is only an example, and should not impose any limitation on the functions and the scope of use of the embodiment of the present application.
As shown in fig. 7, the computer system 700 includes a Central Processing Unit (CPU) 701, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 702 or a program loaded from a storage section 708 into a Random Access Memory (RAM) 703. In the RAM703, various programs and data required for the operation of the computer system 700 are also stored. The CPU701, ROM702, and RAM703 are connected to each other through a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.
The following components are connected to the I/O interface 705: an input section 706 including a keyboard, a mouse, and the like; an output section 707 including a Cathode Ray Tube (CRT), a liquid crystal credit authorization query processor (LCD), and the like, and a speaker, and the like; a storage section 708 including a hard disk or the like; and a communication section 709 including a network interface card such as a LAN card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. The drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read therefrom is mounted into the storage section 708 as necessary.
In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication portion 709, and/or installed from the removable medium 711. The above-described functions defined in the system of the present application are performed when the computer program is executed by a Central Processing Unit (CPU) 701.
The computer readable medium shown in the present application may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium may include, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present application, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments of the present application may be implemented in software or in hardware. The described units may also be provided in a processor, for example, described as: a processor includes an acquisition unit, a registration verification unit, a registration currency identification generation unit, a quick payment identification generation unit, and an execution unit. Wherein the names of the units do not constitute a limitation of the units themselves in some cases.
As another aspect, the present application also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be present alone without being fitted into the device. The computer readable medium carrying one or more programs which, when executed by one of the devices, cause the device to obtain corresponding channel identification and currency data in response to an addressing transaction request; based on the channel identification and the currency data, performing registration verification, and acquiring a user identification in response to a registration verification failure; determining a currency number in response to the currency data corresponding to the plurality of currencies, generating respective registered currency identifications based on the currency number and the currency data; generating each quick payment identifier based on the user identifier, the channel identifier and each registered currency identifier; in response to successful insertion of each quick payment identification into the registration information table, the account status of the account corresponding to each quick payment identification is modified as available, and the addressing transaction is performed based on the account.
The computer program product of the present application comprises a computer program which, when executed by a processor, implements the addressing transaction processing method of the embodiments of the present application.
According to the technical scheme provided by the embodiment of the application, the efficiency and the accuracy of addressing transaction processing related to multiple currencies can be improved.
The above embodiments do not limit the scope of the present application. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives can occur depending upon design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present application should be included in the scope of the present application.

Claims (16)

1. A method of addressing transaction processing, comprising:
responding to the addressing transaction request, and acquiring corresponding channel identification and currency data;
Based on the channel identification and the currency data, performing registration verification, and acquiring a user identification in response to a registration verification failure;
determining a currency number in response to the currency data corresponding to a plurality of currencies, generating respective registered currency identifications based on the currency number and the currency data;
generating each quick payment identifier based on the user identifier, the channel identifier and each registered currency identifier;
And in response to the successful insertion of the quick payment identifiers into the registration information table, modifying the account state of the account corresponding to the quick payment identifiers to be available, and further executing the addressing transaction based on the account.
2. The method of claim 1, wherein the performing a registration check comprises:
Inquiring whether a quick payment identifier simultaneously corresponding to the channel identifier and the currency data exists in the registration information table, if not, determining that the registration check fails, and if so, determining that the registration check is successful.
3. The method of claim 1, wherein generating each registered currency identity comprises:
And determining a currency type corresponding to the currency data, and generating each registered currency identifier corresponding to the currency quantity based on the currency type.
4. The method of claim 1, wherein the performing an addressing transaction based on the account comprises:
Acquiring a type identifier corresponding to the addressing transaction request;
responding to the type identifier to initiate addressing modification corresponding to a channel, and acquiring an uploading field;
Inquiring a local registration information table according to the uploading field, and initiating an addressing modification request to a target node based on a corresponding quick payment identifier after verifying that addressing information corresponding to the uploading field is registered;
And in response to receiving the modification result data returned by the target node, modifying the registration information table according to the modification result data.
5. The method of claim 1, wherein the performing an addressing transaction based on the account comprises:
Acquiring a type identifier corresponding to the addressing transaction request;
responding to the type identifier to initiate addressing revocation corresponding to the channel, and acquiring an uploading field;
Inquiring a local registration information table according to the uploading field, and initiating an addressing revocation request to a target node based on a corresponding quick payment identifier after verifying that addressing information corresponding to the uploading field is registered;
and in response to receiving revocation result data returned by the target node, modifying the registration information table according to the revocation result data and modifying the account state to be unavailable.
6. The method of claim 1, wherein the performing an addressing transaction based on the account comprises:
Acquiring a type identifier corresponding to the addressing transaction request;
responding to the type identifier corresponding to the channel to initiate addressing inquiry, acquiring a corresponding quick payment identifier, and initiating an addressing inquiry request to a target node based on the quick payment identifier;
And responding to the received query result data returned by the target node, and initiating transfer service based on the quick payment identification after the query result data is verified to be successful.
7. The method according to any one of claims 4-6, wherein the target node corresponds one-to-one to the currency corresponding to the corresponding fast payment identity.
8. An addressing transaction processing device, comprising:
An acquisition unit configured to acquire corresponding channel identification and currency data in response to an addressing transaction request;
A registration verification unit configured to perform registration verification based on the channel identification and the currency data, and acquire a user identification in response to a registration verification failure;
A registered-currency-identification generating unit configured to determine a currency number in response to the currency data corresponding to a plurality of currencies, generate respective registered-currency identifications based on the currency number and the currency data;
A quick payment identification generation unit configured to generate respective quick payment identifications based on the user identification, the channel identification, and the respective registered currency identifications;
and the execution unit is configured to respond to the successful insertion of the quick payment identifiers into the registration information table, modify the account states of the accounts corresponding to the quick payment identifiers to be available, and further execute the addressing transaction based on the accounts.
9. The apparatus of claim 8, wherein the registration verification unit is further configured to:
Inquiring whether a quick payment identifier simultaneously corresponding to the channel identifier and the currency data exists in the registration information table, if not, determining that the registration check fails, and if so, determining that the registration check is successful.
10. The apparatus according to claim 8, wherein the registered currency identification generating unit is further configured to:
And determining a currency type corresponding to the currency data, and generating each registered currency identifier corresponding to the currency quantity based on the currency type.
11. The apparatus of claim 8, wherein the execution unit is further configured to:
Acquiring a type identifier corresponding to the addressing transaction request;
responding to the type identifier to initiate addressing modification corresponding to a channel, and acquiring an uploading field;
Inquiring a local registration information table according to the uploading field, and initiating an addressing modification request to a target node based on a corresponding quick payment identifier after verifying that addressing information corresponding to the uploading field is registered;
And in response to receiving the modification result data returned by the target node, modifying the registration information table according to the modification result data.
12. The apparatus of claim 8, wherein the execution unit is further configured to:
Acquiring a type identifier corresponding to the addressing transaction request;
responding to the type identifier to initiate addressing revocation corresponding to the channel, and acquiring an uploading field;
Inquiring a local registration information table according to the uploading field, and initiating an addressing revocation request to a target node based on a corresponding quick payment identifier after verifying that addressing information corresponding to the uploading field is registered;
and in response to receiving revocation result data returned by the target node, modifying the registration information table according to the revocation result data and modifying the account state to be unavailable.
13. The apparatus of claim 8, wherein the execution unit is further configured to:
Acquiring a type identifier corresponding to the addressing transaction request;
responding to the type identifier corresponding to the channel to initiate addressing inquiry, acquiring a corresponding quick payment identifier, and initiating an addressing inquiry request to a target node based on the quick payment identifier;
And responding to the received query result data returned by the target node, and initiating transfer service based on the quick payment identification after the query result data is verified to be successful.
14. An addressing transaction processing electronic device, comprising:
one or more processors;
Storage means for storing one or more programs,
The one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1-7.
15. A computer readable medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any of claims 1-7.
16. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any of claims 1-7.
CN202410375184.3A 2024-03-29 2024-03-29 Addressing transaction processing method, addressing transaction processing device, electronic equipment and computer readable medium Pending CN118052639A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202410375184.3A CN118052639A (en) 2024-03-29 2024-03-29 Addressing transaction processing method, addressing transaction processing device, electronic equipment and computer readable medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202410375184.3A CN118052639A (en) 2024-03-29 2024-03-29 Addressing transaction processing method, addressing transaction processing device, electronic equipment and computer readable medium

Publications (1)

Publication Number Publication Date
CN118052639A true CN118052639A (en) 2024-05-17

Family

ID=91048596

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202410375184.3A Pending CN118052639A (en) 2024-03-29 2024-03-29 Addressing transaction processing method, addressing transaction processing device, electronic equipment and computer readable medium

Country Status (1)

Country Link
CN (1) CN118052639A (en)

Similar Documents

Publication Publication Date Title
US10990977B2 (en) System communications with non-sensitive identifiers
US10977632B2 (en) Electronic bill management method, apparatus, and storage medium
CN110612546B (en) Method and apparatus for digital asset account management
US11250391B2 (en) Token check offline
US20170221053A1 (en) Digital asset conversion
US20150142673A1 (en) Methods and systems for token request management
WO2023178924A1 (en) Payment method, user terminal, apparatus, device, system, and medium
US20170083914A1 (en) Method and system for managing authentication services customer data
EP4358000A1 (en) Digital currency-based payment method, platform, terminal, and payment system
CN111833066A (en) Account authorization method, device and system
JP6721724B2 (en) Methods and devices that facilitate the expansion of payment entities
CN111192040B (en) Registration method and system for mechanism identification number
CN118052639A (en) Addressing transaction processing method, addressing transaction processing device, electronic equipment and computer readable medium
US20140006271A1 (en) Cross-network electronic payment processing system and method
CN111415245A (en) Account opening method and device
TWI839875B (en) Payment method, user terminal, device, equipment, system and medium
CN111127006A (en) Transaction processing method and system based on block chain
CN112785380B (en) Transaction processing method and device
US20220114589A1 (en) Aggregated transaction accounts
US20220122177A1 (en) Blockchain-based transaction
CN116245518A (en) Method and device for transferring digital money
CN116468532A (en) Service processing method, device, electronic equipment and computer readable medium
CN105556476A (en) Method and system for conducting mobile application to mobile application data exchange
CN117439982A (en) Resource management method, device, computer equipment and storage medium
CN115619550A (en) Service data processing method and device

Legal Events

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