針對上述技術問題，本說明書實施例提供一種支付方法、裝置、及業務伺服器，技術方案如下：
根據本說明書實施例的第一方面，提供一種支付方法，應用於收款端掃描支付資訊碼並向伺服端提交支付請求、且未收到支付結果的情況下，其中，支付資訊碼為支付端產生，所述支付資訊碼與支付請求至少包含本次交易的標識資訊，該方法包括：
支付端接收用戶的重新支付操作，透過掃描收款端提供的收款資訊碼獲取收款端用戶資訊，向伺服端發送重新支付請求，所述重新支付請求中至少包含所述本次交易的標識資訊；
支付端在無需確定所述重新支付請求是否成功的情況下，展示支付成功資訊；以及
支付端判斷所述重新支付請求是否成功；
若重新支付請求沒有成功，支付端將所述重新支付請求快取在本地，當滿足發送條件時自動再次發送；
其中，伺服端接收到重新支付請求後，根據所述重新支付請求中包含的交易標識資訊查詢所述交易標識對應的交易是否已經成功支付，若所述交易沒有成功支付，伺服端處理所述重新支付請求以使所述交易成功支付。
根據本說明書實施例的第二方面，還提供一種支付方法，應用於收款端掃描支付資訊碼並向伺服端提交支付請求、且未收到支付結果的情況下，其中，支付資訊碼為支付端產生，所述支付資訊碼與支付請求至少包含本次交易的標識資訊，該方法包括：
支付端接收用戶的重新支付操作，透過掃描收款端提供的收款資訊碼獲取收款端用戶資訊，向伺服端發送重新支付請求，所述重新支付請求中至少包含所述本次交易的標識資訊；
支付端判斷所述重新支付請求是否成功；
若重新支付請求沒有成功，支付端展示支付成功資訊，並將所述重新支付請求快取在本地，當滿足發送條件時自動再次發送；
若重新支付請求成功，支付端展示支付成功資訊，本次交易結束。
根據本說明書實施例的第三方面，還提供一種支付方法，應用於收款端掃描支付資訊碼並向伺服端提交支付請求、且未收到支付結果的情況下，其中，支付資訊碼為支付端產生，所述支付資訊碼與支付請求至少包含本次交易的標識資訊，該方法包括：
伺服端接收支付端在用戶重新支付操作後發送的重新支付請求，所述重新支付請求中至少包含所述本次交易的標識資訊；
伺服端根據所述重新支付請求中包含的交易標識資訊查詢所述交易標識對應的交易是否已經成功支付，若所述交易沒有成功支付，伺服端處理所述重新支付請求以使所述交易成功支付。
根據本說明書實施例的第四方面，提供一種支付裝置，應用於收款端掃描支付資訊碼並向伺服端提交支付請求、且未收到支付結果的情況下，其中，支付資訊碼為支付端產生，所述支付資訊碼與支付請求至少包含本次交易的標識資訊，該裝置包括：
重新支付模組：用於使支付端接收用戶的重新支付操作，透過掃描收款端提供的收款資訊碼獲取收款端用戶資訊，向伺服端發送重新支付請求，所述重新支付請求中至少包含所述本次交易的標識資訊；
請求判斷模組：用於使支付端判斷所述重新支付請求是否成功；
請求快取模組：用於當重新支付請求沒有成功後，使支付端展示支付成功資訊，並將所述重新支付請求快取在本地，當滿足發送條件時自動再次發送；
資訊展示模組：用於當重新支付請求成功後，使支付端展示支付成功資訊，本次交易結束。
根據本說明書實施例的第五方面，還提供一種支付裝置，應用於收款端掃描支付資訊碼並向伺服端提交支付請求、且未收到支付結果的情況下，其中，支付資訊碼為支付端產生，所述支付資訊碼與支付請求至少包含本次交易的標識資訊，該裝置包括：
請求接收模組：用於使伺服端接收支付端在用戶重新支付操作後發送的重新支付請求，所述重新支付請求中至少包含所述本次交易的標識資訊；
交易判斷模組：用於使伺服端根據所述重新支付請求中包含的交易標識資訊查詢所述交易標識對應的交易是否已經成功支付，若所述交易沒有成功支付，伺服端處理所述重新支付請求以使所述交易成功支付。
本說明書實施例所提供的技術方案，在支付端的付款資訊碼中增加本次交易標識資訊，以使本次交易具有唯一性。當支付雙方的第一次支付沒有及時接收到支付成功資訊時，支付端可透過新增的重新支付功能進入掃碼模式，透過掃描收款端提供的收款資訊碼再次完成支付。其中，重新支付時會將攜帶之前交易標識資訊的重新支付請求再次發送給伺服端，若沒有發送成功，則支付端快取該重新支付請求，在滿足發送條件時自動再次發送直到發送成功。而伺服端透過第一次支付資訊和重新支付資訊中攜帶的相同的交易標識資訊避免雙倍支付。本方案既不會使支付端用戶多付錢，又能保證支付成功，提升了支付雙方的體驗。
應當理解的是，以上的一般描述和後文的細節描述僅是示例性和解釋性的，並不能限制本說明書實施例。
此外，本說明書實施例中的任一實施例並不需要達到上述的全部效果。In response to the above technical problems, the embodiments of this specification provide a payment method, device, and business server. The technical solutions are as follows:
According to the first aspect of the embodiment of the present specification, a payment method is provided, which is applied to the case where the payment terminal scans the payment information code and submits a payment request to the server, and no payment result is received, wherein the payment information code is the payment terminal Generated, the payment information code and the payment request at least contain identification information of the transaction, the method includes:
The payment terminal receives the user's repayment operation, obtains the user information of the collection terminal by scanning the collection information code provided by the collection terminal, and sends a repayment request to the server, where the repayment request includes at least the identifier of the transaction News;
The payment terminal displays payment success information without determining whether the repayment request is successful; and
The payment terminal judges whether the repayment request is successful;
If the repayment request is not successful, the payment terminal caches the repayment request locally and automatically sends it again when the sending conditions are met;
After receiving the repayment request, the server checks whether the transaction corresponding to the transaction identifier has been successfully paid according to the transaction identifier information contained in the repayment request. If the transaction is not successfully paid, the server handles the repayment Payment request to make the transaction successful.
According to the second aspect of the embodiment of the present specification, a payment method is also provided, which is applied to the case where the payee scans the payment information code and submits a payment request to the server, and no payment result is received, wherein the payment information code is payment Generated by the terminal, the payment information code and the payment request at least contain the identification information of the transaction, the method includes:
The payment terminal receives the user's repayment operation, obtains the user information of the collection terminal by scanning the collection information code provided by the collection terminal, and sends a repayment request to the server, where the repayment request includes at least the identifier of the transaction News;
The payment terminal judges whether the repayment request is successful;
If the repayment request is not successful, the payment terminal displays the payment success information, and caches the repayment request locally, and automatically sends it again when the sending conditions are met;
If the repayment request is successful, the payment terminal displays the payment success information, and the transaction ends.
According to the third aspect of the embodiments of the present specification, a payment method is also provided, which is applied to the case where the payee scans the payment information code and submits a payment request to the server, and no payment result is received, wherein the payment information code is payment Generated by the terminal, the payment information code and the payment request at least contain the identification information of the transaction, the method includes:
The server end receives the repayment request sent by the payment terminal after the user repays the operation, and the repayment request at least contains the identification information of the transaction;
The server checks whether the transaction corresponding to the transaction identifier has been successfully paid according to the transaction identifier information contained in the repayment request. If the transaction is not successfully paid, the server processes the repayment request to make the transaction successful .
According to a fourth aspect of the embodiments of the present specification, a payment device is provided, which is applied when a payment information code is scanned by a payee and a payment request is submitted to a server, and no payment result is received, wherein the payment information code is the payment terminal Generated, the payment information code and the payment request at least contain identification information of the transaction, the device includes:
Repayment module: used to enable the payment terminal to receive the user's repayment operation, obtain the information of the payment terminal user by scanning the payment information code provided by the payment terminal, and send a repayment request to the server, at least at least Contains the identification information of this transaction;
Request judgment module: used to make the payment terminal judge whether the repayment request is successful;
Request cache module: used to make the payment terminal display payment success information after the repayment request is unsuccessful, and cache the repayment request locally, and automatically send again when the sending conditions are met;
Information display module: used to make the payment terminal display the payment success information after the repayment request is successful, and the transaction ends.
According to a fifth aspect of the embodiments of the present specification, there is also provided a payment device, which is applied to the case where the payee scans the payment information code and submits a payment request to the server, and no payment result is received, wherein the payment information code is payment Generated by the terminal, the payment information code and the payment request at least contain the identification information of the transaction, the device includes:
Request receiving module: used to enable the server to receive the repayment request sent by the payment terminal after the user repays the payment operation, where the repayment request at least contains the identification information of the transaction;
Transaction judgment module: used to enable the server to query whether the transaction corresponding to the transaction identifier has been successfully paid according to the transaction identifier information contained in the repayment request, and if the transaction has not been successfully paid, the server to process the repayment Request for successful payment of the transaction.
The technical solution provided by the embodiment of this specification adds the identification information of the transaction to the payment information code of the payment terminal, so as to make the transaction unique. When the first payment of both parties fails to receive the payment success information in time, the payment terminal can enter the scan code mode through the newly added repayment function, and complete the payment again by scanning the payment information code provided by the payment terminal. Among them, during the repayment, the repayment request carrying the previous transaction identification information is sent to the server again. If the transmission is not successful, the payment terminal caches the repayment request and automatically sends it again when the transmission conditions are met until the transmission is successful. The server side avoids double payment through the same transaction identification information carried in the first payment information and the repayment information. This solution will not only make the payment end user pay more, but also ensure that the payment is successful, which improves the experience of both parties.
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.
這裡將詳細地對示例性實施例進行說明，其示例表示在圖式中。下面的描述涉及圖式時，除非另有表示，不同圖式中的相同數字表示相同或相似的要素。以下示例性實施例中所描述的實施方式並不代表與本案相一致的所有實施方式。相反，它們僅是與如所附申請專利範圍中所詳述的、本案的一些方面相一致的裝置和方法的例子。
在本案使用的術語是僅僅出於描述特定實施例的目的，而非旨在限制本案。在本案和所附申請專利範圍中所使用的單數形式的“一種”、“所述”和“該”也旨在包括多數形式，除非上下文清楚地表示其他含義。還應當理解，本文中使用的術語“和/或”是指並包含一個或多個相關聯的列出項目的任何或所有可能組合。
應當理解，儘管在本案可能採用術語第一、第二、第三等來描述各種資訊，但這些資訊不應限於這些術語。這些術語僅用來將同一類型的資訊彼此區分開。例如，在不脫離本案範圍的情況下，第一資訊也可以被稱為第二資訊，類似地，第二資訊也可以被稱為第一資訊。取決於語境，如在此所使用的詞語“如果”可以被解釋成為“在……時”或“當……時”或“響應於確定”。
隨著行動支付的普及，越來越多的人在線下商鋪購買商品時，會透過終端設備的支付裝置進行支付，其中，掃描資訊碼進行支付是一種常見的支付方式，而資訊碼是資訊碼的常見展現形式之一，當前資訊碼的支付方式有兩種：商戶掃描顧客的資訊碼或顧客掃描商戶的資訊碼，透過掃描資訊碼獲取對方的資訊，並將包含各種資訊的支付請求發送給伺服端，伺服端成功處理這筆交易後，將支付成功的提示資訊返回給支付雙方。
現有技術中，商戶掃描顧客的資訊碼後，可能會因為網路或設備等問題，導致雙方支付操作之後遲遲收不到支付成功的提示資訊。此時支付結果未知，可能在伺服端已經支付成功，也可能並沒有支付成功。此時如果顧客重新支付，可能會造成雙倍支付，如果顧客不重新支付，交易就無法繼續正常進行。這種情況影響了雙方的體驗。
針對以上問題，本說明書實施例提供一種支付方法，以及一種用於執行該方法的支付裝置，下面首先對本說明書實施例方案的運行系統架構進行說明。參，本說明書實施例方案涉及的實體包括：支付端、伺服端、收款端，其中：
支付端是交易的支付發起方，是顧客支付錢款時所使用的終端。支付端可以是專門用於支付的設備，也可以是安裝在智慧型終端的具有支付功能的軟體（例如安裝了支付寶錢包的手機），支付端具備掃碼功能，資訊碼產生功能與快取功能；
伺服端是交易的中間處理方，可以是一個獨立的支付平台，伺服端負責接收支付端或收款端發送的交易請求資訊，根據交易請求資訊中的內容對交易做出處理，並將處理結果返回給支付端或收款端，例如，伺服端接收支付端發送的支付請求，按照支付請求中包含的資訊扣除支付端的相應金額，給付收款端相應金額，並分別將交易結果資訊發送給支付端和收款端；
收款端是交易的收款方，是商戶收款所使用的終端，通常可以為具備掃碼功能的機具。
為了發送與接收相關的交易請求，上述三種實體均需要具備連接網際網路的功能。資訊碼的具體形式可以是二維碼（也稱二維條碼）、一維條碼或可變條碼等，資訊碼的形式不影響本案方案的實現。
下面對本實施例涉及的支付方法進行詳細說明，參見圖1a與圖1b所示，該支付方法應用於收款端掃描支付資訊碼並向伺服端提交支付請求、且未收到支付結果的情況下，其中，支付資訊碼為支付端產生，所述支付資訊碼與支付請求至少包含本次交易的標識資訊，該方法可以包括以下步驟：
S101，支付端接收用戶的重新支付操作；
在支付端用戶發起重新支付操作的應用場景為：支付端產生並展示支付資訊碼，收款端掃描支付資訊碼並向伺服端提交支付請求，在某些情況下，如設備出現問題或網路出現問題，支付雙方遲遲無法收到支付結果，此時支付結果未知，為了使交易儘快完成，避免浪費雙方用戶的時間，需要由支付端用戶發起重新支付。
在上述過程中，支付端產生的支付資訊碼包含本次交易的標識資訊，收款端透過掃描支付資訊碼獲取該標識資訊，並將標識資訊攜帶到支付請求中，一併提交到伺服端。該標識資訊可在伺服端的所有交易中唯一標識本次交易。
重新支付操作可以為用戶對支付端提供的重新支付介面的操作，重新支付介面的實現方式可以為：支付端支成支付資訊碼頁面，在支付資訊碼頁面展示支付資訊碼，並提供重新支付操作介面。如圖2所示，以按鈕的形式提供該重新支付介面，支付端用戶可透過點擊該按鈕實現對重新支付介面的操作。
S102，伺服端產生收款資訊碼；
S103，支付端掃描收款端的收款資訊碼。以獲取收款端的用戶資訊；
通常來說，發送給伺服端的支付請求由掃碼的一端提交的，若收款端提交支付請求沒有收到支付結果，則很可能是收款端的設備或網路有問題，此時換由支付端掃碼並提交請求，收到支付結果的成功率較高。
支付端接收用戶對重新支付介面的操作並進入掃碼模式，透過掃描收款端提供的收款資訊碼獲取收款端用戶的身份識別資訊，需要注意的是，重新支付與首次支付屬同一次交易，在支付端開始重新支付進入掃碼模式時，會攜帶之前的交易標識資訊。
S104，支付端向伺服端發送重新支付請求，所述重新支付請求中至少包含所述本次交易的標識資訊；
在支付端向伺服端發送重新支付請求之前，通常需要先由支付端用戶輸入支付金額並點擊確認支付。此時將收款端用戶的身份識別資訊，支付端用戶本身的身份識別資訊，支付金額資訊，支付時間資訊和本次交易的標識資訊一併整合到重新支付請求中，將該重新支付請求發送給伺服端。
S105，支付端在無需確定所述重新支付請求是否成功的情況下，展示支付成功資訊；
重新支付請求發送後，根據是否收到伺服端對該重新支付請求的反饋資訊，後續執行步驟有所不同。參見圖1a與圖1b，分為S106a和S106b。
S106a，支付端收到伺服端對重新支付請求的反饋資訊，則說明伺服端已能接收並處理重新交易請求，支付端不再處理。
S106b，若重新支付請求沒有成功，支付端快取重新支付請求，當滿足發送條件時自動再次發送；
當展示支付成功資訊後，支付端用戶（顧客）即可離開收款端（商戶），但此時支付請求可能仍會因為某些原因無法成功。例如：支付端網路不通，則由支付端將該次交易快取在本地，當網路連通時，支付端將自動將重新支付請求發送給伺服端，以使伺服端能夠收到該重新支付請求。
S107，伺服端根據所述重新支付請求中包含的交易標識資訊查詢對應的交易是否已經成功支付，若沒有成功支付，伺服端處理所述重新支付請求以使其成功支付。
伺服端收到重新支付請求後，根據重新支付請求中包含的交易標識資訊查詢對應的先前的支付請求，可能出現兩種情況：
情況一，支付已經成功，伺服端收到了先前的支付請求並對支付端用戶和收款端用戶的帳戶做出了金額處理，即先前的支付請求已經使該交易成功，但處理結果資訊沒有發送回支付端和收款端。此時伺服端不需要再對交易做出處理。
情況二，支付沒有成功，或沒有查詢到對應的支付請求。此時伺服端處理該交易，完成支付。
需要注意的是，重新支付請求可能先到達伺服端，而首次支付請求後到達伺服端，此時伺服端仍可遵循上述的處理邏輯，即，伺服端先收到重新支付請求時遵循情況二：沒有查詢到對應的支付請求，伺服端處理交易，完成支付；伺服端再收到首次支付請求，遵循情況一，伺服端根據交易標識資訊查詢到支付已經成功，不再對交易做出處理。
在某些情況下，可能會出現惡意顧客，即顧客在支付端點擊重新支付卻不再讓支付端繼續連網或刪除本地交易快取，導致交易快取在支付端後無法透過上網發送給伺服端。
針對上述問題，本說明書實施例提供一種用戶資格評估方法，以在一定程度上杜絕惡意顧客，參見圖3所示，該方法可以包括以下步驟：
S301，獲取支付端用戶的資格資訊；
S302，確定支付端用戶的資格資訊是否滿足預設條件，若符合預設條件，執行步驟S303，若不滿足預設條件，執行步驟S304；
資格資訊通常情況下可以為支付端用戶的信用資訊，如：獲取支付端用戶的芝麻信用分，騰訊信用分等等信用資訊，並透過判斷支付端用戶的信用資訊來決定是否開放重新支付功能。但資格資訊並不局限於信用資訊，也可以根據實際情況選擇性獲取其他的資格資訊，如：獲取支付端用戶與收款端用戶的交易次數，交易時間等資訊。透過這些資訊判斷支付端用戶是否為商戶的常客，再根據判斷結果確定是否開放重新支付功能，等等。
S303，開放支付端的重新支付功能；
開放重新支付功能可以是開放支付端的重新支付介面，例如：當開放重新支付功能時，支付二維碼頁面顯示重新支付按鈕，當未開放重新支付功能時，支付二維碼頁面不顯示重新支付按鈕。
或，開放重新支付功能可以是開放支付端用戶對於重新支付介面的操作權限，例如：不管是否開放重新支付功能，支付二維碼頁面均顯示重新支付按鈕，區別在於支付端用戶是否能夠透過點擊該按鈕開啟重新支付。在某些情況下，可將重新支付按鈕設為灰色表示其不可操作。
S304，關閉支付端的重新支付功能。
需要注意的是，即使惡意顧客（支付端用戶）不再讓支付端繼續連網或刪除本地交易快取，因為在首次支付，即收款端掃描支付端的支付二維碼並向伺服端提交支付請求時，本次交易資訊和支付端用戶的相關資訊已經儲存於收款端，收款端仍可提供交易資訊並透過後續申訴等操作追回該筆錢款，無需擔心安全問題。
本說明書實施例中的重新支付是在發生在首次支付不成功的情況下，參見圖4所示，對於首次支付時執行的方法進行說明：
S401，支付端產生支付資訊碼，所述支付資訊碼中包含交易標識資訊；
S402，收款端透過掃描支付端的支付資訊碼獲取交易標識資訊與支付端用戶資訊；
S403，向伺服端發送支付請求，所述支付請求中至少包含所述本次交易的標識資訊；
S404，未接收到客戶端針對支付請求的回饋資訊。
為了更清楚地說明本說明書實施例的方案，下面分別再從單側的角度，對於執行的方法進行說明：
參見圖5所示，為本說明書實施例在支付端執行的支付方法。
S501，支付端接收用戶的重新支付操作，透過掃描收款端提供的收款二維碼獲取收款端用戶資訊；
S502，支付端向伺服端發送重新支付請求，所述重新支付請求中至少包含所述本次交易的標識資訊；
S503，支付端在無需確定所述重新支付請求是否成功的情況下，展示支付成功資訊；
S504，支付端判斷所述重新支付請求是否成功；若支付請求不成功，執行步驟S505，若支付請求成功，則支付端流程結束；
S505，支付端將所述重新支付請求快取在本地，當滿足發送條件時自動再次發送。
參見圖6所示，為本說明書實施例在伺服端執行的支付方法。
S601，伺服端接收支付端在用戶重新支付操作後發送的重新支付請求，所述重新支付請求中至少包含所述本次交易的標識資訊；
S602，伺服端根據所述重新支付請求中包含的交易標識資訊查詢所述交易標識對應的重新支付請求是否已經成功支付，若沒有成功支付，執行步驟S603，若已經成功支付，則伺服端流程結束；
S603，伺服端處理所述重新支付請求以使所述交易成功支付。
關於支付端與伺服端的單側執行方法細節，可以參見前面實施例的描述，這裡不再贅述。
相應於上述方法實施例，本說明書實施例還提供一種支付裝置，參見圖7所示，該裝置應用於收款端掃描支付二維碼並向伺服端提交支付請求、且未收到支付結果的情況下，其中，支付二維碼為支付端產生，所述支付二維碼與支付請求至少包含本次交易的標識資訊，所述裝置可以包括：重新支付模組710，請求判斷模組720，請求快取模組730和資訊展示模組740，
重新支付模組710：用於使支付端接收用戶的重新支付操作，透過掃描收款端提供的收款二維碼獲取收款端用戶資訊，向伺服端發送重新支付請求，所述重新支付請求中至少包含所述本次交易的標識資訊；
請求判斷模組720：用於使支付端判斷所述重新支付請求是否成功；
請求快取模組730：用於當重新支付請求沒有成功後，使支付端展示支付成功資訊，並將所述重新支付請求快取在本地，當滿足發送條件時自動再次發送；
資訊展示模組740：用於當重新支付請求成功後，使支付端展示支付成功資訊，本次交易結束。
相應於上述方法實施例，本說明書實施例還提供一種支付裝置，參見圖8所示，該裝置應用於收款端掃描支付二維碼並向伺服端提交支付請求、且未收到支付結果的情況下，其中，支付二維碼為支付端產生，所述支付二維碼與支付請求至少包含本次交易的標識資訊，所述裝置可以包括：請求接收模組810和交易判斷模組820。
請求接收模組810：用於使伺服端接收支付端在用戶重新支付操作後發送的重新支付請求，所述重新支付請求中至少包含所述本次交易的標識資訊；
交易判斷模組820：用於使伺服端根據所述重新支付請求中包含的交易標識資訊查詢所述交易標識對應的交易是否已經成功支付，若所述交易沒有成功支付，伺服端處理所述重新支付請求以使所述交易成功支付。
本案實施例還提供一種電子設備，其至少包括記憶體、處理器及儲存在記憶體上並可在處理器上運行的電腦程式，其中，處理器執行所述程式時實現前述支付方法，該方法應用於收款端掃描支付二維碼並向伺服端提交支付請求、且未收到支付結果的情況下，其中，支付二維碼為支付端產生，所述支付二維碼與支付請求至少包含本次交易的標識資訊，所述方法至少包括：
支付端接收用戶的重新支付操作，透過掃描收款端提供的收款二維碼獲取收款端用戶資訊，向伺服端發送重新支付請求，所述重新支付請求中至少包含所述本次交易的標識資訊；
支付端判斷所述重新支付請求是否成功；
若重新支付請求沒有成功，支付端展示支付成功資訊，並將所述重新支付請求快取在本地，當滿足發送條件時自動再次發送；
若重新支付請求成功，支付端展示支付成功資訊，本次交易結束。
本案實施例還提供另一種電子設備，其至少包括記憶體、處理器及儲存在記憶體上並可在處理器上運行的電腦程式，其中，處理器執行所述程式時實現前述支付方法，該方法應用於收款端掃描支付二維碼並向伺服端提交支付請求、且未收到支付結果的情況下，其中，支付二維碼為支付端產生，所述支付二維碼與支付請求至少包含本次交易的標識資訊，所述方法至少包括：
伺服端接收支付端在用戶重新支付操作後發送的重新支付請求，所述重新支付請求中至少包含所述本次交易的標識資訊；
伺服端根據所述重新支付請求中包含的交易標識資訊查詢所述交易標識對應的交易是否已經成功支付，若所述交易沒有成功支付，伺服端處理所述重新支付請求以使所述交易成功支付。
圖9示出了本說明書實施例所提供的一種更為具體的計算設備硬體結構示意圖，該設備可以包括：處理器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，但是在具體實施過程中，該設備還可以包括實現正常運行所必需的其他組件。此外，本領域的技術人員可以理解的是，上述設備中也可以僅包含實現本說明書實施例方案所必需的組件，而不必包含圖中所示的全部組件。
本說明書實施例還提供一種電腦可讀儲存媒體，其上儲存有電腦程式，該程式被處理器執行時實現前述的支付方法，該方法應用於收款端掃描支付二維碼並向伺服端提交支付請求、且未收到支付結果的情況下，其中，支付二維碼為支付端產生，所述支付二維碼與支付請求至少包含本次交易的標識資訊，所述方法至少包括：
支付端接收用戶的重新支付操作，透過掃描收款端提供的收款二維碼獲取收款端用戶資訊，向伺服端發送重新支付請求，所述重新支付請求中至少包含所述本次交易的標識資訊；
支付端判斷所述重新支付請求是否成功；
若重新支付請求沒有成功，支付端展示支付成功資訊，並將所述重新支付請求快取在本地，當滿足發送條件時自動再次發送；
若重新支付請求成功，支付端展示支付成功資訊，本次交易結束。
本說明書實施例還提供一種電腦可讀儲存媒體，其上儲存有電腦程式，該程式被處理器執行時實現前述的支付方法，該方法應用於收款端掃描支付二維碼並向伺服端提交支付請求、且未收到支付結果的情況下，其中，支付二維碼為支付端產生，所述支付二維碼與支付請求至少包含本次交易的標識資訊，所述方法至少包括：
伺服端接收支付端在用戶重新支付操作後發送的重新支付請求，所述重新支付請求中至少包含所述本次交易的標識資訊；
伺服端根據所述重新支付請求中包含的交易標識資訊查詢所述交易標識對應的交易是否已經成功支付，若所述交易沒有成功支付，伺服端處理所述重新支付請求以使所述交易成功支付。
電腦可讀媒體包括永久性和非永久性、可移動和非可移動媒體可以由任何方法或技術來實現資訊儲存。資訊可以是電腦可讀指令、資料結構、程式的模組或其他資料。電腦的儲存媒體的例子包括，但不限於相變記憶體（PRAM）、靜態隨機存取記憶體（SRAM）、動態隨機存取記憶體（DRAM）、其他類型的隨機存取記憶體（RAM）、唯讀記憶體（ROM）、電可擦除可程式化唯讀記憶體（EEPROM）、快閃記憶體或其他記憶體技術、唯讀光碟唯讀記憶體（CD-ROM）、數位多功能光碟（DVD）或其他光學儲存、磁盒式磁帶，磁帶磁碟儲存或其他磁性儲存設備或任何其他非傳輸媒體，可用於儲存可以被計算設備訪問的資訊。按照本文中的界定，電腦可讀媒體不包括暫存電腦可讀媒體（transitory media），如調變的資料信號和載波。
本說明書實施例還提供一種支付系統，應用於收款端掃描支付資訊碼並向伺服端提交支付請求、且未收到支付結果的情況下，其中，支付資訊碼為支付端產生，所述支付資訊碼與支付請求至少包含本次交易的標識資訊，該系統包括：
支付端、收款端、伺服端；
所述支付端，用於接收用戶的重新支付操作，透過掃描收款端提供的收款資訊碼獲取收款端用戶資訊，向伺服端發送重新支付請求，所述重新支付請求中至少包含所述本次交易的標識資訊；
所述收款端，用於產生收款資訊碼以供支付端掃描；
所述支付端，用於在無需確定所述重新支付請求是否成功的情況下，展示支付成功資訊；以及判斷所述重新支付請求是否成功；
所述支付端，用於在支付請求沒有成功的情況下，將所述重新支付請求快取在本地，當滿足發送條件時自動再次發送；
所述伺服端，用於接收到重新支付請求後，根據所述重新支付請求中包含的交易標識資訊查詢所述交易標識對應的交易是否已經成功支付，若所述交易沒有成功支付，伺服端處理所述重新支付請求以使所述交易成功支付。
上述裝置中各個單元的功能和作用的實現過程具體詳見上述方法中對應步驟的實現過程，在此不再贅述。
對於裝置實施例而言，由於其基本對應於方法實施例，所以相關之處參見方法實施例的部分說明即可。以上所描述的裝置實施例僅僅是示意性的，其中所述作為分離部件說明的單元可以是或者也可以不是物理上分開的，作為單元顯示的部件可以是或者也可以不是物理單元，即可以位於一個地方，或者也可以分佈到多個網路單元上。可以根據實際的需要選擇其中的部分或者全部模組來實現本案方案的目的。本領域普通技術人員在不付出創造性勞動的情況下，即可以理解並實施。
透過以上的實施方式的描述可知，本領域的技術人員可以清楚地瞭解到本說明書實施例可借助軟體加必需的通用硬體平台的方式來實現。基於這樣的理解，本說明書實施例的技術方案本質上或者說對現有技術做出貢獻的部分可以以軟體產品的形式體現出來，該電腦軟體產品可以儲存在儲存媒體中，如ROM/RAM、磁碟、光碟等，包括若干指令用以使得一台電腦設備（可以是個人電腦，伺服器，或者網路設備等）執行本說明書實施例各個實施例或者實施例的某些部分所述的方法。
上述實施例闡明的系統、裝置、模組或單元，具體可以由電腦芯片或實體實現，或者由具有某種功能的產品來實現。一種典型的實現設備為電腦，電腦的具體形式可以是個人電腦、膝上型電腦、蜂巢式電話、相機電話、智慧型電話、個人數位助理、媒體播放器、導航設備、電子郵件收發設備、遊戲控制台、平板電腦、可穿戴設備或者這些設備中的任意幾種設備的組合。
本說明書中的各個實施例均採用遞進的方式描述，各個實施例之間相同相似的部分互相參見即可，每個實施例重點說明的都是與其他實施例的不同之處。尤其，對於裝置實施例而言，由於其基本相似於方法實施例，所以描述得比較簡單，相關之處參見方法實施例的部分說明即可。以上所描述的裝置實施例僅僅是示意性的，其中所述作為分離部件說明的模組可以是或者也可以不是物理上分開的，在實施本說明書實施例方案時可以把各模組的功能在同一個或多個軟體和/或硬體中實現。也可以根據實際的需要選擇其中的部分或者全部模組來實現本實施例方案的目的。本領域普通技術人員在不付出創造性勞動的情況下，即可以理解並實施。
以上所述僅是本說明書實施例的具體實施方式，應當指出，對於本技術領域的普通技術人員來說，在不脫離本說明書實施例原理的前提下，還可以做出若干改進和潤飾，這些改進和潤飾也應視為本說明書實施例的保護範圍。
以上所述僅為本案的較佳實施例而已，並不用以限制本案，凡在本案的精神和原則之內，所做的任何修改、等同替換、改進等，均應包含在本案保護的範圍之內。Exemplary embodiments will be described in detail here, examples of which are shown in the drawings. When the following description refers to drawings, unless otherwise indicated, the same numerals in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all the embodiments consistent with this case. Rather, they are merely examples of devices and methods consistent with some aspects of the case as detailed in the scope of the attached patent application.
The terminology used in this case is for the purpose of describing particular embodiments only, and is not intended to limit this case. The singular forms "a", "said" and "the" used in this case and the appended patent applications are also intended to include most forms unless the context clearly indicates other meanings. It should also be understood that the term "and/or" as used herein refers to and includes any or all possible combinations of one or more associated listed items.
It should be understood that although the terms first, second, third, etc. may be used to describe various information in this case, the information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this case, the first information may also be referred to as second information. Similarly, the second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when" or "when" or "in response to a determination".
With the popularity of mobile payment, more and more people will pay through the payment device of the terminal device when buying goods in offline stores. Among them, scanning the information code to pay is a common payment method, and the information code is information One of the common display forms of codes. There are two payment methods for current information codes: merchants scan customer's information codes or customers scan merchant's information codes, obtain the other party's information by scanning information codes, and send payment requests containing various information To the server, after successfully processing the transaction, the server returns the prompt message of successful payment to both parties.
In the prior art, after the merchant scans the customer's information code, it may cause problems such as network or equipment that both parties may not receive the prompt information of successful payment after the payment operation. At this time, the payment result is unknown, and the payment may be successful on the server side, or may not be successful. At this time, if the customer repays, it may result in double payment. If the customer does not repay, the transaction cannot continue normally. This situation affects the experience of both parties.
In view of the above problems, the embodiments of the present specification provide a payment method and a payment device for executing the method. The following first describes the operating system architecture of the solution of the embodiment of the present specification. For reference, the entities involved in the embodiment of the present specification include: a payment terminal, a server terminal, and a payment terminal, where:
The payment terminal is the payment initiator of the transaction, and is the terminal used by the customer to pay the money. The payment terminal can be a device dedicated to payment, or it can be a software with payment function installed on a smart terminal (such as a mobile phone with Alipay wallet installed). The payment terminal has a code scanning function, information code generation function and cache function ;
The server is the intermediate processor of the transaction, which can be an independent payment platform. The server is responsible for receiving the transaction request information sent by the payment terminal or the payment terminal, processing the transaction according to the content of the transaction request information, and processing the result Return to the payment or payment terminal, for example, the server receives the payment request sent by the payment terminal, deducts the corresponding amount of the payment terminal according to the information contained in the payment request, pays the corresponding amount of the payment terminal, and sends the transaction result information to the payment separately End and collection end;
The receiving end is the beneficiary of the transaction, and is the terminal used by merchants to receive payment. It can usually be a machine with a barcode scanning function.
In order to send and receive transaction requests, the above three entities need to be able to connect to the Internet. The specific form of the information code can be a two-dimensional code (also called a two-dimensional bar code), a one-dimensional bar code or a variable bar code, etc. The form of the information code does not affect the realization of the scheme in this case.
The payment method involved in this embodiment will be described in detail below. As shown in FIGS. 1a and 1b, this payment method is applied when the receiving end scans the payment information code and submits a payment request to the server, and no payment result is received. , Where the payment information code is generated by the payment terminal, and the payment information code and the payment request at least contain the identification information of the transaction. The method may include the following steps:
S101. The payment terminal receives the user's repayment operation;
The application scenario where the payment end user initiates the repayment operation is: the payment end generates and displays the payment information code, the payment end scans the payment information code and submits the payment request to the server, in some cases, such as a problem with the device or the Internet If there is a problem, both payment parties are unable to receive the payment result. At this time, the payment result is unknown. In order to complete the transaction as soon as possible and avoid wasting the time of both users, the payment end user needs to initiate a repayment.
In the above process, the payment information code generated by the payment terminal contains the identification information of the transaction. The receiving terminal scans the payment information code to obtain the identification information, and carries the identification information into the payment request, and submits it to the server. This identification information can uniquely identify this transaction in all transactions on the server side.
The repayment operation can be the operation of the user on the repayment interface provided by the payment terminal. The repayment interface can be implemented as follows: the payment terminal branches into a payment information code page, displays the payment information code on the payment information code page, and provides a repayment operation interface. As shown in FIG. 2, the repayment interface is provided in the form of a button, and the user at the payment end can click the button to implement the operation of the repayment interface.
S102, the server generates a payment information code;
S103: The payment terminal scans the collection information code of the collection terminal. To obtain user information of the receiving end;
Generally speaking, the payment request sent to the server is submitted by the end of the scan code. If the payment request is not received by the receiving end, it is likely that there is a problem with the equipment or network of the receiving end. The terminal scans the code and submits the request, and the success rate of receiving the payment result is high.
The payment terminal receives the user's operation of the repayment interface and enters the scan code mode. By scanning the collection information code provided by the collection terminal to obtain the identification information of the payment terminal user, it should be noted that the repayment is the same as the first payment. For transactions, when the payment terminal starts to re-pay to enter the scanning mode, it will carry the previous transaction identification information.
S104: The payment terminal sends a repayment request to the server, where the repayment request includes at least the identification information of the transaction;
Before the payment end sends a repayment request to the server, it is usually necessary for the payment end user to enter the payment amount and click to confirm the payment. At this time, the identification information of the receiving end user, the identification information of the paying end user itself, the payment amount information, the payment time information and the identification information of the transaction are integrated into the repayment request, and the repayment request is sent To the server.
S105. The payment terminal displays payment success information without determining whether the repayment request is successful;
After the repayment request is sent, the subsequent steps are different depending on whether the server receives feedback information about the repayment request. Referring to FIGS. 1a and 1b, it is divided into S106a and S106b.
S106a, the payment terminal receives the feedback information of the server on the repayment request, it means that the server has been able to receive and process the re-transaction request, and the payment terminal no longer processes it.
S106b, if the repayment request is unsuccessful, the payment terminal caches the repayment request and automatically sends it again when the sending conditions are met;
When the payment success information is displayed, the payment end user (customer) can leave the collection end (merchant), but at this time the payment request may still be unsuccessful for some reason. For example, if the payment terminal is not connected to the network, the payment terminal will cache the transaction locally. When the network is connected, the payment terminal will automatically send a repayment request to the server to enable the server to receive the repayment request.
S107: The server queries whether the corresponding transaction has been successfully paid according to the transaction identification information included in the repayment request. If the payment is not successful, the server processes the repayment request to make the payment successful.
After receiving the repayment request, the server checks the corresponding previous payment request according to the transaction identification information contained in the repayment request. Two situations may occur:
In the first case, the payment has been successful. The server received the previous payment request and processed the amount of money on the accounts of the paying user and the payee user. That is, the previous payment request has made the transaction successful, but the processing result information has not been sent. Back to the payment and collection ends. At this time, the server does not need to process the transaction.
Case 2: The payment was not successful, or the corresponding payment request was not found. At this time, the server processes the transaction and completes the payment.
It should be noted that the repayment request may arrive at the server first, and then arrive at the server after the first payment request. At this time, the server can still follow the above processing logic, that is, the server follows the second case when receiving the repayment request first: If the corresponding payment request is not found, the server processes the transaction and completes the payment; the server receives the first payment request again, and according to the first situation, the server inquires that the payment has been successful according to the transaction identification information and no longer processes the transaction.
In some cases, malicious customers may appear, that is, customers click on the payment side to repay but no longer allow the payment side to continue to connect to the network or delete the local transaction cache, resulting in the transaction cache cannot be sent to the server via the Internet after the payment side end.
In response to the above problems, the embodiments of the present specification provide a user qualification evaluation method to eliminate malicious customers to a certain extent. As shown in FIG. 3, the method may include the following steps:
S301: Obtain the qualification information of the user of the payment terminal;
S302. Determine whether the qualification information of the payment terminal user meets the preset condition. If the preset condition is met, perform step S303; if the preset condition is not met, perform step S304;
Qualification information can usually be the credit information of the payment end user, such as: obtaining the credit information of the payment end user's sesame credit, Tencent credit score, etc., and determining whether to open the repayment function by judging the payment end user's credit information. However, the qualification information is not limited to credit information. You can also selectively obtain other qualification information according to the actual situation, such as: obtaining the information on the number of transactions and transaction time of the payment end user and the payment end user. Use this information to determine whether the payment end user is a regular customer of the merchant, and then determine whether to open the repayment function based on the judgment result, and so on.
S303, open the payment function of the payment terminal;
The open repayment function can be the repayment interface of the open payment terminal, for example: when the repayment function is opened, the repayment button is displayed on the payment QR code page, and when the repayment function is not opened, the repayment button is not displayed on the payment QR code page .
Or, the open repayment function may be to open the operation authority of the payment end user to the repayment interface, for example: no matter whether the repayment function is opened, the payment QR code page displays the repayment button, the difference is whether the payment end user can click the Button to start repayment. In some cases, the repay button can be grayed out to indicate that it is inoperable.
S304: Close the repayment function of the payment terminal.
It should be noted that even malicious customers (paying end users) no longer allow the paying end to continue to connect to the network or delete the local transaction cache, because in the first payment, the receiving end scans the payment QR code of the paying end and submits the payment to the server At the time of the request, the transaction information and relevant information of the payment end user have been stored in the receiving end. The receiving end can still provide transaction information and recover the money through subsequent appeals and other operations without worrying about security issues.
The repayment in the embodiment of the present specification is in the case where the first payment is unsuccessful, as shown in FIG. 4, and the method executed at the time of the first payment is described:
S401, the payment terminal generates a payment information code, and the payment information code includes transaction identification information;
S402, the receiving end obtains the transaction identification information and the payment end user information by scanning the payment information code of the payment end;
S403. Send a payment request to the server, where the payment request includes at least the identification information of the transaction;
S404: No feedback information about the payment request from the client is received.
In order to more clearly explain the solutions of the embodiments of the present specification, the following describes the execution method from a one-sided perspective:
Referring to FIG. 5, it is a payment method executed at a payment terminal according to an embodiment of this specification.
S501, the payment terminal receives the user's repayment operation, and obtains the information of the payment terminal user by scanning the payment QR code provided by the payment terminal;
S502, the payment terminal sends a repayment request to the server, where the repayment request includes at least the identification information of the transaction;
S503, the payment terminal displays payment success information without determining whether the repayment request is successful;
S504, the payment terminal judges whether the repayment request is successful; if the payment request is unsuccessful, step S505 is executed; if the payment request is successful, the payment terminal process ends;
S505. The payment terminal caches the repayment request locally, and automatically sends again when the sending condition is met.
Referring to FIG. 6, it is a payment method executed on the server according to an embodiment of the present specification.
S601. The server receives the repayment request sent by the payment terminal after the user repays the payment operation. The repayment request includes at least the identification information of the transaction;
S602. The server queries whether the repayment request corresponding to the transaction identifier has been successfully paid according to the transaction identifier information included in the repayment request. If the payment is not successful, step S603 is executed. If the payment has been successfully paid, the server side process ends ;
S603. The server processes the repayment request to make the transaction successful.
For details of the one-sided execution method of the payment end and the server end, refer to the description of the foregoing embodiment, and details are not described herein again.
Corresponding to the above method embodiment, the embodiment of the present specification also provides a payment device. As shown in FIG. 7, the device is applied to a payment terminal that scans a payment QR code and submits a payment request to a server, and no payment result is received. In this case, where the payment QR code is generated by the payment terminal, the payment QR code and the payment request at least contain the identification information of the transaction, the device may include: a repayment module 710, a request judgment module 720, Request cache module 730 and information display module 740,
Repayment module 710: used to enable the payment terminal to receive the user's repayment operation, obtain the information of the payment terminal user by scanning the payment QR code provided by the payment terminal, and send a repayment request to the server, the repayment request Contains at least the identification information of the transaction;
Request judgment module 720: used to make the payment terminal judge whether the repayment request is successful;
Request cache module 730: used to make the payment terminal display payment success information after the repayment request is unsuccessful, and cache the repayment request locally, and automatically send again when the sending conditions are met;
Information display module 740: used to make the payment terminal display the payment success information after the repayment request is successful, and the transaction ends.
Corresponding to the above method embodiment, the embodiment of the present specification also provides a payment device. As shown in FIG. 8, the device is applied to a payment terminal that scans a payment QR code and submits a payment request to a server, and no payment result is received. In this case, where the payment QR code is generated by the payment terminal, the payment QR code and the payment request at least contain the identification information of the transaction. The device may include a request receiving module 810 and a transaction judgment module 820.
Request receiving module 810: used to enable the server to receive the repayment request sent by the payment terminal after the user repays the payment operation, where the repayment request includes at least the identification information of the transaction;
Transaction judgment module 820: used to enable the server to inquire whether the transaction corresponding to the transaction identifier has been successfully paid according to the transaction identifier information contained in the repayment request, and if the transaction has not been successfully paid, the server to process the renewal Payment request to make the transaction successful.
The embodiment of the present invention also provides an electronic 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 implements the program to implement the foregoing payment method, and the method It is used when the payment terminal scans the payment QR code and submits the payment request to the server, and no payment result is received. The payment QR code is generated by the payment terminal. The payment QR code and the payment request at least include For the identification information of this transaction, the method at least includes:
The payment terminal receives the user's repayment operation, obtains the information of the payment terminal user by scanning the payment QR code provided by the payment terminal, and sends a repayment request to the server, the repayment request includes at least the transaction Identification information
The payment terminal judges whether the repayment request is successful;
If the repayment request is not successful, the payment terminal displays the payment success information, and caches the repayment request locally, and automatically sends it again when the sending conditions are met;
If the repayment request is successful, the payment terminal displays the payment success information, and the transaction ends.
The embodiment of the present invention also provides another electronic 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 implements the program to implement the foregoing payment method, the The method is applied when the payment terminal scans the payment QR code and submits a payment request to the server, and no payment result is received, wherein the payment QR code is generated by the payment terminal, and the payment QR code and the payment request are at least Containing the identification information of this transaction, the method at least includes:
The server end receives the repayment request sent by the payment terminal after the user repays the operation, and the repayment request at least contains the identification information of the transaction;
The server checks whether the transaction corresponding to the transaction identifier has been successfully paid according to the transaction identifier information contained in the repayment request. If the transaction is not successfully paid, the server processes the repayment request to make the transaction successful .
9 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 assigned to be 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. Among them, 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, memory 1020, input/output interface 1030, and 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. When the program is executed by a processor, the aforementioned payment method is implemented. This method is applied to the payment terminal to scan the payment QR code and submit it to the server. In the case of a payment request and no payment result is received, wherein the payment QR code is generated by the payment terminal, the payment QR code and the payment request at least contain identification information of the transaction, and the method at least includes:
The payment terminal receives the user's repayment operation, obtains the information of the payment terminal user by scanning the payment QR code provided by the payment terminal, and sends a repayment request to the server, the repayment request includes at least the transaction Identification information
The payment terminal judges whether the repayment request is successful;
If the repayment request is not successful, the payment terminal displays the payment success information, and caches the repayment request locally, and automatically sends it again when the sending conditions are met;
If the repayment request is successful, the payment terminal displays the payment success information, and the transaction ends.
The embodiments of the present specification also provide a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the aforementioned payment method is implemented. This method is applied to the payment terminal to scan the payment QR code and submit it to the server. In the case of a payment request and no payment result is received, wherein the payment QR code is generated by the payment terminal, the payment QR code and the payment request at least contain identification information of the transaction, and the method at least includes:
The server end receives the repayment request sent by the payment terminal after the user repays the operation, and the repayment request at least contains the identification information of the transaction;
The server checks whether the transaction corresponding to the transaction identifier has been successfully paid according to the transaction identifier information contained in the repayment request. If the transaction is not successfully paid, the server processes the repayment request to make the transaction successful .
Computer-readable media, including permanent and non-permanent, removable and non-removable media, can be stored 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 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 and programmable read-only memory (EEPROM), flash memory or other memory technologies, read-only disc read-only memory (CD-ROM), digital multifunction Optical discs (DVD) or other optical storage, magnetic cassette tapes, magnetic tape storage or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices. According to the definition in this article, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.
The embodiment of the present specification also provides a payment system, which is applied to the case where the payment terminal scans the payment information code and submits a payment request to the server, and no payment result is received, wherein the payment information code is generated by the payment terminal, and the payment The information code and payment request contain at least the identification information of the transaction. The system includes:
Paying end, receiving end, server end;
The payment terminal is used to receive the user's repayment operation, obtain the user information of the collection terminal by scanning the collection information code provided by the collection terminal, and send a repayment request to the server, where the repayment request includes at least the Logo information for this transaction;
The collection terminal is used to generate a collection information code for the payment terminal to scan;
The payment terminal is used to display payment success information without determining whether the repayment request is successful; and determine whether the repayment request is successful;
The payment terminal is used to cache the repayment request locally when the payment request is unsuccessful, and automatically send it again when the sending conditions are met;
The server is used to query whether the transaction corresponding to the transaction identifier has been successfully paid according to the transaction identification information contained in the repayment request after receiving the repayment request, and if the transaction is not successfully paid, the server side processes The repayment request makes the transaction successful.
For the implementation process of the functions and functions of the units in the above device, please refer to the implementation process of the corresponding steps in the above method for details, which will not be repeated here.
As for the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to the description of the method embodiments. The device embodiments described above are only schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located One place, or it can be distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in this case. Those of ordinary skill in the art can understand and implement without paying creative labor.
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, server, or network device, etc.) to perform the methods described in the embodiments of this specification or some parts of the embodiments.
The system, device, 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 laptop 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 A console, 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 device 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 device embodiments described above are only schematic, wherein the modules described as separate components may or may not be physically separated, and the functions of each module can be 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.
The above are only the preferred embodiments of the case, and are not used to limit the case. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the case should be included in the scope of protection of the case Inside.
