CN115689706A - One-stop type banking business signing system - Google Patents
One-stop type banking business signing system Download PDFInfo
- Publication number
- CN115689706A CN115689706A CN202211296575.3A CN202211296575A CN115689706A CN 115689706 A CN115689706 A CN 115689706A CN 202211296575 A CN202211296575 A CN 202211296575A CN 115689706 A CN115689706 A CN 115689706A
- Authority
- CN
- China
- Prior art keywords
- user
- signing
- result
- module
- message
- 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
Links
- 238000000034 method Methods 0.000 claims abstract description 85
- 238000012423 maintenance Methods 0.000 claims abstract description 82
- 238000012545 processing Methods 0.000 claims abstract description 53
- 230000008569 process Effects 0.000 claims abstract description 52
- 238000003032 molecular docking Methods 0.000 claims abstract description 11
- 230000009467 reduction Effects 0.000 claims description 22
- 230000005540 biological transmission Effects 0.000 claims description 16
- 230000008859 change Effects 0.000 claims description 12
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 claims description 6
- 230000002159 abnormal effect Effects 0.000 claims description 5
- 239000003795 chemical substances by application Substances 0.000 claims description 5
- 230000005012 migration Effects 0.000 claims description 3
- 238000013508 migration Methods 0.000 claims description 3
- 230000003993 interaction Effects 0.000 abstract description 4
- 238000010586 diagram Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 238000006467 substitution reaction Methods 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
Images
Landscapes
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The invention discloses a one-stop type signing system for banking business, which comprises the following modules: the system comprises a user side module, a message processing module and a message sending module, wherein the user side module is used for receiving an operation instruction input by a user and outputting a message to the user after a transaction related to the operation instruction input by the user is finished; the channel module is used for providing a channel interface which is used for determining the affairs related to the operation instruction input by the user; the message platform module is used for executing corresponding affairs by using an operation instruction input by a user to obtain an output message corresponding to the affairs; the core system module is used for registering transaction information; and the ECIF docking module is used for docking with a bank system to acquire user information. The invention can reduce the data interaction with the core system and objectively improve the processing efficiency of the banking business by providing the unified processes of signing, contracting, signing maintenance, card changing and card selling, charging record generation, fee deduction file generation and bank charging result file processing.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a banking business one-stop signing system.
Background
The signing service is that the bank collects short message fee monthly rent mode to provide short message service for the user, the user transacts the signing service with the bank through a counter/online mode, and when the fund on the account of the user changes, the user informs the user of the information of specific amount, account moving time and the like through the form of short messages. Therefore, when the card account number has abnormal fund change, the user can check and track the account in time and recover the fund loss in time.
The existing signing process is basically completed in a core system in a bank; and a set of signing systems are required to be developed aiming at one message type (such as short messages and WeChat), and the signing systems are not shared mutually. With the increasing of information interaction modes between banks and bank users, the banks can develop signing systems aiming at other message types gradually, but the signing systems basically need to interact with a core system at present. Thus, with the development of services, more and more subscription systems need to be docked, and the data interaction amount is larger and larger, which inevitably and gradually increases the burden of the core system. Thereby affecting the performance of the core system data processing.
Disclosure of Invention
In view of this, the embodiment of the present invention provides a banking business one-stop signing system.
The invention provides a banking business one-stop signing system in a first aspect, which comprises the following modules:
the system comprises a user side module, a message processing module and a message sending module, wherein the user side module is used for receiving an operation instruction input by a user and outputting a message to the user after a transaction related to the operation instruction input by the user is finished;
the system comprises a channel module, a channel module and a processing module, wherein the channel module is used for providing a channel interface which is used for determining a transaction related to an operation instruction input by a user;
the message platform module is used for executing corresponding affairs by using an operation instruction input by a user to obtain an output message corresponding to the affairs;
the core system module is used for registering transaction information;
and the ECIF docking module is used for docking with the ECIF module in the bank system to acquire user information.
Further, the operation instruction includes subscription information, the channel interface includes a subscription transaction interface, the transaction includes a subscription transaction, and the output message includes a subscription result; the banking business one-stop signing system is used for executing a signing process, and the signing process comprises the following steps:
the user side module receives the subscription information;
the channel module authenticates the subscription information, provides a subscription transaction interface after the authentication is passed, and records the subscription information into the message platform module;
the message platform module executes a signing transaction to obtain a signing result;
and the user side module outputs the signing result.
Further, the signing transaction specifically includes the following steps:
checking a signing record of a user and determining whether the user is a personal account;
when the user is a personal account, determining whether the user is a core authentication mobile phone number;
when the user is not a personal account number or the user is a core authentication mobile phone number, determining whether a bank card number and a message type input by the user exist;
when the bank card number and the message type selected by the user do not exist, judging that the signing is successful, and outputting the successful signing as a signing result;
when the user does not authenticate the mobile phone number for the core or the bank card number and the message type selected by the user are determined to exist, judging that the signing fails, and outputting the signing failure as a signing result;
before the judgment that the subscription is successful, the method further comprises the following steps:
determining a fee deduction mode, setting the bank card input by the user as a fee deduction card when the bank card input by the user is a first card, and otherwise, setting the bank card input by the user as a non-fee deduction card;
updating an address book of a user, and newly adding a signing label in the address book;
after the subscription is judged to be successful, the method further comprises the following steps:
and determining whether the message type input by the user is the first message type signed by the user, if so, setting a callback core for the subscription.
Further, after the subscription result is obtained, the method further includes a step of processing the subscription result, where the step of processing the subscription result specifically includes the following steps:
acquiring a signing result;
the message platform module sends a signing result through a message interface;
checking whether a subscription sets a callback core; if yes, registering the signing result in the core system module;
checking whether the bank card input by the user is the first card; if yes, generating preferential information for the user and sending the preferential information to the user.
Further, the operation instruction comprises contract information, the channel interface comprises a contract transaction interface, the transaction comprises a contract transaction, and the output message comprises a contract result; the banking business one-stop signing system is used for executing a contract-resolving process, and the contract-resolving process comprises the following steps:
the client module receives the contract-release information;
the channel module authenticates the contract-resolving information, provides a contract-resolving transaction interface after the authentication is passed, and inputs the contract-resolving information into the message platform module;
the message platform module executes the reduction affair to obtain a reduction result;
and the client module outputs the contracting result.
Further, the contracting transaction specifically comprises the following steps:
checking a signing record of a user, and determining whether a bank card number and a message type input by the user exist;
when the bank card number and the message type input by the user exist, judging that the contract is successful, and outputting the successful contract as a judgment result;
when the bank card number and the message type input by the user are determined to be absent, judging that the settlement fails, and outputting the settlement failures as a judgment result;
before the judgment result shows that the reduction is successful, the method further comprises the following steps:
checking a signing record migration history table, determining whether a bank card input by a user is a fee deduction card, if so, setting other bank cards of the user as fee deduction cards;
updating an address book of a user, and deleting a signing label from the address book;
after the subscription is judged to be successful, the method further comprises the following steps:
determining whether the message type input by the user is the last message type of the user; if yes, resetting the callback core for the user.
Further, after obtaining the result of the reduction, the method further includes a step of processing the result of the reduction, and the step of processing the result of the reduction specifically includes the following steps:
obtaining a result of the reduction;
the message platform module sends the result of the reduction through a message interface;
checking whether a callback core is reset; if yes, the result of the solution is registered in the core system module.
Further, the operation instruction includes subscription maintenance information, the channel interface includes a subscription maintenance transaction interface, the transaction includes a subscription maintenance transaction, and the output message includes a subscription maintenance result; the banking business one-stop signing system is used for executing a signing maintenance process, and the signing process comprises the following steps:
the user end module receives the signing maintenance information;
the channel module authenticates the signing maintenance information, provides a signing maintenance transaction interface after the authentication is passed, and records the signing maintenance information into the message platform module;
the message platform module executes a signing maintenance transaction to obtain a signing maintenance result;
and the user side module outputs the signing maintenance result.
Further, the signing maintenance transaction specifically includes the following steps:
checking a signing record of a user and determining whether the user is a personal account;
when the user is a personal account, determining whether the user is a core authentication mobile phone number;
when the user is not a personal account or the user is a core authentication mobile phone number, determining whether a bank card number and a message type input by the user exist or not;
when the bank card number and the message type selected by the user exist, judging that the signing maintenance is successful, and outputting the successful signing maintenance as a signing maintenance result;
when the user does not authenticate the mobile phone number for the core or the bank card number and the message type selected by the user do not exist, judging that the signing maintenance fails, and outputting the signing maintenance failure as a signing maintenance result;
before the subscription maintenance is judged to be successful, the method further comprises the following steps:
modifying the user subscription record;
modifying the fee deduction mode of the user;
the displayed balance of the user is modified.
Further, after obtaining the contract maintenance result, the method further includes a step of processing the contract maintenance result, where the step of processing the contract maintenance result specifically includes the following steps:
acquiring a signing maintenance result;
the message platform module sends a signing maintenance result through a message interface;
checking whether the signing calls back the core; if yes, registering the contract maintenance result in the core system module.
Furthermore, the banking business one-stop signing system also comprises a user synchronization module, wherein the user synchronization module is used for synchronizing user signing information between the one-stop signing system and the banking system; the banking business one-stop signing system is used for executing a card changing and selling process, and the card changing and selling process comprises the following steps:
the ECIF docking module sends a card changing and selling instruction to the bank system; the user synchronization module receives a data change message sent back by the bank system;
the user synchronization module analyzes the data change message to obtain an analysis result; the analysis result comprises an operation type, a core user number, a new card number and an old card number;
judging whether the user changes the card or not according to the analysis result, when the user changes the card, updating the card number information in the subscription list and the subscription detail list of the user by the user synchronization module, and returning a normal processing result to the user side module for outputting;
when the user does not change the card, judging whether the user sells the number according to the analysis result, and when the user sells the number, deleting the card number information in the subscription list and the subscription detail list of the user by the user synchronization module, and returning a normal processing result to the user side module for outputting;
and when the user does not sell the number, returning the abnormal message result to the user side module for outputting.
Further, the banking business one-stop signing system is configured to execute a charging record generation process, where the charging record generation process includes the following steps:
the message platform module judges whether the number of days elapsed since the initial charging time of the contract signing record is less than 28 days;
when the number of days elapsed since the initial charging time of the subscription record is less than 28 days, the message platform module inquires the subscription data of the user based on the actual number of days elapsed; otherwise, inquiring the subscription data based on any one of the days 28, 29, 30 and 31;
the message platform module judges whether the current date is the fee deduction time or not based on the initial charging time, and if not, the charging record is filtered;
if yes, setting specific fee deduction time, and judging whether the user enjoys the preference by the message platform module; if so, forming a charging record based on the discount deduction amount; otherwise, forming a charging record based on the original amount;
and the message platform module stores the charging record into a database.
Further, the banking business one-stop subscription system is used for executing a deduction file generation process, and the deduction file generation process comprises the following steps:
the message platform module generates a cost flow record based on the current date;
the message platform module writes the expense flow records into local files in batches;
the message platform module sends a fee deduction file to the core system module through a TFT protocol; if the transmission is successful, the core system module stores the deduction file in a core deduction file storage directory; if the transmission fails, the deduction file is retransmitted after waiting for the first preset time;
the message platform module sends a fee deduction notice to the core system module based on the ESB agent forwarding module; if the transmission is successful, the core system module stores the fee deduction file and the fee deduction notice in the database; and if the transmission fails, the fee deduction notice is retransmitted after waiting for a second preset time.
Further, the banking business one-stop sign-up system is configured to execute a charging result file processing procedure, where the charging result file processing procedure includes the following steps:
the message platform module acquires the result file record, and sends a charging result file generation judgment request to the core system module through the ESB agent forwarding module; if the transmission is successful, the core system module judges whether a charging result file is generated or not based on the result file record; if the sending fails, the charging result file is sent again to generate a judgment request after waiting for a third preset time;
the message platform module downloads the charging result file to the local through a TFT protocol; if the downloading fails, the charging result file is downloaded again after waiting for a fourth preset time;
the message platform module reads a charging file record, wherein the charging file record comprises a fee deduction success record and a fee deduction failure record;
for the fee deduction success record, the message platform module stores the running water information recorded by the fee deduction success record into a database, and deletes the backup running water information;
for the fee deduction failure record, the message platform model sends a fee deduction failure message to the user, updates the flow information and judges whether the fee deduction failure times is greater than a first threshold value or not;
when the number of times of fee deduction failure is larger than a first threshold value, the user is contracted, the fee deduction card of the user and the initial charging time are updated, and the fee deduction card and the initial charging time are written into a database;
and when the fee deduction failure times are smaller than the first threshold value, adjusting the fee deduction time, positioning the fee deduction time in the next fee deduction period, and writing the fee deduction time into the database.
The embodiment of the invention has the following beneficial effects: the one-stop signing system for banking business can reduce data interaction with a core system and objectively improve the processing efficiency of banking business by providing unified signing, contracting maintenance, card changing and card selling, charging record generation, fee deduction file generation and bank charging result file processing flows. The invention sets a uniform message platform module and integrates various signing services, thereby integrating message sending services and improving the message management efficiency.
Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the description below are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
Fig. 1 is a subscription flow chart of a banking one-stop subscription system according to the present invention;
fig. 2 is a flowchart of a contract-resolving process of a banking one-stop sign-up system according to the present invention;
fig. 3 is a subscription maintenance flow chart of a banking one-stop subscription system according to the present invention;
fig. 4 is a flow chart of card changing and selling of a one-stop signing system of banking business according to the present invention;
fig. 5 is a flow chart of generating a charging record of a banking one-stop subscription system according to the present invention;
fig. 6 is a flowchart of generating a fee deduction file of a banking one-stop subscription system according to the present invention;
fig. 7 is a flowchart of processing a charging result file in a banking one-stop sign-up system according to the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more clearly understood, the present application is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The embodiment introduces a banking business one-stop signing system, which comprises the following modules:
the client module is used for receiving the operation instruction input by the user and outputting a message to the user after the transaction related to the operation instruction input by the user is finished;
the system comprises a channel module, a channel module and a processing module, wherein the channel module is used for providing a channel interface which is used for determining a transaction related to an operation instruction input by a user;
the message platform module is used for executing corresponding affairs by using an operation instruction input by a user to obtain an output message corresponding to the affairs;
the core system module is used for registering transaction information;
and the ECIF docking module is used for docking with the ECIF module in the bank system to acquire user information.
The signing service is that the bank collects short message fee monthly rental mode to provide short message service for the user, the user transacts the signing service with the bank in a counter/online mode, and when the fund on the account of the user changes, the user informs the user of information such as specific amount, account moving time and the like in a short message mode. Therefore, when abnormal fund change occurs in the card account, the user can check and track the account in time and recover the fund loss in time.
For banks, the capital flow direction of a user is recorded clearly through a signing service, the related records can be called quickly when the user needs to check accounts, in addition, accurate marketing can be carried out according to the consumption level of the user through a short message signing service, two different marketing modes are adopted for signed users and non-signed users, and marketing activities of products in the banks are further realized.
The main signing process is to provide a service interface for the user to input card number/ID card/mobile phone number/signed package (preference) and other information via other terminals such as counter to process the signing, and then store the signed package into the system. Message service process after signing: after the signing card generates account transaction, the system inquires whether the card signs the signature or not and whether the transaction amount meets the requirement or not, triggers a short message, and successfully sends the short message to the user.
The related service of the subscription matching comprises the following steps: contract signing, contract releasing, contract information changing, fee deducting, discount information, contract signing record, fee deducting record and the like. The invention provides a one-stop signing system covering signing, contracting relief, signing information change, fee deduction, preferential information, signing record and fee deduction record, which is convenient for users and banking business.
The following describes the flow of executing various services in the present invention in an embodiment.
Example 1
This embodiment describes a subscription process of a banking one-stop subscription system. As shown in fig. 1, the operation instruction includes subscription information, the channel interface includes a subscription transaction interface, the transaction includes a subscription transaction, and the output message includes a subscription result; the banking business one-stop signing system is used for executing a signing process, and the signing process comprises the following steps:
s110, a user side module receives subscription information;
s120, the channel module authenticates the subscription information, provides a subscription transaction interface after the authentication is passed, and inputs the subscription information into the message platform module;
s130, executing a signing transaction by the message platform module to obtain a signing result;
and S140, the user side module outputs the signing result.
The signing transaction specifically comprises the following steps:
s131, checking a signing record of a user, and determining whether the user is a personal account;
s132, when the user is a personal account, determining whether the user is a core authentication mobile phone number;
s133, when the user is not a personal account or is a core authentication mobile phone number, determining whether a bank card number and a message type input by the user exist;
s134, when the bank card number and the message type selected by the user do not exist, judging that the signing is successful, and outputting the successful signing as a signing result;
and S135, when the user does not authenticate the mobile phone number for the core or the bank card number and the message type selected by the user are determined to be existed, judging that the signing fails, and outputting the signing failure as a signing result.
Before the step S134 determines that the subscription is successful, the method further includes the following steps:
s133-1, determining a fee deduction mode, and setting the bank card input by the user as a fee deduction card when the bank card input by the user is the first card, or setting the bank card input by the user as a non-fee deduction card;
s133-2, updating the address book of the user, and adding a signing label in the address book.
After determining that the subscription is successful, step S134 further includes the steps of:
s134-1, determining whether the message type input by the user is the first message type signed by the user, if so, setting a callback core for the subscription. The step of calling back the core in this embodiment is to notify the subscription result of the user to the core system module in real time in an interface form.
After the step S130 obtains the signing result, the method further includes a step of processing the signing result, and the step of processing the signing result specifically includes the following steps:
s136, obtaining a signing result;
s137, the message platform module sends a signing result through a message interface;
s138, checking whether the subscription sets a callback core; if yes, registering the signing result in the core system module;
s139, checking whether the bank card input by the user is a first card; if yes, generating preferential information for the user and sending the preferential information to the user.
In this embodiment, data processing in the signed transaction is basically performed in the memory, so that an effect of fast release can be achieved, and a deadlock or a queue waiting situation is avoided. Subsequent processing of the obtained signing result is carried out through MQ asynchronous decoupling processing; the signing result is arranged in the MQ queue, the information required by the context processed in the signing transaction is converted into 'signing result information' to be output, the processes of sending the information, informing the ECIF signing result, generating preferential information and the like are independently and asynchronously processed in different consumption groups, and the congestion of the service is avoided.
Example 2
This embodiment describes a contract-resolving process of a banking one-stop subscription system. As shown in fig. 2, the operation instruction includes the contract information, the channel interface includes a contract transaction interface, the transaction includes a contract transaction, and the output message includes a contract result; the banking business one-stop signing system is used for executing a contract-resolving process, and the contract-resolving process comprises the following steps:
s210, a user side module receives contract-release information;
s220, the channel module authenticates the contract-clearing information, provides a contract-clearing transaction interface after the authentication is passed, and inputs the contract-clearing information into the message platform module;
s230, the message platform module executes the reduction affair to obtain a reduction result;
and S240, the client module outputs the contracting result.
In step S230, the transaction is contracted, which specifically includes the following steps:
s231, checking a signing record of the user, and determining whether the bank card number and the message type input by the user exist;
s232, when the bank card number and the message type input by the user exist, judging that the contract-resolving is successful, and outputting the success of the contract-resolving as a judgment result;
s233, when determining that the bank card number and the message type input by the user do not exist, determining that the reduction fails, and outputting the reduction failure as a determination result;
step S232 further includes the following steps before determining that the solution is successful:
s231-1, checking a signing record migration history table, and determining whether the bank card input by the user is a fee deducting card, if so, setting other bank cards of the user as fee deducting cards;
s231-2, updating the address list of the user, and deleting the signing label from the address list;
after the step S232 determines that the subscription is successful, the method further includes the following steps:
s232-1, determining whether the message type input by the user is the last message type of the user; if yes, resetting the callback core for the user.
After obtaining the result of the reduction, the step S230 further includes a step of processing the result of the reduction, and the step of processing the result of the reduction specifically includes the following steps:
s234, obtaining a reduction result;
s235, the message platform module sends a contracting result through a message interface;
s236, checking whether the callback core is reset or not; if yes, the result of the solution is registered in the core system module.
In this embodiment, the resolution transaction is also set in the memory for processing, and the subsequent processing of the subscription result is performed through the MQ asynchronous decoupling processing, asynchronous processing message sending, ECIF resolution result notification, and other processes.
Example 3
The embodiment describes a subscription maintenance process of a banking one-stop subscription system. As shown in fig. 3, the operation instruction includes subscription maintenance information, the channel interface includes a subscription maintenance transaction interface, the transaction includes a subscription maintenance transaction, and the output message includes a subscription maintenance result; the banking business one-stop signing system is used for executing a signing maintenance process, and the signing process comprises the following steps:
s310, a user side module receives subscription maintenance information;
s320, authenticating the signing maintenance information by the channel module, providing a signing maintenance transaction interface after the authentication is passed, and inputting the signing maintenance information into the message platform module;
s330, executing a signing maintenance transaction by the message platform module to obtain a signing maintenance result;
and S340, the user side module outputs the signing maintenance result.
In step S330, signing a maintenance transaction specifically includes the following steps:
s331, checking a signing record of a user, and determining whether the user is a personal account;
s332, when the user is a personal account, determining whether the user is a core authentication mobile phone number;
s333, when the user is not a personal account or is a core authentication mobile phone number, determining whether a bank card number and a message type input by the user exist;
s334, when the bank card number and the message type selected by the user exist, judging that the signing maintenance is successful, and outputting the successful signing maintenance as a signing maintenance result;
s335, when the user does not authenticate the mobile phone number for the core or the bank card number and the message type selected by the user do not exist, judging that the signing maintenance fails, and outputting the signing maintenance failure as a signing maintenance result;
before the step S334 is determined that the subscription maintenance is successful, the method further includes the following steps:
s333-1, modifying the user signing record;
s333-2, modifying the fee deduction mode of the user;
s333-3, modifying the displayed balance of the user.
Step S334, after obtaining the contract maintenance result, further includes a step of processing the contract maintenance result, and the step of processing the contract maintenance result specifically includes the following steps:
s334-1, obtaining a signing maintenance result;
s334-2, the message platform module sends a signing maintenance result through a message interface;
s334-3, checking whether the subscription calls back the core; if yes, registering the contract maintenance result in the core system module.
The embodiment supports updating of the terminal number, the payment mode and the display balance when the subscription is maintained.
Example 4
The embodiment describes a card changing and selling process of a banking one-stop signing system. As shown in fig. 4, the banking-service one-stop signing system further comprises a user synchronization module, where the user synchronization module is configured to synchronize user signing information between the one-stop signing system and the banking system; the banking business one-stop signing system is used for executing a card changing and selling process, and the card changing and selling process comprises the following steps:
s410, the ECIF docking module sends a card changing and selling instruction to the bank system; the user synchronization module receives a data change message sent back by the bank system;
s420, analyzing the data change message by the user synchronization module to obtain an analysis result; the analysis result comprises an operation type, a core user number, a new card number and an old card number;
s430, judging whether the user changes the card or not according to the analysis result, updating the card number information in the subscription list and the subscription detail list of the user by the user synchronization module when the user changes the card, and returning a normal processing result to the user side module for outputting;
s440, when the user does not change the card, judging whether the user sells the number according to the analysis result, and when the user sells the number, deleting the card number information in the subscription list and the subscription detail list of the user by the user synchronization module, and returning a normal processing result to the user side module for outputting;
and S450, when the user does not sell the number, returning the abnormal message result to the user side module for outputting.
Example 5
The embodiment describes a charging record generation process of a banking one-stop subscription system. As shown in fig. 5, the charging record generation process includes the following steps:
s510, the message platform module judges whether the number of days elapsed since the initial charging time of the contract signing record is less than 28 days;
s520, when the number of days elapsed since the initial charging time of the subscription record is less than 28 days, the message platform module inquires the subscription data of the user based on the actual number of days elapsed; otherwise, inquiring the subscription data based on any one of the days 28, 29, 30 and 31;
s530, the message platform module judges whether the current date is the fee deduction time or not based on the initial charging time, and if not, the charging records are filtered;
s540, if yes, setting specific fee deduction time, and judging whether the user enjoys the preference by the message platform module; if so, forming a charging record based on the discount deduction amount; otherwise, forming a charging record based on the original amount;
and S550, the message platform module stores the charging record into a database.
In this embodiment, the data subscription list is specifically queried according to the conditions of whether to charge the account and the number of days to obtain the user subscription short message record information (the number of days of the initial charging time of the subscription record field is set to be in the range of 1-28 according to the service rule).
Secondly, judging whether the current time is the fee deduction time or not, and if not, directly filtering. Illustratively, the judgment rule is as follows: if the charging type is monthly payment, subtracting the charging starting time based on the current time, then taking the remainder by 100, and if the charging type is 0, indicating that the current time is the fee deduction time; if the charging type is a pack year, the charging starting time is subtracted from the current time, and then 10000 is used for surplus, and if the charging type is 0, the charging time is represented.
And judging whether the account is the preferential list and the preferential card again, if the account belongs to the preferential list and the preferential card, calculating the charging amount according to the corresponding discount, and if not, calculating the original charging amount.
4. And the charging records meeting the conditions are stored in a database fee deduction record table in batch and are used for charging file data sources.
In this embodiment, the start time of the charging record timing task is set to be from No. 1 to No. 28 a.m. 2 a.each month.
Example 6
The embodiment introduces a deduction file generation process of a banking one-stop subscription system. As shown in fig. 6, the banking one-stop subscription system is configured to execute a deduction file generation process, where the deduction file generation process includes the following steps:
s610, the message platform module generates a cost running record based on the current date;
s620, the message platform module writes the expense flow records into local files in batches;
s630, the message platform module sends a deduction file to the core system module through a TFT protocol; if the transmission is successful, the core system module stores the deduction file in a core deduction file storage directory; if the transmission fails, the deduction file is retransmitted after waiting for the first preset time;
s640, the message platform module sends a fee deduction notice to the core system module based on the ESB agent forwarding module; if the transmission is successful, the core system module stores the fee deduction file and the fee deduction notice in the database; and if the transmission fails, the fee deduction notice is retransmitted after waiting for a second preset time.
In this embodiment, the first and second preset times are set to 2 minutes.
In this embodiment, first, the database fee deduction record table is queried for the current time condition according to the charging time to obtain the corresponding fee deduction record. The deduction record types include: a record of initial deduction or failure of deduction and a retry number less than 3.
Secondly, the charging record is written into the charging file based on the batch mode.
And thirdly, uploading the charging file based on an ESB file transfer protocol, and informing a core system of processing the uploaded file by a message.
And finally, after the message notification is successful, moving the charging file to an appointed directory, and simultaneously constructing file record information to a database fee deduction file table and a charging result file table.
In this embodiment, the start of the charging file generation timing task is set to 6 am, no. 1 to 28 per month.
Example 7
This embodiment describes a processing flow of a charging result file in a banking one-stop subscription system. As shown in fig. 7, the banking-service one-stop subscription system is configured to execute a charging result file processing procedure, where the charging result file processing procedure includes the following steps:
s710, the message platform module acquires a result file record and sends a charging result file generation judgment request to the core system module through the ESB proxy forwarding module; if the transmission is successful, the core system module judges whether a charging result file is generated or not based on the result file record; if the transmission fails, the charging result file is retransmitted to generate a judgment request after waiting for a third preset time;
s720, the message platform module downloads the charging result file to the local through a TFT protocol; if the downloading fails, the charging result file is downloaded again after waiting for a fourth preset time;
s730, the message platform module reads a charging file record, wherein the charging file record comprises a fee deduction success record and a fee deduction failure record;
s740, for the fee deduction success record, the message platform module stores the running water information recorded by the fee deduction success record into a database, and deletes the backup running water information;
s750, for the fee deduction failure record, the message platform model sends a fee deduction failure message to a user, updates the flow information and judges whether the fee deduction failure times are larger than a first threshold value or not;
s760, when the number of times of fee deduction failure is larger than a first threshold value, the user is contracted, the fee deduction card of the user and the initial charging time are updated, and the time is written into a database;
and S770, when the number of times of fee deduction failure is smaller than a first threshold value, adjusting the fee deduction time, positioning the fee deduction time in the next fee deduction period, and writing the fee deduction time into a database.
In this embodiment, the first threshold is set to 3, that is, the billing is not performed after the number of times of fee deduction failures reaches 3 times, but the contract is directly solved. In this embodiment, first, the record information of the database deduction file table is queried, and then the message requests the core to determine whether the charging result file is generated.
Secondly, inquiring the recording information of the charging result file if the response is successful, and downloading the result file based on the ESB file transfer protocol, wherein the result file comprises a successfully processed file and a unsuccessfully processed file.
Wherein, the following steps are used for processing the successful file: and traversing the file record information, updating the backup charging record information to the historical fee deduction file table in batches based on the charging account information, and deleting the fee deduction file table charging data in batches.
The following steps are used for processing the failure file: traversing file record information, updating backup charging record information to a historical fee deduction file table in batches based on the charging account information, judging whether to delete fee deduction records or not according to a fee deduction file table number field, deleting the fee deduction records in batches if the number of times is 3, and recalculating the charging time and updating the table records if the number of times is not 3.
Thirdly, when the short message charging fails, short message notification is carried out based on the asynchronous thread.
And finally, carrying out the contracting relieving operation when the short message charging times is 3, and carrying out the contracting relieving operation based on an ESB interface, wherein the step is asynchronous processing.
In this embodiment, the start time of the charging result file processing timing task is set to 12 am, no. 1-28 per month.
It should be noted that, in this specification, each embodiment is described in a progressive manner, and each embodiment focuses on differences from other embodiments, and portions that are the same as and similar to each other in each embodiment may be referred to. The multi-product signing method and the multi-product signing device provided by the embodiment of the invention have the same implementation principle and the same technical effect as the method embodiment, and for brief description, the corresponding content in the method embodiment can be referred to where the device embodiment is not mentioned.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method can be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present invention. 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 and/or flowchart illustration, and combinations of blocks in the block diagrams and/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.
In addition, each functional module or unit in each embodiment of the present invention may be integrated together to form an independent part, or each module may exist alone, or two or more modules may be integrated to form an independent part.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions or without necessarily implying any relative importance. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising one of 8230; \8230;" 8230; "does not exclude the presence of additional like elements in a process, method, article, or apparatus that comprises the element.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention. It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims. In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
While embodiments of the present invention have been shown and described, it will be understood by those of ordinary skill in the art that: various changes, modifications, substitutions and alterations can be made to the embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the claims and their equivalents.
Claims (14)
1. A banking one-stop signing system is characterized by comprising the following modules:
the client module is used for receiving the operation instruction input by the user and outputting a message to the user after the transaction related to the operation instruction input by the user is finished;
the channel module is used for providing a channel interface which is used for determining a transaction related to an operation instruction input by a user;
the message platform module is used for executing corresponding affairs by using an operation instruction input by a user to obtain an output message corresponding to the affairs;
the core system module is used for registering transaction information;
and the ECIF docking module is used for docking with the ECIF module in the bank system to acquire user information.
2. The banking one-stop sign-up system according to claim 1, wherein the operation instruction includes sign-up information, the channel interface includes a sign-up transaction interface, the transaction includes a sign-up transaction, and the output message includes a sign-up result; the banking business one-stop signing system is used for executing a signing process, and the signing process comprises the following steps:
the user side module receives the subscription information;
the channel module authenticates the signing information, provides a signing transaction interface after the authentication is passed, and inputs the signing information into the message platform module;
the message platform module executes a signing transaction to obtain a signing result;
and the user side module outputs the signing result.
3. The banking one-stop signing system according to claim 2, wherein the signing transaction specifically comprises the steps of:
checking a signing record of a user and determining whether the user is a personal account;
when the user is a personal account, determining whether the user is a core authentication mobile phone number;
when the user is not a personal account number or the user is a core authentication mobile phone number, determining whether a bank card number and a message type input by the user exist;
when the bank card number and the message type selected by the user do not exist, judging that the signing is successful, and outputting the successful signing as a signing result;
when the user does not authenticate the mobile phone number for the core or the bank card number and the message type selected by the user are determined to exist, judging that the signing fails, and outputting the signing failure as a signing result;
before the subscription is judged to be successful, the method further comprises the following steps:
determining a fee deduction mode, and setting the bank card input by the user as a fee deduction card when the bank card input by the user is a first card, or setting the bank card input by the user as a non-fee deduction card;
updating an address book of a user, and newly adding a signing label in the address book;
after the subscription is judged to be successful, the method further comprises the following steps:
and determining whether the message type input by the user is the first message type signed by the user, if so, setting a callback core for the subscription.
4. The banking one-stop sign-up system according to claim 3, wherein, after obtaining the sign-up result,
the method further comprises a step of processing the signing result, wherein the step of processing the signing result specifically comprises the following steps:
acquiring a signing result;
the message platform module sends a signing result through a message interface;
checking whether a subscription sets a callback core; if yes, registering the signing result in the core system module;
checking whether the bank card input by the user is the first card; if yes, generating preferential information for the user and sending the preferential information to the user.
5. The banking one-stop sign-up system according to claim 1, wherein the operation instruction includes a resolution information, the channel interface includes a resolution transaction interface, the transaction includes a resolution transaction, and the output message includes a resolution result; the banking business one-stop signing system is used for executing a contract-resolving process, and the contract-resolving process comprises the following steps:
the client module receives the contract-release information;
the channel module authenticates the contract-resolving information, provides a contract-resolving transaction interface after the authentication is passed, and inputs the contract-resolving information into the message platform module;
the message platform module executes the reduction transaction to obtain a reduction result;
and the client module outputs the solution result.
6. The banking one-stop sign-up system according to claim 5, wherein the contracting transaction comprises the following steps:
checking a signing record of a user, and determining whether a bank card number and a message type input by the user exist;
when the bank card number and the message type input by the user exist, judging that the contract-resolving is successful, and outputting the success of the contract-resolving as a judgment result;
when the bank card number and the message type input by the user are determined to be absent, judging that the settlement fails, and outputting the settlement failures as a judgment result;
before the judgment of successful solution, the method also comprises the following steps:
checking a signing record migration history table, determining whether a bank card input by a user is a fee deduction card, if so, setting other bank cards of the user as fee deduction cards;
updating an address book of a user, and deleting a signing label from the address book;
after the subscription is judged to be successful, the method further comprises the following steps:
determining whether the message type input by the user is the last message type of the user; if yes, resetting the callback core for the user.
7. The banking one-stop sign-up system according to claim 6, wherein, after obtaining the result of the resolution,
the method also comprises a step of processing the result of the reduction, and the step of processing the result of the reduction specifically comprises the following steps:
obtaining a result of the reduction;
the message platform module sends the result of the reduction through a message interface;
checking whether a callback core is reset; if yes, the result of the solution is registered in the core system module.
8. The banking one-stop sign-up system according to claim 1, wherein the operation instruction includes sign-up maintenance information, the channel interface includes a sign-up maintenance transaction interface, the transaction includes a sign-up maintenance transaction, and the output message includes a sign-up maintenance result; the banking business one-stop signing system is used for executing a signing maintenance process, and the signing process comprises the following steps:
the user end module receives the signing maintenance information;
the channel module authenticates the signing maintenance information, provides a signing maintenance transaction interface after the authentication is passed, and records the signing maintenance information into the message platform module;
the message platform module executes a signing maintenance transaction to obtain a signing maintenance result;
and the user side module outputs the signing maintenance result.
9. The banking one-stop sign-up system according to claim 8, wherein the sign-up maintenance transaction specifically includes the steps of:
checking a signing record of a user and determining whether the user is a personal account;
when the user is a personal account, determining whether the user is a core authentication mobile phone number;
when the user is not a personal account number or the user is a core authentication mobile phone number, determining whether a bank card number and a message type input by the user exist;
when the bank card number and the message type selected by the user exist, judging that the signing maintenance is successful, and outputting the successful signing maintenance as a signing maintenance result;
when the user does not authenticate the mobile phone number for the core or the bank card number and the message type selected by the user do not exist, judging that the signing maintenance fails, and outputting the signing maintenance failure as a signing maintenance result;
before the contract maintenance is judged to be successful, the method further comprises the following steps:
modifying the user subscription record;
modifying the fee deduction mode of the user;
the displayed balance of the user is modified.
10. The banking-service one-stop sign-on system according to claim 9, further comprising a step of processing a sign-on maintenance result after obtaining the sign-on maintenance result, wherein the step of processing the sign-on maintenance result specifically comprises the steps of:
acquiring a signing maintenance result;
the message platform module sends a signing maintenance result through a message interface;
checking whether the subscription calls back the core; if yes, registering the contract maintenance result in the core system module.
11. The banking one-stop signing system according to claim 1, further comprising a user synchronization module, wherein the user synchronization module is configured to synchronize user signing information between the one-stop signing system and the banking system; the banking business one-stop signing system is used for executing a card changing and selling process, and the card changing and selling process comprises the following steps:
the ECIF docking module sends a card changing and selling instruction to the bank system; the user synchronization module receives a data change message sent back by the bank system;
the user synchronization module analyzes the data change message to obtain an analysis result; the analysis result comprises an operation type, a core user number, a new card number and an old card number;
judging whether the user changes the card or not according to the analysis result, when the user changes the card, updating the card number information in the subscription list and the subscription detail list of the user by the user synchronization module, and returning a normal processing result to the user side module for outputting;
when the user does not change the card, judging whether the user sells the number according to the analysis result, and when the user sells the number, deleting the card number information in the subscription list and the subscription detail list of the user by the user synchronization module, and returning a normal processing result to the user side module for outputting;
and when the user does not sell the number, returning the message abnormal result to the user side module for outputting.
12. The banking-service one-stop signing system according to claim 1, wherein the banking-service one-stop signing system is configured to execute a charging record generation process, and the charging record generation process comprises the following steps:
the message platform module judges whether the number of days elapsed since the initial charging time of the contract signing record is less than 28 days;
when the number of days elapsed since the initial charging time of the subscription record is less than 28 days, the message platform module inquires the subscription data of the user based on the actual number of days elapsed; otherwise, inquiring the subscription data based on any one of the days 28, 29, 30 and 31;
the message platform module judges whether the current date is the fee deduction time or not based on the initial charging time, and if not, the charging record is filtered;
if yes, setting specific fee deduction time, and judging whether the user enjoys the preference by the message platform module; if so, forming a charging record based on the discount deduction amount; otherwise, forming a charging record based on the original amount;
and the message platform module stores the charging record into a database.
13. The banking business one-stop signing system according to claim 1, wherein the banking business one-stop signing system is configured to execute a deduction file generation process, and the deduction file generation process comprises the following steps:
the message platform module generates a cost flow record based on the current date;
the message platform module writes the expense flow records into local files in batches;
the message platform module sends a deduction file to the core system module through a TFT protocol; if the transmission is successful, the core system module stores the deduction file in a core deduction file storage directory; if the transmission fails, the deduction file is retransmitted after waiting for the first preset time;
the message platform module sends a fee deduction notice to the core system module based on the ESB agent forwarding module; if the transmission is successful, the core system module stores the fee deduction file and the fee deduction notice in a database; and if the transmission fails, the fee deduction notice is retransmitted after waiting for a second preset time.
14. The banking-service one-stop signing system according to claim 1, wherein the banking-service one-stop signing system is configured to execute a charging result file processing procedure, and the charging result file processing procedure comprises the following steps:
the message platform module acquires the result file record, and sends a charging result file generation judgment request to the core system module through the ESB agent forwarding module; if the transmission is successful, the core system module judges whether the charging result file is generated or not based on the result file record; if the sending fails, the charging result file is sent again to generate a judgment request after waiting for a third preset time;
the message platform module downloads the charging result file to the local through a TFT protocol; if the downloading fails, the charging result file is downloaded again after waiting for a fourth preset time;
the message platform module reads a charging file record, wherein the charging file record comprises a fee deduction success record and a fee deduction failure record;
for the fee deduction success record, the message platform module stores the running water information recorded successfully in fee deduction into the database, and deletes the backup running water information;
for the fee deduction failure record, the message platform model sends a fee deduction failure message to the user, updates the flow information and judges whether the fee deduction failure times is greater than a first threshold value or not;
when the number of times of fee deduction failure is larger than a first threshold value, the user is contracted, the fee deduction card of the user and the initial charging time are updated, and the fee deduction card and the initial charging time are written into a database;
and when the times of fee deduction failure are smaller than a first threshold value, adjusting the fee deduction time, positioning the fee deduction time in the next fee deduction period, and writing the fee deduction time into the database.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211296575.3A CN115689706A (en) | 2022-10-21 | 2022-10-21 | One-stop type banking business signing system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211296575.3A CN115689706A (en) | 2022-10-21 | 2022-10-21 | One-stop type banking business signing system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115689706A true CN115689706A (en) | 2023-02-03 |
Family
ID=85067131
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211296575.3A Pending CN115689706A (en) | 2022-10-21 | 2022-10-21 | One-stop type banking business signing system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115689706A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115860745A (en) * | 2023-03-02 | 2023-03-28 | 深圳市深圳通有限公司 | Secret payment-free signing method, gateway equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6990466B1 (en) * | 2000-08-08 | 2006-01-24 | International Business Machines Corporation | Method and system for integrating core banking business processes |
| CN101877158A (en) * | 2010-03-23 | 2010-11-03 | 苏州德融嘉信信用管理技术有限公司 | Front service platform of bank and operation processing method thereof |
| CN107958551A (en) * | 2017-12-29 | 2018-04-24 | 福建省农村信用社联合社 | A kind of full channel remote centralized authoring system of the expansible bank of business |
-
2022
- 2022-10-21 CN CN202211296575.3A patent/CN115689706A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6990466B1 (en) * | 2000-08-08 | 2006-01-24 | International Business Machines Corporation | Method and system for integrating core banking business processes |
| CN101877158A (en) * | 2010-03-23 | 2010-11-03 | 苏州德融嘉信信用管理技术有限公司 | Front service platform of bank and operation processing method thereof |
| CN107958551A (en) * | 2017-12-29 | 2018-04-24 | 福建省农村信用社联合社 | A kind of full channel remote centralized authoring system of the expansible bank of business |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115860745A (en) * | 2023-03-02 | 2023-03-28 | 深圳市深圳通有限公司 | Secret payment-free signing method, gateway equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8498914B2 (en) | Method and system for increasing client participation in a network-based bill pay service | |
| US20190318424A1 (en) | Systems and methods for implementing a blockchain-based money transfer | |
| CN105868915B (en) | Service evaluation system based on mobile internet service application | |
| AU2011237500B2 (en) | Facilitating billing of embedded applications | |
| US7848736B2 (en) | Package billing for micro-transactions | |
| US20080215456A1 (en) | Systems and methods for facilitating exchanges of items | |
| US7603313B2 (en) | Charging system and charging method | |
| WO2019196231A1 (en) | Daily payment method and system based on fund share redemption-to-payment transfer | |
| US20150088709A1 (en) | Bill payment by image recognition | |
| JP2001516105A (en) | Electronic invoice creation and payment system | |
| CN105931094B (en) | Service system based on mobile internet terminal | |
| US20100057742A1 (en) | Mrw interface and method for support of merchant data processing | |
| CN115689706A (en) | One-stop type banking business signing system | |
| CN110889686A (en) | Multi-level account data processing method, device, equipment and readable storage medium | |
| US8744998B2 (en) | FTP device and method for merchant data processing | |
| US20100077464A1 (en) | Merchant device and method for support of merchant data processing | |
| JP5148161B2 (en) | Card usage notification system | |
| CN111429125B (en) | Account management method and device, storage medium and electronic equipment | |
| CN110807679B (en) | Taxi invoice generation method and device based on blockchain | |
| CN113379523A (en) | Bill generation method, device, medium and electronic equipment | |
| CN110009496B (en) | Recharging and extracting method, device and system for block voucher | |
| CN113706045B (en) | Funds payment method, apparatus, device, medium and program product | |
| JP2002082870A (en) | System and server for information bulletin board and recording medium with information bulletin board program recorded thereon | |
| US11587115B2 (en) | System and methods for facilitating content promotion transactions between content promoters and artists | |
| KR20160012452A (en) | Method of managing financial products and server performing the same |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20230203 |