Data processing method and device, equipment, computer storage medium and program product

By receiving and verifying the remittance and recharge request of the prepaid card, the necessary account and institutional information are provided, allowing overseas people to remit money to the prepaid card account directly through overseas accounts, solving the problems of complex operations and difficult fund deposits when overseas people use prepaid cards, improving the success rate and reducing handling fees.

CN120069860APending Publication Date: 2025-05-30CHINA UNIONPAY
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202411923967.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-12-24
Publication Date
2025-05-30

AI Technical Summary

Technical Problem

Foreigners use prepaid cards for complex operations, difficult deposit of funds, and low success rate.

Method used

Provide a data processing method, which can receive remittance recharge requests from prepaid cards, perform user identity verification, and provide the corresponding collection account information, collection institution information and international unique identification of the prepaid card after passing the verification, allowing overseas people to remit money to the prepaid card account through overseas accounts, avoiding binding of personal bank cards.

Benefits of technology

It effectively reduces the risk of remittance of prepaid cards, simplifies the operation process of overseas people, improves the success rate of funds deposits, and avoids the high handling fees caused by binding to wild cards.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120069860A_ABST
    Figure CN120069860A_ABST
Patent Text Reader

Abstract

The invention discloses a data processing method and device, equipment, a computer storage medium and a program product. The method comprises the following steps: receiving a remittance and recharging request for the prepayment card; performing identity verification on the user who initiates the remittance and recharge request; under the condition that verification is passed, collection account information, collection mechanism information and an international unique identifier of a collection mechanism corresponding to the prepaid card are provided, and the collection account information, the collection mechanism information and the international unique identifier corresponding to the prepaid card are used for a remittance account to remit money to a collection account corresponding to the prepaid card. The remittance account is an overseas account; and receiving a remittance recharging response for the prepaid card, and generating a remittance recharging result of the prepaid card, thereby solving the problems of complex operation and high fund storage difficulty when overseas people use the prepaid card.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application belongs to the field of data processing, and in particular, relates to a data processing method, device, equipment, computer storage medium and program product. Background Art

[0002] With the development of Internet technology, various payment methods have emerged. For example, people can use prepaid cards, bind the prepaid cards with their personal bank cards, deposit the funds in the bank cards into the prepaid card accounts through transactions, and then use the funds in the prepaid cards to make payments.

[0003] However, this method of depositing funds is not convenient for overseas persons. It requires overseas persons to bind foreign cards, which is a complicated operation. Moreover, overseas persons cannot deposit funds if they do not have a personal bank card that can be bound. It is difficult to deposit funds and the success rate is low. Summary of the invention

[0004] The embodiments of the present application provide a data processing method, apparatus, device, computer storage medium and program product, which can solve the problems of complicated operation and difficulty in depositing funds when foreigners use prepaid cards.

[0005] In a first aspect, an embodiment of the present application provides a data processing method, including: receiving a remittance recharge request for a prepaid card; performing identity verification on a user who initiates the remittance recharge request; if the verification is passed, providing the receiving account information, receiving institution information and the internationally unique identifier of the receiving institution corresponding to the prepaid card, wherein the receiving account information, receiving institution information and the internationally unique identifier corresponding to the prepaid card are used for the remittance account to remit money to the receiving account corresponding to the prepaid card, and the remittance account is an overseas account; receiving a remittance recharge response for the prepaid card, and generating a remittance recharge result for the prepaid card.

[0006] In a second aspect, an embodiment of the present application provides a data processing device, comprising: a request receiving module, used to receive a remittance recharge request for a prepaid card; an identity verification module, used to perform identity verification on a user who initiates the remittance recharge request; an information output module, which, if the verification is passed, provides the receiving account information, receiving institution information and the internationally unique identifier of the receiving institution corresponding to the prepaid card, wherein the receiving account information, receiving institution information and the internationally unique identifier corresponding to the prepaid card are used for the remittance account to remit money to the receiving account corresponding to the prepaid card, and the remittance account is an overseas account; a result generation module, which receives a remittance recharge response to the prepaid card and generates a remittance recharge result for the prepaid card.

[0007] In a third aspect, an embodiment of the present application provides a data processing device, comprising: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the data processing method as described in the first aspect is implemented.

[0008] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the data processing method described in the first aspect is implemented.

[0009] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the data processing method as described in the first aspect.

[0010] An embodiment of the present application provides a data processing method, which receives a remittance recharge request for a prepaid card, performs identity verification on the user who initiates the remittance recharge request, effectively reduces the risk of fraudulently using the prepaid card for remittance, and, if the verification is passed, provides the collection account information, collection institution information and international unique identifier of the collection institution corresponding to the prepaid card, so that foreigners can remit money to the collection account corresponding to the prepaid card through a remittance account belonging to the foreign account based on the collection account information, collection institution information and international unique identifier corresponding to the prepaid card, without the need for foreigners to bind their personal bank cards, thereby solving the problems of complex operations, difficulty in depositing funds and low success rate when foreigners use prepaid cards, improving the success rate, and effectively avoiding high handling fees caused by binding foreign cards to complete recharge transactions. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the technical solution of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0012] Figure 1 is a schematic diagram of the system architecture of the data processing method provided in the embodiment of the present application;

[0013] Figure 2 is a flow chart of a data processing method provided by an embodiment of the first aspect of the present application;

[0014] Figure 3 is a flow chart of a data processing method provided by an embodiment of the first aspect of the present application;

[0015] Figure 4 is a flow chart of a data processing method provided by an embodiment of the first aspect of the present application;

[0016] Figure 5 is a structural diagram of a data processing device provided in an embodiment of the second aspect of the present application;

[0017] Figure 6 It is a structural diagram of a data processing device provided in an embodiment of the third aspect of the present application. DETAILED DESCRIPTION

[0018] The features and exemplary embodiments of various aspects of the present application will be described in detail below. In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are intended only to explain the present application, rather than to limit the present application. For those skilled in the art, the present application can be implemented without the need for some of these specific details. The following description of the embodiments is only to provide a better understanding of the present application by showing examples of the present application. It should be noted that the acquisition, storage, use, and processing of information and data in the embodiments of the present application are authorized by users or relevant agencies, in compliance with the relevant provisions of national laws and regulations.

[0019] The current method of depositing funds into prepaid cards is not convenient for overseas people to use. Overseas people need to bind foreign cards, which is complicated. Moreover, overseas people cannot deposit funds if they do not have a personal bank card that can be bound. Depositing funds is difficult and the success rate is low.

[0020] In view of this, an embodiment of the present application provides a data processing method, which receives a remittance recharge request for a prepaid card, performs identity verification on the user who initiates the remittance recharge request, effectively reduces the risk of impersonating the prepaid card to remit money, and, if the verification is passed, provides the receiving account information, receiving institution information and the internationally unique identifier of the receiving institution corresponding to the prepaid card, so that overseas persons can remit money to the receiving account corresponding to the prepaid card through a remittance account belonging to an overseas account based on the receiving account information, receiving institution information and the internationally unique identifier corresponding to the prepaid card, without the need for overseas persons to bind their personal bank cards, thereby solving the problems of complex operations, difficulty in depositing funds and low success rate when overseas persons use prepaid cards, and can effectively avoid the high handling fees caused by binding foreign cards to complete recharge transactions.

[0021] Figure 1 Schematic diagram of the system architecture of the data processing method provided in the embodiment of the present application. Figure 1 As shown, the system architecture of the data processing method provided in the embodiment of the present application may include: a user terminal 102 and a server 104 for managing prepaid cards.

[0022] Among them, the user terminal 102 is used to perform processing on the prepaid card according to the data processing method provided in the embodiment of the present application, and according to the processing, interact with the institutional platform of the payment institution through the service end 104. The processing may include: account opening, recharge, refund, card return and other processing. Specifically, the user terminal 102 is used to receive a remittance recharge request from a user for a prepaid card, perform identity verification on the user who initiated the remittance recharge request, and provide the collection account information, collection institution information and international unique identification of the collection institution corresponding to the prepaid card when the verification passes, wherein the collection account information, collection institution information and international unique identification corresponding to the prepaid card are used for the remittance account to remit money to the collection account corresponding to the prepaid card, and the remittance account is an overseas account, and a remittance recharge response for the prepaid card is received, and a remittance recharge result of the prepaid card is generated.

[0023] Exemplarily, the client program corresponding to the prepaid card can be run in the user terminal 102, such as a mobile client program, a computer desktop client program, a web client program, a small program in a third-party payment platform, a small program in an instant messaging tool, etc. In this way, the client program of the user terminal 102 can display a user interface, through which various processing operations of the user on the prepaid card are received, so that the user can process the prepaid card, such as: registration, login, personal information maintenance, opening a new card, checking the card status (activation / freezing), setting card limits, recharging, transfer, refund, card return, etc. The user terminal 102 sends a corresponding request to the server 104 according to the received processing operation, so that the server 104 performs the processing corresponding to the request. Exemplarily, the user interface displayed by the user terminal 102 may include an account opening page, a recharging page, a refund page, a card return page, a record query page, etc.

[0024] The server 104 is used to receive the request sent by the user terminal 102, perform corresponding processing according to the request sent by the user terminal 102, and interact with the institution platform 106 of the payment institution according to the needs of the request of the user terminal 102. In this way, the server 104 can be understood as a service platform that assists the user terminal 102 in managing the prepaid card, and the user terminal 102 interacts with other institution platforms or servers through the server 104.

[0025] In addition, if Figure 1 As shown, the service end 104 can also interact with the institution platform 106 of the payment institution to complete at least one of remittance recharge, refund, card return and inquiry. The institution platform 106 can also interact with the institution platform 108 corresponding to the overseas remittance account to complete at least one of remittance recharge and refund.

[0026] In this application scenario, the user terminal 102 can be any terminal such as a mobile phone, a tablet computer, a smart watch, a smart bracelet, etc. The server 104 can be a single physical server, or can be a server cluster or a distributed system composed of multiple physical servers. It can also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, Content Delivery Network (CDN), and big data and artificial intelligence platforms. The institutional platform 106 can be a bank platform, a third-party payment platform, etc. The institutional platform 108 can be an overseas institutional platform that belongs to a different country from the institutional platform 106, such as an overseas bank platform, an overseas third-party payment platform, etc.

[0027] It can be seen that in the above application scenario, the user terminal 102 receives the remittance recharge request for the prepaid card through the user interface, verifies the remittance recharge request, effectively reducing the risk of misusing the prepaid card for remittance. Moreover, when the verification is passed, the user terminal 102 provides the user with the corresponding receiving account information, receiving institution information, and international unique identifier of the receiving institution of the prepaid card through the user interface. Thus, overseas persons can remit money to the receiving account corresponding to the prepaid card based on the receiving account information, receiving institution information, and international unique identifier corresponding to the prepaid card through the remittance account belonging to the overseas account, without the overseas persons binding their personal bank cards, solving the problems of complex operations, difficult fund deposit, and low success rate when overseas persons use prepaid cards, and effectively avoiding the high handling fees brought by binding foreign card payments.

[0028] It should be noted that the above system architecture is a possible implementation manner of the data processing method provided in the embodiments of the present application. According to actual application needs, it can also be implemented through other system architectures. Based on different system architectures, the execution subject of the data processing method provided in the embodiments of the present application can be different. For example, in some embodiments, the data processing method can be executed by the server, in some other embodiments, the data processing method can be executed by the user terminal, and in some other embodiments, the data processing method can be executed through the cooperation of the user terminal and the server. The embodiments of the present application do not limit this.

[0029] Next, the data processing method, device, equipment, computer storage medium, and program product in the embodiments of the present application will be described separately.

[0030] Figure 2 It is a flowchart of the data processing method provided in an embodiment of the first aspect of the present application. As Figure 2 shown, the data processing method may include steps S210 - S240.

[0031] S210: Receive a remittance recharge request for a prepaid card.

[0032] A prepaid card is a carrier that deposits funds into a corresponding payment account and uses the prepaid funds within a specified range. A prepaid card can be an electronic card or a physical card, and this application does not limit this.

[0033] For example, a prepaid card can be used to use the pre-stored funds in the public transportation system to take one or more modes of transportation, such as subways, buses, light rails, etc., and can also be used to consume the pre-stored funds in other specified ranges. For example, a prepaid card can be a physical card or an electronic transportation card that the cardholder can carry with him / her, and can be paid through online, contact or contactless methods, so that it is easy to transfer to various modes of transportation in different cities or countries without having to buy a separate ticket for each ride.

[0034] A remittance recharge request is used to indicate a request for remittance recharge of a prepaid card. The remittance recharge request is initiated by a user through a recharge operation in the user interface. For example, a user can initiate a remittance recharge request by clicking a remittance recharge button in the user interface. The remittance recharge request may have corresponding user identity information, prepaid card identification information such as a card number, and other information. The user identity and the prepaid card to be recharged can be determined through the information corresponding to the remittance recharge request.

[0035] Taking the execution subject of the data processing method as a user terminal as an example, in step 210, the user terminal can receive a remittance recharge request initiated by the user through a user interface. Exemplarily, the user terminal displays a recharge interface, which includes a remittance recharge button. In response to the user clicking the remittance recharge button, the user terminal receives the remittance recharge request and displays the remittance recharge page. The remittance recharge page can also display a text message verification interface component so that the user can enter a text message verification code to enter the verification process.

[0036] Optionally, the recharge interface may further include a foreign card recharge button. The user terminal may also enter a process of recharging the prepaid card by binding a foreign card in response to the user clicking the foreign card recharge button.

[0037] S220: Perform identity verification on the user who initiated the remittance recharge request.

[0038] The identity verification in step S220 can be implemented in a variety of ways, such as SMS verification, biometrics, etc.

[0039] Exemplarily, the user triggers "Send Verification Code" on the remittance recharge page displayed on the user terminal, and the user terminal sends a verification code sending request containing the mobile phone number to the server. After receiving the verification code sending request, the server passes the generated verification code together with the mobile phone number to the SMS gateway, so as to send the verification code to the user's mobile phone in the form of a text message. The user terminal then sends the verification code input by the user to the server, and the server compares the received verification code with the previously generated verification code. If they are the same, the verification passes; otherwise, the verification fails, thus completing the identity verification process.

[0040] S230: In the case where the verification passes, provide the collection account information, collection institution information, and international unique identifier of the collection institution corresponding to the prepaid card. Among them, the collection account information, collection institution information, and international unique identifier corresponding to the prepaid card are used for the remittance account to remit money to the collection account corresponding to the prepaid card, and the remittance account is an overseas account.

[0041] The collection account corresponding to the prepaid card can be the collection account opened when the prepaid card is issued on the server, or the collection account set after the prepaid card is issued on the server. This collection account can be understood as the prepaid card account opened by the server for managing the prepaid card, which is managed and maintained by the server. The collection account information can be expressed as information such as the prepaid card account number and the prepaid card user name.

[0042] The collection institution can be the bank corresponding to the server. The collection institution information can be the bank name.

[0043] The international unique identifier of the collection institution, also known as the Swift number, is the unique code used by international financial institutions such as banks to identify each other, and is used in international transfers and financial transactions to ensure that funds can accurately reach the specified bank account.

[0044] Exemplarily, the server can send the collection account information, collection institution information, and international unique identifier of the collection institution corresponding to the prepaid card to the user terminal for caching. When the user initiates a remittance recharge request, the user terminal reads these three elements from the cache and displays them on the user interface such as the remittance recharge page. The user can copy these three elements displayed on the remittance recharge page and enter the information of these three elements in the remittance application or remittance website to complete the transfer and remittance. Optionally, the user terminal can also obtain information such as the country list, institution list, supported currencies, collection institution of the prepaid card, Swift number, etc. through any means, such as the interface of the institution platform / offline, etc., and cache them locally on the user terminal. When needed for display, the corresponding information is read from the cache and displayed.

[0045] In addition, to facilitate the user to confirm the foreign currency amount to be remitted, the user terminal can also display the exchange rate between the region to which the remittance account belongs and the region to which the receiving account belongs on the remittance recharge page, display the recharge amount of the local currency entered by the user, and the corresponding foreign currency amount to be remitted. The displayed recharge amount is the same as the recharge amount entered by the user and cannot be edited. To facilitate determining the exchange rate according to the currency, the remittance recharge page can also include a foreign currency input control, and the user can modify the currency of the foreign currency to be remitted through the foreign currency input control. For example, the remittance recharge page can include a list of foreign currencies with selectable currencies, so that the user can select the currency of the foreign currency to be remitted. The list of foreign currencies with selectable currencies can display the currency name and abbreviation, such as: US dollar USD. The selection operation method of the list of foreign currencies with selectable currencies is not limited. For example, it can support the user to slide and then click on the checkbox to confirm the selected foreign currency. Optionally, the remittance recharge page can also provide a bank support list for displaying the country list and bank name. For example, it can support the user to first select the country and then select the bank.

[0046] Optionally, the server can obtain the exchange rate through the interface of the bank platform or other interfaces, send the exchange rate to the user terminal, and the user terminal can calculate the foreign currency amount to be remitted according to the exchange rate and display the calculated foreign currency amount to the user. Among them, when calculating the foreign currency amount, the general calculation method can be used, such as: remittance foreign currency amount = local currency amount to be recharged / exchange rate. In the case of non-integer division, two decimal places can be reserved and the extra digits can be rounded off.

[0047] Furthermore, to enable the user to fully understand the relevant requirements for the remittance recharge of the prepaid card, the user terminal can also provide the following prompt text to the user through the user interface, such as the remittance recharge page:

[0048] "1. The page amount is for reference only, and the actual credited amount is subject to the remittance bank.";

[0049] "2. The issuing bank only provides services on weekdays from 9:30 to 19:00, and generally arrives within 15 minutes. It may be delayed due to the remitting bank and the receiving bank. If you need to consume immediately, it is recommended to choose [Recharge by Entering Foreign Card Information] for recharge.";

[0050] "3. The balance refund for remittance recharge involves cross-border services, and the issuing bank will charge a certain handling fee. It is recommended that you recharge as needed."

[0051] S240: Receive the remittance recharge response for the prepaid card and generate the remittance recharge result for the prepaid card.

[0052] Exemplarily, the user terminal can send a query request to the institutional platform of the receiving institution, such as a bank platform or a third-party payment platform, through the server to inquire whether the remittance has arrived at the receiving account, receive the query result returned by the institutional platform for the query request through the server, and then generate the remittance recharge result based on the query result.

[0053] Optionally, when the remittance end successfully completes the transfer and remittance, the receiving account will receive the remittance from the remittance account. In this case, the institution platform of the receiving institution can send a recharge response to the user terminal through the service end indicating that the receiving account has received the remittance from the remittance account, and the user terminal will generate a remittance recharge result indicating that the remittance recharge is successful. Optionally, the remittance recharge result can also include recharge amount information.

[0054] Optionally, when the remittance transfer fails, the institution platform of the payee institution may send a recharge response indicating the remittance transfer failure to the user terminal through the service end, and the user terminal correspondingly generates a remittance recharge result indicating the remittance recharge failure.

[0055] It can be seen from the above embodiments that the method receives a remittance recharge request for a prepaid card, performs identity verification on the user who initiates the remittance recharge request, and effectively reduces the risk of fraudulently using a prepaid card to remit money. Moreover, when the verification is passed, the receiving account information, the receiving institution information and the internationally unique identifier of the receiving institution corresponding to the prepaid card are provided, so that foreigners can remit money to the receiving account corresponding to the prepaid card through a remittance account belonging to an overseas account based on the receiving account information, the receiving institution information and the internationally unique identifier corresponding to the prepaid card. There is no need for foreigners to bind their personal bank cards, which solves the problems of complex operations, difficulty in depositing funds and low success rate when foreigners use prepaid cards, and can effectively avoid the high handling fees caused by binding foreign card payments.

[0056] Figure 3 This is a flow chart of a data processing method provided in an embodiment of the first aspect of the present application. Figure 3 As shown, the data processing method may further include steps S310-S330.

[0057] S310: Receive a first refund request for the prepaid card.

[0058] The first refund request is used to indicate a request for refunding the funds in the prepaid card account. The first refund request is initiated by the user's refund operation in the user interface, and the first refund request may have corresponding user identity identification, prepaid card identification such as card number, refund amount and other information. Through the information corresponding to the first refund request, the user identity, the prepaid card to be refunded and the refund amount can be determined.

[0059] Taking the execution entity of this data processing method as the user terminal as an example, in this embodiment, the user terminal can receive a first refund request initiated by the user through the user interface. Exemplarily, the user terminal displays the user interface, which includes a refund button. In response to the user clicking the refund button, the user terminal receives the first refund request and displays a refund page. The refund page may include input controls for information such as the refund amount and refund account. The input controls are default filled with the refundable amount and refund account of the user, and the user can re-enter information such as the refund amount and refund account. The information corresponding to the first refund request shall be subject to the information re-entered by the user.

[0060] Exemplarily, the following refund prompt information may also be displayed on the refund page:

[0061] "1. For refunds by remittance recharge, XX Bank will charge NN yuan in handling fees for each transaction, subject to the issuing bank. If the single refund amount is insufficient to cover the handling fees, the transaction cannot be initiated;

[0062] 2. Affected by exchange rate fluctuations and receiving bank service fees, the specific refund amount shall be subject to the actual amount credited to your account. If you have any questions, please contact XX Bank for handling."

[0063] Through the above page prompts, users can be helped to accurately understand the relevant refund rules.

[0064] S320: Perform identity verification on the user who initiated the first refund request.

[0065] The implementation method of identity verification is not limited, and the implementation method introduced in other embodiments can be referred to, which will not be elaborated here.

[0066] S330: In the case of successful verification, perform a refund operation according to the first refund request. The refund operation returns the refund corresponding to the first refund request to the remittance account corresponding to the refund at the time of recharge.

[0067] Exemplarily, the user can initiate first refund requests corresponding to multiple refunds, and the refund page can display a list of these multiple refunds.

[0068] Exemplarily, performing a refund operation according to the first refund request may include:

[0069] Determine the remittance account information corresponding to the single refund corresponding to the first refund request;

[0070] Generate a second refund request based on the remittance account information, the receiving account information corresponding to the prepaid card, and the amount of the single refund, and send the second refund request to the institutional platform of the receiving institution. The second refund request causes the institutional platform of the receiving institution to initiate a third refund request to the overseas institutional platform corresponding to the remittance account;

[0071] Obtain refund response information for the second refund request.

[0072] The second refund request is used to represent a request for refunding the funds in the prepaid card account. The second refund request may carry remittance account information, the receiving account information corresponding to the prepaid card, and the amount of this single refund. Through the information corresponding to the second refund request, the institutional platform of the receiving institution can determine the remittance account information, the receiving account information corresponding to the prepaid card, and the amount of this single refund, and then initiate a third refund request to the overseas institution corresponding to the remittance account. The third refund request is used to represent refunding the amount of this single refund from the corresponding receiving account back to the corresponding remittance account.

[0073] After the institutional platform of the receiving institution sends the third refund request, it will obtain refund response information from the overseas institutional platform. In this way, the institutional platform of the receiving institution can further send the refund response information for the second refund request to the user terminal through the server. The refund response information may include: refund success information, refund failure information, or refund in progress information.

[0074] Exemplarily, after the user terminal obtains the refund response information, it can generate a corresponding refund result and display it on the refund page.

[0075] In this embodiment, the user terminal enters the refund process according to the first refund request initiated by the user. After completing the identity verification, the user terminal displays the corresponding refund page. The refund of the prepaid card follows the principle of original in and original out, and is directly refunded to the remittance account corresponding to the recharge, which can reduce user operations and improve the refund efficiency.

[0076] Figure 4 It is a flowchart of the data processing method provided by an embodiment of the first aspect of this application. As Figure 4 shown, the data processing method may further include steps S410 - S450.

[0077] S410: Receive a card return request for the prepaid card.

[0078] The card return request is used to represent a request for canceling the prepaid card. The card return request is initiated by the user's card return operation in the user interface. The card return request may have corresponding user identity identification and prepaid card identification such as card number and other information. Through the information corresponding to the card return request, the user identity and the prepaid card to be returned can be determined.

[0079] Taking the execution entity of this data processing method as the user terminal as an example, in this embodiment, the user terminal can receive a card refund request initiated by the user through the user interface. Exemplarily, the user terminal displays the user interface, and the user interface includes a card refund button. The user terminal receives the card refund request in response to the user clicking the card refund button and enters the identity verification process.

[0080] S420: Perform identity verification on the user who initiated the card refund request.

[0081] The implementation method of identity verification is not limited and can refer to the implementation methods introduced in other embodiments, which will not be elaborated here.

[0082] S430: When the verification is passed, obtain the balance information of the prepaid card.

[0083] Exemplarily, when the verification is passed, a refund page can be displayed. The refund page may include input controls for information such as balance information, refund amount, and refund account. The input controls are default filled with the refundable amount of the user and the refund account, and the user can re-enter information such as the refund amount and refund account.

[0084] S440: When the balance information is not zero, perform a balance refund operation on the prepaid card. The balance refund operation causes the refund in the balance of the prepaid card to be returned to the remittance account corresponding to the refund recharge.

[0085] In some embodiments, when performing the balance refund operation, a refund page can be displayed. The information displayed on the refund page may include:

[0086] Refund prompt information. The content of this refund prompt information can be implemented with reference to other embodiments and will not be elaborated here.

[0087] A sorted list of one or more refundable single refunds. For example: This sorted list is sorted in descending order of the refundable amount. Optionally, if the maximum refundable amount of the prepaid card for card refund is zero, the sorted list of refunds may not be displayed.

[0088] Among them, each refundable single refund has a corresponding refund amount. Exemplarily, the user terminal can call the refund information query interface of the institution platform of the collection institution through the server to query out each refundable single refund. Among them, when calling this refund information query interface, the query command can distinguish between foreign card recharge refunds or remittance recharge refunds to accurately obtain the refundable refunds corresponding to the two different recharge methods. Exemplarily, the information obtained by the user terminal query may include the refund card number (such as the first four digits and the last four digits of the refund card number), the refundable amount, the refund currency, etc.

[0089] In some embodiments, the balance refund operation on the prepaid card by S440 may include the following steps:

[0090] Determine one or more single refunds corresponding to the balance information;

[0091] Determine the remittance account information corresponding to the single refund at the time of recharge;

[0092] Generate a second refund request based on the remittance account information, the receiving account information corresponding to the prepaid card, and the amount of the single refund, and send the second refund request to the institutional platform of the receiving institution. The second refund request causes the institutional platform of the receiving institution to initiate a third refund request to the overseas institutional platform corresponding to the remittance account;

[0093] Obtain the refund response information for the second refund request.

[0094] Through the refund of one or more single refunds by returning along the original path for each single refund, the refund can be accurately directly returned to the remittance account corresponding to the time of recharge, reducing user operations and improving the refund efficiency.

[0095] The above refund process can refer to Figure 3 the embodiments shown, which will not be elaborated here.

[0096] Optionally, in the case where the amount of any single refund is not sufficient to cover the refund handling fee, a refund failure risk prompt message can be output.

[0097] Exemplarily, before the user terminal determines one or more single refunds corresponding to the balance information, it can also receive the refund amount input by the user. That is, the user terminal supports the user to manually modify the refund amount. The refund amount can be a natural number greater than or equal to zero, but cannot exceed the total balance of the prepaid card. And when the refund amount input by the user is greater than zero, further determine whether the input amount is higher than the bank handling fee.

[0098] Optionally, if it exceeds the total balance of the prepaid card, output the following refund failure risk prompt message:

[0099] "[The maximum refundable amount of this card has been exceeded. Please modify.]"

[0100] Optionally, if the input amount is not higher than the bank handling fee, output the following refund failure risk prompt message:

[0101] "[Lower than the handling fee amount. It is recommended to reallocate.]"

[0102] In addition, on the refund page, a button for generating a confirmation message for card cancellation may also be included, such as a "Cancel Immediately" button. When the user clicks this button, the user terminal correspondingly receives a confirmation message for card cancellation. To ensure that all the remaining balance of the prepaid card is refunded to the original remittance account before card cancellation, in some embodiments of the present application, the method further includes:

[0103] When receiving the confirmation message for card cancellation, comparing the total amount of the one or more single refunds with the balance information;

[0104] When the total amount is inconsistent with the balance information, outputting an error message for the refund amount.

[0105] Exemplarily, when the user clicks the "Cancel Immediately" button on the refund page displayed on the user terminal, the user terminal checks whether the total refund amount is equal to the account balance. If not, an error message can be output: "The refund amount should be equal to the account balance. Please re-enter."

[0106] In addition, similar to the embodiment of outputting a refund failure risk prompt message, after completing the check on whether the total refund amount is equal to the account balance, if there is still a situation where the amount of a single refund is insufficient to pay the refund handling fee, a refund failure risk prompt message such as "Since part of the refund amount is insufficient to pay the refund handling fee, the refund may fail. It is recommended that you reallocate or use up the remaining amount before canceling the card" can be output by means of a pop-up window on the refund page. A subsequent processing button corresponding to the pop-up window may also be provided on the refund page. For example, the subsequent processing button may include: a "Got it" button and a "Continue to Cancel" button. If the user clicks "Got it", they can continue to stay on the refund page. If the user clicks the "Continue to Cancel" button, the refund is continued to be completed.

[0107] After completing the refund of all the remaining balance, the refund result page can be entered.

[0108] S450: When the balance information is zero, perform a card cancellation operation on the prepaid card, and the card cancellation operation closes the account of the prepaid card.

[0109] In this embodiment, the principle of original in and original out is also followed. When canceling the card, the refund is directly returned to the remittance account corresponding to the recharge, which can reduce user operations and improve the refund efficiency.

[0110] In some embodiments of the present application, to ensure that the card cancellation operation is performed when all the remaining balance has been successfully refunded, before performing the card cancellation operation on the prepaid card, the method further includes:

[0111] Sending a refund query request for the single refund to the institutional platform of the receiving institution;

[0112] Receive the refund query result returned by the institutional platform of the receiving collection institution for the refund query request;

[0113] In the case where it is determined according to the refund query result that each single refund of the one or more single refunds has been successfully refunded, enter the step of performing a card return operation on the prepaid card when the balance information is zero.

[0114] A refund query request is a query request used to indicate whether the refund is successful. The refund query request can be initiated automatically by the user terminal or initiated under the trigger of the user. For example: The user terminal can call the refund interface of the institutional platform of the receiving collection institution through the server to send a refund query request. The refund query request can carry information such as the refund type (such as the remittance recharge refund type or the foreign card recharge transaction refund type), the receiving account of the refund, the refund amount, and the refund currency. During the process of the institutional platform of the receiving collection institution executing the query, the user terminal can display a prompt message indicating that the query is being processed.

[0115] It can be understood that the single refunds of multiple transactions do not affect each other. For example, after a single refund fails, the next single refund will still be initiated normally.

[0116] Optionally, the user terminal can initiate a refund query request through the server at a certain period at a preset time (such as 23:00 every night), so that the refund result can be obtained as soon as possible through multi-period queries.

[0117] There may be a situation where a single refund fails. For example, a network problem causes the request not to be sent successfully. Based on this, in some embodiments of the present application, targeted processing is also performed on the situation where the refund fails, so that the user can timely obtain information and decide whether to continue the refund. Specifically, the method further includes:

[0118] In the case where it is determined according to the refund query result that any single refund fails, output a refund failure prompt message;

[0119] If a continue card return request is received for the failed single refund of any one, continue to send the second refund request for the single refund to the institutional platform of the receiving collection institution.

[0120] Through the prompt, it helps the user understand the reason for the failure and provides an input entry for the user to continue with the card return.

[0121] For example, a refund failure prompt message can be displayed on the refund page: "The XXth refund failed". In this way, if a refund failure record is found, the page will display a refund failure prompt message. For refund failures, the user interface can also display a "Continue to refund" button. After the user clicks it, the refund page is entered, and the user continues to initiate a second refund request for the failed single refund.

[0122] In addition, in order to ensure that the prepaid card can be successfully cancelled according to the user's card return request, in some embodiments of the present application, after the prepaid card is returned, the method further includes:

[0123] Sending an account cancellation inquiry request for the prepaid card to the institution platform of the payment collection institution;

[0124] receiving an account cancellation query result returned by the institution platform of the payment receiving institution in response to the account cancellation query request, and outputting the account cancellation query result;

[0125] In the case of account cancellation failure, if a request to continue card return is received, determining whether the prepaid card supports account cancellation;

[0126] If supported, return to the step of returning the prepaid card.

[0127] Among them, the account cancellation query request is a query request used to indicate whether the account cancellation is successful. The account cancellation query request can be initiated automatically by the user terminal or triggered by the user. For example, the user terminal can call the account cancellation query interface through the server and send an account cancellation query request. The account cancellation query request can carry the user identity information of the prepaid card, the payment account information, etc. During the process of executing the query on the user terminal, the user terminal can display the prompt information in the query process.

[0128] The account cancellation query result can be displayed as successful account cancellation, failed account cancellation or account cancellation in progress.

[0129] It is understandable that in some scenarios, prepaid cards may or may not support account cancellation. Therefore, in the case of account cancellation failure, it is necessary to determine whether the prepaid card supports account cancellation. If it supports account cancellation, the steps of returning the prepaid card can be returned to ensure successful card return. If it does not support account cancellation, there is no need to continue returning the prepaid card, thus avoiding repeated invalid operations of returning the prepaid card.

[0130] In addition, if the prepaid card does not support account cancellation, the process can be triggered by the user or automatically return to the step of refunding the balance of the prepaid card so that the user can complete the refund of any remaining balance on the prepaid card.

[0131] It should be understood that for multiple single refunds in the card return process, if the refund query result of any single refund indicates that it is being processed, the card return process on the card return page will show that it is being processed. If all refunds are successfully processed and the account is successfully closed, the card return page can show that the card return is successful. If the account is not successfully closed, the card return failure page will be displayed. Exemplarily, the card return failure page can display the following information: refund details (such as the first four and last four digits of the refund card number, refund status, refund amount, refund currency). In addition, the judgment conditions for refund failure can be set by the institutional platform of the receiving institution, that is, the bank side. This judgment condition can be manifested as a constraint on the duration of the status during refund processing.

[0132] In some embodiments of the present application, the data processing method may further include:

[0133] When receiving a recharge record query request for the prepaid card, query and output the recharge record of the prepaid card.

[0134] And / or,

[0135] When receiving a refund record query request for the prepaid card, query and output the refund record of the prepaid card.

[0136] Exemplarily, the user can click the recharge record query button on the user interface of the user terminal. The user terminal correspondingly receives the recharge record query request, thereby queries the recharge record of the prepaid card from the server and displays the recharge record in the user interface. It can be understood that the server is used to manage and maintain the prepaid card, and the server can save all the recharge records of the prepaid card for users to query. The recharge record query request can have a corresponding prepaid card identifier, user identity information, and can also include query conditions, such as recharge time, recharge amount, etc.

[0137] When outputting the recharge record of the prepaid card, the recharge record details page may include: recharge amount (foreign currency amount), recharge card number (desensitized, first 4 and last 4, to be stored in the background), etc.

[0138] Exemplarily, the user can click the refund record query button on the user interface of the user terminal. The user terminal correspondingly receives the refund record query request, thereby queries the refund record of the prepaid card from the server and displays the refund record in the user interface. The refund record query request can have a corresponding prepaid card identifier, user identity information, and can also include query conditions, such as refund time, refund amount, etc.

[0139] When outputting the refund record of the prepaid card, the refund record details page may include: refund amount (such as foreign currency amount), refund card number (such as can be desensitized, only display the first four and last four digits of the card number), etc.

[0140] Each record queried may have a corresponding processing status, such as successful processing or failed processing. In addition, in the case of failed processing, the failure reason may also be displayed in the recharge record.

[0141] A second aspect of the present application provides a data processing device. Figure 5 A schematic diagram of the structure of a data processing device provided in an embodiment of the second aspect of the present application. Figure 5 As shown, the data processing device 500 may include a request receiving module 510, which is used to receive a remittance recharge request for a prepaid card; an identity verification module 520, which is used to verify the identity of the user who initiated the remittance recharge request; an information output module 530, which, if the verification is passed, provides the collection account information, collection agency information and international unique identification of the collection agency corresponding to the prepaid card, wherein the collection account information, collection agency information and international unique identification corresponding to the prepaid card are used for the remittance account to remit money to the collection account corresponding to the prepaid card, and the remittance account is an overseas account; a result generation module 540, which receives a remittance recharge response to the prepaid card and generates a remittance recharge result of the prepaid card.

[0142] Optionally, the device further comprises:

[0143] A refund request receiving module, configured to receive a first refund request for the prepaid card;

[0144] A refund user verification module, used to verify the identity of the user who initiated the first refund request;

[0145] The refund operation execution module is used to perform a refund operation according to the first refund request when the verification is passed, and the refund operation causes the refund corresponding to the first refund request to be returned to the remittance account corresponding to the refund when the recharge is performed.

[0146] Optionally, the device further comprises:

[0147] A card return request receiving module, used for receiving a card return request for the prepaid card;

[0148] A card return user verification module, used to verify the identity of the user who initiated the card return request;

[0149] A balance information acquisition module, used to obtain the balance information of the prepaid card if the verification is passed;

[0150] A balance refund execution module, which is used to perform a balance refund operation on the prepaid card when the balance information is not zero, and the balance refund operation causes the refund in the balance of the prepaid card to be refunded to the corresponding remittance account at the time of refund recharge;

[0151] A card cancellation operation module, which is used to perform a card cancellation operation on the prepaid card when the balance information is zero, and the card cancellation operation closes the account of the prepaid card.

[0152] Optionally, the balance refund execution module further includes:

[0153] A refund confirmation sub-module, which is used to determine one or more single refunds corresponding to the balance information;

[0154] A remittance confirmation sub-module, which is used to determine the remittance account information corresponding to the single refund at the time of recharge;

[0155] A remittance return sub-module, which is used to generate a second refund request according to the remittance account information, the receiving account information corresponding to the prepaid card, and the amount of the single refund, and send the second refund request to the institutional platform of the receiving institution, and the second refund request causes the institutional platform of the receiving institution to initiate a third refund request to the overseas institutional platform corresponding to the remittance account;

[0156] A response acquisition sub-module, which is used to acquire refund response information for the second refund request.

[0157] Optionally, the balance refund execution module further includes:

[0158] A handling fee verification sub-module, which is used to output a refund failure risk prompt message when the amount of any single refund is insufficient to pay the refund handling fee.

[0159] Optionally, the balance refund execution module further includes:

[0160] A balance comparison sub-module, which is used to compare the total amount of the one or more single refunds with the balance information when receiving the confirmation message for card cancellation;

[0161] A refund error reporting sub-module, which is used to output a refund amount error message when the total amount is inconsistent with the balance information.

[0162] Optionally, the card cancellation operation module further includes:

[0163] A refund query sub-module, which is used to send a refund query request for the single refund to the institutional platform of the receiving institution;

[0164] A refund result receiving sub-module, configured to receive a refund query result returned by the institutional platform of the receiving institution for the refund query request;

[0165] A refund confirmation sub-module, configured to trigger the card cancellation operation module to execute the step of performing a card cancellation operation on the prepaid card when the balance information is zero, when it is determined according to the refund query result that each single refund of the one or more single refunds is successfully refunded.

[0166] Optionally, the card cancellation operation module further includes:

[0167] A failure prompt sub-module, configured to output a refund failure prompt message when it is determined according to the refund query result that any single refund fails;

[0168] A failure handling sub-module, configured to, if a continue card cancellation request is received for the failed single refund, continue to send the second refund request for the single refund to the institutional platform of the receiving institution.

[0169] Optionally, the card cancellation operation module further includes:

[0170] A cancellation query sub-module, configured to send a cancellation query request for the prepaid card to the institutional platform of the receiving institution;

[0171] A cancellation result receiving sub-module, configured to receive a cancellation query result returned by the institutional platform of the receiving institution for the cancellation query request, and output the cancellation query result;

[0172] A cancellation judgment sub-module, configured to, when the cancellation fails, if a continue card cancellation request is received, judge whether the prepaid card supports cancellation;

[0173] A cancellation return sub-module, configured to, if it supports, return to the card cancellation operation module.

[0174] Optionally, the device further includes:

[0175] A recharge record query module, configured to query and output the recharge record of the prepaid card when a recharge record query request for the prepaid card is received; and / or,

[0176] A refund record query module, configured to query and output the refund record of the prepaid card when a refund record query request for the prepaid card is received.

[0177] The third aspect of the present application further provides a project data processing device. Figure 6 It is a schematic structural diagram of a project data processing device provided by an embodiment of the present application. As Figure 6As shown, the project data processing device 600 includes a memory 601, a processor 602, and a computer program stored on the memory 601 and executable on the processor 602.

[0178] In some examples, the above-mentioned processor 602 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured as one or more integrated circuits for implementing the embodiments of the present application.

[0179] The memory 601 may include a mass storage for data or instructions. By way of example and not limitation, the memory 601 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disc, a magneto-optical disc, a magnetic tape, or a universal serial bus (USB) drive, or a combination of two or more of these.

[0180] The memory 601 may include a read-only memory (ROM), a random access memory (RAM), a magnetic disk storage media device, an optical storage media device, a flash memory device, an electrical, optical, or other physical / tangible memory storage device. Thus, generally, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the project data processing method in the embodiments of the present application.

[0181] The processor 602 runs a computer program corresponding to the executable program code by reading the executable program code stored in the memory 601, so as to implement the project data processing method in the above embodiments.

[0182] In some examples, the project data processing device 600 may further include a communication interface 603 and a bus 604. Among them, as Figure 6 shown, the memory 601, the processor 602, and the communication interface 603 are connected through the bus 604 to complete communication with each other.

[0183] The communication interface 603 is mainly used to implement communication between the various modules, devices, units, and / or devices in the embodiments of the present application. It is also possible to access an input device and / or an output device through the communication interface 603.

[0184] The bus 604 includes hardware, software, or both, and couples the components of the item data processing device 600 to each other. By way of example and not limitation, the bus 604 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an InfiniBand interconnect, a Low pin count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-E) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or other suitable buses or a combination of two or more of these. Where appropriate, the bus 604 may include one or more buses. Although the embodiments of the present application describe and illustrate specific buses, the present application contemplates any suitable bus or interconnect.

[0185] A fourth aspect of the present application provides a computer-readable storage medium, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the item data processing method in the above embodiments can be implemented and the same technical effects can be achieved. To avoid repetition, it will not be described here again. Among them, the above computer-readable storage medium may include a non-transitory computer-readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disc, etc., which is not limited herein.

[0186] The present application provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the item data processing method in the above embodiments is implemented and the same technical effects can be achieved. To avoid repetition, it will not be described here again.

[0187] It should be clear that each embodiment in this specification is described in a progressive manner. For the parts that are the same or similar among the embodiments, reference can be made to each other. Each embodiment focuses on the differences from other embodiments. For the apparatus embodiments, device embodiments, and computer-readable storage medium embodiments, the relevant parts can refer to the description part of the method embodiments. This application is not limited to the specific steps and structures described above and shown in the figures. Those skilled in the art can make various changes, modifications, and additions after understanding the spirit of this application, or change the order of the steps. And, for the sake of brevity, the detailed description of known method technologies is omitted here.

[0188] The above has described various aspects of the present application with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to embodiments of the present application. It should be understood that each block in the flowchart and / or block diagram, as well as the combinations of blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing devices enable the implementation of the functions / actions specified in one or more blocks of the flowchart and / or block diagram. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It can also be understood that each block in the block diagram and / or flowchart, as well as the combinations of blocks in the block diagram and / or flowchart, can also be implemented by dedicated hardware that performs the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0189] Those skilled in the art should be able to understand that the above embodiments are all exemplary rather than restrictive. Different technical features appearing in different embodiments can be combined to achieve beneficial effects. Those skilled in the art should be able to understand and implement other variations of the disclosed embodiments based on the study of the drawings, the specification, and the claims. In the claims, the term "comprising" does not exclude other devices or steps; the quantifier "one" does not exclude a plurality; the terms "first" and "second" are used to label names rather than to indicate any specific order. Any reference signs in the claims should not be construed as limiting the scope of protection. The functions of multiple parts in the claims can be implemented by a single hardware or software module. The fact that certain technical features appear in different dependent claims does not mean that these technical features cannot be combined to achieve beneficial effects.

Claims

1. A data processing method, characterized in that: The method comprises: receiving a remittance recharge request for a prepaid card; Performing identity verification on the user who initiated the remittance recharge request; If the verification is passed, provide the payment account information, payment institution information and international unique identifier of the payment institution corresponding to the prepaid card, wherein the payment account information, payment institution information and international unique identifier corresponding to the prepaid card are used for the remittance account to remit money to the payment account corresponding to the prepaid card, and the remittance account is an overseas account; A remittance recharge response for the prepaid card is received, and a remittance recharge result for the prepaid card is generated.

2. The method according to claim 1, characterized in that The method further comprises: receiving a first refund request for the prepaid card; Performing identity verification on the user who initiated the first refund request; When the verification is passed, a refund operation is performed according to the first refund request, and the refund operation causes the refund corresponding to the first refund request to be returned to the remittance account corresponding to the refund when the recharge was made.

3. The method according to claim 1, characterized in that The method further comprises: receiving a request for returning the prepaid card; Performing identity verification on the user who initiated the card return request; If the verification is successful, obtaining the balance information of the prepaid card; When the balance information is not zero, a balance refund operation is performed on the prepaid card, wherein the balance refund operation causes the refund in the balance of the prepaid card to be returned to the remittance account corresponding to the refund recharge; When the balance information is zero, a card return operation is performed on the prepaid card, and the card return operation cancels the account of the prepaid card.

4. The method according to claim 3, characterized in that The balance refund operation is performed on the prepaid card, including: Determine one or more single refunds corresponding to the balance information; Determine the remittance account information corresponding to the single refund during recharge; Generate a second refund request according to the remittance account information, the receiving account information corresponding to the prepaid card, and the amount of the single refund, and send the second refund request to the institutional platform of the receiving institution, wherein the second refund request causes the institutional platform of the receiving institution to initiate a third refund request to the overseas institutional platform corresponding to the remittance account; Obtain refund response information for the second refund request.

5. The method according to claim 4, characterized in that The method further comprises: If the amount of any single refund is insufficient to cover the refund handling fee, a refund failure risk warning message will be output.

6. The method according to claim 4, characterized in that The method further comprises: Upon receiving a confirmation message of the card refund, comparing the total amount of the one or more single refunds with the balance information; When the total amount is inconsistent with the balance information, a refund amount error message is output.

7. The method according to claim 4, characterized in that Before performing a card return operation on the prepaid card, the method further includes: Sending a refund query request for the single refund to the institutional platform of the payment collection institution; Receiving a refund query result returned by the institution platform of the payment collection institution in response to the refund query request; When it is determined according to the refund query result that the one or more single refunds are successfully refunded, the process proceeds to the step of returning the prepaid card when the balance information is zero.

8. The method according to claim 7, characterized in that The method further comprises: When it is determined according to the refund query result that any single refund fails, outputting a refund failure prompt message; If a request for continuing to refund the card is received for any of the failed single refunds, the second refund request for the single refund will continue to be sent to the institutional platform of the collection institution.

9. The method according to claim 3, characterized in that: After the prepaid card is returned, the method further includes: Sending an account cancellation inquiry request for the prepaid card to the institution platform of the payment collection institution; receiving an account cancellation query result returned by the institution platform of the payment receiving institution in response to the account cancellation query request, and outputting the account cancellation query result; In the case of account cancellation failure, if a request to continue card return is received, determining whether the prepaid card supports account cancellation; If supported, return to the step of returning the prepaid card.

10. The method according to claim 1, characterized in that The method further comprises: Upon receiving a request for querying the recharge record of the prepaid card, querying and outputting the recharge record of the prepaid card; and / or, In case of receiving a request for querying the refund record of the prepaid card, querying and outputting the refund record of the prepaid card.

11. A data processing device, characterized in that: The device comprises: A request receiving module, used for receiving a remittance recharge request for a prepaid card; An identity verification module, used to verify the identity of the user who initiated the remittance recharge request; The information output module provides the payment account information, payment institution information and international unique identifier of the payment institution corresponding to the prepaid card when the verification is passed, wherein the payment account information, payment institution information and international unique identifier corresponding to the prepaid card are used for the remittance account to remit money to the payment account corresponding to the prepaid card, and the remittance account is an overseas account; The result generating module receives a remittance recharge response to the prepaid card and generates a remittance recharge result of the prepaid card.

12. A data processing device, characterized in that: include: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, the data processing method according to any one of claims 1 to 10 is implemented.

13. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed by a processor, the data processing method according to any one of claims 1 to 10 is implemented.

14. A computer program product, characterized in that The invention comprises a computer program, which, when executed by a processor, implements the data processing method according to any one of claims 1 to 10.

Citation Information

Cited By

  • Data processing method, apparatus, and device, computer storage medium, and program product

    WO2026137936A1