針對現有轉帳方案中存在的問題，為實現更有效率的轉帳，本說明書實施例提供一種轉帳方法，用於第一用戶和第二用戶當面進行轉帳的場景下，具體包括：
第一客戶端獲取第二用戶的生物特徵，以及，發送該生物特徵至服務端，以便服務端根據該生物特徵確定第二用戶標識；
接收服務端返回的第二用戶標識，顯示該第二用戶標識；
接收第一用戶的確認指令，產生包含第一用戶標識、第二用戶標識和轉帳金額的轉帳請求，並發送至服務端，以便服務端進行轉帳處理；
其中，當第一用戶為收款方時，第二用戶為付款方；當第一用戶為付款方時，第二用戶為收款方。
同時，本說明書還提供應用於服務端的一種轉帳方法，用於第一用戶和第二用戶當面進行轉帳的場景下，包括：
接收第一客戶端所發送的生物特徵；
根據該生物特徵，基於預先儲存的包含用戶生物特徵的資料庫，確定第二用戶標識；
發送該第二用戶標識至第一方客戶端；
接收包含第一用戶標識、第二用戶標識和轉帳金額的轉帳請求，進行轉帳處理；
其中，當第一用戶為收款方時，第二用戶為付款方；當第一用戶為付款方時，第二用戶為收款方。
對應的，本說明書實施例提供一種轉帳裝置，用於第一用戶和第二用戶當面進行轉帳的場景下，具體包括：
獲取模組，獲取第二用戶的生物特徵；
發送模組，發送該生物特徵至服務端，以便服務端根據該生物特徵確定第二用戶標識；
接收模組，接收服務端返回的第二用戶標識；
顯示模組，顯示該第二用戶標識；
產生模組，接收第一用戶的確認指令，產生包含第一用戶標識、第二用戶標識和轉帳金額的轉帳請求，並發送至服務端，以便服務端進行轉帳處理；
其中，當第一用戶為收款方時，第二用戶為付款方；當第一用戶為付款方時，第二用戶為收款方。
對應的，本說明書實施例還提供另一種轉帳裝置，用於第一用戶和第二用戶當面進行轉帳的場景下，包括：
接收模組，接收第一客戶端所發送的生物特徵；
確定模組，根據該生物特徵，基於預先儲存的包含用戶生物特徵的資料庫，確定第二用戶標識；
發送模組，發送該第二用戶標識至第一方客戶端；
該接收模組還用於，接收包含第一用戶標識、第二用戶標識和轉帳金額的轉帳請求；
處理模組，進行轉帳處理；
其中，當第一用戶為收款方時，第二用戶為付款方；當第一用戶為付款方時，第二用戶為收款方。
對應的，本說明書實施例還提供一種電腦設備，包括記憶體、處理器及儲存在記憶體上並可在處理器上運行的電腦程式，其中，該處理器執行該程式時實現上述的轉帳方法。
對應的，本說明書實施例還提供電腦可讀儲存介質，其上儲存有電腦程式，該程式被處理器執行時，執行實現上述的轉帳方法。
本說明書實施例所提供的方案，在面對面進行轉帳的場景下，第一用戶利用第一客戶端掃描第二用戶獲取其生物特徵，並上傳服務端，讓服務端基於生物特徵對第二用戶進行身份識別，進而在第一客戶端產生相應的轉帳請求，並發送轉帳請求至服務端進行轉帳，並進行轉帳/支付,減少用戶操作步驟，提高轉帳效率和用戶體驗。
應當理解的是，以上的一般描述和後文的細節描述僅是示例性和解釋性的，並不能限制本說明書實施例。
此外，本說明書實施例中的任一實施例並不需要達到上述的全部效果。
In view of the problems in the existing transfer scheme, in order to achieve more efficient transfer, the embodiments of this specification provide a transfer method, which is used in the scenario where the first user and the second user transfer in person, specifically including:
The first client obtains the biometrics of the second user, and sends the biometrics to the server, so that the server determines the second user identity according to the biometrics;
Receiving the second user ID returned by the server, and displaying the second user ID;
Receive a confirmation instruction from the first user, generate a transfer request that includes the first user ID, the second user ID, and the transfer amount, and send it to the server for the server to perform the transfer process;
Wherein, when the first user is the payee, the second user is the payer; when the first user is the payer, the second user is the payee.
At the same time, this specification also provides a transfer method applied to the server side, which is used in the scenario where the first user and the second user transfer in person, including:
Receiving the biometrics sent by the first client;
According to the biometrics, determine the second user identification based on a pre-stored database containing the user's biometrics;
Send the second user identification to the first party client;
Receive a transfer request containing the first user ID, second user ID, and transfer amount, and perform transfer processing;
Wherein, when the first user is the payee, the second user is the payer; when the first user is the payer, the second user is the payee.
Correspondingly, the embodiments of the present specification provide a device for transferring funds, which is used in the scenario where the first user and the second user transfer funds in person, specifically including:
Obtaining a module to obtain the biological characteristics of the second user;
The sending module sends the biometrics to the server, so that the server determines the second user identification according to the biometrics;
The receiving module receives the second user ID returned by the server;
A display module displaying the second user identification;
The generating module receives the confirmation instruction of the first user, generates a transfer request including the first user ID, the second user ID, and the transfer amount, and sends it to the server, so that the server can perform the transfer process;
Wherein, when the first user is the payee, the second user is the payer; when the first user is the payer, the second user is the payee.
Correspondingly, the embodiment of the present specification also provides another transfer device, which is used in the scenario where the first user and the second user transfer funds in person, including:
The receiving module receives the biometrics sent by the first client;
A determination module, based on the biometrics, based on a pre-stored database containing the biometrics of the user, to determine the second user identification;
Sending module, sending the second user identification to the first party client;
The receiving module is also used to receive a transfer request including the first user ID, the second user ID and the transfer amount;
Processing module for transfer processing;
Wherein, when the first user is the payee, the second user is the payer; when the first user is the payer, the second user is the payee.
Correspondingly, the embodiments of the present specification also provide a computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor implements the program to implement the above transfer method .
Correspondingly, the embodiments of the present specification also provide a computer-readable storage medium on which a computer program is stored, and when the program is executed by the processor, the above-mentioned transfer method is executed.
In the scenario provided by the embodiment of the present specification, in the scenario of face-to-face transfer, the first user uses the first client to scan the second user to obtain their biometrics, and uploads it to the server to allow the server to perform the second user based on the biometrics Identification, and then generate a corresponding transfer request on the first client, and send the transfer request to the server for transfer, and transfer/payment, reduce user operation steps, improve transfer efficiency and user experience.
It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the embodiments of the present specification.
In addition, any of the embodiments of the present specification does not need to achieve all the above-mentioned effects.
為了使本領域技術人員更好地理解本說明書實施例中的技術方案，下面將結合本說明書實施例中的圖式，對本說明書實施例中的技術方案進行詳細地描述，顯然，所描述的實施例僅僅是本說明書的一部分實施例，而不是全部的實施例。基於本說明書中的實施例，本領域普通技術人員所獲得的所有其他實施例，都應當屬保護的範圍。
以下結合圖式，詳細說明本說明書各實施例提供的技術方案。如圖1所示，圖1是本說明書實施例提供的轉帳方案的架構示意圖，在該圖中，第一用戶和第二用戶作為收款方和付款方的兩類用戶，當第一用戶為收款方時，第二用戶為付款方；當第一用戶為付款方時，第二用戶為收款方。容易理解，第一用戶對應的客戶端即為第一客戶端，第二用戶對應的客戶端即為第二客戶端。此外，第一客戶端和第二客戶端可以作為不同的功能模組集成在一個軟體程式或者硬體中，也可以分別作為獨立的功能模組分別執行各自的功能。
下面結合圖1所提供的架構示意圖，詳細解釋本說明書實施例所提供的轉帳方案。該方案具體包括客戶端和服務端兩個方面，對於客戶端方面，其流程具體包括如下步驟，如圖2所示，圖2為本說明書實施例所提供的客戶端方面的轉帳方法流程示意圖，包括：
S201，第一客戶端獲取第二用戶的生物特徵，以及，發送該生物特徵至服務端，以便服務端根據該生物特徵確定第二用戶標識。
與第一客戶端所對應的第一用戶可以是付款方，也可以是收款方。當第一用戶為收款方時，第二用戶為付款方；當第一用戶為付款方時，第二用戶為收款方。所述的生物特徵可以包括面部特徵、虹膜特徵、指紋特徵等等其它可以用於識別用戶身份的生物特徵。在本身可採用其他方式(例如掃碼)進行轉帳支付的第一客戶端中，上述的掃描功能可以透過在相應的業務頁面中增加相應的功能選項來實現，例如，在執行掃碼進行支付的頁面中，添加“掃臉”的功能選項，以方便用戶進行操作。如圖3所示，圖3為本說明書實施例所提供的在客戶端中提供掃描面部選項的示例圖。
在第一用戶使用第一客戶端的轉帳支付功能時，一般而言，第一用戶已經在第一客戶端執行了登錄，第一客戶端此時已經可以獲取第一用戶標識，例如，第一用戶的帳號、身份證號、手機號碼等等。
S203，接收服務端返回的第二用戶標識，顯示該第二用戶標識。
服務端接收到第二用戶的生物特徵，即可進行識別，並返回第二用戶標識。容易理解，第二用戶標識的形式和第一用戶並無區別。第一用戶端接收到該標識以後，即可以跳轉至相應的頁面中顯示該第二用戶標識。在面對面的轉帳場景下，可以讓雙方用戶對服務端返回的第二用戶標識進行當面確認，避免出錯。
S205，接收第一用戶的確認指令，產生包含第一用戶標識、第二用戶標識和轉帳金額的轉帳請求，並發送至服務端，以便服務端進行轉帳處理。
上述的確認指令可以包括對第二用戶身份的確認，對於轉帳金額的輸入確認，以及對於產生轉帳請求的確認等等。當然，若返回的第二用戶標識有誤，第一用戶還可以終止上述的轉帳支付進程。
透過本說明書實施例所提供的上述方案，在面對面進行轉帳的場景下，第一用戶利用第一客戶端掃描第二用戶獲取其生物特徵，並上傳服務端，讓服務端基於生物特徵對第二用戶進行身份識別，進而在第一客戶端產生相應的轉帳請求，並發送轉帳請求至服務端進行轉帳，並進行轉帳/支付，減少用戶操作步驟，提高了轉帳效率和用戶體驗。
在實際應用中，獲取第二用戶生物特徵的方式可以包括如下方式：掃描第二用戶的面部，獲取該第二用戶的面部特徵；或者，掃描第二用戶的眼睛，獲取該第二用戶的虹膜特徵。
此外，服務端在返回第二用戶標識時，還可以返回一些第二用戶的其它資訊，用於輔助識別第二用戶身份，例如，第二用戶的註冊郵箱、暱稱、頭像等等。以及，為保護第二用戶的隱私，返回的第二用戶標識或者其它資訊還可以經過演算法加密，進行脫敏處理，例如，對第二用戶的暱稱或者手機號碼隱藏中間部分字符，對其頭像的眼部進行馬賽克處理或者只顯示部分頭像等等。從而，在第一用戶顯示第二用戶標識時，還可以一併顯示第二用戶的其它資訊，若上述資訊已經被服務端進行了脫敏處理，則顯示的就是脫敏處理後的資訊。如圖4所示，圖4為本說明書實施例所提供第一客戶端中對第二用戶標識和其他資訊進行脫敏顯示的示意圖。
在實際應用中，脫敏處理也可以在第一客戶端這方面進行，即對於S203中的，顯示該第二用戶標識，還可以包括：對該第二用戶標識進行脫敏處理；顯示脫敏處理後的第二用戶標識。透過對第二用戶標識或者其相關的其它資訊進行脫敏處理，可以更好的保護第二用戶的隱私。
在第一用戶為付款方時，第二用戶為收款方。此時，第一用戶作為付款方掃描收款方，在第一用戶即可以直接進行確認。
但是，在第一用戶為收款方，第二用戶為付款方時，此時，第二用戶作為付款方，由於掃描用戶的面部特徵或者虹膜特徵通常需要第二用戶的同意，此時可以認為第二用戶已經授權進行支付。或者，在某些情形下，第二用戶可以無需對第一用戶發起的轉帳支付進行確認，例如，在第二用戶開啟了小額支付免確認，且轉帳金額不超過小額支付的範圍時；或者，在者服務端中第一用戶標識和第二用戶標識均存在於對方的好友列表中等等。但是，在另一種實施方式中，服務端還可以將第轉帳請求中的相關資訊推送給轉帳請求中的付款方(此時，即第二用戶的第二客戶端)進行驗證。第二客戶端在接收到該驗證請求後，即可以方便第二用戶對相應的轉帳請求進行確認，包括驗證透過或者驗證失敗，並且返回驗證成功/失敗資訊至服務端，以便服務端進行相應的處理。透過上述發送驗證請求至付款方，可以進一步提高本說明書實施例所提供的轉帳方案的安全性。
上述部分對客戶端方面的執行流程進行了說明，對於本說明實施例所提供的方案，在服務端方面，其執行流程如圖5所示，圖5為本說明書實施例所提供的服務端方面的流程示意圖，具體包括：
S501，接收第一客戶端所發送的生物特徵，生物特徵包括面部特徵，或者虹膜特徵，或者指紋特徵等等。
S503，根據該生物特徵，基於預先儲存的包含用戶生物特徵的資料庫，確定第二用戶標識。換言之，生物特徵既可以用於用戶在客戶端進行登錄，也可以用於服務端對用戶進行身份識別。
S505，發送該第二用戶標識至第一方客戶端。
S507，接收包含第一用戶標識、第二用戶標識和轉帳金額的轉帳請求，進行轉帳處理。
在實際應用中，服務端還可以根據第二用戶標識確定第二用戶的其它資訊(例如頭像、暱稱、姓名等等，用來輔助確認身份)，並且將上述其它資訊一起發送給第一用戶端。以及，服務端還可以將第二用戶標識以及上述其它資訊進行脫敏處理，再發送至第一客戶端。具體實施方式已經在前文詳細說明，此處不再贅述。
在一種實施方式下，當第一用戶為收款方，第二用戶為付款方時，服務端還可以將轉帳請求的相關資訊發送至第二服務端，以便第二用戶進行確認。當接收到第二用戶驗證透過的資訊時，才執行轉帳，否則，不執行轉帳。透過上述方式，進一步提高轉帳過程中的安全性。
對應的，本說明書實施例還提供一種轉帳裝置，用於第一用戶和第二用戶當面進行轉帳的場景下，如圖6所示，圖6是本說明書實施例提供的客戶端方面的一種轉帳裝置的結構示意圖，包括：
獲取模組601，獲取第二用戶的生物特徵；
發送模組602，發送該生物特徵至服務端，以便服務端根據該生物特徵確定第二用戶標識；
接收模組603，接收服務端返回的第二用戶標識；
顯示模組604，顯示該第二用戶標識；
產生模組605，接收第一用戶的確認指令，產生包含第一用戶標識、第二用戶標識和轉帳金額的轉帳請求，並發送至服務端，以便服務端進行轉帳處理；
其中，當第一用戶為收款方時，第二用戶為付款方；當第一用戶為付款方時，第二用戶為收款方。
進一步地，該該獲取模組601，掃描第二用戶的面部，獲取該第二用戶的面部特徵；或者，掃描第二用戶的眼睛，獲取該第二用戶的虹膜特徵。
進一步地，該接收模組603，接收服務端返回的第二用戶標識和第二用戶的其它資訊，其中，該第二用戶的其它資訊由服務端根據該第二用戶標識確定，用於輔助識別第二用戶身份；該顯示模組604，顯示該第二用戶標識和該第二用戶的其它資訊。
進一步地，該顯示模組604，對該第二用戶標識進行脫敏處理；顯示脫敏處理後的第二用戶標識。
當第一用戶為收款方，第二用戶為付款方時，該裝置中還包括驗證模組606，用於第二用戶接收服務端返回的驗證請求，以便第二用戶對轉帳進行確認；接收第二用戶的確認指令，發送驗證成功/失敗資訊至服務端。
對應的，本說明書實施例還提供領一種轉帳裝置，用於第一用戶和第二用戶當面進行轉帳的場景下，如圖7所示，圖7是本說明書實施例提供的服務端方面的一種轉帳裝置的結構示意圖，包括：
接收模組701，接收第一客戶端所發送的生物特徵；
確定模組702，根據該生物特徵，基於預先儲存的包含用戶生物特徵的資料庫，確定第二用戶標識；
發送模組703，發送該第二用戶標識至第一方客戶端；
該接收模組701還用於，接收包含第一用戶標識、第二用戶標識和轉帳金額的轉帳請求；
處理模組704，進行轉帳處理；
其中，當第一用戶為收款方時，第二用戶為付款方；當第一用戶為付款方時，第二用戶為收款方。
進一步地，在確定第二用戶標識之後，該確定模組702還用於，根據第二用戶標識確定第二用戶的其它資訊，其中，該第二用戶的其它資訊由服務端根據該第二用戶標識確定，用於輔助識別第二用戶身份；該發送模組703，發送該第二用戶標識和該第二用戶的其它資訊至第一客戶端。
進一步地，該裝置還包括脫敏模組705，將該第二用戶標識進行脫敏處理；該發送模組703，發送脫敏處理後的第二用戶標識至該第一方客戶端。
當第一用戶為收款方，第二用戶為付款方時，該發送模組703還用於，發送驗證請求至第二客戶端，以便第二用戶對轉帳進行驗證；該處理模組704，若接收第二客戶端所發送的驗證成功消息，執行轉帳處理，否則，不執行轉帳處理。
本說明書實施例還提供一種電腦設備，其至少包括記憶體、處理器及儲存在記憶體上並可在處理器上運行的電腦程式，其中，處理器執行該程式時實現圖2或者圖5所示的轉帳方法。
圖8示出了本說明書實施例所提供的一種更為具體的計算設備硬體結構示意圖，該設備可以包括：處理器1010、記憶體1020、輸入/輸出介面1030、通信介面1040和匯流排1050。其中處理器1010、記憶體1020、輸入/輸出介面1030和通信介面1040透過匯流排1050實現彼此之間在設備內部的通信連接。
處理器1010可以採用通用的CPU(Central Processing Unit，中央處理器)、微處理器、應用專用積體電路(Application Specific Integrated Circuit，ASIC)、或者一個或多個積體電路等方式實現，用於執行相關程式，以實現本說明書實施例所提供的技術方案。
記憶體1020可以採用ROM(Read Only Memory，唯讀記憶體)、RAM(Random Access Memory，隨機存取記憶體)、靜態儲存設備，動態儲存設備等形式實現。記憶體1020可以儲存操作系統和其他應用程式，在透過軟體或者韌體來實現本說明書實施例所提供的技術方案時，相關的程式碼保存在記憶體1020中，並由處理器1010來呼叫執行。
輸入/輸出介面1030用於連接輸入/輸出模組，以實現資訊輸入及輸出。輸入輸出/模組可以作為組件配置在設備中(圖中未示出)，也可以外接於設備以提供相應功能。其中輸入設備可以包括鍵盤、滑鼠、觸摸螢幕、麥克風、各類傳感器等，輸出設備可以包括顯示器、揚聲器、振動器、指示燈等。
通信介面1040用於連接通信模組(圖中未示出)，以實現本設備與其他設備的通信交互。其中通信模組可以透過有線方式(例如USB、網路線等)實現通信，也可以透過無線方式(例如移動網路、WIFI、藍牙等)實現通信。
匯流排1050包括一通路，在設備的各個組件(例如處理器1010、記憶體1020、輸入/輸出介面1030和通信介面1040)之間傳輸資訊。
需要說明的是，儘管上述設備僅示出了處理器1010、記憶體1020、輸入/輸出介面1030、通信介面1040以及匯流排1050，但是在具體實施過程中，該設備還可以包括實現正常運行所必需的其他組件。此外，本領域的技術人員可以理解的是，上述設備中也可以僅包含實現本說明書實施例方案所必需的組件，而不必包含圖中所示的全部組件。
本說明書實施例還提供一種電腦可讀儲存介質，其上儲存有電腦程式，該程式被處理器執行時實現圖2或者圖5所示的轉帳方法。
電腦可讀介質包括永久性和非永久性、可移動和非可移動媒體可以由任何方法或技術來實現資訊儲存。資訊可以是電腦可讀指令、資料結構、程式的模組或其他資料。電腦的儲存介質的例子包括，但不限於相變內部記憶體(PRAM)、靜態隨機存取記憶體(SRAM)、動態隨機存取記憶體(DRAM)、其他類型的隨機存取記憶體(RAM)、唯讀記憶體(ROM)、電可抹除可編程唯讀記憶體(EEPROM)、快閃記憶體或其他內部記憶體技術、唯讀光碟唯讀記憶體(CD-ROM)、數位多功能光碟(DVD)或其他光學儲存、磁盒式磁帶，磁帶磁磁碟儲存或其他磁性儲存設備或任何其他非傳輸介質，可用於儲存可以被計算設備存取的資訊。按照本文中的界定，電腦可讀介質不包括暫存電腦可讀媒體(transitory media)，如調變的資料信號和載波。
透過以上的實施方式的描述可知，本領域的技術人員可以清楚地瞭解到本說明書實施例可借助軟體加必需的通用硬體平台的方式來實現。基於這樣的理解，本說明書實施例的技術方案本質上或者說對現有技術做出貢獻的部分可以以軟體產品的形式體現出來，該電腦軟體產品可以儲存在儲存介質中，如ROM/RAM、磁碟、光碟等，包括若干指令用以使得一台電腦設備(可以是個人電腦，伺服器，或者網路設備等)執行本說明書實施例各個實施例或者實施例的某些部分所述的方法。
上述實施例闡明的系統、方法、模組或單元，具體可以由電腦晶片或實體實現，或者由具有某種功能的產品來實現。一種典型的實現設備為電腦，電腦的具體形式可以是個人電腦、筆記型電腦、蜂巢式電話、相機電話、智慧型電話、個人數位助理、媒體播放器、導航設備、電子郵件收發設備、遊戲控制台、平板電腦、可穿戴設備或者這些設備中的任意幾種設備的組合。
本說明書中的各個實施例均採用遞進的方式描述，各個實施例之間相同相似的部分互相參見即可，每個實施例重點說明的都是與其他實施例的不同之處。尤其，對於方法實施例而言，由於其基本相似於方法實施例，所以描述得比較簡單，相關之處參見方法實施例的部分說明即可。以上所描述的方法實施例僅僅是示意性的，其中該作為分離部件說明的模組可以是或者也可以不是實體上分開的，在實施本說明書實施例方案時可以把各模組的功能在同一個或多個軟體和/或硬體中實現。也可以根據實際的需要選擇其中的部分或者全部模組來實現本實施例方案的目的。本領域普通技術人員在不付出創造性勞動的情況下，即可以理解並實施。
以上所述僅是本說明書實施例的具體實施方式，應當指出，對於本技術領域的普通技術人員來說，在不脫離本說明書實施例原理的前提下，還可以做出若干改進和潤飾，這些改進和潤飾也應視為本說明書實施例的保護範圍。In order to enable those skilled in the art to better understand the technical solutions in the embodiments of the present specification, the technical solutions in the embodiments of the present specification will be described in detail in conjunction with the drawings in the embodiments of the present specification. Obviously, the described implementation Examples are only a part of the embodiments of this specification, but not all the embodiments. Based on the embodiments in this specification, all other embodiments obtained by those of ordinary skill in the art should fall within the scope of protection.
The technical solutions provided by the embodiments of this specification will be described in detail below in conjunction with the drawings. As shown in FIG. 1, FIG. 1 is a schematic structural diagram of a transfer scheme provided by an embodiment of the present specification. In this figure, the first user and the second user are two types of users of the payee and the payer. When the first user is When the payee is the second user is the payer; when the first user is the payer, the second user is the payee. It is easy to understand that the client corresponding to the first user is the first client, and the client corresponding to the second user is the second client. In addition, the first client and the second client may be integrated into a software program or hardware as different functional modules, or may be used as independent functional modules to perform their respective functions.
In the following, in conjunction with the architecture schematic diagram provided in FIG. 1, the transfer scheme provided by the embodiment of the present specification is explained in detail. The solution specifically includes the client and the server. For the client, the process includes the following steps. As shown in FIG. 2, FIG. 2 is a schematic flowchart of the client-side transfer method provided by the embodiment of the present specification. include:
S201. The first client obtains the biometrics of the second user, and sends the biometrics to the server, so that the server determines the second user identifier according to the biometrics.
The first user corresponding to the first client may be the payer or the payee. When the first user is the payee, the second user is the payer; when the first user is the payer, the second user is the payee. The biological features may include facial features, iris features, fingerprint features, and other biological features that can be used to identify the user's identity. In the first client that can adopt other methods (for example, scan code) for transfer payment, the above scanning function can be realized by adding corresponding function options in the corresponding business page, for example, when performing scan code for payment On the page, add the "sweep face" function option to facilitate the user to operate. As shown in FIG. 3, FIG. 3 is an example diagram of providing a face scanning option in a client provided by an embodiment of the present specification.
When the first user uses the transfer payment function of the first client, generally speaking, the first user has already performed login on the first client, and the first client can already obtain the first user identification at this time, for example, the first user Account number, ID card number, mobile phone number, etc.
S203: Receive the second user ID returned by the server, and display the second user ID.
After receiving the biometrics of the second user, the server can perform identification and return the second user identification. It is easy to understand that the form of the second user identification is no different from that of the first user. After receiving the identifier, the first user terminal can jump to the corresponding page to display the second user identifier. In the face-to-face transfer scenario, users of both parties can confirm the second user ID returned by the server in person to avoid errors.
S205: Receive the confirmation instruction of the first user, generate a transfer request including the first user ID, the second user ID, and the transfer amount, and send it to the server to facilitate the server to perform the transfer process.
The foregoing confirmation instruction may include confirmation of the identity of the second user, confirmation of the input of the transfer amount, confirmation of the generation of the transfer request, and so on. Of course, if the returned second user ID is wrong, the first user can also terminate the above transfer payment process.
Through the above solution provided by the embodiment of the present specification, in the scenario of face-to-face transfer, the first user uses the first client to scan the second user to obtain their biometrics, and uploads it to the server, allowing the server to check the second based on the biometrics. The user performs identity recognition, and then generates a corresponding transfer request on the first client, and sends the transfer request to the server for transfer, and transfer/payment, reducing user operation steps and improving transfer efficiency and user experience.
In practical applications, the method of acquiring the biometrics of the second user may include the following methods: scanning the face of the second user to obtain the facial features of the second user; or scanning the eyes of the second user to obtain the iris of the second user feature.
In addition, when the server returns the second user ID, it can also return some other information of the second user to assist in identifying the second user's identity, for example, the registered mailbox, nickname, avatar, etc. of the second user. And, in order to protect the privacy of the second user, the returned second user ID or other information can also be encrypted by an algorithm for desensitization processing, for example, hiding the middle part of the character of the second user’s nickname or mobile phone number, and avatar Mosaic processing of the eyes or display only part of the avatar, etc. Therefore, when the first user displays the second user logo, other information of the second user can also be displayed together. If the above information has been desensitized by the server, the information after desensitization is displayed. As shown in FIG. 4, FIG. 4 is a schematic diagram of desensitization display of the second user identification and other information in the first client provided by the embodiment of the present specification.
In practical applications, the desensitization process may also be performed on the first client side. That is, for S203, displaying the second user ID may further include: performing desensitization on the second user ID; displaying desensitization The processed second user ID. By desensitizing the second user's logo or other related information, the privacy of the second user can be better protected.
When the first user is the payer, the second user is the payee. At this time, the first user as the payer scans the payee, and the first user can directly confirm it.
However, when the first user is the payee and the second user is the payer, at this time, the second user is the payer. Since scanning the user's facial features or iris features usually requires the second user's consent, it can be considered at this time The second user has authorized payment. Or, in some cases, the second user may not need to confirm the transfer payment initiated by the first user, for example, when the second user has enabled the small payment exemption confirmation and the transfer amount does not exceed the range of the small payment; or, Both the first user ID and the second user ID exist in the other party's friend list on the server side, and so on. However, in another embodiment, the server can also push the relevant information in the first transfer request to the payer in the transfer request (in this case, the second client of the second user) for verification. After receiving the verification request, the second client can facilitate the second user to confirm the corresponding transfer request, including verification pass or verification failure, and return verification success/failure information to the server, so that the server can perform the corresponding deal with. By sending the verification request to the payer as described above, the security of the transfer scheme provided by the embodiments of the present specification can be further improved.
The above part describes the execution flow of the client. For the solution provided by the embodiment of this description, the execution flow of the solution is shown in FIG. 5, which is the server side provided by the embodiment of the specification Schematic diagram of the process, including:
S501. Receive biometrics sent by the first client, and the biometrics include facial features, or iris features, or fingerprint features, and so on.
S503: According to the biometrics, determine the second user identifier based on a pre-stored database containing the user's biometrics. In other words, the biometrics can be used for users to log in on the client or for the server to identify the user.
S505: Send the second user identifier to the first-party client.
S507: Receive a transfer request including the first user ID, the second user ID, and the transfer amount, and perform transfer processing.
In practical applications, the server can also determine other information of the second user (such as avatar, nickname, name, etc., to help confirm identity) according to the second user ID, and send the other information to the first user together . And, the server can also desensitize the second user ID and the other information and send it to the first client. The specific embodiments have been described in detail in the foregoing, and will not be repeated here.
In one embodiment, when the first user is the payee and the second user is the payer, the server can also send the relevant information of the transfer request to the second server for the second user to confirm. The transfer is only performed when the information verified by the second user is received, otherwise, the transfer is not performed. Through the above methods, the security during the transfer process is further improved.
Correspondingly, the embodiment of the present specification also provides a transfer device, which is used in the scenario where the first user and the second user transfer funds face-to-face, as shown in FIG. 6, which is a type of client-side transfer provided by the embodiment of the present specification Schematic diagram of the device, including:
An obtaining module 601, obtaining the biological characteristics of the second user;
The sending module 602 sends the biometrics to the server, so that the server determines the second user identifier according to the biometrics;
The receiving module 603 receives the second user ID returned by the server;
A display module 604, displaying the second user identification;
The generating module 605 receives the confirmation instruction of the first user, generates a transfer request including the first user ID, the second user ID, and the transfer amount, and sends it to the server for the server to perform the transfer process;
Wherein, when the first user is the payee, the second user is the payer; when the first user is the payer, the second user is the payee.
Further, the acquisition module 601 scans the second user's face to acquire the second user's facial features; or, scans the second user's eyes to acquire the second user's iris features.
Further, the receiving module 603 receives the second user identifier and other information of the second user returned by the server, wherein the other information of the second user is determined by the server according to the second user identifier and is used for auxiliary identification Second user identity; the display module 604 displays the second user logo and other information of the second user.
Further, the display module 604 performs desensitization processing on the second user identification; and displays the second user identification after desensitization processing.
When the first user is the payee and the second user is the payer, the device further includes a verification module 606 for the second user to receive the verification request returned by the server so that the second user can confirm the transfer; The confirmation instruction of the second user sends verification success/failure information to the server.
Correspondingly, an embodiment of the present specification also provides a transfer device for scenarios where the first user and the second user transfer funds face-to-face, as shown in FIG. 7, which is a type of server side provided by the embodiment of the specification Schematic diagram of the structure of the transfer device, including:
The receiving module 701 receives the biometrics sent by the first client;
The determining module 702 determines the second user identifier based on the biometrics based on a pre-stored database containing the user's biometrics;
The sending module 703 sends the second user identifier to the first party client;
The receiving module 701 is also used to receive a transfer request including the first user ID, the second user ID and the transfer amount;
The processing module 704 performs transfer processing;
Wherein, when the first user is the payee, the second user is the payer; when the first user is the payer, the second user is the payee.
Further, after determining the second user identification, the determination module 702 is further used to determine other information of the second user according to the second user identification, wherein the other information of the second user is determined by the server according to the second user The identification is determined to assist in identifying the identity of the second user; the sending module 703 sends the second user identification and other information of the second user to the first client.
Further, the device further includes a desensitization module 705 to desensitize the second user ID; the sending module 703 sends the desensitized second user ID to the first-party client.
When the first user is the payee and the second user is the payer, the sending module 703 is also used to send a verification request to the second client so that the second user can verify the transfer; the processing module 704, If the verification success message sent by the second client is received, the transfer process is executed; otherwise, the transfer process is not executed.
The embodiments of the present specification also provide a computer device, which at least includes a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor executes the program to implement the program shown in FIG. 2 or FIG. 5. The transfer method shown.
8 shows a schematic diagram of a more specific hardware structure of a computing device provided by an embodiment of the present specification. The device may include: a processor 1010, a memory 1020, an input/output interface 1030, a communication interface 1040, and a bus 1050 . Among them, the processor 1010, the memory 1020, the input/output interface 1030, and the communication interface 1040 realize the communication connection among the devices through the bus 1050.
The processor 1010 may be implemented by a general-purpose CPU (Central Processing Unit, central processing unit), a microprocessor, an application specific integrated circuit (ASIC), or one or more integrated circuits, etc., for Execute relevant programs to realize the technical solutions provided by the embodiments of this specification.
The memory 1020 may be implemented in the form of ROM (Read Only Memory, read only memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 1020 can store an operating system and other application programs. When the technical solutions provided by the embodiments of the present specification are implemented through software or firmware, related program codes are stored in the memory 1020 and are called and executed by the processor 1010. .
The input/output interface 1030 is used to connect input/output modules to realize information input and output. The input/output/module can be configured as a component in the device (not shown in the figure), or can be externally connected to the device to provide corresponding functions. The input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, and an indicator light.
The communication interface 1040 is used to connect a communication module (not shown in the figure) to implement communication interaction between the device and other devices. The communication module can realize communication through wired methods (such as USB, network cable, etc.), and can also realize communication through wireless methods (such as mobile network, WIFI, Bluetooth, etc.).
The bus 1050 includes a path for transmitting information between various components of the device (such as the processor 1010, the memory 1020, the input/output interface 1030, and the communication interface 1040).
It should be noted that although the above device only shows the processor 1010, the memory 1020, the input/output interface 1030, the communication interface 1040, and the bus 1050, in the specific implementation process, the device may also include Required other components. In addition, those skilled in the art may understand that the above-mentioned device may also include only the components necessary to implement the solutions of the embodiments of the present specification, rather than including all the components shown in the figures.
The embodiments of the present specification also provide a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the transfer method shown in FIG. 2 or FIG. 5 is realized.
Computer-readable media, including permanent and non-permanent, removable and non-removable media, can store information by any method or technology. The information can be computer readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change internal memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), and other types of random access memory (RAM ), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other internal memory technology, read-only disc read-only memory (CD-ROM), multiple digits A functional optical disc (DVD) or other optical storage, magnetic cassette tape, magnetic tape magnetic disk storage or other magnetic storage device or any other non-transmission medium can be used to store information that can be accessed by a computing device. As defined in this article, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.
It can be known from the description of the above implementation manners that those skilled in the art can clearly understand that the embodiments of this specification can be implemented by means of software plus a necessary general hardware platform. Based on this understanding, the technical solutions of the embodiments of this specification can be embodied in the form of software products in essence or part that contributes to the existing technology, and the computer software products can be stored in storage media, such as ROM/RAM, magnetic Discs, optical discs, etc., include several instructions to enable a computer device (which may be a personal computer, a server, or a network device, etc.) to perform the methods described in the various embodiments of the embodiments of the present specification or some parts of the embodiments.
The system, method, module or unit explained in the above embodiments may be implemented by a computer chip or entity, or by a product with a certain function. A typical implementation device is a computer, and the specific form of the computer may be a personal computer, a notebook computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email sending and receiving device, and a game control Desk, tablet, wearable device, or any combination of these devices.
The embodiments in this specification are described in a progressive manner. The same or similar parts between the embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. In particular, for the method embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant part can be referred to the description of the method embodiment. The method embodiments described above are only schematic, wherein the modules described as separate components may or may not be physically separated, and the functions of the modules may be the same when implementing the embodiment solutions of this specification Implemented in one or more software and/or hardware. Part or all of the modules may also be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art can understand and implement without paying creative labor.
The above is only a specific implementation manner of the embodiments of this specification. It should be pointed out that for those of ordinary skill in the art, without departing from the principles of the embodiments of this specification, several improvements and retouches can be made. These Improvements and retouching should also be regarded as the scope of protection of the embodiments of this specification.
