Method, system, device, storage medium and product for remittance
By receiving and processing customers’ remittance requests, judging account balances and queries regularly, the repeated input problem caused by insufficient remittance account balances is solved, the remittance process is optimized, and the customer’s time is saved.
Patent Information
- Application Number
- CN202110851256.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-07-27
- Publication Date
- 2024-12-24
- Estimated Expiration
- 2041-07-27
AI Technical Summary
When a customer handles remittance business through the client, if the remittance account balance is insufficient, the existing technology will cause the remittance request to fail, and the customer needs to re-enter the information, resulting in a cumbersome process and a waste of time.
Provide a method to receive a customer's remittance request instruction, determine whether the request time exceeds the transaction time, and call the deduction interface if it does not exceed it. If the deduction fails, determine the reason for the insufficient balance, generate key information and record the pending table, and regularly Check the account balance until the balance is sufficient before deduction is made to avoid repeated input of information by customers.
The remittance operation steps have been optimized, which reduces the remittance of customers, saves customers' time, and improves the efficiency of remittance.
Smart Images

Figure CN113506170B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the financial field, and in particular to a method, system, device, storage medium and product for remittance. Background Art
[0002] When a customer applies for a remittance through the client, the remittance request may fail due to insufficient balance in the current remittance account. The customer is required to replenish the amount in the remittance account, re-enter the necessary information, and then send the remittance request information again. During this process, the customer enters the same necessary information and verifies the information again, which wastes too much of the customer's time and makes the remittance procedure cumbersome. Summary of the invention
[0003] The present application aims to solve at least one of the technical problems existing in the prior art.
[0004] For example, the present application provides a method for remittance, through which the steps of the remittance operation can be optimized, making it convenient for customers to use and saving customers' time.
[0005] The first aspect of the present application provides a method for remittance, comprising the following steps:
[0006] Receive the customer's remittance request instruction and record the remittance request time t;
[0007] According to the remittance request instruction of the customer, obtaining the account information of the customer;
[0008] Determine whether the remittance request time t exceeds the transaction time;
[0009] When the remittance request time t does not exceed the transaction time, the debit message interface is called to deduct the customer's account;
[0010] When the deduction fails, determining whether the reason for the deduction failure is insufficient balance in the customer's account;
[0011] When it is confirmed that the customer's account balance is insufficient, a first operation is performed,
[0012] The first operation includes:
[0013] Generate key information according to the remittance request instruction of the customer and record it in a pending table; and
[0014] The customer's account balance is queried every time period T.
[0015] According to the method of the present application, when a customer encounters an insufficient balance in a remittance account during an overseas remittance operation, the customer can wait for the account to be replenished with a sufficient balance within a certain period of time, thereby avoiding the customer from repeatedly entering request information. This optimizes the steps of re-initiating a remittance due to a remittance failure caused by insufficient balance, making it more convenient for customers to use and saving their time.
[0016] Further, according to the remittance request instruction of the customer, the account information of the customer is obtained, including:
[0017] According to the remittance request instruction of the customer, the currency information in the customer account and the balance information of the currency are obtained.
[0018] Further, when the deduction fails, determining whether the reason for the deduction failure is insufficient balance in the customer's account includes:
[0019] When the deduction fails, an error is actively reported and a specified error code is generated, and it is determined based on the error code whether the account balance is insufficient.
[0020] Furthermore, it also includes:
[0021] When the sum of the remittance request time t and the mth time period T exceeds the transaction time, the customer's remittance request instruction is closed, and a completion mark is generated correspondingly at the key information in the pending table, where m is a positive integer.
[0022] Furthermore, the key information includes: transaction instruction serial number, remittance currency, remittance amount and remittance account.
[0023] Furthermore, the transaction time is specifically the settlement time of the remitted currency.
[0024] Furthermore, the customer's account balance is queried every time period T, including:
[0025] When it is confirmed that the customer's account balance is sufficient, a second operation is performed,
[0026] The second operation includes:
[0027] Calling the debit message interface and deducting the customer's account, and generating a completion mark corresponding to the key information in the pending table;
[0028] When it is confirmed that the account balance of the customer is insufficient, the first operation is performed.
[0029] Furthermore, the pending table contains a plurality of key information generated in accordance with the remittance request instruction, the plurality of key information are arranged in the order of generation time, and the customer's account balance is queried every time period T according to the generation order of the key information.
[0030] Furthermore, the customer's account balance is queried every time period T according to the generation order of key information, including:
[0031] When querying the customer's account balance according to the generation order of key information, the accounts marked as completed in the pending table are automatically skipped.
[0032] Furthermore, after confirming that the customer's account balance is insufficient and before performing the first operation, the method further includes determining whether the customer participates in a remittance waiting mechanism,
[0033] Wherein, the first operation is performed when the customer agrees to participate in the remittance waiting mechanism.
[0034] A second aspect of the present application provides a system for remittance, comprising: a receiving module, the receiving module is used to receive a customer's remittance request instruction and record the remittance request time t; an acquisition module, the acquisition module is used to: acquire the customer's account information according to the customer's remittance request instruction; a first judgment module, the first judgment module is used to judge whether the remittance request time t exceeds the transaction time; a first execution module, the first execution module is used to: when the remittance request time t does not exceed the transaction time, call the deduction message interface and deduct the customer's account; a second judgment module, the second judgment module is used to: when the deduction fails, judge whether the reason for the deduction failure is insufficient balance in the customer's account; a second execution module, the second execution module is used to: when it is confirmed that the customer's account balance is insufficient, execute a first operation, wherein the first operation includes: generating key information corresponding to the customer's remittance request instruction and recording it in a pending table; and querying the customer's account balance every time period T.
[0035] The third aspect of the present application provides an electronic device, comprising: one or more processors; a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors execute the above-mentioned method for remittance.
[0036] The fourth aspect of the present application also provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to execute the above-mentioned method for remittance.
[0037] The fifth aspect of the present application also provides a computer program product, including a computer program, which implements the above-mentioned method for remittance when executed by a processor.
[0038] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS
[0039] The above contents and other purposes, features and advantages of the present application will become more apparent through the following description of the embodiments of the present application with reference to the accompanying drawings, in which:
[0040] Figure 1 An application scenario diagram of the method for remittance according to an embodiment of the present application is schematically shown;
[0041] Figure 2 A flowchart of a method for remittance with a waiting mechanism according to an embodiment of the present application is schematically shown;
[0042] Figure 3 A flowchart for performing a first operation according to an embodiment of the present application is schematically shown;
[0043] Figure 4 A flowchart of a remittance method according to an embodiment of the present application is schematically shown;
[0044] Figure 5 A schematic diagram of a system for remittance according to an embodiment of the present application is shown; and
[0045] Figure 6 A block diagram of an electronic device suitable for implementing a remittance method according to an embodiment of the present application is schematically shown. DETAILED DESCRIPTION
[0046] Below, embodiments of the present application will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present application. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present application. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present application.
[0047] The terms used herein are only for describing specific embodiments and are not intended to limit the present application. The terms "include", "comprising", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.
[0048] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification, and should not be interpreted in an idealized or overly rigid manner.
[0049] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).
[0050] When a customer conducts a remittance transaction through the client, the remittance request may fail due to insufficient balance in the current remittance account. Generally, if the deduction fails, the transaction will be closed, and the customer needs to first replenish the amount in the remittance account, then re-enter the necessary information, and initiate the remittance request instruction again. During this process, the customer needs to repeatedly enter the same necessary information as last time, and re-check whether the entered necessary information is correct, which will waste too much customer time and make the remittance procedure cumbersome.
[0051] The embodiments of the present application provide a method for remittance, which can optimize the steps of remittance operation, save the customer's secondary operation, facilitate customer use, and save the customer's time.
[0052] It should be noted that this application can be applied to bank remittance business in the financial field, and is not limited to domestic remittance or overseas remittance. Of course, it is also applicable to other remittance businesses, for example: implementing remittance on non-bank application software.
[0053] Figure 1 The diagram schematically shows an application scenario diagram of interaction between a customer and a server when remitting money through a terminal device according to an embodiment of the present application.
[0054] like Figure 1 As shown, the application scenario 100 according to this embodiment may include domestic or overseas remittance business of a bank. The network 104 is used to provide a medium for a communication link between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.
[0055] Clients can use terminal devices 101, 102, 103 to interact with server 105 through network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only examples).
[0056] The terminal devices 101 , 102 , and 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, and desktop computers.
[0057] The server 105 may be a server that provides various services, such as a background management server (only an example) that provides support for websites browsed by clients using the terminal devices 101, 102, and 103. The background management server may analyze and process the received data such as client requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to client requests) to the terminal device.
[0058] It should be noted that the method for remittance provided in the embodiment of the present application can generally be performed by the server 105. Accordingly, the system for remittance provided in the embodiment of the present application can generally be arranged in the server 105. The method for remittance provided in the embodiment of the present application can also be performed by a server or server cluster that is different from the server 105 and can communicate with the terminal device 101, 102, 103 and / or the server 105. Correspondingly, the device for remittance provided in the embodiment of the present application can also be arranged in a server or server cluster that is different from the server 105 and can communicate with the terminal device 101, 102, 103 and / or the server 105.
[0059] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.
[0060] The following will be based on Figure 1 The scene described by Figure 2-Figure 4 The method for remittance in the embodiment of the application is described in detail.
[0061] Figure 2 A flowchart of a method for remittance according to an embodiment of the present application is schematically shown.
[0062] like Figure 2 As shown, according to one embodiment of the present application, the method includes steps S210 to S260.
[0063] In step S210, a remittance request instruction from a customer is received and the remittance request time t is recorded.
[0064] When a client initiates a remittance request, the server receives the remittance request instruction issued by the client, and then records the current remittance request time t, where the request time t can be specific and accurate to seconds, that is, the year, month, day, hour, minute, and second of the initiation time of this remittance transaction is obtained.
[0065] After receiving the remittance request instruction and recording the request time, step S220 is executed.
[0066] In step S220, the customer's account information is obtained according to the customer's remittance request instruction, wherein the account information includes: user name, account number, all currency information in the account, and balance information of each currency.
[0067] After receiving the customer's remittance request, we can obtain the location, currency and other information of the account initiating the remittance and the account that needs to receive the remittance. Based on the currencies that the account that needs to receive the remittance can receive, we can determine what currency the account that issues the remittance request needs to remit, and based on the currency that needs to be remitted, we can inquire about the balance of the currency in the account that issues the remittance request.
[0068] After obtaining the customer's account information, execute step S230.
[0069] In step S230, it is determined whether the remittance request time t exceeds the transaction time, wherein the transaction time is specifically the settlement time of the remittance currency.
[0070] Banks need to clear the day's inflow and outflow business every day, including domestic and international clearing, so as to monitor and grasp the inflow and outflow of funds in a timely manner. During the clearing process, domestic transactions and international transactions will have different clearing times, and the clearing times of different currencies for international transactions are also different. Therefore, it is necessary to pay attention to whether the remittance request time t exceeds the transaction time. For this application, it is necessary to determine whether the currency that the customer wants to remit has not been cleared.
[0071] In one embodiment, after completing the checking of various items in the account to obtain the currency to be remitted, it is determined whether the request time t for the remittance exceeds the settlement time of this currency on the same day.
[0072] If the clearing has started, the system closes the transaction and determines that the remittance has failed; if the transaction time has not exceeded, step S240 is executed.
[0073] In step S240, when the request time t for the remittance does not exceed the transaction time, the debit message interface is called and the customer's account is deducted.
[0074] If the transaction time is not exceeded, the debit message interface is called to process the user's remittance request and the customer's account is deducted. The interface will feedback the processing result to the caller. The processing result includes: a success result and a failure result. After the account is deducted successfully, the success result is directly output, and the transaction is successful; after the account is deducted unsuccessfully, step S250 is executed.
[0075] In step S250, when the deduction fails, it is determined whether the reason for the failure is insufficient balance in the customer's account.
[0076] There are many reasons for the failure of deduction, such as: poor network signal or system upgrade and maintenance, abnormality in the account receiving the remittance, incorrect filling of the payee, insufficient balance in the remittance account, etc.
[0077] Among the many reasons for failed deductions, whether it is due to insufficient balance in the remittance account is mainly determined by the failure result fed back to the caller by the interface.
[0078] Specifically, when the deduction fails, an error is actively reported and a specified error code is generated, and it is determined based on the error code whether the account balance is insufficient.
[0079] The error code represents the reason why the deduction failed. Each error message has a specific error code. By interpreting the error code, you can get the reason why the remittance failed.
[0080] After confirmation, if the transaction failure is not caused by insufficient balance in the customer's account, the system determines that the transaction is completed and the remittance fails; if the transaction failure is caused by insufficient balance in the customer's account, execute step S260.
[0081] In step S260, when it is confirmed that the customer's account balance is insufficient, a first operation is performed, wherein the first operation includes steps S261 and S262, specifically, Figure 3 shown.
[0082] Specifically, in step S261, key information is generated according to the customer's remittance request instruction and recorded in a to-be-processed table.
[0083] After the transaction fails, the key information of the remittance will be recorded in the pending table and managed by the insufficient balance processing thread. The key information includes: transaction instruction number, remittance currency, remittance amount and remittance account.
[0084] In step S262, the customer's account balance is queried every time period T.
[0085] After the remittance fails, the customer's account balance is queried at an interval time period T. When it is found that the balance in the remittance account is still insufficient, the balance in the remittance account is queried again at an interval time period T.
[0086] In one embodiment, in the insufficient balance processing thread, the thread is started every 15 seconds, unprocessed instructions are scanned from the pending table, a remittance account is found according to the unprocessed instructions, and the balance in the remittance account is checked to see whether it is sufficient.
[0087] Of course, the specific value of the time period T can be set according to the actual needs of the bank, and can also be set according to the number of transactions that need to be processed in the pending table.
[0088] Furthermore, when the sum of the remittance request time t and the mth time period T exceeds the transaction time, the customer's remittance request instruction is closed, and a completion mark is generated correspondingly at the key information in the pending table, where m is a positive integer.
[0089] The sum of the remittance request time t and the mth time period T, that is, whether the time of querying the account balance exceeds the transaction time during the loop query of the pending table.
[0090] Before querying the balance in the remittance account each time, it is necessary to first determine whether the current time has exceeded the transaction time. If it has not exceeded the transaction time, execute the query on the balance in the remittance account; if it has exceeded the transaction time, directly close the customer's remittance request instruction and generate a completion mark at the key information in the pending table.
[0091] The above completion mark can be marked as transaction timeout, transaction failure, failure to remit within the specified time, etc.
[0092] Furthermore, when it is confirmed that the customer's account balance is sufficient, a second operation is performed, wherein the second operation includes: calling a debit message interface and deducting money from the customer's account, and generating a completion mark corresponding to the key information in the pending table.
[0093] The above completion mark can be marked as successful transaction, successful remittance, etc.
[0094] Of course, both failed and successful remittances need to be marked as completed at the key information in the pending table. The completion marks of the two can be the same, for example, both generate a "completed" mark; or they can be different, for example, failure generates a completion mark "transaction failed" and success generates a completion mark "transaction successful".
[0095] Since both failed and successful remittances need to be marked as completed at the key information in the pending table, it can be ensured that every transaction in the pending table has been processed, which is convenient for later inquiries.
[0096] When it is confirmed that the customer's account balance is insufficient, the first operation is performed, specifically, step S262 is performed to query the customer's account balance for each transaction in the pending table every time period T until a completion mark is generated for each transaction in the pending table.
[0097] Generally, the pending table contains multiple key information generated according to the remittance request instruction. The multiple key information are arranged in the order of generation time, and the customer's account balance is queried every time period T according to the generation order of the key information.
[0098] It can be understood that each key information corresponds to a transaction record of a remittance request. The order of the key information in the pending table is related to the time of initiating the remittance request transaction. During the processing, the corresponding account balance is queried according to the order of each transaction in the pending table. When the customer's account balance is queried according to the generation order of the key information, the account marked as completed in the pending table is automatically skipped.
[0099] The accounts marked as completed in the pending table can be understood as having been traded successfully or failed. In either case, the transaction has ended. Therefore, when scanning the accounts in the pending table, the accounts marked as completed are automatically skipped to save execution time.
[0100] According to a specific embodiment, after confirming that the customer's account balance is insufficient and before executing the first operation, the method also includes determining whether the customer participates in a remittance waiting mechanism, wherein the first operation is executed if the customer agrees to participate in the remittance waiting mechanism.
[0101] Of course, the customer can be asked first whether he wants to use the waiting mechanism. If the customer agrees to participate in the remittance waiting mechanism, the pending table channel will be opened, and key information can be generated in the pending table when the balance is insufficient. If the customer does not agree to participate in the remittance waiting mechanism, the current remittance will be processed, that is, when the balance is insufficient, the transaction will be directly judged as failed and closed.
[0102] According to the method of the present application, when a customer encounters an insufficient balance in a remittance account during an overseas remittance operation, the customer can wait for the account to be replenished with a sufficient balance within a certain period of time, which is equivalent to adding a remittance waiting mechanism, thereby avoiding the customer from repeatedly entering request information, optimizing the steps of re-initiating a remittance due to a remittance failure caused by insufficient balance, making it convenient for customers to use and saving their time.
[0103] Figure 4 The complete operation flow chart of the remittance method according to the embodiment of the present application is schematically shown.
[0104] like Figure 4As shown, this embodiment includes operations S310 to S391.
[0105] In operation S310, a remittance request instruction from a customer is received and the remittance request time t is recorded.
[0106] The request time t may be specific and accurate to seconds, that is, the year, month, day, hour, minute, and second of the initiation time of the remittance transaction is obtained.
[0107] In operation S320, the customer's account information is obtained according to the customer's remittance request instruction.
[0108] For example: based on the customer's remittance request, obtain their user name, account number, all currency information in the account, and balance information of each currency.
[0109] In operation S330, it is determined whether the request time t for the remittance exceeds the transaction time.
[0110] For example: according to the receiving currency of the receiving account, obtain the transaction deadline of this currency, and determine whether the remittance request time t exceeds the transaction deadline of this currency.
[0111] In operation S341, when the request time t for the remittance exceeds the transaction time, the transaction fails and the process ends.
[0112] In operation S342, when the request time t for the remittance does not exceed the transaction time, the debit message interface is called and the customer's account is deducted.
[0113] In operation S350, it is determined whether the deduction is successful.
[0114] In operation S351, the deduction is successful, the transaction is successful, and the process ends.
[0115] In operation S360, when the deduction fails, it is determined whether the reason for the deduction failure is insufficient balance in the customer's account.
[0116] After the deduction, the system will feedback to the caller whether the deduction is successful. If the deduction fails, an error code will be actively generated. Different error reports have different specified error codes. The cause of the failure can be determined based on the error code generated by the active error report.
[0117] In operation S361, the reason for the failure of the deduction is not due to insufficient account balance, the transaction fails, and the process ends.
[0118] In operation S370, after confirming that the customer's account balance is insufficient, it is determined whether the customer participates in the remittance waiting mechanism.
[0119] For example: During the customer operation, there will be a prompt option to participate in the remittance waiting mechanism. After the customer checks the option, this account will be included in the whitelist. When implementing account remittances, the process with the waiting mechanism will be followed. If the customer does not check the option, the current remittance process will proceed normally.
[0120] In operation S371, the customer does not agree to participate in the remittance waiting mechanism, the transaction fails, and the process ends.
[0121] Because the deduction from the remittance account failed during operation S350, and because the customer did not agree to participate in the waiting mechanism, the system directly determines that the transaction has failed and ends the process.
[0122] In operation S372, the customer agrees to participate in the remittance waiting mechanism, and key information is generated according to the customer's remittance request instruction and recorded in the pending table.
[0123] For example, after a transaction fails, the key information of the remittance is recorded in the pending table and managed by the insufficient balance processing thread. The key information includes: transaction instruction number, remittance currency, remittance amount and remittance account.
[0124] In operation S373, the customer's account balance is queried every time period T.
[0125] For example, after the first query on the customer's account balance, the second query on the customer's account balance is separated from the first query by a time period T.
[0126] Of course, within the interval time period T, all transactions in the pending table may have completed a sequential account query, or may still be queried one by one. The value of the time period T can be set according to the needs of the bank, or in order to prevent errors in the generation of the pending table, the time period T should not be less than the time it takes for the pending table to complete a cycle.
[0127] In operation S380, it is determined whether the sum of the remittance request time t and the mth time period T exceeds the transaction time.
[0128] The sum of the remittance request time t and the mth time period T, that is, whether the time of querying the account balance exceeds the transaction time during the loop query of the pending table.
[0129] In operation S381, when the transaction time is exceeded, the remittance request instruction of the customer is closed, and a completion mark is generated corresponding to the key information in the to-be-processed table, and the process ends.
[0130] If the transaction time is exceeded, the transaction is determined to have failed, and a completion mark is generated correspondingly at the key information in the pending table. When the pending table is cyclically queried for the balance again from the beginning, the transaction with the completion mark is skipped.
[0131] In operation S382, the customer's account balance is queried before the transaction time expires.
[0132] In operation S390, it is determined whether the customer's account balance is sufficient.
[0133] In operation S391, when it is confirmed that the customer's account balance is sufficient, the debit message interface is called to deduct the customer's account, and a completion mark is generated corresponding to the key information in the pending table to end the process.
[0134] After the deduction is successful, a completion mark is generated at the key information in the pending table. When the pending table is cyclically queried for the balance again, this transaction with the completion mark is skipped.
[0135] In operation S392, when it is confirmed that the customer's account balance is insufficient, return to operation S373.
[0136] For example: After checking all the accounts in the pending table in sequence, start checking the account balance again from the first account in the pending table that has not been marked as completed.
[0137] Based on the above-mentioned remittance method, the present application also provides a system for remittance. Figure 5 The device is described in detail.
[0138] Figure 5 The structural block diagram of a remittance system according to an embodiment of the present application is schematically shown.
[0139] like Figure 5 As shown, the system 400 for remittance in this embodiment includes a receiving module 410 , an acquiring module 420 , a first determining module 430 , a first executing module 440 , a second determining module 450 and a second executing module 460 .
[0140] The receiving module 410 is used to receive the remittance request instruction of the customer and record the remittance request time t. In one embodiment, the receiving module 410 can be used to perform the operation S210 described above, which will not be repeated here.
[0141] The acquisition module 420 is used to obtain the customer's account information according to the customer's remittance request instruction. In one embodiment, the acquisition module 420 can be used to perform the operation S220 described above, which will not be repeated here.
[0142] The first judgment module 430 is used to judge whether the request time t of the remittance exceeds the transaction time. In one embodiment, the first judgment module 430 can be used to perform the operation S230 described above, which will not be repeated here.
[0143] The first execution module 440 is used to call the debit message interface and deduct money from the customer's account when the request time t of the remittance does not exceed the transaction time. In one embodiment, the first execution module 440 can be used to execute the operation S240 described above, which will not be repeated here.
[0144] The second judgment module 450 is used to: when the deduction fails, determine whether the reason for the deduction failure is insufficient balance in the customer's account. In one embodiment, the second judgment module 450 can be used to perform the operation S250 described above, which will not be repeated here.
[0145] The second execution module 460 is used to: when confirming that the customer's account balance is insufficient, execute a first operation, wherein the first operation includes: generating key information corresponding to the customer's remittance request instruction and recording it in a pending table; and querying the customer's account balance every time period T. In one embodiment, the second execution module 460 can be used to execute the operation S260 described above, which will not be repeated here.
[0146] According to the system of the present application, the above steps S210-S260 can be completed using this system, so that when the customer's remittance account balance is insufficient during the overseas remittance operation, the customer can wait for the account to replenish the sufficient balance within a certain period of time, avoiding the customer from repeatedly entering request information due to remittance failure due to insufficient balance, optimizing the steps of re-initiating remittance due to remittance failure, facilitating customer use, and saving customers' time.
[0147] According to an embodiment of the present application, any multiple modules in the receiving module 410, the acquisition module 420, the first judgment module 430, the first execution module 440, the second judgment module 450, and the second execution module 460 can be combined in one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present application, at least one of the receiving module 410, the acquisition module 420, the first judgment module 430, the first execution module 440, the second judgment module 450, and the second execution module 460 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or by any one of the three implementation methods of software, hardware, and firmware, or by a suitable combination of any of them. Alternatively, at least one of the receiving module 410, the acquiring module 420, the first judging module 430, the first executing module 440, the second judging module 450 and the second executing module 460 may be at least partially implemented as a computer program module, which may execute corresponding functions when the computer program module is executed.
[0148] Figure 6 A block diagram of an electronic device suitable for implementing a remittance method according to an embodiment of the present application is schematically shown.
[0149] like Figure 6 As shown, the electronic device 500 according to an embodiment of the present application includes a processor 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage part 508 into a random access memory (RAM) 503. The processor 501 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 501 may also include an onboard memory for caching purposes. The processor 501 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present application.
[0150] In RAM 503, various programs and data required for the operation of electronic device 500 are stored. Processor 501, ROM 502 and RAM 503 are connected to each other via bus 504. Processor 501 performs various operations of the method flow according to the embodiment of the present application by executing the program in ROM 502 and / or RAM 503. It should be noted that the program can also be stored in one or more memories other than ROM 502 and RAM 503. Processor 501 can also perform various operations of the method flow according to the embodiment of the present application by executing the program stored in the one or more memories.
[0151] According to an embodiment of the present application, the electronic device 500 may further include an input / output (I / O) interface 505, which is also connected to the bus 504. The electronic device 500 may further include one or more of the following components connected to the I / O interface 505: an input portion 506 including a keyboard, a mouse, etc.; an output portion 507 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 508 including a hard disk, etc.; and a communication portion 509 including a network interface card such as a LAN card, a modem, etc. The communication portion 509 performs communication processing via a network such as the Internet. A drive 510 is also connected to the I / O interface 505 as needed. A removable medium 511, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 510 as needed, so that a computer program read therefrom is installed into the storage portion 508 as needed.
[0152] The present application also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present application is implemented.
[0153] According to an embodiment of the present application, the computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus or a device. For example, according to an embodiment of the present application, a computer-readable storage medium may include the ROM 502 and / or RAM 503 described above and / or one or more memories other than ROM 502 and RAM 503.
[0154] The embodiments of the present application also include a computer program product, which includes a computer program, and the computer program includes a program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the item recommendation method provided in the embodiments of the present application.
[0155] The above functions defined in the system / device of the embodiment of the present application are performed when the computer program is executed by the processor 501. According to the embodiment of the present application, the system, device, module, unit, etc. described above can be implemented by a computer program module.
[0156] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 509, and / or installed from the removable medium 511. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.
[0157] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 509, and / or installed from the removable medium 511. When the computer program is executed by the processor 501, the above functions defined in the system of the embodiment of the present application are performed. According to the embodiment of the present application, the system, device, means, module, unit, etc. described above can be implemented by a computer program module.
[0158] According to an embodiment of the present application, the program code for executing the computer program provided in the embodiment of the present application can be written in any combination of one or more programming languages, specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages include, but are not limited to, such as Java, C++, python, "C" language or similar programming languages. The program code can be executed completely on the client computing device, partially on the client device, partially on the remote computing device, or completely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the client computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (e.g., using an Internet service provider to connect through the Internet).
[0159] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the above-mentioned module, program segment or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0160] It will be appreciated by those skilled in the art that the features described in the various embodiments and / or claims of the present application may be combined in a variety of ways and / or combinations, even if such combinations or combinations are not explicitly described in the present application. In particular, without departing from the spirit and teachings of the present application, the features described in the various embodiments and / or claims of the present application may be combined in a variety of ways and / or combinations. All of these combinations and / or combinations fall within the scope of the present application.
[0161] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.
[0162] The embodiments of the present application are described above. However, these embodiments are only for the purpose of illustration, and are not intended to limit the scope of the present application. Although the embodiments are described above, this does not mean that the measures in the various embodiments cannot be used in combination. The scope of the present application is limited by the attached claims and their equivalents. Without departing from the scope of the present application, those skilled in the art may make various substitutions and modifications, which should all fall within the scope of the present application.
Claims
1. A method for remittance, characterized in that The following steps are involved: Receive the customer's remittance request instruction and record the remittance request time t; According to the remittance request instruction of the customer, obtain the account information of the customer and the location and acceptable currency of the account receiving the remittance; Determine whether the request time t of the remittance exceeds the transaction time, where the transaction time is specifically the settlement time of the remittance of the receivable currency; When the remittance request time t does not exceed the settlement time of the remittance of the acceptable currency, call the debit message interface and deduct the customer's account; When the deduction fails, determining whether the reason for the deduction failure is insufficient balance in the customer's account; When it is confirmed that the customer's account balance is insufficient, a first operation is performed, The first operation includes: Generate key information according to the remittance request instruction of the customer and record it in a pending table; and Query the customer's account balance every time period T. And wherein, when the sum of the remittance request time t and the mth time period T exceeds the transaction time, the customer's remittance request instruction is closed, and a completion mark is generated corresponding to the key information in the pending table, wherein m is a positive integer, and the key information includes: transaction instruction sequence number, remittance currency, remittance amount and remittance account number.
2. The method according to claim 1, characterized in that According to the remittance request instruction of the customer, obtain the customer's account information, including: According to the remittance request instruction of the customer, the currency information in the customer account and the balance information of the currency are obtained.
3. The method according to claim 1, characterized in that When the deduction fails, determining whether the reason for the deduction failure is insufficient balance in the customer's account includes: When the deduction fails, an error is actively reported and a specified error code is generated, and it is determined based on the error code whether the account balance is insufficient.
4. The method according to claim 1, characterized in that: Query the customer's account balance every time period T, including: When it is confirmed that the customer's account balance is sufficient, a second operation is performed, The second operation includes: Calling the debit message interface and deducting the customer's account, and generating a completion mark corresponding to the key information in the pending table; When it is confirmed that the account balance of the customer is insufficient, the first operation is performed.
5. The method according to claim 4, characterized in that The pending table contains a plurality of key information generated in accordance with the remittance request instruction. The plurality of key information are arranged in the order of generation time, and the customer's account balance is queried every time period T according to the generation order of the key information.
6. The method according to claim 5, characterized in that The customer's account balance is queried every time period T according to the generation order of key information, including: When querying the customer's account balance according to the generation order of key information, the accounts marked as completed in the pending table are automatically skipped.
7. The method according to claim 1, characterized in that After confirming that the customer's account balance is insufficient and before performing the first operation, the method further includes determining whether the customer participates in a remittance waiting mechanism, Wherein, the first operation is performed when the customer agrees to participate in the remittance waiting mechanism.
8. A system for remittance, characterized in that include: A receiving module, the receiving module is used to receive a remittance request instruction from a customer and record the remittance request time t; An acquisition module, the acquisition module is used to: acquire the customer's account information and the location and receivable currency of the account receiving the remittance according to the customer's remittance request instruction; A first judgment module, the first judgment module is used to judge whether the request time t of the remittance exceeds the transaction time, and the transaction time is specifically the settlement time of the remittance of the receivable currency; A first execution module, the first execution module is used to: when the request time t of the remittance does not exceed the settlement time of the remittance of the acceptable currency, call the debit message interface and deduct the customer's account; A second judgment module, the second judgment module is used to: when the deduction fails, determine whether the reason for the deduction failure is insufficient balance in the customer's account; The second execution module is used to: execute a first operation when confirming that the customer's account balance is insufficient, The first operation includes: generating key information according to the remittance request instruction of the customer and recording it in a pending table; and querying the customer's account balance every time period T. And wherein, when the sum of the remittance request time t and the mth time period T exceeds the transaction time, the customer's remittance request instruction is closed, and a completion mark is generated corresponding to the key information in the pending table, wherein m is a positive integer, and the key information includes: transaction instruction sequence number, remittance currency, remittance amount and remittance account number.
9. An electronic device, comprising: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors are caused to execute the method according to any one of claims 1 to 7.
10. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to perform the method according to any one of claims 1 to 7.
11. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.
Citation Information
Patent Citations
Resource transfer monitoring method and resource transfer monitoring device
CN106548402A
Cross-border remittance method, first electronic device and payment server
CN108154356A
Method, system and computing device for account processing
CN110020850A
Overdraft prevention method and device for electronic account
CN110866757A
Automatic re-deduction system
TWM572508U
