Method and server device for performing cross-border money transfers

Abstract

A computer-implemented method and server device for performing a cross-border remittance is provided, the method comprising: initiating, using a remittance application on a first device, a cross-border remittance for transferring funds from a bank account of a first user to a digital wallet or bank account of a second user; sending, to a first messaging application on the first device, remittance information regarding the cross-border remittance; the first messaging application requesting user information indicative of the second user; the first messaging application sending a transaction notification to a second messaging application on a second device of the second user; in response to receiving the transaction notification, the second messaging application requesting that the second user initiate receipt of the funds; in response to initiating receipt of the funds, completing the cross-border remittance by transferring the funds to the digital wallet or bank account of the second user.

Description

Technical Field

[0001] The various aspects involve computer-implemented methods, user equipment, and server equipment for performing cross-border remittances. Background Technology

[0002] The following discussion of the background of the invention is intended to facilitate understanding of the invention. However, it should be understood that this discussion is not an admission or endorsement that any material mentioned is publicly available, known, or part of common general knowledge in any jurisdiction at the priority date of this application.

[0003] In various scenarios of cross-border remittances, the user sending funds (referred to herein as the sender or sender) and the user receiving funds (referred to herein as the receiver or recipient) may operate on different platforms (e.g., banks). Therefore, the sender's institution (referred to herein as the sending institution) and the receiver's institution (referred to herein as the receiving institution) may be associated with different platforms and / or applications. In this case, additional work may be required (e.g., switching from the sending institution's application to a communication application to notify the receiver that a cross-border remittance has been executed) and / or security risks may arise (e.g., when erroneous data about the receiver is inserted into the sending institution's application). For example, when executing a cross-border remittance using the sending institution's application, the sender may enter incorrect data about the receiver due to typos (mistakes) by the sender or typos (mistakes) by the receiver when sending the data to the sender beforehand, due to the sender mistaking incorrect data for correct data, due to translation errors (e.g., when translating from a language with one alphabet to a language with another alphabet), etc.

[0004] Therefore, there is a need to provide an improved method for performing cross-border remittances. Summary of the Invention

[0005] Various aspects of this disclosure relate to a computer-implemented method for cross-border remittances, executed by at least one processor, and comprising: initiating a cross-border remittance using a remittance application (e.g., a banking application of a first institution or an application associated with a digital wallet) running on a first user device for transferring funds from a first user's bank account to a second user's digital wallet (e.g., a WeChat Pay account) or bank account; (e.g., in response to initiating the cross-border remittance) sending remittance information (e.g., including remittance data) regarding the cross-border remittance to a first communication application on the first user device; and, in response to receiving the remittance information regarding the cross-border remittance, the first communication application requesting (e.g., ... The first communication application, provided by the first user, instructs a second user (different from the first user) on user information; (e.g., in response to receiving user information) the first communication application sends a transaction notification (e.g., to notify the second user about a cross-border remittance) to a second communication application running on a second user device (different from the first user device) associated with the second user, the transaction notification including information about the cross-border remittance; in response to receiving the transaction notification, the second communication application requests the second user to initiate the receipt of the funds; and in response to the second user initiating the receipt of the funds, the cross-border remittance is completed by transferring the funds to the second user's digital wallet or bank account.

[0006] Various aspects of this disclosure relate to a server device for performing cross-border remittances, the server device comprising: at least one processor configured to: receive, from a remittance application of a first user device (e.g., via a first institutional platform associated with the remittance application), an application programming interface (API) call associated with a communication application, the API call including remittance information regarding a cross-border remittance for transferring funds from a first user's bank account to a digital wallet (e.g., a WeChat Pay account) or a second user's bank account; and, in response to receiving the API call, (e.g., via the first institutional platform) send a transaction identifier (e.g., a Uniform Resource Locator, URL) unique to the cross-border remittance to the remittance application of the first user device, the transaction identifier including... The method includes: receiving the remittance information; receiving a transaction notification from a first instance of the communication application running on the first user device, the transaction notification including user information indicating a second user device associated with the second user; in response to receiving the transaction notification, sending remittance data to a second instance of the communication application running on the second user device, the remittance data representing the remittance information and a receiving request, wherein the receiving request includes an instruction requesting the second user on the second user device to initiate the receipt of the funds; receiving an initiation notification from the second user device, the initiation notification indicating that the second user has initiated the receipt of the funds; and in response to receiving the initiation notification, providing control instructions to complete the cross-border remittance by transferring the funds to the second user's digital wallet or bank account.

[0007] The method disclosed in this paper provides a link between a remittance application and a communication application, thereby allowing both to directly notify another user of the cross-border remittance when it is being executed via the remittance application, and increasing the security of cross-border remittances by ensuring that funds are transferred to the correct recipient user. Attached Figure Description

[0008] Throughout the accompanying drawings, it should be noted that the same reference numerals are used to depict the same or similar elements, features, and structures. The drawings are not necessarily drawn to scale; rather, the emphasis is generally placed on illustrating aspects of this disclosure. In the following description, some aspects of this disclosure are described with reference to the following drawings, in which: Figure 1 This is a block diagram illustrating an example electronic device according to various aspects of this disclosure; Figure 2 This is a block diagram illustrating an example system according to various aspects of this disclosure; Figure 3 This is a flowchart illustrating methods for performing cross-border remittances according to various aspects of this disclosure; Figure 4Aand Figure 4B This is a communication flowchart illustrating methods for performing cross-border remittances according to various aspects of this disclosure; and Figures 5A to 5C An exemplary front-end implementation of a method for performing cross-border remittances according to various aspects of this disclosure is shown. Detailed Implementation

[0009] The following detailed description refers to the accompanying drawings, which illustrate, by way of illustration, specific details and aspects in which this disclosure may be practiced. One or more aspects are described in sufficient detail to enable those skilled in the art to practice this disclosure. Other aspects may be utilized, and structural, logical, and / or electrical changes may be made, without departing from the scope of this disclosure. The aspects of this disclosure are not necessarily mutually exclusive, as some aspects may be combined with one or more other aspects to form new aspects or embodiments. The aspects are described in connection with methods, and the aspects are described in connection with devices. However, it is understood that the aspects described in connection with methods can be similarly applied to devices, and vice versa.

[0010] Figure 1 This is a block diagram illustrating an example electronic device (e.g., a user device, which may also be referred to as a client device) 100 according to various aspects. Electronic device 100 may be a laptop computer, desktop computer, tablet computer, automotive computer, smartphone, personal digital assistant, server, or other electronic device capable of running computer applications. In some aspects, electronic device 100 includes one or more processors 102, input / output (I / O) modules 104, memory (referred to in some aspects as a memory device) 106, a power supply unit 108, and one or more network interfaces 110. Electronic device 100 may include additional components. In some embodiments, processor 102, input / output (I / O) modules 104, memory 106, power supply unit 108, and network interfaces 110 may be housed together in a common housing or other components.

[0011] One or more processors 102 may be configured to execute instructions, for example, to generate output data based on data input. Instructions may include programs, code, scripts, modules, or other types of data stored in memory (e.g., memory 106). Additionally or alternatively, instructions may be encoded as pre-programmed or reprogrammable logic circuits, logic gates, or other types of hardware or firmware components or modules. The processors in one or more processors 102 may be or may include multi-core processors with multiple cores, each of which may have an independent power domain and may be configured to enter and exit different operating or performance states based on workload. Additionally or alternatively, the processors in one or more processors 102 may be or may include general-purpose microprocessors as dedicated coprocessors or another type of data processing device. In some cases, one or more processors 102 may perform high-level operations of the electronic device 100. For example, one or more processors 102 may be configured to execute or interpret software, scripts, programs, functions, executable files, or other instructions stored in memory 106.

[0012] The example I / O module 104 may include a mouse, keypad, touchscreen, scanner, optical reader and / or stylus (or other input device), through which a user of electronic device 100 can provide input to electronic device 100, and I / O module 104 may also include one or more audio speakers for providing audio output and video display devices for providing text, audiovisual and / or graphic output.

[0013] The example power unit 108 can be configured to provide power to other components of the electronic device 100. For example, other components may operate based on power provided by the power unit 108 via a voltage bus or other connection. In some embodiments, the power unit 108 may include a battery or battery system, such as a rechargeable battery. In some embodiments, the power unit 108 may include an adapter (e.g., an AC adapter) that receives an external power signal (from an external source) and converts the external power signal into an internal power signal regulated for the components of the electronic device 100. The power unit 108 may include other components or operate in other ways.

[0014] Electronic device 100 can be configured to operate in a wireless, wired, or cloud network environment (or a combination thereof). In some embodiments, electronic device 100 can access a network using network interface 110. Network interface 110 may include one or more adapters, modems, connectors, receptacles, terminals, ports, slots, etc. The wireless network accessed by electronic device 100 can operate, for example, according to a wireless network standard or another type of wireless communication protocol. For example, the wireless network can be configured to operate as a Wireless Local Area Network (WLAN), a Personal Area Network (PAN), a Metropolitan Area Network (MAN), or other types of wireless networks. Examples of WLANs include networks configured to operate according to one or more of the IEEE 802.11 family of standards (e.g., Wi-Fi networks). Examples of PANs include networks operating according to short-range communication standards (e.g., Bluetooth®, Near Field Communication (NFC), ZigBee), millimeter-wave communication, etc. The wired network accessed by electronic device 100 can include, for example, Ethernet, SONET, circuit-switched networks (e.g., using components such as SS7, cables, etc.).

[0015] Memory 106 may include a computer-readable storage medium, such as a volatile memory device, a non-volatile memory device, or both. Memory 106 may include one or more read-only memory devices, random access memory devices, buffer memory devices, or combinations of these and other types of memory devices. In some cases, one or more components of the memory may be integrated with or otherwise associated with another component of the electronic device 100. Memory 106 may store instructions executable by one or more processors 102. In some examples, memory 106 may store instructions for operating system 112 and for application 114 (hereinafter referred to as: application or app).

[0016] Depending on various aspects, memory 106 may store instructions for implementing remittance application 116. Remittance application 116 may be associated with a corresponding institution, such as a banking institution (e.g., remittance application 116 may be a banking application of a banking institution) or an online payment institution (e.g., remittance application 116 may be a digital wallet application). Remittance application 116 may be configured to enable a user to transfer funds to another institution located in another country. For example, remittance application 116 may be a banking application of a banking institution located in Singapore, allowing users to transfer funds from the banking institution's bank account to another account (e.g., a bank account or digital wallet) of another institution located in another country (e.g., China). The user's digital wallet may be a digital account that allows transfers and / or receipts. For example, a digital wallet (account) may be a WeChat Pay (WePay) account. For example, funds in a WePay account can be used for WeChat Pay.

[0017] Therefore, the remittance application 116 can be associated with a corresponding institution and can communicate with the corresponding institution's server. The corresponding institution's server can also be referred to as the corresponding institution's platform.

[0018] Depending on various aspects, memory 106 may store instructions for implementing the communication application (also referred to as the communications application) 118. The communications application 118 may be a program application of an instant messaging service provider for instant messaging (between two or more users). Depending on various aspects, the communications application 118 may include a cross-border remittance (mini) application (e.g., WeRemit) that provides the communications application 118 with the features of the cross-border remittance 208 disclosed herein.

[0019] Depending on various aspects, memory 106 may store instructions for implementing browser application 120. Browser application 120 (also known as web browser application) may be configured to allow users to access websites (also known as web pages), for example, using the website's Uniform Resource Locator (URL).

[0020] Figure 2 An exemplary system 200 according to various aspects of this disclosure is shown. System 200 may include a first user equipment 100 (1) configured to conform to electronic device 100 and a second user equipment 100 (2) configured to conform to electronic device 100. The first user equipment 100 (1) may be associated with a first user 202 (1), and the second user equipment 100 (2) may be associated with a second user 202 (2) (different from the first user).

[0021] The memory 106 of the first user equipment 100 (1) may store instructions for implementing the remittance application 116. The remittance application 116 may be associated with a first institution 204 (which may also be referred to as a sending institution). The first institution 204 may provide a first institution platform (e.g., a first institution server) for processing transactions generated via the remittance application 116.

[0022] The memory 106 of the first user device 100 (1) may store instructions for implementing the communication application 118. One or more processors 102 of the first user device 100 (1) may implement a (first) instance 118 (1) of the communication application 118 on the first user device 100 (1). The memory 106 of the second user device 100 (2) may also store instructions for implementing the communication application 118. One or more processors 102 of the second user device 100 (2) may implement a (second) instance 118 (2) of the communication application 118 on the second user device 100 (2). Hereinafter, the instance of the communication application 118 running on the first user device 100 (1) is referred to as the first communication application 118 (1), and the instance of the communication application 118 running on the second user device 100 (2) is referred to as the second communication application 118 (2). It should be understood that both the first communication application 118 (1) and the second communication application 118 (2) may be communication applications of the same instant messaging service provider (e.g., WeChat). The first user 202 (1) can log in to the first communication application 118 (1) using the corresponding first user account, and the second user 202 (2) can log in to the second communication application 118 (2) using the corresponding second user account (different from the first user account).

[0023] The second user 202 (2) may have an account at the second institution 206 (e.g., a bank account of a banking institution or a digital wallet (account) of an online payment institution). The second institution may also be referred to as the receiving institution.

[0024] According to the various aspects detailed herein, a first user 202 (1) may use remittance application 116 and a first communication application 118 (1) to make cross-border remittances 208 for transferring funds from an account (e.g., a bank account) at a first institution 204 to an account (e.g., a bank account or digital wallet) at a second institution 206 of a second user 202 (2).

[0025] System 200 may include server device 210. Server device 210 may provide one or more services (e.g., Tencent Remittance Service) associated with cross-border remittance 208. It should be understood that server device 210 is for illustrative purposes, and server device 210 may be a distributed server system providing the functions (e.g., services) detailed herein. Hereinafter, various aspects of exemplary methods for performing cross-border remittance 208 are described in detail. These aspects relate to the transmission of information between at least two devices of system 200. Such transmission may occur via the Internet. Therefore, the devices of system 200 may be linked to each other (directly or indirectly) via the Internet.

[0026] Figure 3 A flowchart is shown of a method 300 for performing cross-border remittances, according to various aspects. Method 300 may be a computer-implemented method. The method steps associated with a corresponding device (e.g., user equipment or server equipment) may be executed by at least one processor of the corresponding device.

[0027] Method 300 may include (at 302) initiating a cross-border remittance (e.g., cross-border remittance 208) using a remittance application (e.g., remittance application 116) running on a first user device (e.g., first user device 100 (1)) to transfer funds from the bank account of the first user (e.g., first user 202 (1)) to the digital wallet or bank account of the second user (e.g., second user 202 (2)).

[0028] Method 300 may include (at 304) sending remittance information about the cross-border remittance to a first communication application (e.g., first communication application 118(1)) on a first user device in response to initiating the cross-border remittance.

[0029] Method 300 may include (at 306) in response to receiving remittance information, a first communication application requesting (e.g., provided by a first user) user information indicating a second user.

[0030] Method 300 may include (at 308) in response to receiving user information, a first communication application sending a transaction notification to a second communication application (e.g., second communication application 118(2)) running on a second user device (e.g., second user device 100(2)) associated with the second user. The transaction notification may include information about cross-border remittances. The first communication application may send the transaction notification via server device 210.

[0031] Method 300 may include (at 310) in response to receiving a transaction notification, a second communication application requesting a second user to initiate the receipt of funds (e.g., by implementing a receive button within a dialog box (chat) window associated with a text conversation between the first user and the second user).

[0032] Method 300 may include (at 312) responding to a second user's initiation of receiving funds by completing a cross-border remittance by transferring the funds to the second user's digital wallet or bank account.

[0033] Figure 4A and Figure 4B A communication flowchart 400 is shown, including an exemplary detailed implementation of method 300, and Figures 5A to 5C An exemplary front-end implementation is shown.

[0034] In 402, the first (sending) user 202 (1) can initiate a cross-border remittance 208 using the remittance application 116 on the first user equipment 100 (1). The remittance application 116 can access the platform of the first (sending) institution 204 to initiate the cross-border remittance 208. The graphical user interface (GUI) of the remittance application 116 can display one or more pages 502 corresponding to the cross-border remittance 208.

[0035] If the first institution 204 directly completes the cross-border remittance 208 and the process is finished, the sending user 202(1) will not know whether the receiving user 202(2) has received a notification that the remittance transaction has been initiated, and may have to manually exit the remittance application 116 to the communication application 118 to notify the receiving user 202(2) that the funds have been sent via text message or screenshot. Therefore, after receiving a personal message from the sending user 202(1), the receiving user 202(2) may have to exit the communication application 118 and enter the receiving platform separately to track whether the funds have been received. In addition, if the sending user 202(1) enters incorrect data (incorrectly or without better understanding) about the receiving user 202(2), they will not know. The processing according to this disclosure allows for the mitigation of these two problems. The aspects improve the experience by providing the sender with a seamless way to send transaction notifications directly from the remittance application 116 to the communication application 118 (e.g., WeChat, which can be connected to a mini-program). The receiving user can then click the notification button within the dialog window of the conversation to complete the process of receiving funds.

[0036] At 404, the first institution 204 may send a transfer request to the server device 210 in accordance with the cross-border remittance 208. The remittance application 116 may (e.g., via the first institution 204) send an application programming interface (API) call to the server device 210. The API call may (e.g., in addition to the transfer request) also include a first user identifier identifying the second user 202 (2). For example, the user identifier may be or may include the second user 202 (2)’s mobile identifier (such as a mobile phone number) and / or the second user 202 (2)’s legal name. The mobile phone number may be linked to an account of the communication application 118 and may be used as a routing identifier (e.g., as key routing information). Optionally, the server device 210 may check the balance of the first user 202 (1)’s bank account.

[0037] At 406, server device 210 sends a transfer request to second institution 206 (e.g., forwarding a transfer request received from first institution 204). In response to receiving (at 408) a response instructing the creation of a transfer, server device 210 may (at 412) send a unique transaction identifier for cross-border remittance 208 to remittance application 116 (e.g., via first institution 204 at 410 and 412). The transaction identifier may include remittance information about cross-border remittance 208 (e.g., one or more of the following: the date and / or time of the transaction (i.e., cross-border remittance 208), the legal name of the sending user, the legal name of the receiving user, the amount of the transaction (i.e., how much money is being transferred), the currency to be transferred, etc.). Therefore, if the transaction is successfully processed, server device 210 may provide an API response (an API call) to first institution 204. A unique transaction identifier can be generated for each cross-border remittance 208.

[0038] In response to receiving a transaction identifier, the remittance application 116 may provide graphical components (e.g., buttons, such as a share button) on its graphical user interface (GUI) that allow the first user 202(1) to provide processing instructions (instructing the first communication application 118(1) to process the cross-border remittance 208), for example, by selecting the share button. For example, the remittance application 116 may display a transaction completion page with the share button 504 embedded (e.g., as shown in the image). Figure 5A(②) Therefore, it should be understood that graphical components (e.g., share buttons) can be directly linked to transaction identifiers. Thus, when a specific cross-border remittance 208 is initiated and a corresponding unique transaction identifier is received, the graphical component (e.g., share button) can be dynamically provided on the GUI (e.g., displayed in the bottom area of ​​the GUI of the first communication application 118 (1)). Illustratively, each time a transaction identifier associated with a cross-border remittance 208 allocated by the dual-signal is received, the unique transaction identifier (hereinafter: transaction identifier) ​​can be dynamically mapped to the GUI (e.g., displayed in its bottom area). Illustratively, the information behind the graphical element (e.g., share button) can be dynamic based on the (received, unique) transaction identifier. This ensures that when the sending user 202 (1) clicks the graphical element (e.g., share button), the remittance information (which is included in the transaction identifier, such as transaction date and / or transaction time, legal name of the sending user, legal name of the receiving user, transaction amount, funds, etc.) can be automatically mapped to the corresponding share instance (for sharing via the first communication application 118 (1)). Therefore, depending on various aspects, the remittance application 116 may dynamically provide graphical components (e.g., a share button) on the GUI of the remittance application 116 in response to receiving a transaction identifier.

[0039] In 414, the first user can provide processing instructions (e.g., by selecting a share button), and the remittance application 116 can (directly or indirectly) invoke (in 416) the first communication application 118 (1). Thus, remittance information can be sent to the first communication application 118 (1).

[0040] In some respects, remittance application 116 may include a (pre-packaged) software development kit (SDK) that allows remittance application 116 to invoke first communication application 118 (1). In this case, remittance application 116 may, in response to receiving a processing instruction (e.g., in response to a first user 202 (1) selecting (e.g., clicking) a share (to first communication application 118 (1)) button), directly invoke first communication application 118 (1) (and provide it with remittance information).

[0041] In other respects, the transaction identifier may include or may be a Uniform Resource Locator (URL), and the remittance application 116 may, in response to receiving a processing instruction (e.g., in response to a first user 202 (1) selecting (e.g., clicking) a share (to first communication application 118 (1)) button), invoke browser application 120 to invoke a website corresponding to the URL. The website may include functionality to invoke (at 510) the first communication application 118 (1) using a (pre-packaged) SDK (e.g., in response to selecting a button 506 embedded in the website and optionally further allowing invocation of the first communication application 118 (1) at 508). The website may be an H5 browser page. This browser page may be uniquely generated for a specific cross-border remittance 208. As described above, graphical components (e.g., the share button) may be directly linked to the transaction identifier (unique to cross-border remittance 208) and thus may be dynamically mapped to the GUI (e.g., at its bottom) for each cross-border remittance 208 being processed.

[0042] Depending on the circumstances, a URL can be encrypted using urlencode (and therefore needs to be decrypted using urlencode).

[0043] Then, the first communication application 118(1) can display information about cross-border remittance 208 (e.g., at 512). The first communication application 118(1) may include a cross-border remittance (mini) application (e.g., WeRemit) configured to display information. The information about cross-border remittance 208 may also be referred to as information relating to cross-border remittance 208 and may be information relating to cross-border remittance 208. Information relating to cross-border remittance 208 (e.g., information relating to cross-border remittance 208) may include, for example, one or more of the following: the amount of the transaction, the sending country of the first institution 204, the receiving country of the second institution 206, the legal name of the second user 202(2), the legal name of the first user 202(1), etc.

[0044] At 418, the first communication application 118 (1) may request (the first user 202 (1) to provide (e.g., select)) user information indicating the second user 202 (2) (e.g., at 516). In some aspects, the first user 202 (1) may be allowed to select himself / herself as the second user 202 (2) in order to transfer funds from a bank account in one country to a digital wallet or bank account in another country via cross-border remittance 208.

[0045] The first communication application 118 (1) can be configured such that the first user 202 (1) can provide user information by selecting the second user 202 (2) from his / her contact list (pre-stored in the first communication application 118 (1)).

[0046] In response to receiving user information (and optionally, if the second user is different from the first user), the first communication application 118(1) can (in 420) send a transaction notification (e.g., via server device 210) to a second communication application 118(2) running on the second user device 100(2). Thus, the second user 202(2) can be notified of the cross-border remittance 208 initiated by the first user 202(1). The second communication application 118(2) can be configured to display information about the cross-border remittance 208 on the GUI 520, 522 of the second communication application 118(2). The first communication application 118(1) can be configured to display information about the cross-border remittance 208 on the GUI 520 of the first communication application 118(1). The first communication application 118 (1) and / or the second communication application 118 (2) can be configured to display information about the cross-border remittance 208 in a dialog box (also referred to as a chat box (abbreviated as: chat) or conversation box) window associated with a text conversation between the first user 202 (1) and the second user 202 (2) on the GUI 520. For example, a clickable app card 520 can be displayed to the first user 202 (1) and / or the second user 202 (2). The clickable app card 520 can include some information about the cross-border remittance 208. When the app card is clicked, the (first and / or second) communication application 118 can enter pages 522, 526, 528 to display transaction details (and optionally, display a further customizable skin selected by the sending user).

[0047] Depending on the aspects, the first communication application 118(1) can be configured such that when a request is made for user information about the second user 202(2), the first user 202(1) can (on the GUI of the first communication application 118(1)) select how the GUI of the second communication application 118(2) should display (transaction) information (e.g., theme and / or font) about the cross-border remittance 208. For example, the first user 202(1) can select a theme and / or font and / or skin in 514 (see also...). Figure 5B Exemplary themes and / or skins are shown. Figure 5B These instructions regarding themes and / or fonts can be sent along with transaction notifications to the second communication application 118 (2). Optionally, the first communication application 118 (1) can be configured such that the first user 202 (1) can also upload one or more photos and / or one or more videos and send them along with transaction notifications.

[0048] Depending on the aspects, the first communication application 118(1) can be configured such that the first user 202(1) can (e.g., in 518) provide a user-specific text message that will be displayed on the GUI of the second communication application 118(2) (e.g., in 520) along with transaction information. This text message can be sent to the second communication application 118(2) along with a transaction notification.

[0049] Illustratively, personalized options can be inserted into (remittance) transaction notifications, where the sending user can choose different skins and / or themes for how the receiving user receives the transaction notification (optionally along with a personalized text message).

[0050] Information about Cross-Border Remittance 208 can be displayed via the GUI of a Cross-Border Remittance (mini) application (e.g., WeRemit, also known as a mini program in WeChat).

[0051] In 422, the second communication application 118(2) can request the second user 202(2) to initiate the receipt of funds. For example, the GUI of the second communication application 118(2) can display a button 524 requesting the second user 202(2) to initiate the receipt of funds. The receiving button 524 can be an operable button that allows the initiation of an action to receive funds (e.g., money).

[0052] In response to a second user 202 (2) initiating the receipt of funds, a second communication application 118 (2) can (at 424) send a receipt instruction to server device 210. Server device 210 can then communicate with first institution 204 (at 426) and / or second institution 206 to complete a cross-border remittance 208 by transferring funds to the second user 202 (2)'s digital wallet or bank account (at second institution 206). In some respects, the transfer of funds can occur via the online payment account of server device 210.

[0053] Depending on the aspects, server device 210 can be configured to ensure the security and / or confidentiality of cross-border remittance 208. The receiving instruction may include a second identifier of the second user 202 (2). The second identifier may be a user identifier (e.g., a mobile phone number) of the account that the second user 202 (2) logs into in the second communication application 118 (2). Server device 210 can be configured to determine whether the first identifier and the second identifier correspond to each other (i.e., are the same), and to complete cross-border remittance 208 only if the first identifier and the second identifier correspond to each other. Therefore, if the transaction notification is sent to the wrong receiving user (different from the second user selected when initiating cross-border remittance 208), cross-border remittance 208 may not be completed (e.g., may not be processed further). As detailed herein, the first identifier can be used as transaction routing information. An incorrect receiving user may be due, for example, because the first user 202 (1) selected the wrong receiving user in 418, 516.

[0054] refer to Figure 4B Server device 210 (e.g., at least one of its processors) can be configured to allow a first user 202 (1) and / or a second user 202 (2) to request the status of cross-border remittance 208 after it has been completed. For example, the first user 202 (1) can request the status of cross-border remittance 208 via a first communication application 118 (1) at 430. Server device 210 can request a first status of cross-border remittance 208 from a first institution 204 (at 434) and a second status of cross-border remittance 208 from a second institution 206 (at 436). In response to receiving a corresponding response, server device 210 can use the first and second statuses to determine the status of cross-border remittance 208. Server device 210 can send the status of cross-border remittance 208 to the first communication application 118 (1) at 438. Therefore, the second user 202 (2) can request the status of cross-border remittance 208 via the second communication application 118 (2) at 432. Server device 210 can request a first status and a second status, and then send the status of cross-border remittance 208 (at 440) to the second communication application 118 (2).

[0055] refer to Figure 5C Server device 210 (e.g., at least one of its processors) may be configured to control the GUI of the first communication application 118 (1) to display the status of cross-border remittance 208 (at 526). Server device 210 (e.g., at least one of its processors) may be configured to control the GUI of the second communication application 118 (2) to display the status of cross-border remittance 208 (at 528).

[0056] Illustratively, the sending and receiving users can check the status of cross-border remittance 208 within the communication application 118 (e.g., within the cross-border remittance (mini) application).

[0057] Illustratively, the various aspects relate to methods for connecting sending and receiving users operating on different (banking) platforms (which is likely the case for most cross-border remittance scenarios). For example, the method provides a connection between sending and receiving users operating on two different (mobile) applications.

[0058] Illustratively, the functions of remittance application 116 and communication application 118 are linked to each other, thereby increasing the security and convenience of performing cross-border remittances 208. Furthermore, skin options are provided, allowing the sending user to choose how the receiving user will see transaction notifications (notifying the receiving user about cross-border remittances 208).

[0059] While the methods described above are illustrated and depicted as a series of steps or events, it should be understood that any order of these steps or events should not be construed as limiting. For example, some steps may occur in a different order and / or simultaneously with other steps or events besides those shown and / or described herein. Furthermore, not all steps shown are necessary to implement one or more aspects or embodiments described herein. Additionally, one or more steps depicted herein may be performed in one or more separate actions and / or phases.

[0060] A non-transitory computer-readable medium is also provided for storing computer-executable code, the computer-executable code including instructions for performing at least a portion of cross-border remittances according to method 300 (and optionally according to one or more aspects of detailed communication flowchart 400). The aforementioned instructions may include computer program elements or computer program products.

[0061] Some of the subjects and operations described in this specification can be implemented in digital electronic circuits, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations thereof. Some of the subjects described in this specification can be implemented as one or more computer programs, that is, one or more modules of computer program instructions encoded on a computer storage medium for execution by a data processing apparatus or for controlling the operation of a data processing apparatus. The computer storage medium can be or can be included in a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination thereof. Furthermore, although the computer storage medium is not a propagating signal, it can be a source or destination of computer program instructions encoded in an artificially generated propagating signal. The computer storage medium can also be or be contained in one or more separate physical components or media (e.g., multiple CDs, disks, or other storage devices).

[0062] The following embodiments relate to various aspects of this disclosure. It should be noted that aspects described with reference to the device can be implemented accordingly in the method, and vice versa.

[0063] Example 1 is a computer-implemented method for cross-border remittances, executed by at least one processor, and comprising: initiating a cross-border remittance using a remittance application (e.g., a banking application of a first institution or an application associated with a digital wallet) running on a first user device to transfer funds from a first user's bank account to a second user's digital wallet (e.g., a WeChat Pay account) or bank account; (e.g., in response to initiating the cross-border remittance) sending remittance information (e.g., including remittance data) regarding the cross-border remittance to a first communication application on the first user device; and, in response to receiving the remittance information regarding the cross-border remittance, the first communication application requesting (e.g., provided by the first user) an instruction. User information of a second user (different from the first user); (e.g., in response to receiving user information) a first communication application sends a transaction notification (e.g., to notify the second user of cross-border remittance information) to a second communication application running on a second user device (different from the first user device) associated with the second user, the transaction notification including information about the cross-border remittance (e.g., cross-border remittance information); in response to receiving the transaction notification, the second communication application requests the second user to initiate the receipt of the funds; and in response to the second user initiating the receipt of the funds, the cross-border remittance is completed by transferring the funds to the second user's digital wallet or bank account.

[0064] In Example 2, the method of Example 1 may optionally further include: the remittance application receiving a processing instruction to process cross-border remittances using a first communication application (e.g., in response to a first user selecting a button, such as a button displayed in the remittance application to share to the first communication application), wherein in response to receiving the processing instruction, remittance information is sent to the first communication application.

[0065] In Example 3, the method of Example 1 or 2 may optionally further include: the remittance application sending an application programming interface (API) call to a server associated with a first communication application, the API call including remittance information (e.g., key routing information including a second user); the remittance application receiving from the server a transaction identifier (e.g., a Uniform Resource Locator, URL) unique to the cross-border remittance, the transaction identifier including the remittance information.

[0066] In Example 4, the method of Example 3 may optionally include sending remittance information to a first communication application, including: in response to receiving a transaction identifier (and optionally further in response to receiving a processing instruction, provided that in conjunction with Example 2), the remittance application invokes the first communication application and sends the transaction identifier to the first communication application.

[0067] In Example 5, the method of Example 3 may optionally include: the transaction identifier including a Uniform Resource Locator (URL), and sending remittance information to the first communication application includes: in response to receiving the transaction identifier (and optionally further in response to receiving a processing instruction, provided that in conjunction with Example 2), the remittance application instructs a browser application on the first user device to invoke the website corresponding to the Uniform Resource Locator; and the browser application invokes the first communication application to transmit the transaction identifier to the first communication application.

[0068] In Example 6, the subject matter of any one of Examples 1 to 5 may optionally include: remittance information and transaction notification each including a first user identifier identifying the second user (e.g., the second user's mobile identifier, such as a mobile phone number and / or the second user's legal name); and wherein completing the cross-border remittance in response to the second user initiating the receipt of the funds includes: in response to the second user initiating the receipt of the funds, determining whether the first user identifier corresponds to a second user identifier associated with the second communication application; and completing the cross-border remittance only if it is determined that the first user identifier corresponds to the second user identifier.

[0069] In Example 7, the subject of any one of Examples 1 to 6 may optionally include: a transaction notification including transaction information about cross-border remittances; and the method further includes a graphical user interface (GUI) of the second communication application, the GUI displaying the transaction information.

[0070] In Example 8, the subject of Example 7 may optionally include: a second communication application requesting a second user to initiate the receipt of funds includes a graphical user interface of the second communication application displaying a receive button that requests the second user to initiate the receipt of funds (wherein, optionally, the second user initiating the receipt of funds includes receiving data indicating that the second user has selected the receive button).

[0071] In Example 9, the subject of Example 7 or 8 may optionally include: the graphical user interface of the second communication application displays transaction information (and optionally further displays a receive button) within a dialog box (chat) window associated with a text conversation between the first user and the second user.

[0072] In Example 10, the method of any one of Examples 7 to 9 may optionally further include: a first communication application receiving a first instruction regarding how the graphical user interface of a second communication application should display transaction information (e.g., a subject), wherein the transaction notification includes the first instruction; and / or the first communication application receiving a second instruction instructing a user-specific text message, the user-specific text message being displayed on the graphical user interface of the second communication application together with the transaction information, wherein the transaction notification includes the second instruction.

[0073] In Example 11, the subject matter of any one of Examples 1 to 10 may optionally include: a first user’s bank account is associated with a first institutional platform, and a second user’s digital wallet or bank account is associated with a second institutional platform that is different from the first institutional platform.

[0074] In Example 12, the subject of any of Examples 1 to 11 may optionally include: a first communication application and / or a second communication application including a cross-border remittance (small, mini) application.

[0075] In Example 13, the method of any one of Examples 1 to 12 may optionally further include: in response to the first communication application receiving an instruction indicating the status of a request for cross-border remittance, the graphical user interface (GUI) of the first communication application displays information indicating whether the second user has initiated the receipt of funds and / or whether the funds have been transferred to the second user's digital wallet or bank account.

[0076] In Example 14, the method of any one of Examples 1 to 13 may optionally further include: in response to the second communication application receiving an instruction indicating the status of a request for cross-border remittance, the graphical user interface (GUI) of the second communication application displays information indicating whether the funds have been transferred to the second user's digital wallet or bank account.

[0077] Example 15 is a non-transitory computer-readable medium storing computer-executable code, the computer-executable code including instructions for cross-border remittances according to any one of Examples 1 to 14.

[0078] Example 16 is a user device for performing cross-border remittances, the user device comprising: at least one processor configured to: initiate a cross-border remittance using a remittance application (e.g., a banking application of a first institution or an application associated with a digital wallet) to transfer funds from a first user's bank account to a second user's digital wallet (e.g., a WeChat Pay account) or bank account; (e.g., in response to initiating the cross-border remittance) send remittance information (e.g., including remittance data) about the cross-border remittance to a first communication application on the user device; control the first communication application to request (e.g., provided by the first user) user information of a second user (different from the first user), and in response to receiving the user information, send a transaction notification and a reception request (e.g., to notify the second user of information about the cross-border remittance) to a second communication application running on another (e.g., a second) user device associated with the second user, wherein the transaction notification includes information about the cross-border remittance, and wherein the reception request includes an instruction to request the second user to initiate the receipt of the funds.

[0079] In Example 17, the subject matter of Example 16 may optionally include that the at least one processor is further configured to: receive a processing instruction via a remittance application to process a cross-border remittance using a first communication application (e.g., in response to a first user selection button, such as a button displayed in the remittance application to share to the first communication application); and in response to receiving the processing instruction, send the remittance information to the first communication application.

[0080] In Example 18, the subject matter of Example 16 or 17 may optionally include: the at least one processor is further configured to: control the remittance application to send an application programming interface (API) call to a server associated with the first communication application, the API call including the remittance information (e.g., including key routing information of the second user); and receive, via the remittance application, a transaction identifier (e.g., a Uniform Resource Locator, URL) unique to the cross-border remittance from the server, the transaction identifier including the remittance information.

[0081] In Example 19, the subject matter of Example 18 may optionally include that the at least one processor is further configured to: in response to receiving a transaction identifier (and optionally further in response to receiving a processing instruction, provided that in conjunction with Example 2), control the remittance application to invoke the first communication application and transmit the transaction identifier to the first communication application.

[0082] In Example 20, the subject of Example 18 may optionally include a transaction identifier comprising a Uniform Resource Locator (URL), wherein at least one processor is further configured to: in response to receiving the transaction identifier (and optionally further in response to receiving a processing instruction, provided that in conjunction with Example 2), control a remittance application to instruct a browser application on a first user device to invoke a website corresponding to the Uniform Resource Locator; and control the browser application to invoke the first communication application to transmit the transaction identifier to the first communication application.

[0083] In Example 21, the subject of any one of Examples 16 to 20 may optionally include that the at least one processor is further configured to: receive via the first communication application a first instruction regarding how the graphical user interface of the second communication application should display the transaction information (e.g., the subject), wherein the transaction notification includes the first instruction; and / or receive via the first communication application a second instruction instructing a user-specific text message to be displayed on the graphical user interface of the second communication application along with the transaction information, wherein the transaction notification includes the second instruction.

[0084] In Example 22, the subject matter of any one of Examples 16 to 21 may optionally include: a first user’s bank account is associated with a first institutional platform, and wherein a second user’s digital wallet or bank account is associated with a second institutional platform that is different from the first institutional platform.

[0085] In Example 23, the subject of any of Examples 16 through 22 may optionally include: the first communication application includes a cross-border remittance (small, mini) application.

[0086] In Example 24, the subject matter of any one of Examples 16 to 23 may optionally include that the at least one processor is further configured to: receive, via the first communication application, an instruction requesting the status of the cross-border remittance; and, in response to receiving the instruction, control the graphical user interface (GUI) of the first communication application to display information indicating whether the second user has initiated the receipt of the funds and / or whether the funds have been transferred to the second user's digital wallet or bank account.

[0087] Example 25 is a user device for receiving cross-border remittances, the user device comprising: at least one processor configured to: receive remittance data representing a transaction notification and a receipt request from another (e.g., a first) user device, wherein the transaction notification includes information regarding a cross-border remittance for transferring funds from a bank account of the other (e.g., the first) user to a digital wallet (e.g., a MyPay account) or bank account of a user of the user device, and wherein the receipt request includes an instruction requesting a user of the user device to initiate the receipt of the funds; in response to receiving the remittance data, controlling a communication application on the user device to request the user to initiate the receipt of the funds; and in response to receiving an initiation instruction indicating that the second user has initiated the receipt of the funds, providing control instructions to complete the cross-border remittance by transferring the funds to the user's digital wallet or bank account.

[0088] In Example 26, the subject matter of Example 25 may optionally include: remittance data including a first user identifier (e.g., a second user's mobile identifier, such as a mobile phone number and / or the second user's legal name) that identifies a user device; and wherein the at least one processor is further configured to: determine, in response to receiving the initiation instruction, whether the first user identifier corresponds to a second user identifier associated with the communication application; and only provide the control instruction to complete the cross-border remittance if it is determined that the first user identifier corresponds to the second user identifier.

[0089] In Example 27, the subject matter of Example 25 or 26 may optionally include that the at least one processor is further configured to: in response to receiving the remittance data, control the graphical user interface (GUI) of the communication application to display transaction information about the cross-border remittance.

[0090] In Example 28, the subject matter of Example 27 may optionally include that the at least one processor is further configured to: control the graphical user interface of the communication application to display a receive button to request the user to initiate the receipt of the funds (and optionally in response to the user selecting the receive button to receive the initiation instruction).

[0091] In Example 29, the subject of Example 27 or 28 may optionally include that the at least one processor is further configured to control the graphical user interface to display the transaction information (and optionally also the receive button) within a dialog box (chat) window associated with a text conversation between the user and the other user.

[0092] In Example 30, the subject of any one of Examples 27 to 29 may optionally include that the at least one processor is further configured to: wherein the remittance data further includes a first instruction (e.g., subject) regarding how the graphical user interface of the communication application should display the transaction information, wherein the at least one processor is further configured to control the communication application to display the transaction information according to the first instruction; and / or wherein the remittance data further includes a second instruction instructing (from the other user) a text message to be displayed together with the transaction information on the graphical user interface of the communication application, wherein the at least one processor is further configured to control the communication application to display the text message and the transaction information together.

[0093] In Example 31, the subject matter of any one of Examples 25 to 30 may optionally include: the other user’s bank account is associated with a first institutional platform, and wherein the user’s digital wallet or bank account is associated with a second institutional platform different from the first institutional platform.

[0094] In Example 32, the subject of any of Examples 25 to 31 may optionally include: the communication application includes a cross-border remittance (mini) application.

[0095] In Example 33, the subject matter of any one of Examples 25 to 32 may optionally include that the at least one processor is further configured to: receive, via the communication application, an instruction requesting the status of the cross-border remittance; and, in response to receiving the instruction, control the graphical user interface (GUI) of the communication application to display information indicating whether the funds have been transferred to the user's digital wallet or bank account.

[0096] Example 34 is a server device for performing cross-border remittances, the server device comprising: at least one processor configured to: receive, from a remittance application of a first user device (e.g., via a first institutional platform associated with the remittance application) an application programming interface (API) call associated with a communication application, the API call including remittance information for a cross-border remittance to transfer funds from a first user's bank account to a second user's digital wallet (e.g., a WeChat Pay account) or bank account; and, in response to receiving the API call, (e.g., via the first institutional platform) send a transaction identifier (e.g., a Uniform Resource Locator URL) unique to the cross-border remittance to the remittance application of the first user device, the transaction identifier including the remittance information. The process includes: receiving transaction notifications from a first instance of the communication application running on the first user device, the transaction notifications including user information indicating a second user device associated with the second user; in response to receiving the transaction notifications, sending remittance data to a second instance of the communication application running on the second user device, the remittance data representing the remittance information and a receiving request, wherein the receiving request includes an instruction requesting the second user on the second user device to initiate the receipt of the funds; receiving an initiation notification from the second user device, the initiation notification indicating that the second user has initiated the receipt of the funds; and in response to receiving the initiation notification, providing control instructions to complete the cross-border remittance by transferring the funds to the second user's digital wallet or bank account.

[0097] In Example 35, the subject matter of Example 34 may optionally include: remittance information including a first user identifier identifying the second user (e.g., a mobile identifier of the second user, such as a mobile phone number and / or the legal name of the second user); wherein the initiating notification includes a second user identifier associated with a second instance of the communication application running on the second user's device; and wherein the at least one processor is configured to determine whether the first user identifier corresponds to the second user identifier, and to provide the control instruction to complete the cross-border remittance only if it is determined that the first user identifier corresponds to the second user identifier.

[0098] In Example 36, the subject matter of Example 34 or 35 may optionally include: a first user’s bank account is associated with a first institution (platform), and a second user’s digital wallet or bank account is associated with a second institution (platform) that is different from the first institution (platform).

[0099] In Example 37, the subject matter of Example 36 may optionally include that the at least one processor is further configured to: in response to receiving an instruction from the first instance of the communication application running on the first user device to request a status of the cross-border remittance, send a first request to the first institution requesting a first status of the cross-border remittance, and send a second request to the second institution requesting a second status of the cross-border remittance; and in response to receiving a first response from the first institution in response to the first request and a second response from the second institution in response to the second request, determine the status of the cross-border remittance using the first status and the second status, and send the status of the cross-border remittance to the first instance of the communication application running on the first user device.

[0100] In Example 38, the subject matter of Example 36 or 37 may optionally include that the at least one processor is further configured to: in response to receiving an instruction from the second instance of the communication application running on the second user device to request the status of the cross-border remittance, send a first request to the first institution requesting a first status of the cross-border remittance, and send a second request to the second institution requesting a second status of the cross-border remittance; and in response to receiving a first response from the first institution in response to the first request and a second response from the second institution in response to the second request, determine the status of the cross-border remittance using the first status and the second status, and send the status of the cross-border remittance to the second instance of the communication application running on the second user device.

[0101] Example 39 is a system for cross-border remittances, the system comprising: a first user equipment according to any one of Examples 16 to 24; a second user equipment according to any one of Examples 25 to 33; and optionally, a server equipment according to any one of Examples 34 to 38.

[0102] It should be understood that examples involving devices (e.g., user devices or server devices) can be executed in the corresponding computer-implemented method, and a non-transitory computer-readable medium can store instructions for executing (using at least one processor) the corresponding computer-implemented method.

[0103] This article details various aspects of the ShareLink-Messenger embedded remittance feature.

[0104] It should be understood that, unless the context clearly indicates otherwise, the singular terms “a,” “an,” and “the” include plural references. Similarly, unless the context clearly indicates otherwise, the word “or” is intended to include “and.”

[0105] It will be further understood that the terms “comprising,” “having,” “including,” and “containing” are open-ended connecting verbs. Therefore, a method or apparatus that “comprising,” “having,” “including,” or “containing” one or more steps or elements possesses one or more of those steps or elements, but is not limited to possessing only one or more of those steps or elements. Similarly, the elements of a method step or apparatus that “comprising,” “having,” “including,” or “containing” one or more features possess one or more of those features, but are not limited to possessing only those one or more features. Furthermore, a device or structure configured in a certain way is configured at least in this manner, but may also be configured in a manner not listed.

[0106] As used herein throughout the specification and claims, approximate language can be applied to modify any quantitative representation that may vary permissibly without altering its underlying function. Therefore, values ​​modified by one or more terms such as “about” or “substantially” are not limited to specified exact values, but rather refer to values ​​within operational tolerances acceptable for the intended application of the embodiment. In some cases, approximate language may correspond to the precision of the instrument used to measure the value.

[0107] As used herein, a phrase of the form “at least one of A or B” may include A, or B, or both A and B. Accordingly, a phrase of the form “at least one of A, B, or C”, or including further listed items, may include any and all combinations of one or more of the relevant listed items.

[0108] The term “exemplary” may be used herein to mean “serving as an example, instance, or illustration.” Any aspect or design described herein as “exemplary” is not necessarily to be construed as superior to or better than other aspects or designs.

[0109] The terms “at least one” and “one or more” can be understood to include numerical values ​​greater than or equal to one (e.g., one, two, three, four, [...], etc.). The term “multiple” can be understood to include numerical values ​​greater than or equal to 2 (e.g., 2, 3, 4, 5, ..., etc.). The phrase “at least one of ...” relating to a group of elements can be used herein to mean at least one element from the group of these elements. For example, the phrase “at least one of ...” relating to a group of components can be used herein to indicate a choice of: one of the listed components, multiple of the listed components, multiple individual listed components, or multiple of multiple listed components.

[0110] The terms “plural” and “multiple” in the specification and claims explicitly refer to a quantity greater than one. Therefore, any phrase explicitly referring to the aforementioned terms (e.g., “multiple (objects)”) explicitly refers to more than one of the stated objects. The terms “group”, “set”, “collection”, “series”, “sequence”, “grouping”, etc., in the specification and claims, if applicable, refer to a quantity equal to or greater than one, i.e., one or more.

[0111] As used herein, the term "data" can be understood to include information in any suitable analog or digital form, such as as a file, a portion of a file, a collection of files, a signal or stream, a portion of a signal or stream, a collection of signals or streams, etc. Furthermore, the term "data" can also be used to refer to information, for example, in the form of a pointer. However, the term "data" is not limited to the foregoing examples and can take various forms and represent any information as understood in the art. Any type of information as described herein can be processed, for example, via one or more processors in a suitable manner, such as as data.

[0112] The "transmission" of information can be the transmission of data representing that information. The "transmission" of data can be direct transmission (without any manipulation of the data) or indirect transmission (with some processing of the data). For example, a first device that sends data to a second device can indirectly send data by sending data representing some specific information to a third device (e.g., a server device), and the third device can send data representing information (e.g., processed or unprocessed) to the second device.

[0113] For example, the terms "processor" or "controller" as used herein can be understood as any type of entity that allows the processing of data. Data can be processed according to one or more specific functions performed by the processor or controller. Furthermore, as used herein, a processor or controller can be understood as any type of circuit, such as any type of analog or digital circuit. A processor or controller can therefore be or include analog circuits, digital circuits, mixed-signal circuits, logic circuits, processors, microprocessors, central processing units (CPUs), graphics processing units (GPUs), digital signal processors (DSPs), field-programmable gate arrays (FPGAs), integrated circuits, application-specific integrated circuits (ASICs), etc., or any combination thereof. Any other type of implementation of the corresponding functions, which will be further described in detail below, can also be understood as a processor, controller, or logic circuit. It should be understood that any two (or more) processors, controllers, or logic circuits detailed herein can be implemented as a single entity with equivalent functions, and conversely, any single processor, controller, or logic circuit detailed herein can be implemented as two (or more) separate entities with equivalent functions.

[0114] As used herein, the term "memory" can be understood as a computer-readable medium (e.g., a non-transitory computer-readable medium) in which data or information can be stored for retrieval. Therefore, references to "memory" included herein can be understood to refer to volatile or non-volatile memory, including random access memory (RAM), read-only memory (ROM), flash memory, solid-state storage, magnetic tape, hard disk drive, optical drive, and any combination thereof. Furthermore, it should be understood that registers, shift registers, processor registers, data buffers, etc., are also covered by the term memory herein. It should also be understood that a single component referred to as "memory" or "memory" can consist of more than one different type of memory, and therefore can refer to a collection of components including one or more types of memory. It is readily understood that any single memory component can be separated into multiple commonly equivalent memory components, and vice versa. Furthermore, while memory can be depicted as separate from one or more other components (as in the figures), it should be understood that memory can be integrated within another component, such as on a common integrated chip.

[0115] The term "module" as detailed herein refers to or forms part of or constitutes, in a system-on-a-chip, an application-specific integrated circuit (ASIC), electronic circuitry, combinational logic circuitry, a field-programmable gate array (FPGA), a processor (shared, dedicated, or grouped) that executes code, other suitable hardware components that provide said functionality, or a combination of some or all of the foregoing. The term "module" may include memory (shared, dedicated, or grouped) that stores code executed by the processor.

[0116] Unless otherwise stated, the terms “first,” “second,” and “third” used in detail herein are used to distinguish one element from another similar element and do not necessarily indicate order or relative importance. For example, a first table and a second table can be used to distinguish two tables that include different data points.

[0117] Some of the operations described herein can be implemented as operations performed by a data processing device on data stored on one or more computer-readable storage devices or received from other sources.

[0118] The term "data processing device" encompasses all types of devices, apparatuses, and machines used for processing data, including, for example, programmable processors, computers, systems-on-a-chip, or a combination thereof. The device may include special-purpose logic circuitry, such as FPGAs (Field-Programmable Gate Arrays) or ASICs (Application-Specific Integrated Circuits). In addition to hardware, the device may also include code that creates an execution environment for the computer program in question, such as code constituting processor firmware, protocol stacks, database management systems, operating systems, cross-platform runtime environments, virtual machines, or combinations thereof.

[0119] A computer program (also known as a program, software, software application, script, or code) can be written in any programming language, including compiled or interpreted languages, declarative or procedural languages, and can be deployed in any form, including as a standalone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment. A computer program may, but does not necessarily, correspond to a file in a file system. A program may be stored as a part of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), as a single file dedicated to that program, or as multiple coordinating files (e.g., a file storing one or more modules, subroutines, or code sections). A computer program can be deployed to execute on a single computer or on multiple computers located at a site or distributed across multiple sites and interconnected by a communication network.

[0120] As described herein, a user device can be any suitable device capable of interacting with a user via one or more user interfaces, including speakers, displays (e.g., touchscreens), etc. User devices can be, for example, smartphones, tablets, laptops, smartwatches, TVs, head-mounted displays, augmented reality glasses, etc.

[0121] Applications (or simply apps) are involved in all aspects. An application can be a computer program that is configured to be executed by one or more processors on a device, such as a user's device.

[0122] The processor of a user device can be configured to implement a graphical user interface (GUI). A graphical user interface can be a digital interface that provides graphical components (e.g., graphical icons) on a display device (e.g., a touchscreen, a screen, etc.) and allows users to interact with the graphical components.

[0123] As used herein, the term "remittance" can refer to the transfer of funds from one country's (e.g., a bank) institution to another country's (e.g., a bank) institution. Therefore, the term "remittance" can also be referred to as "cross-border remittance" or "cross-border fund transfer." The term "cross-border" can include transfers across national borders (i.e., from one country to another). Thus, a remittance can be a financial transaction from a first institution in a first country to a second institution in a second country (different from the first institution). The user sending the funds can be referred to as the sending user (or simply: sender), and the user to whom the funds are sent (i.e., the user receiving the funds) can be referred to as the receiving user (or simply: receiver).

[0124] Transactions can include the transfer of funds from a first institution to a second institution. An institution can be a banking institution that provides a bank account, from which funds can be transferred or to which funds can be transferred. An institution can be an online payment institution that provides a digital wallet (also known as an online payment account), from which funds can be transferred or to which funds can be transferred. A digital wallet can be linked to a banking institution's bank account. A digital wallet can include (for example, store) digital versions of bank cards (e.g., debit cards, credit cards, etc.) associated with a banking institution.

[0125] The various aspects detailed in this article refer to elements that are "unique to a cross-border remittance" (e.g., identifiers, information, data, web pages, etc.). The term "unique" can indicate that the element is associated with exactly one specific cross-border remittance. Therefore, this element is explicitly assigned to a single cross-border remittance. Thus, in an exemplary scenario of processing (e.g., initiating and / or completing) multiple cross-border remittances, multiple elements (e.g., transaction identifiers) may exist, and each of these multiple elements can be bijectively assigned to exactly one of the multiple cross-border remittances.

[0126] Some of the processes and logical flows described herein can be executed by one or more programmable processors, which execute one or more computer programs to perform actions by manipulating input data and generating outputs. The processes and logical flows can also be executed by special-purpose logic circuitry (e.g., FPGAs (Field-Programmable Gate Arrays) or ASICs (Application-Specific Integrated Circuits)), and the devices can also be implemented as special-purpose logic circuitry.

[0127] While this specification contains numerous details, these should not be construed as limiting the scope of claims, but rather as descriptions of features specific to particular examples. Certain features described herein or illustrated in the accompanying drawings in the context of individual embodiments may also be combined. Conversely, various features described or illustrated in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0128] Similarly, although operations are depicted in a specific order in the accompanying drawings, this should not be construed as requiring such operations to be performed in the specific order shown or sequentially, or requiring all illustrated operations to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Furthermore, the separation of various system components in the above embodiments should not be construed as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single product or packaged into multiple products.

[0129] Several embodiments have been described. However, it should be understood that various modifications can be made. Therefore, other embodiments are within the scope of the appended claims.

Claims

1. A computer-implemented method for cross-border remittances, the method being executed by at least one processor, and comprising: Initiating cross-border remittances using a remittance application running on the first user's device to transfer funds from the first user's bank account to the second user's digital wallet or bank account; Send remittance information about the cross-border remittance to a first communication application on the first user device; In response to receiving the remittance information regarding the cross-border remittance, the first communication application requests the user information of the second user; The first communication application sends a transaction notification to a second communication application running on a second user device associated with the second user, the transaction notification including information about the cross-border remittance; In response to receiving the transaction notification, the second communication application requests the second user to initiate the receipt of the funds; and In response to the second user's initiation of receiving the funds, the cross-border remittance is completed by transferring the funds to the second user's digital wallet or bank account.

2. The method according to claim 1, further comprising: The remittance application receives a processing instruction to process the cross-border remittance using the first communication application, wherein in response to receiving the processing instruction, the remittance information is sent to the first communication application.

3. The method according to claim 1 or 2, further comprising: The remittance application sends an application programming interface (API) call to a server associated with the first communication application, the API call including the remittance information; The remittance application receives a unique transaction identifier for the cross-border remittance from the server, the transaction identifier including the remittance information.

4. The method according to claim 3, wherein, Sending the remittance information to the first communication application includes: In response to receiving the transaction identifier, the remittance application invokes the first communication application and sends the transaction identifier to the first communication application.

5. The method according to claim 3, wherein, The transaction identifier includes a Uniform Resource Locator (URL), and sending the remittance information to the first communication application includes: In response to receiving the transaction identifier, the remittance application instructs the browser application on the first user device to invoke the website corresponding to the Uniform Resource Locator; and The browser application invokes the first communication application, thereby transmitting the transaction identifier to the first communication application.

6. The method according to any one of claims 1 to 5, wherein, The remittance information and the transaction notification each include a first user identifier used to identify the second user; Furthermore, the process of completing the cross-border remittance in response to the second user's initiation of receiving the funds includes: In response to the second user initiating the receipt of the funds, determine whether the first user identifier corresponds to a second user identifier associated with the second communication application; and The cross-border remittance will only be completed if it is determined that the first user identifier corresponds to the second user identifier.

7. The method according to any one of claims 1 to 6, in, The transaction notification includes transaction information regarding the cross-border remittance; and The method further includes a graphical user interface (GUI) of the second communication application, which displays the transaction information.

8. The method according to claim 7, in, The second communication application requests the second user to initiate the receipt of the funds by displaying a receive button in the graphical user interface of the second communication application to request the second user to initiate the receipt of the funds.

9. The method according to claim 8, The graphical user interface of the second communication application displays the transaction information and the receive button within a dialog window associated with the text conversation between the first user and the second user.

10. The method according to any one of claims 7 to 9, further comprising: The first communication application receives a first instruction, which relates to how the graphical user interface of the second communication application should display the transaction information, wherein the transaction notification includes the first instruction; and / or The first communication application receives a second instruction that indicates a user-specific text message, which is displayed on the graphical user interface of the second communication application along with the transaction information, wherein the transaction notification includes the second instruction.

11. The method according to any one of claims 1 to 10, in, The first user's bank account is associated with a first institutional platform, and the second user's digital wallet or bank account is associated with a second institutional platform that is different from the first institutional platform.

12. The method according to any one of claims 1 to 11, in, The first communication application and / or the second communication application includes a cross-border remittance application.

13. The method according to any one of claims 1 to 12, further comprising: In response to the first communication application receiving an instruction requesting the status of the cross-border remittance, the graphical user interface (GUI) of the first communication application displays information indicating whether the second user has initiated the receipt of the funds and / or whether the funds have been transferred to the second user's digital wallet or bank account.

14. The method according to any one of claims 1 to 13, further comprising: In response to the second communication application receiving an instruction requesting the status of the cross-border remittance, the graphical user interface (GUI) of the second communication application displays information indicating whether the funds have been transferred to the second user's digital wallet or bank account.

15. A non-transitory computer-readable medium storing computer-executable code, the computer-executable code including instructions for performing cross-border remittances according to any one of claims 1 to 14.

16. A server device for performing cross-border remittances, the server device comprising: At least one processor, configured as follows: The system receives an application programming interface (API) call associated with a communication application from a remittance application on a first user's device. The API call includes remittance information related to a cross-border remittance used to transfer funds from the first user's bank account to the second user's digital wallet or bank account. In response to receiving the API call, a unique transaction identifier for the cross-border remittance is sent to the remittance application of the first user device, the transaction identifier including the remittance information; Receive a transaction notification from a first instance of the communication application running on the first user device, the transaction notification including user information indicating a second user device associated with the second user; In response to receiving the transaction notification, remittance data is sent to a second instance of the communication application running on the second user device, the remittance data representing the remittance information and a receipt request, wherein the receipt request includes an instruction to request the second user on the second user device to initiate the receipt of the funds; Receive an initiation notification from the second user equipment, the initiation notification indicating that the second user has initiated the receipt of the funds; In response to receiving the initiation notification, control instructions are provided to complete the cross-border remittance by transferring the funds to the second user's digital wallet or bank account.

17. The server device according to claim 16, in, The remittance information includes a first user identifier that identifies the second user; The notification initiation includes a second user identifier associated with the second instance of the communication application running on the second user device; and The at least one processor is configured to determine whether the first user identifier corresponds to the second user identifier, and to provide the control instruction to complete the cross-border remittance only if it is determined that the first user identifier corresponds to the second user identifier.

18. The server device according to claim 16 or 17, in, The first user's bank account is associated with a first institution, and the second user's digital wallet or bank account is associated with a second institution that is different from the first institution.

19. The server device according to claim 18, wherein, The at least one processor is further configured to: In response to receiving an instruction from the first instance of the communication application running on the first user device to request the status of the cross-border remittance, a first request for the first status of the cross-border remittance is sent to the first institution, and a second request for the second status of the cross-border remittance is sent to the second institution. In response to receiving a first response from the first institution in response to the first request and a second response from the second institution in response to the second request, the status of the cross-border remittance is determined using the first status and the second status, and the status of the cross-border remittance is sent to the first instance of the communication application running on the first user device; and / or In response to receiving an instruction from the second instance of the communication application running on the second user device to request the status of the cross-border remittance, a first request for the first status of the cross-border remittance is sent to the first institution, and a second request for the second status of the cross-border remittance is sent to the second institution. In response to receiving a first response from the first institution in response to the first request and a second response from the second institution in response to the second request, the status of the cross-border remittance is determined using the first status and the second status, and the status of the cross-border remittance is sent to a second instance of a communication application running on the second user device.

20. A system for cross-border remittances, the system comprising: The first user equipment; The second user equipment; and The server device according to any one of Examples 16 to 19.

Images