為克服相關技術中存在的問題，本發明提供了支付方法、裝置及設備。
根據本發明實施例的第一態樣，提供一種支付方法，所述方法包括：
支付伺服端接收交易支付請求，所述交易支付請求至少包括：支付方資訊、消費方與收費端的交易資訊、以及收費端資訊；
支付伺服端基於預設的支付方與醫保支付卡的綁定關係，獲取與所述支付方資訊對應的醫保支付卡資訊，將所述醫保支付卡資訊、交易資訊和收費端資訊發送至醫保系統；
醫保系統依據所接收資訊對本次交易進行結算，獲得本次交易的醫保費用和自費費用，基於所述收費端資訊執行向收費端支付醫保費用的支付處理，並向支付伺服端回饋處理結果；
支付伺服端根據所述處理結果執行向收費端支付自費費用的支付處理。
在一個實施例中，所述方法還包括：收費端透過調用支付伺服端的支付介面，向支付伺服端發送交易支付請求，所述交易支付請求中還攜帶有用於表示利用醫保進行支付的醫保支付標識。
在一個實施例中，所述交易支付請求還包括醫保系統標識，所述方法還包括：支付伺服端將攜帶有所述醫保支付卡資訊、交易資訊和收費端資訊的預結算請求發送至與所述醫保系統標識對應的醫保系統，並接收醫保系統回饋的本次交易的醫保費用和自費費用，向支付用戶端發送包含醫保費用和自費費用的支付提醒資訊；
所述將所述醫保支付卡資訊、交易資訊和收費端資訊發送至醫保系統，包括：在接收到支付用戶端回饋的確認付款指令時，將攜帶有所述醫保支付卡資訊、交易資訊和收費端資訊的結算請求發送至與所述醫保系統標識對應的醫保系統。
在一個實施例中，所述交易支付請求還包括醫保系統標識，所述方法還包括：支付伺服端透過調用醫保系統的預結算介面，將所述醫保支付卡資訊、交易資訊和收費端資訊發送至與所述醫保系統標識對應的醫保系統，並接收醫保系統回饋的本次交易的醫保費用和自費費用，向支付用戶端輸出包含醫保費用和自費費用的支付提醒資訊；
所述將所述醫保支付卡資訊、交易資訊和收費端資訊發送至醫保系統，包括：在接收到支付用戶端回饋的確認付款指令時，透過調用醫保系統的結算介面，將所述醫保支付卡資訊、交易資訊和收費端資訊發送至所述醫保系統標識對應的醫保系統。
在一個實施例中，支付方與醫保支付卡的綁定關係在支付用戶端上進行配置，所述方法還包括：
支付用戶端確定醫保支付卡的卡主與支付方為同一用戶；對當前操作者進行身份驗證，若透過驗證判定當前操作者為所述用戶，則確定支付方和設備保障卡具有綁定關係。
根據本發明實施例的第二態樣，提供一種支付方法，所述方法包括：
接收交易支付請求，所述交易支付請求至少包括：支付方資訊、消費方與收費端的交易資訊、以及收費端資訊；
基於預設的支付方與醫保支付卡的綁定關係，獲取與所述支付方資訊對應的醫保支付卡資訊，將所述醫保支付卡資訊、交易資訊和收費端資訊發送至醫保系統，以供醫保系統依據所接收資訊對本次交易進行結算處理和醫保費用支付處理；
根據醫保系統回饋的處理結果執行向收費端支付自費費用的支付處理。
在一個實施例中，所述交易資訊中包括隱私加密資訊，所述隱私加密資訊是對交易過程中產生的指定類型的隱私資訊進行加密後的資訊、且該隱私資訊是醫保系統進行結算時所需的資訊。
在一個實施例中，所述交易支付請求還包括消費方資訊，所述將所述醫保支付卡資訊、交易資訊和所述收費端資訊發送至醫保系統之前，還包括：
依據所述支付方資訊和消費方資訊判定消費方與支付方為同一用戶。
在一個實施例中，所述交易支付請求還包括醫保系統標識，所述方法還包括：將攜帶有所述醫保支付卡資訊、交易資訊和收費端資訊的預結算請求發送至與所述醫保系統標識對應的醫保系統，並接收醫保系統回饋的本次交易的醫保費用和自費費用，向支付用戶端發送包含醫保費用和自費費用的支付提醒資訊；
所述將所述醫保支付卡資訊、交易資訊和收費端資訊發送至醫保系統，包括：在接收到支付用戶端回饋的確認付款指令時，將攜帶有所述醫保支付卡資訊、交易資訊和收費端資訊的結算請求發送至與所述醫保系統標識對應的醫保系統。
在一個實施例中，所述交易支付請求還包括醫保系統標識，所述方法還包括：透過調用醫保系統的預結算介面，將所述醫保支付卡資訊、交易資訊和收費端資訊發送至與所述醫保系統標識對應的醫保系統，並接收醫保系統回饋的本次交易的醫保費用和自費費用，向支付用戶端輸出包含醫保費用和自費費用的支付提醒資訊；
所述將所述醫保支付卡資訊、交易資訊和收費端資訊發送至醫保系統，包括：在接收到支付用戶端回饋的確認付款指令時，透過調用醫保系統的結算介面，將所述醫保支付卡資訊、交易資訊和收費端資訊發送至所述醫保系統標識對應的醫保系統。
在一個實施例中，所述方法還包括：
若基於支付方資訊以及預設的支付方與醫保支付卡的綁定關係，確定支付方未綁定醫保支付卡，輸出交易失敗的提醒資訊，或，輸出是否進行全自費支付的提醒資訊。
在一個實施例中，所述方法還包括：
若所述處理結果中指示本次交易不能使用醫保進行支付，輸出是否進行全自費支付的提醒資訊。
根據本發明實施例的第三態樣，提供一種支付裝置，所述裝置包括：
請求接收模組，用於：接收交易支付請求，所述交易支付請求至少包括：支付方資訊、消費方與收費端的交易資訊、以及收費端資訊；
資訊發送模組，用於：基於預設的支付方與醫保支付卡的綁定關係，獲取與所述支付方資訊對應的醫保支付卡資訊，將所述醫保支付卡資訊、交易資訊和收費端資訊發送至醫保系統，以供醫保系統依據所接收資訊對本次交易進行結算處理和醫保費用支付處理；
費用支付模組，用於：根據醫保系統回饋的處理結果執行向收費端支付自費費用的支付處理。
根據本發明實施例的第四態樣，提供一種電腦設備，包括記憶體、處理器及儲存在記憶體上並可在處理器上運行的電腦程式，其中，所述處理器執行所述程式時實現如下方法：
接收交易支付請求，所述交易支付請求至少包括：支付方資訊、消費方與收費端的交易資訊、以及收費端資訊；
基於預設的支付方與醫保支付卡的綁定關係，獲取與所述支付方資訊對應的醫保支付卡資訊，將所述醫保支付卡資訊、交易資訊和收費端資訊發送至醫保系統，以供醫保系統依據所接收資訊對本次交易進行結算處理和醫保費用支付處理；
根據醫保系統回饋的處理結果執行向收費端支付自費費用的支付處理。
本發明的實施例提供的技術方案可以包括以下有益效果：
本發明實施例透過支付伺服端和收費端和醫保系統的交互，在接收到交易支付請求時，基於預設的支付方與醫保支付卡的綁定關係，獲取與支付方資訊對應的醫保支付卡資訊，將醫保支付卡資訊、交易資訊和收費端資訊發送至醫保系統，以供醫保系統依據所接收資訊對本次交易進行結算處理和醫保費用支付處理，並根據醫保系統回饋的處理結果執行向收費端支付自費費用的支付處理，從而實現透過一次支付行為完成醫保費用和自費費用的混合支付，提高支付效率。
應當理解的是，以上的一般描述和後文的細節描述僅是示例性和解釋性的，並不能限制本發明。In order to overcome the problems in the related art, the present invention provides a payment method, device and device.
According to a first aspect of the embodiments of the present invention, there is provided a payment method, the method including:
The payment server receives a transaction payment request, and the transaction payment request includes at least: payment party information, consumer and toll terminal transaction information, and toll terminal information;
Based on the preset binding relationship between the payer and the medical insurance payment card, the payment server obtains the medical insurance payment card information corresponding to the payer information, and sends the medical insurance payment card information, transaction information and toll terminal information to the medical insurance system ；
The medical insurance system settles the transaction based on the received information, obtains the medical insurance fee and self-paid expenses of the transaction, executes the payment processing of the medical insurance fee to the toller based on the toller information, and returns the processing result to the payment server;
The payment server executes payment processing of paying the self-paid expenses to the tolling terminal according to the processing result.
In one embodiment, the method further includes: the charging terminal sends a transaction payment request to the payment server by invoking the payment interface of the payment server, and the transaction payment request also carries a medical insurance payment identifier used to indicate payment by medical insurance .
In one embodiment, the transaction payment request further includes a medical insurance system identification, and the method further includes: the payment server sends a pre-settlement request carrying the medical insurance payment card information, transaction information, and toll-end information to the company The medical insurance system identifies the corresponding medical insurance system, and receives the medical insurance costs and self-paid expenses of this transaction as feedback from the medical insurance system, and sends payment reminders including medical insurance costs and self-paid expenses to the payment client;
The sending of the medical insurance payment card information, transaction information, and toll-end information to the medical insurance system includes: when receiving a confirmation payment instruction returned by the payment client, carrying the medical insurance payment card information, transaction information, and charging The settlement request of the terminal information is sent to the medical insurance system corresponding to the medical insurance system identifier.
In one embodiment, the transaction payment request further includes a medical insurance system identification, and the method further includes: the payment server sends the medical insurance payment card information, transaction information, and toll terminal information by calling the pre-settlement interface of the medical insurance system To the medical insurance system corresponding to the medical insurance system identifier, and receive the medical insurance cost and self-paid expenses of this transaction as feedback from the medical insurance system, and output the payment reminder information including the medical insurance cost and self-paid expenses to the payment client;
The sending of the medical insurance payment card information, transaction information, and toll terminal information to the medical insurance system includes: upon receiving the payment confirmation instruction returned by the payment client, by calling the settlement interface of the medical insurance system to transfer the medical insurance payment card The information, transaction information, and toll terminal information are sent to the medical insurance system corresponding to the medical insurance system identifier.
In an embodiment, the binding relationship between the payer and the medical insurance payment card is configured on the payment client, and the method further includes:
The payment user terminal determines that the card owner and the payer of the medical insurance payment card are the same user; the current operator is authenticated, and if the current operator is determined to be the user through the verification, it is determined that the payer and the equipment guarantee card have a binding relationship.
According to a second aspect of the embodiments of the present invention, there is provided a payment method, the method including:
Receiving a transaction payment request, the transaction payment request including at least: payment party information, consumer and toll terminal transaction information, and toll terminal information;
Based on the preset binding relationship between the payer and the medical insurance payment card, obtain the medical insurance payment card information corresponding to the payer information, and send the medical insurance payment card information, transaction information and toll terminal information to the medical insurance system for The medical insurance system performs settlement processing and medical insurance fee payment processing for this transaction based on the received information;
According to the processing results returned by the medical insurance system, the payment processing of paying out-of-pocket expenses to the tolling terminal is executed.
In one embodiment, the transaction information includes privacy encrypted information, the privacy encrypted information is information obtained by encrypting the specified type of privacy information generated during the transaction, and the privacy information is used by the medical insurance system for settlement. Required information.
In one embodiment, the transaction payment request further includes consumer information, and before the medical insurance payment card information, transaction information, and toll terminal information are sent to the medical insurance system, it further includes:
Based on the payer information and the consumer information, it is determined that the consumer and the payer are the same user.
In one embodiment, the transaction payment request further includes a medical insurance system identification, and the method further includes: sending a pre-settlement request carrying the medical insurance payment card information, transaction information, and toll terminal information to the medical insurance system Identify the corresponding medical insurance system, receive the medical insurance cost and self-paid expenses of this transaction as feedback from the medical insurance system, and send the payment reminder information including medical insurance expenses and self-paid expenses to the payment client;
The sending of the medical insurance payment card information, transaction information, and toll-end information to the medical insurance system includes: when receiving a confirmation payment instruction returned by the payment client, carrying the medical insurance payment card information, transaction information, and charging The settlement request of the terminal information is sent to the medical insurance system corresponding to the medical insurance system identifier.
In one embodiment, the transaction payment request further includes a medical insurance system identifier, and the method further includes: sending the medical insurance payment card information, transaction information, and toll terminal information to the company by calling the pre-settlement interface of the medical insurance system. The medical insurance system identifies the corresponding medical insurance system, and receives the medical insurance cost and self-paid expenses of this transaction as feedback from the medical insurance system, and outputs the payment reminder information including the medical insurance expenses and self-paid expenses to the payment client;
The sending of the medical insurance payment card information, transaction information, and toll terminal information to the medical insurance system includes: upon receiving the payment confirmation instruction returned by the payment client, by calling the settlement interface of the medical insurance system to transfer the medical insurance payment card The information, transaction information, and toll terminal information are sent to the medical insurance system corresponding to the medical insurance system identifier.
In an embodiment, the method further includes:
If based on the information of the payer and the preset binding relationship between the payer and the medical insurance payment card, it is determined that the payer is not bound to the medical insurance payment card, and the reminder information of transaction failure is output, or the reminder information of whether the payment is fully paid is output.
In an embodiment, the method further includes:
If the processing result indicates that the medical insurance cannot be used for payment in this transaction, output reminder information about whether to make full self-payment.
According to a third aspect of the embodiments of the present invention, there is provided a payment device, the device including:
The request receiving module is used to receive a transaction payment request, the transaction payment request including at least: payment party information, consumer and toll terminal transaction information, and toll terminal information;
The information sending module is used to: obtain the medical insurance payment card information corresponding to the payer information based on the preset binding relationship between the payer and the medical insurance payment card, and transfer the medical insurance payment card information, transaction information, and charging terminal The information is sent to the medical insurance system for the medical insurance system to settle the transaction and process the medical insurance fee payment based on the received information;
The fee payment module is used to perform payment processing of paying self-paid expenses to the toll terminal according to the processing results returned by the medical insurance system.
According to a fourth aspect of the embodiments of the present invention, there is provided a computer device, including a memory, a processor, and a computer program stored on the memory and running on the processor, wherein the processor executes the program when the program is executed. Implement the following methods:
Receiving a transaction payment request, the transaction payment request including at least: payment party information, consumer and toll terminal transaction information, and toll terminal information;
Based on the preset binding relationship between the payer and the medical insurance payment card, obtain the medical insurance payment card information corresponding to the payer information, and send the medical insurance payment card information, transaction information and toll terminal information to the medical insurance system for The medical insurance system performs settlement processing and medical insurance fee payment processing for this transaction based on the received information;
According to the processing results returned by the medical insurance system, the payment processing of paying out-of-pocket expenses to the tolling terminal is executed.
The technical solutions provided by the embodiments of the present invention may include the following beneficial effects:
The embodiment of the present invention obtains the medical insurance payment card corresponding to the payer information based on the preset binding relationship between the payer and the medical insurance payment card when a transaction payment request is received through the interaction between the payment server and the toll end and the medical insurance system Information, the medical insurance payment card information, transaction information and toll terminal information are sent to the medical insurance system for the medical insurance system to perform settlement processing and medical insurance fee payment processing for this transaction based on the received information, and execute the processing results according to the processing results returned by the medical insurance system The payment processing of paying out-of-pocket expenses by the toll-end, so as to realize the mixed payment of medical insurance expenses and out-of-pocket expenses through one payment behavior, and improve payment efficiency.
It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present invention.
這裡將詳細地對示例性實施例進行說明，其示例表示在圖式中。下面的描述涉及圖式時，除非另有表示，不同圖式中的相同數字表示相同或相似的要素。以下示例性實施例中所描述的實施方式並不代表與本發明相一致的所有實施方式。相反，它們僅是與如所附申請專利範圍中所詳述的、本發明的一些態樣相一致的裝置和方法的例子。
在本發明使用的術語是僅僅出於描述特定實施例的目的，而非旨在限制本發明。在本發明和所附申請專利範圍中所使用的單數形式的“一種”、“所述”和“該”也旨在包括多數形式，除非上下文清楚地表示其他含義。還應當理解，本文中使用的術語“和/或”是指並包含一個或多個相關聯的列出專案的任何或所有可能組合。
應當理解，儘管在本發明可能採用術語第一、第二、第三等來描述各種資訊，但這些資訊不應限於這些術語。這些術語僅用來將同一類型的資訊彼此區分開。例如，在不脫離本發明範圍的情況下，第一資訊也可以被稱為第二資訊，類似地，第二資訊也可以被稱為第一資訊。取決於語境，如在此所使用的詞語“如果”可以被解釋成為“在……時”或“當……時”或“回應於確定”。
在某些應用場景中，醫保帳戶可以分為醫保個人帳戶和醫保統籌帳戶。醫保個人帳戶的全稱為基本醫療保險個人帳戶，簡稱個人帳戶。個人帳戶主要用於記錄、儲存個人帳戶資金，並按規定用於個人醫療消費。個人帳戶通常被用來支付參保人的特定醫療費用，包括定點醫療機構發生的門診費用、定點零售藥店的購藥支出、定點醫院住院、門診特定項目等基本醫療費用中。甚至個人帳戶還可以用於購買其他醫療保險等。醫保統籌帳戶基金屬於全體參保人員，由社會保險經辦機構集中管理，統一使用。主要用於支付參保人員發生的醫藥費、手術費、護理費、基本檢查費等。不管是個人帳戶還是統籌帳戶，在使用過程中都有限制條件，當一筆費用產生時，能否利用個人帳戶或統籌帳戶進行支付，可以由相應的醫保系統進行判斷和支付。而針對不能使用醫保進行支付的自費費用，消費方採用其他支付方式支付自費費用。以去醫院就診為例，用戶在支付醫療費用時，需要先出示社保卡，由收費人員利用醫保系統計算醫保費用和自費費用。針對醫保費用，可以由醫保系統直接劃扣。針對自費費用，由用戶採用其他支付方式進行支付。可見，針對一筆交易需要透過兩種支付方式進行支付，操作繁瑣，支付效率低。
鑒於此，本發明實施例提供一種支付方案，可以透過一次支付行為完成醫保費用和自費費用的混合支付。以下結合圖式對本發明支付方案的實施例進行示例說明。
首先從交互的角度對支付方案進行示例說明。如圖1所示，是本發明根據一示例性實施例示出的一種支付方法的應用場景圖。在該應用場景中，可以包括支付伺服端和醫保系統，進一步的，還可以包括收費端和用戶端。在一個例子中，用戶端可以安裝有用於與收費端和支付伺服端進行交互的用戶端，例如，可以是支付用戶端。支付伺服端可以是與支付用戶端相對應的服務端。例如，支付用戶端可以是支付寶，則支付伺服端可以是與支付寶對應的支付平臺。醫保系統可以是用於進行結算處理和醫保費用支付處理的系統。在醫保系統中可以配置有判斷待支付費用是否屬於醫保費用或是否包含醫保費用的醫保報銷策略。例如，如果診間繳費，醫保系統可以判斷該筆交易對應的掛號費是否滿足醫保報銷策略的條件，如果掛號費屬於專家號，則判定不滿足條件，不允許診間使用醫保繳費。具體策略由醫保系統而定，在此不做限制。結算處理可以是利用醫保報銷策略確定待支付費用中的醫保費用和自費費用。收費端可以是交易發生時收取費用的一端，也可以理解為提供服務的一端。收費端可以是醫院、可利用社保卡進行消費的產品的銷售端(諸如，藥物銷售端，醫療保險銷售端)等。相應的，消費方可以是交易發生時享受服務的一方，消費方可以是就診方、藥物購買方、醫療保險購買方等。
如圖2所示，是本發明根據一示例性實施例示出的一種支付方法的流程圖，所述方法包括：
在步驟202中，支付伺服端接收交易支付請求，所述交易支付請求至少包括：支付方資訊、消費方與收費端的交易資訊、以及收費端資訊。
在步驟204中，支付伺服端基於預設的支付方與醫保支付卡的綁定關係，獲取與所述支付方資訊對應的醫保支付卡資訊，將所述醫保支付卡資訊、交易資訊和收費端資訊發送至醫保系統。
其中，醫保支付卡可以是社保卡、醫保卡等可以用於進行醫療相關費用保險的卡。
在步驟206中，醫保系統依據所接收資訊對本次交易進行結算，獲得本次交易的醫保費用和自費費用，基於所述收費端資訊執行向收費端支付醫保費用的支付處理，並向支付伺服端回饋處理結果；
在步驟208中，支付伺服端根據所述處理結果執行向收費端支付自費費用的支付處理。
關於交易支付請求，可以是針對消費方和收費端所發生的交易進行費用支付的請求。交易支付請求可以是由收費端主動向支付伺服端發起的，也可以由其他端代收費端向支付伺服端發起的。
舉例說明，在一種應用場景中，支付方可以利用支付用戶端展示付款碼，收費端透過掃描付款碼獲得支付方資訊後，可以向支付伺服端發送交易支付請求。在這種應用場景中，可以在收費端鋪設當面付機具，支援醫保消費者能進行醫保當面付。
在另一種應用場景中，可以針對人社局配置醫保用戶端和醫保服務端。醫保用戶端用於提供醫保線上支付伺服。支付方可以透過醫保用戶端展示攜帶醫保系統資訊的圖形碼(如二維條碼)，收費端透過掃描圖形碼獲得醫保系統資訊後，可以向對應的醫保服務端發送交易相關資訊，醫保服務端向醫保用戶端推送待繳費明細，以便在醫保用戶端展示待繳費明細的頁面。醫保用戶端監聽到確認繳費事件後，可以直接向支付伺服端發送交易支付請求，或者透過醫保服務端向支付伺服端發送交易支付請求。又或者，醫保用戶端監聽到確認繳費事件後，通知收費端，由收費端向支付伺服端發送交易支付請求。
針對由收費端向支付伺服端發送交易支付請求的情況，在一個實施例中，支付伺服端可以為收費端提供支付介面，當該實施例應用在當面付場景中時，支付介面可以是當面付介面。所述方法還包括：收費端透過調用支付伺服端的支付介面，向支付伺服端發送交易支付請求。
其中，所述交易支付請求中還攜帶有用於表示利用醫保進行支付的醫保支付標識。支付伺服端可以根據醫保支付標識判定本次交易的費用期望用醫保進行支付。收費端還可以透過調用支付伺服端的支付介面，向支付伺服端發送攜帶非醫保支付標識的交易支付請求，非醫保支付標識用於表示不利用醫保進行支付，從而，可以實現普通支付和醫保支付可以共用同一個支付介面，節省開發成本。由於支付伺服端為消費端提供支付介面，雙方還可以簽一個銷售方案。
在另一個實施例中，針對普通支付和醫保支付提供不同的支付介面，例如，利用支付伺服端提供的醫保支付介面進行醫保支付的相關操作；利用支付伺服端提供的普通支付介面進行非醫保支付的相關操作。可見，該實施例透過醫保支付介面和非醫保支付介面區分當前支付屬於醫保支付還是普通支付，無需利用參數進行區分。
交易支付請求中至少包括支付方資訊、消費方與收費端的交易資訊、以及收費端資訊。
關於消費方和支付方，消費方可以是消費收費端所提供服務的一方，如就診方。消費方資訊可以是消費方身份資訊，例如，姓名、證件類型、證件號等。支付方是對交易所產生費用進行支付的一方。支付方資訊可以是支付方身份資訊，例如，支付帳號。以支付用戶端提供付款碼為例，收費端可以透過掃描付款碼而獲得支付帳號。
消費方和支付方可能是同一個用戶，也可能是不同用戶。為了避免出現套保的現象，實現對套保的多重防範，在一個實施例中，所述交易支付請求中還包括消費方資訊，在將所述醫保支付卡資訊、交易資訊和所述收費端資訊發送至醫保系統之前，還包括：依據所述支付方資訊和消費方資訊判定消費方與支付方為同一用戶。例如，可以根據支付方資訊中表示用戶身份的資訊以及消費方中表示用戶身份的資訊是否一致，來判斷消費方與支付方為同一用戶。消費方與支付方為同一用戶時，才將醫保支付卡資訊、交易資訊和收費端資訊發送至醫保系統。若消費方與支付方不是同一用戶，可以輸出支付失敗的提醒資訊。所謂輸出，可以是向收費端輸出，也可以是向支付用戶端輸出。提醒資訊可以是錯誤碼、失敗詳情等資訊。
可見，該實施例增加了對支付方和消費方是否為同一用戶的判斷，從而避免出現套保的現象。
交易資訊是消費方與收費端發生交易時所產生的資訊。以應用在就診的場景中為例，交易資訊可以包括：就診人掛號資訊、病歷、門診費用清單、診間支付的預結算ID等資訊。實際應用中，消費方可能並不期望某部分交易資訊被洩露，因此，交易資訊中可以包括隱私加密資訊，該隱私加密資訊還可以稱為醫保透傳結構體。所述隱私加密資訊是對交易過程中產生的指定類型的隱私資訊進行加密後的資訊、且該隱私資訊是醫保系統進行結算時所需的資訊。收費端與醫保系統可以事先約定所需加密的隱私資訊的類型，以及加密演算法。結算時所需的資訊，可以包括用來判斷交易費用是否為醫保費用的相關資訊。而交易資訊中的某些資訊無需加密，例如，業務流水號、業務單據號等，這類交易資訊可以直接攜帶在交易支付請求中。
收費端可以是醫院、可利用醫保支付卡進行消費的產品的銷售端(諸如，藥物銷售端，醫療保險銷售端)等。收費端資訊可以是收費端的標識，例如，可以是機構名稱、機構編碼等。
在獲得交易支付請求後，可以基於支付方資訊以及預設的支付方與醫保支付卡的綁定關係，判斷支付方資訊所指示的支付方是否綁定醫保支付卡，若支付方綁定醫保支付卡，則獲取與支付方資訊對應的醫保支付卡資訊。若支付方未綁定醫保支付卡，則輸出交易失敗的提醒資訊，例如，向收費端和支付用戶端發送交易失敗的提醒資訊。或者，若支付方未綁定醫保支付卡，輸出是否進行全自費支付的提醒資訊。例如，向支付用戶端發送進行全自費支付的提醒資訊，以供用戶選擇是否繼續支付。
在醫保系統中往往會對支付方和消費方進行判斷，以確保是否為同一用戶。然而實際應用中，可能因為消費方的身份作假出現套保的現象，在一個實施例中，還可以限制綁定關係中醫保支付卡的卡主與支付方為同一用戶，從而進一步避免出現套保的情況。
為了提高用戶可操作性，還提供一種支付方與醫保支付卡的綁定服務。在一個實施例中，為了節約研發成本，以支付用戶端與付費端和支付伺服端進行交互為例，支付方與醫保支付卡的綁定關係可以在支付用戶端上進行配置，並為了確保本次綁定為合法綁定，還可以對當前操作者的身份進行驗證，以提高綁定關係的有效性。具體的，在支付用戶端可以執行如下步驟：
確定醫保支付卡的卡主與支付方為同一用戶；
對當前操作者進行身份驗證，若透過驗證判定當前操作者為所述用戶，則確定支付方和設備保障卡具有綁定關係。
其中，可以將醫保支付卡的卡主身份資訊與支付方資訊進行匹配，從而判斷醫保支付卡的卡主與支付方是否為同一用戶。關於身份驗證，可以包括對當前操作者的生物特徵資訊進行驗證、對輸入的個人隱私資訊進行驗證、對輸入的手機驗證碼進行驗證等中的一種或多種。對當前操作者的生物特徵資訊進行驗證可以是人臉識別、指紋識別等。對輸入的個人隱私資訊進行驗證可以是判斷輸入的個人隱私資訊與所述用戶(支付方)的標準個人隱私資訊是否匹配。個人隱私資訊可以是身份證、手機號碼、銀行卡號等。進一步的，在透過驗證判定當前操作者為所述用戶時，還可以將支付方和設備保障卡具有綁定關係發送至支付伺服端，並獲取該用戶的醫保支付卡資訊，並儲存支付方資訊與醫保支付卡資訊的映射關係，以供用戶查詢醫保支付卡資訊。如果醫保支付卡為實體卡，支付方與醫保支付卡的綁定服務，也可以作為電子醫保支付卡的產生服務。
以醫保支付卡為社保卡為例，如圖3所示，圖3是本發明根據一示例性實施例示出的一種電子社保卡產生過程示意圖。在支付用戶端中增加電子社保卡的產生服務，支付用戶端可以安裝在手機、平板等用戶端上。用戶可以透過支付用戶端提供的電子社保卡開通頁面開通電子設備卡。為了確保當前操作者、社保卡的卡主以及支付方為同一用戶，可以將社保卡資訊與支付方資訊進行匹配，以及對當前操作者進行身份驗證。該示例採用人臉識別、活體檢測等手段對當前操作者進行身份驗證，在判定採集的人物圖像為活體、且與預存用戶圖像相匹配，則獲取該用戶的設備卡資訊，建立支付方與社保卡的映射關係，並產生電子社保卡。
結合交易支付請求還包括消費方資訊的情況，在判定支付方綁定有醫保支付卡、且依據支付方資訊和消費方資訊判定消費方與支付方為同一用戶時，將醫保支付卡資訊、交易資訊和收費端資訊發送至醫保系統。
關於如何發送至醫保系統，若醫保系統只有一個，則直接將醫保支付卡資訊、交易資訊和收費端資訊發送至醫保系統。而某些應用場景中，醫保系統也可能有多個，例如，每個區域可以配置相應的醫保系統。區域的劃分方式可以是按地級市進行劃分等。相應的，為了能對醫保系統進行區分，交易支付請求還可以攜帶醫保系統標識，例如，醫保系統標識可以是醫保系統方的結構名稱、機構編碼等。利用醫保系統標識來區分不同醫保系統。步驟204中的將所述醫保支付卡資訊、交易資訊和所述收費端資訊發送至醫保系統，可以是，將醫保支付卡資訊、交易資訊和收費端資訊發送至與醫保系統標識對應的醫保系統。
在一個實施例中，支付伺服端可以將醫保支付卡資訊、交易資訊和收費端資訊發送至醫保系統，由醫保系統直接進行結算處理和醫保費用的支付處理。例如，將攜帶有醫保支付卡資訊和所述交易資訊的結算請求發送至醫保系統，醫保系統依據所接收資訊對本次交易進行結算，獲得本次交易的醫保費用和自費費用，基於收費端資訊執行向收費端支付醫保費用的支付處理，並向支付伺服端回饋處理結果。
該實施例由醫保系統直接進行結算處理和醫保費用的支付處理，可以提高支付效率。
關於醫保系統執行醫保費用的支付處理，以醫保支付卡為社保卡為例，醫保系統執行醫保費用的支付處理可以是從醫保統籌帳戶或醫保個人帳戶劃扣相應費用到收費端，具體處理手段在此不一一贅述。具體劃扣醫保統籌帳戶還是醫保個人帳戶，可以由醫保報銷策略而定。在一個實施例中，針對利用醫保個人帳戶支付醫保費用的情況，還可以透過支付用戶端提醒用戶選擇是否利用醫保個人帳戶支付醫保費用，進而醫保系統根據選擇結果確定是否利用醫保個人帳戶支付醫保費用。
在某些應用場景下，用戶可能期望根據結算結果來確定是否使用醫保支付，鑒於此，在另一個實施例中，還可以先透過醫保系統進行預結算，並將預結算結果通知支付伺服端，並在支付方同意支付時，才進行醫保系統的支付處理和支付伺服端的支付處理，提高用戶可操作性，以及提高用戶體驗。例如，支付伺服端在收到預結算結果後，可以向支付用戶端發送包含醫保費用和自費費用的支付提醒資訊，在支付用戶端展示該支付提醒資訊，基於用戶的操作可以向支付伺服端回饋確認付款指令。
關於如何區分預結算和結算兩次任務，在一個例子中，預結算和結算可以透過不同請求進行區分。例如，利用預結算請求表示期望醫保系統進行預結算處理，結算請求表示期望醫保系統進行結算處理，而預結算請求和結算請求可以透過不同參數進行區分。例如，包括預設的預結算標識的請求為預結算請求，包括預設的結算標識的請求為結算請求。相應的，所述交易支付請求還包括醫保系統標識，所述方法還包括：支付伺服端將攜帶有所述醫保支付卡資訊、交易資訊和收費端資訊的預結算請求發送至與所述醫保系統標識對應的醫保系統，並接收醫保系統回饋的本次交易的醫保費用和自費費用，向支付用戶端發送包含醫保費用和自費費用的支付提醒資訊；
所述將所述醫保支付卡資訊、交易資訊和收費端資訊發送至醫保系統，包括：在接收到支付用戶端回饋的確認付款指令時，將攜帶有所述醫保支付卡資訊、交易資訊和收費端資訊的結算請求發送至與所述醫保系統標識對應的醫保系統。
在該實施例中，利用預結算請求表示期望醫保系統進行預結算處理，利用結算請求表示期望醫保系統進行結算處理，可以實現共用相同介面實現醫保系統和支付伺服端的交互。
在另一個例子中，預結算和結算可以透過醫保系統提供的不同介面進行區分。例如，透過預結算介面傳輸的資料，指示期望醫保系統進行預結算處理，利用結算介面傳輸的資料，指示期望醫保系統進行結算處理。例如，所述交易支付請求還包括醫保系統標識，所述方法還包括：支付伺服端透過調用醫保系統的預結算介面，將所述醫保支付卡資訊、交易資訊和收費端資訊發送至與所述醫保系統標識對應的醫保系統，並接收醫保系統回饋的本次交易的醫保費用和自費費用，向支付用戶端輸出包含醫保費用和自費費用的支付提醒資訊；
所述將所述醫保支付卡資訊、交易資訊和收費端資訊發送至醫保系統，包括：在接收到支付用戶端回饋的確認付款指令時，透過調用醫保系統的結算介面，將所述醫保支付卡資訊、交易資訊和收費端資訊發送至所述醫保系統標識對應的醫保系統。
醫保系統依據醫保支付卡資訊、交易資訊和收費端資訊對本次交易進行結算，獲得本次交易的醫保費用和自費費用，其中，具體結算策略由醫保系統而定，在此不做限制。醫保費用不為0的情況下，可以扣除醫保費用，並向支付伺服端返回支付結果和明細。如果醫保支付成功，可以決定是否執行向收費端支付自費費用的支付處理。支付處理是控制支付方向收費端支付自費費用的處理，具體處理手段與相關技術中的支付手段相似，在此不一一贅述。在一個實施例中，可以獲取支付平臺設置的免密碼額度，在自費費用小於免密碼額度時，可以直接執行向收費端支付自費費用的支付處理；如果自費費用大於免密碼額度時，可以透過收銀台頁面提醒用戶完成支付。在另一個實施例中，社保局可能認為直接支付安全性低，因此，可以要求所有金額都需要用戶確認後才能執行支付處理，則無需判斷自費費用的大小，直接輸出是否對自費費用進行支付的支付提醒資訊，由用戶決定是否繼續進行支付。
此外，在一個實施例中，若所述處理結果中指示本次交易不能使用醫保進行支付，輸出是否進行全自費支付的提醒資訊。可見，在確保無法使用醫保時，直接進入全自費支付的處理流程，無需用戶退出當前訂單，可以提高支付效率。
相應的，本發明還從支付伺服端的角度對支付方法進行示例說明，如圖4所示，是本發明根據一示例性實施例示出的另一種支付方法的流程圖，所述方法可以應用於支付伺服端，所述方法包括：
在步驟402中，接收交易支付請求，所述交易支付請求至少包括：支付方資訊、消費方與收費端的交易資訊、以及收費端資訊；
在步驟404中，基於預設的支付方與醫保支付卡的綁定關係，獲取與所述支付方資訊對應的醫保支付卡資訊，將所述醫保支付卡資訊、交易資訊和收費端資訊發送至醫保系統，以供醫保系統依據所接收資訊對本次交易進行結算處理和醫保費用支付處理；
在步驟406中，根據醫保系統回饋的處理結果執行向收費端支付自費費用的支付處理。
可以理解的是，圖4與圖2中相關技術相同，在此不一一贅述。
在一個實施例中，所述交易資訊中包括隱私加密資訊，所述隱私加密資訊是對交易過程中產生的指定類型的隱私資訊進行加密後的資訊、且該隱私資訊是醫保系統進行結算時所需的資訊。
在一個實施例中，所述交易支付請求還包括消費方資訊，所述將所述醫保支付卡資訊、交易資訊和所述收費端資訊發送至醫保系統之前，還包括：依據所述支付方資訊和消費方資訊判定消費方與支付方為同一用戶。
在一個實施例中，所述交易支付請求還包括醫保系統標識，所述方法還包括：將攜帶有所述醫保支付卡資訊、交易資訊和收費端資訊的預結算請求發送至與所述醫保系統標識對應的醫保系統，並接收醫保系統回饋的本次交易的醫保費用和自費費用，向支付用戶端發送包含醫保費用和自費費用的支付提醒資訊。所述將所述醫保支付卡資訊、交易資訊和收費端資訊發送至醫保系統，包括：在接收到支付用戶端回饋的確認付款指令時，將攜帶有所述醫保支付卡資訊、交易資訊和收費端資訊的結算請求發送至與所述醫保系統標識對應的醫保系統。
在一個實施例中，所述交易支付請求還包括醫保系統標識，所述方法還包括：透過調用醫保系統的預結算介面，將所述醫保支付卡資訊、交易資訊和收費端資訊發送至與所述醫保系統標識對應的醫保系統，並接收醫保系統回饋的本次交易的醫保費用和自費費用，向支付用戶端輸出包含醫保費用和自費費用的支付提醒資訊。所述將所述醫保支付卡資訊、交易資訊和收費端資訊發送至醫保系統，包括：在接收到支付用戶端回饋的確認付款指令時，透過調用醫保系統的結算介面，將所述醫保支付卡資訊、交易資訊和收費端資訊發送至所述醫保系統標識對應的醫保系統。
在一個實施例中，所述方法還包括：若基於支付方資訊以及預設的支付方與醫保支付卡的綁定關係，確定支付方未綁定醫保支付卡，輸出交易失敗的提醒資訊，或，輸出是否進行全自費支付的提醒資訊。
在一個實施例中，所述方法還包括：若所述處理結果中指示本次交易不能使用醫保進行支付，輸出是否進行全自費支付的提醒資訊。
以上實施方式中的各種技術特徵可以任意進行組合，只要特徵之間的組合不存在衝突或矛盾，但是限於篇幅，未進行一一描述，因此上述實施方式中的各種技術特徵的任意進行組合也屬於本發明公開的範圍。
以下以其中一種組合進行示例說明，其中，以醫保支付卡為社保卡為例。
如圖5A所示，是本發明根據一示例性實施例示出的另一種支付方法的流程圖，該方法涉及支付用戶端、支付伺服端、收費端和醫保系統。所述方法包括：
支付用戶端向收費端提供付款碼(步驟501)。
收費端獲取支付用戶端的付款碼，基於付款碼獲得支付方資訊(步驟502)，向支付伺服端發送交易支付請求(步驟503)。其中，交易支付請求可以包括：支付方資訊、消費方與收費端的交易資訊、收費端資訊、醫保系統標識、以及用於表示利用醫保進行支付的醫保支付標識。
支付伺服端若基於預設的支付方與社保卡的綁定關係，判定支付方綁定有社保卡，且依據支付方資訊和消費方資訊判定消費方與支付方為同一用戶時，獲取與支付方資訊對應的社保卡資訊(步驟504)，並透過調用醫保系統的預結算介面，將社保卡資訊、交易資訊和收費端資訊發送至與醫保系統標識對應的醫保系統(步驟505)。另外，若支付方未綁定社保卡，或者消費方與支付方不為同一用戶時，向收款端和支付用戶端發送交易失敗的提醒資訊。
醫保系統依據所接收資訊對本次交易進行結算，獲得本次交易的醫保費用和自費費用，並將醫保費用和自費費用回饋至支付伺服端(步驟506)。
支付伺服端向支付用戶端輸出包含醫保費用和自費費用的支付提醒資訊(步驟507)，並在接收到支付用戶端回饋的確認付款指令時，透過調用醫保系統的結算介面，將社保卡資訊、交易資訊和收費端資訊發送至與醫保系統標識對應的醫保系統(步驟508)。
醫保系統依據所接收資訊對本次交易進行結算處理和醫保費用支付處理，並向支付伺服端回饋處理結果(步驟509)。
在支付伺服端，若根據處理結果確定醫保支付成功，則執行向收費端支付自費費用的支付處理(步驟510)。
相應的，若自費費用支付成功時，支付伺服端向支付用戶端返回收費端訂單支付結果和醫保支付結果。同時，還可以在支付用戶端支付成功頁顯示本次訂單的總金額、自費金額、醫保金額，還可以展示優惠折扣金額(如有優惠的情況下，如沒有優惠不用顯示)等。若自費費用支付失敗，則調用醫保系統的退款介面，通知醫保系統進行退款操作，並通知支付用戶端和收費端付款失敗。
如圖5B所示，是本發明根據一示例性實施例示出的另一種支付方法的應用場景圖。如圖5C所示，是本發明根據一示例性實施例示出的一種支付用戶端頁面示意圖。該應用場景中，可以在原有的支付用戶端中增加綁定服務以及醫保支付伺服。用戶透過點擊電子社保卡頁面的“去刷碼”按鈕，即可進入包括付款碼的頁面。在其他實施例中，也可以透過支付用戶端首頁中的付款碼按鈕，進入包括付款碼的頁面。掃碼台掃描付款碼，並將掃描獲得的資訊傳輸至收費端。收費端獲取到付款碼後可以調用支付介面，傳入付款條碼、指示是否醫保支付的標識、就診人身份資訊(包括姓名、證件類型、證件號)，醫院機構名稱、醫院機構編碼、待進行醫保結算的機構名稱和編碼、業務流水號、業務單據號、醫保透傳結構體(主要是用戶的掛號資訊或者診間支付的預結算ID等資訊)。支付伺服端判斷該用戶是否綁定社保卡，若沒有綁定社保卡，則返回交易失敗，同時給出對應的錯誤碼。若已經綁定社保卡，則判斷就診人身份資訊是否和支付用戶端實名資訊一致，如果一致則進入醫保支付交易建立步驟。如果不一致，則返回交易失敗，同時給出對應的錯誤碼。關於創建醫保支付交易，支付伺服端調用醫保系統的預結算介面，將機構編碼、醫保透傳結構體(掛號明細資訊、診間預結算ID)等資訊發送給醫保系統做預結算。醫保系統進行預結算，返回給支付伺服端所需醫保支付金額和自費支付金額。預結算完成後，支付伺服端調用醫保系統的結算介面，將機構編碼、醫保透傳結構體(掛號明細清單或診間明細ID)等資訊發送給醫保系統做結算。醫保系統進行結算，扣除醫保帳戶金額，向支付伺服端返回醫保支付結果和明細。如果醫保支付成功，則進行自費金額支付，啟動協議進行支付代扣。當面付的額度按照整個訂單額度來判斷，若超過額度則按照當面付的規則跳出收銀台完成支付。如果自費支付成功，則訂單支付成功，返回醫院系統訂單支付結果和醫保支付結果。同時在支付用戶端支付成功頁顯示本次訂單的總金額、自費金額、醫保金額、優惠折扣金額(如有優惠的情況下，如沒有優惠不用顯示)等資訊。
與前述支付方法的實施例相對應，本發明還提供了支付裝置及其所應用的電子設備的實施例。
本發明支付裝置的實施例可以應用在電腦設備。裝置實施例可以透過軟體實現，也可以透過硬體或者軟硬體結合的方式實現。以軟體實現為例，作為一個邏輯意義上的裝置，是透過其所在電腦設備的處理器將非揮發性記憶體中對應的電腦程式指令讀取到記憶體中運行形成的。從硬體層面而言，如圖6所示，為本發明支付裝置所在電腦設備的一種硬體結構圖，除了圖6所示的處理器610、網路介面620、記憶體630、以及非揮發性記憶體640之外，實施例中支付裝置631所在的電腦設備通常根據該設備的實際功能，還可以包括其他硬體，對此不再贅述。
如圖7所示，是本發明根據一示例性實施例示出的一種支付裝置的方塊圖，所述裝置包括：
請求接收模組72，用於：接收交易支付請求，所述交易支付請求至少包括：支付方資訊、消費方與收費端的交易資訊、以及收費端資訊；
資訊發送模組74，用於：基於預設的支付方與醫保支付卡的綁定關係，獲取與所述支付方資訊對應的醫保支付卡資訊，將所述醫保支付卡資訊、交易資訊和收費端資訊發送至醫保系統，以供醫保系統依據所接收資訊對本次交易進行結算處理和醫保費用支付處理；
費用支付模組76，用於：根據醫保系統回饋的處理結果執行向收費端支付自費費用的支付處理。
在一個實施例中，所述交易資訊中包括隱私加密資訊，所述隱私加密資訊是對交易過程中產生的指定類型的隱私資訊進行加密後的資訊、且該隱私資訊是醫保系統進行結算時所需的資訊。
在一個實施例中，所述交易支付請求還包括消費方資訊，所述資訊發送模組還用於：將所述醫保支付卡資訊、交易資訊和所述收費端資訊發送至醫保系統之前，依據所述支付方資訊和消費方資訊判定消費方與支付方為同一用戶。
在一個實施例中，所述交易支付請求還包括醫保系統標識，所述資訊發送模組74具體用於：
將攜帶有所述醫保支付卡資訊、交易資訊和收費端資訊的預結算請求發送至與所述醫保系統標識對應的醫保系統，並接收醫保系統回饋的本次交易的醫保費用和自費費用，向支付用戶端發送包含醫保費用和自費費用的支付提醒資訊；
在接收到支付用戶端回饋的確認付款指令時，將攜帶有所述醫保支付卡資訊、交易資訊和收費端資訊的結算請求發送至與所述醫保系統標識對應的醫保系統。
在一個實施例中，所述交易支付請求還包括醫保系統標識，所述資訊發送模組74具體用於：
透過調用醫保系統的預結算介面，將所述醫保支付卡資訊、交易資訊和收費端資訊發送至與所述醫保系統標識對應的醫保系統，並接收醫保系統回饋的本次交易的醫保費用和自費費用，向支付用戶端輸出包含醫保費用和自費費用的支付提醒資訊；
在接收到支付用戶端回饋的確認付款指令時，透過調用醫保系統的結算介面，將所述醫保支付卡資訊、交易資訊和收費端資訊發送至所述醫保系統標識對應的醫保系統。
在一個實施例中，所述資訊發送模組74還用於：
若基於支付方資訊以及預設的支付方與醫保支付卡的綁定關係，確定支付方未綁定醫保支付卡，輸出交易失敗的提醒資訊，或，輸出是否進行全自費支付的提醒資訊。
在一個實施例中，所述資訊發送模組74還用於：
若所述處理結果中指示本次交易不能使用醫保進行支付，輸出是否進行全自費支付的提醒資訊。
對於裝置實施例而言，由於其基本對應於方法實施例，所以相關之處參見方法實施例的部分說明即可。以上所描述的裝置實施例僅僅是示意性的，其中所述作為分離部件說明的模組可以是或者也可以不是實體上分開的，作為模組顯示的部件可以是或者也可以不是實體模組，即可以位於一個地方，或者也可以分佈到多個網路模組上。可以根據實際的需要選擇其中的部分或者全部模組來實現本發明方案的目的。本領域普通技術人員在不付出創造性勞動的情況下，即可以理解並實施。
相應的，本發明實施例還提供一種電腦設備，包括記憶體、處理器及儲存在記憶體上並可在處理器上運行的電腦程式，其中，所述處理器執行所述程式時實現如下方法：
支付伺服端接收交易支付請求，所述交易支付請求至少包括：支付方資訊、消費方與收費端的交易資訊、以及收費端資訊；
支付伺服端基於預設的支付方與醫保支付卡的綁定關係，獲取與所述支付方資訊對應的醫保支付卡資訊，將所述醫保支付卡資訊、交易資訊和收費端資訊發送至醫保系統；
醫保系統依據所接收資訊對本次交易進行結算，獲得本次交易的醫保費用和自費費用，基於所述收費端資訊執行向收費端支付醫保費用的支付處理，並向支付伺服端回饋處理結果；
支付伺服端根據所述處理結果執行向收費端支付自費費用的支付處理。
本發明中的各個實施例均採用遞進的方式描述，各個實施例之間相同相似的部分互相參見即可，每個實施例重點說明的都是與其他實施例的不同之處。尤其，對於設備實施例而言，由於其基本相似於方法實施例，所以描述的比較簡單，相關之處參見方法實施例的部分說明即可。
相應的，本發明實施例還提供一種電腦儲存介質，所述儲存介質中儲存有程式指令，所述程式指令包括：
支付伺服端接收交易支付請求，所述交易支付請求至少包括：支付方資訊、消費方與收費端的交易資訊、以及收費端資訊；
支付伺服端基於預設的支付方與醫保支付卡的綁定關係，獲取與所述支付方資訊對應的醫保支付卡資訊，將所述醫保支付卡資訊、交易資訊和收費端資訊發送至醫保系統；
醫保系統依據所接收資訊對本次交易進行結算，獲得本次交易的醫保費用和自費費用，基於所述收費端資訊執行向收費端支付醫保費用的支付處理，並向支付伺服端回饋處理結果；
支付伺服端根據所述處理結果執行向收費端支付自費費用的支付處理。
本發明實施例可採用在一個或多個其中包含有程式碼的儲存介質(包括但不限於磁碟記憶體、CD-ROM、光學記憶體等)上實施的電腦程式產品的形式。電腦可用儲存介質包括永久性和非永久性、可移動和非可移動媒體，可以由任何方法或技術來實現資訊儲存。資訊可以是電腦可讀指令、資料結構、程式的模組或其他資料。電腦的儲存介質的例子包括但不限於：相變記憶體(PRAM)、靜態隨機存取記憶體(SRAM)、動態隨機存取記憶體(DRAM)、其他類型的隨機存取記憶體(RAM)、唯讀記憶體(ROM)、電可擦除可程式設計唯讀記憶體(EEPROM)、快閃記憶體或其他記憶體技術、唯讀光碟唯讀記憶體(CD-ROM)、數位多功能光碟(DVD)或其他光學儲存、磁盒式磁帶，磁帶磁片儲存或其他磁性存放裝置或任何其他非傳輸介質，可用於儲存可以被計算設備存取的資訊。
本領域技術人員在考慮說明書及實踐這裡申請的發明後，將容易想到本發明的其它實施方案。本發明旨在涵蓋本發明的任何變型、用途或者適應性變化，這些變型、用途或者適應性變化遵循本發明的一般性原理並包括本發明未申請的本技術領域中的公知常識或慣用技術手段。說明書和實施例僅被視為示例性的，本發明的真正範圍和精神由下面的申請專利範圍指出。
應當理解的是，本發明並不局限於上面已經描述並在圖式中示出的精確結構，並且可以在不脫離其範圍進行各種修改和改變。本發明的範圍僅由所附的申請專利範圍來限制。
以上所述僅為本發明的較佳實施例而已，並不用以限制本發明，凡在本發明的精神和原則之內，所做的任何修改、等同替換、改進等，均應包含在本發明保護的範圍之內。Exemplary embodiments will be described in detail here, examples of which are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings indicate the same or similar elements. The implementation manners described in the following exemplary embodiments do not represent all implementation manners consistent with the present invention. On the contrary, they are only examples of devices and methods consistent with some aspects of the present invention as detailed in the scope of the appended application.
The terms used in the present invention are only for the purpose of describing specific embodiments, and are not intended to limit the present invention. The singular forms of "a", "the" and "the" used in the scope of the present invention and the appended applications are also intended to include plural 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 in the present invention to describe various information, 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 the present invention, the first information can also be referred to as second information, and similarly, the second information can also be referred to as first information. Depending on the context, the word "if" as used herein can be interpreted as "when" or "when" or "responsive to certainty".
In some application scenarios, medical insurance accounts can be divided into medical insurance personal accounts and medical insurance overall accounts. The full name of the medical insurance personal account is the basic medical insurance personal account, or personal account for short. Personal accounts are mainly used for recording and storing personal account funds, and used for personal medical consumption according to regulations. Personal accounts are usually used to pay for the insured’s specific medical expenses, including outpatient expenses incurred by designated medical institutions, drug purchase expenses in designated retail pharmacies, hospitalization in designated hospitals, outpatient specific items and other basic medical expenses. Even personal accounts can be used to purchase other medical insurance. The medical insurance pooled account fund belongs to all the insured persons, and is centrally managed and used by the social insurance agency. It is mainly used to pay for medical expenses, surgical expenses, nursing expenses, and basic inspection expenses incurred by the insured persons. Regardless of whether it is a personal account or an overall account, there are restrictions in the use process. When a fee is incurred, whether the personal account or the overall account can be used for payment can be judged and paid by the corresponding medical insurance system. For self-paid expenses that cannot be paid with medical insurance, consumers use other payment methods to pay self-paid expenses. Take going to the hospital as an example. When paying medical expenses, users need to show their social security card first, and the charging staff uses the medical insurance system to calculate medical insurance expenses and self-pay expenses. Medical insurance costs can be directly deducted by the medical insurance system. For out-of-pocket expenses, users use other payment methods to pay. It can be seen that two payment methods are required for a transaction, which is cumbersome and inefficient.
In view of this, the embodiment of the present invention provides a payment solution, which can complete the mixed payment of medical insurance expenses and self-paid expenses through a single payment behavior. The embodiments of the payment scheme of the present invention are illustrated below in conjunction with the drawings.
First, an example of the payment scheme is explained from the perspective of interaction. As shown in Fig. 1, it is an application scenario diagram of a payment method according to an exemplary embodiment of the present invention. In this application scenario, it may include a payment server and a medical insurance system, and further, it may also include a toll terminal and a user terminal. In an example, the user terminal may be installed with a user terminal for interacting with a toll terminal and a payment server, for example, it may be a payment user terminal. The payment server may be a server corresponding to the payment client. For example, the payment client can be Alipay, and the payment server can be a payment platform corresponding to Alipay. The medical insurance system may be a system for settlement processing and medical insurance fee payment processing. A medical insurance reimbursement strategy can be configured in the medical insurance system to determine whether the expenses to be paid are medical insurance expenses or whether they include medical insurance expenses. For example, if the fee is paid in the clinic, the medical insurance system can determine whether the registration fee corresponding to the transaction meets the conditions of the medical insurance reimbursement strategy. If the registration fee belongs to an expert number, the condition is not met and the medical insurance payment is not allowed in the clinic. The specific strategy is determined by the medical insurance system, and there is no restriction here. The settlement process may be to use the medical insurance reimbursement strategy to determine the medical insurance expenses and self-paid expenses in the expenses to be paid. The charging end can be the end that charges fees when the transaction occurs, or it can be understood as the end that provides services. The charging end may be a hospital, a sales end of products that can be consumed with a social security card (such as a drug sales end, a medical insurance sales end), etc. Correspondingly, the consumer can be the party who enjoys the service when the transaction occurs, and the consumer can be the doctor, the drug purchaser, the medical insurance purchaser, etc.
As shown in Fig. 2, it is a flowchart of a payment method according to an exemplary embodiment of the present invention. The method includes:
In step 202, the payment server receives a transaction payment request, the transaction payment request includes at least: payment party information, consumer and toll terminal transaction information, and toll terminal information.
In step 204, the payment server obtains the medical insurance payment card information corresponding to the payer information based on the preset binding relationship between the payer and the medical insurance payment card, and transfers the medical insurance payment card information, transaction information, and toll terminal The information is sent to the medical insurance system.
Among them, the medical insurance payment card may be a social insurance card, a medical insurance card, and other cards that can be used for medical-related expenses insurance.
In step 206, the medical insurance system settles the transaction based on the received information, obtains the medical insurance fee and self-paid expenses of the transaction, executes the payment processing of the medical insurance fee to the toller based on the toller information, and sends it to the payment server End feedback processing results;
In step 208, the payment server executes payment processing of paying self-paid expenses to the tolling terminal according to the processing result.
Regarding the transaction payment request, it may be a request for payment of fees for transactions between the consumer and the toll terminal. The transaction payment request may be initiated by the charging terminal to the payment server, or may be initiated by another terminal on behalf of the charging terminal to the payment server.
For example, in an application scenario, the payer can use the payment client to display the payment code, and the toller can send a transaction payment request to the payment server after obtaining the payer's information by scanning the payment code. In this application scenario, a face-to-face payment device can be installed at the toll end to support medical insurance consumers to pay face-to-face.
In another application scenario, the medical insurance client and medical insurance server can be configured for the Human Resources and Social Security Bureau. The medical insurance client is used to provide online medical insurance payment server. The payer can display the graphic code (such as a two-dimensional bar code) carrying the medical insurance system information through the medical insurance client. After the toll terminal obtains the medical insurance system information by scanning the graphic code, it can send transaction-related information to the corresponding medical insurance server. The medical insurance client pushes the pending payment details so that the page with the pending payment details is displayed on the medical insurance client. After the medical insurance client monitors the confirmed payment event, it can directly send a transaction payment request to the payment server, or send a transaction payment request to the payment server through the medical insurance server. Or, after the medical insurance client monitors the payment confirmation event, it notifies the charging terminal, and the charging terminal sends a transaction payment request to the payment server.
Regarding the situation where the tolling terminal sends a transaction payment request to the payment server, in one embodiment, the payment server may provide a payment interface for the tolling terminal. When this embodiment is applied in a face-to-face payment scenario, the payment interface may be a face-to-face payment interface. The method further includes: the charging terminal sends a transaction payment request to the payment server by calling the payment interface of the payment server.
Wherein, the transaction payment request also carries a medical insurance payment identifier used to indicate payment by medical insurance. The payment server can determine that the cost of this transaction is expected to be paid with medical insurance according to the medical insurance payment identifier. The toll terminal can also send a transaction payment request carrying a non-medical insurance payment identifier to the payment server by calling the payment interface of the payment server. The non-medical insurance payment identifier is used to indicate that medical insurance is not used for payment, so that ordinary payments and medical insurance payments can be realized. Share the same payment interface, saving development costs. Since the payment server provides a payment interface for the consumer, both parties can also sign a sales plan.
In another embodiment, different payment interfaces are provided for ordinary payment and medical insurance payment, for example, the medical insurance payment interface provided by the payment server is used for medical insurance payment related operations; the ordinary payment interface provided by the payment server is used for non-medical insurance payment Related operations. It can be seen that this embodiment distinguishes whether the current payment is a medical insurance payment or an ordinary payment through the medical insurance payment interface and the non-medical insurance payment interface, without using parameters to distinguish.
The transaction payment request includes at least payment party information, consumer and toll terminal transaction information, and toll terminal information.
Regarding the consumer and the payer, the consumer can be the party that provides services on the consumer toll end, such as the visitor. Consumer information may be consumer identity information, such as name, certificate type, certificate number, etc. The payer is the party who pays the fees incurred by the exchange. The payer information may be payer identity information, for example, a payment account. Taking the payment code provided by the payment client as an example, the toll terminal can obtain a payment account by scanning the payment code.
The consumer and the payer may be the same user or different users. In order to avoid the phenomenon of hedging and realize multiple protections against hedging, in one embodiment, the transaction payment request also includes consumer information, and the medical insurance payment card information, transaction information and the toll terminal Before the information is sent to the medical insurance system, it also includes: determining that the consumer and the payer are the same user based on the payer information and consumer information. For example, it can be determined that the consumer and the payer are the same user based on whether the information representing the user's identity in the payer's information and the information representing the user's identity in the consumer are consistent. Only when the consumer and the payer are the same user, the medical insurance payment card information, transaction information, and toll terminal information are sent to the medical insurance system. If the consumer and the payer are not the same user, a reminder message of payment failure can be output. The so-called output may be output to the charging terminal or output to the payment user terminal. The reminder information can be error code, failure details, and other information.
It can be seen that this embodiment increases the judgment of whether the paying party and the consumer are the same user, thereby avoiding the phenomenon of hedging.
Transaction information is the information generated when the consumer and the toll terminal have a transaction. Taking the scenario of application in a doctor's treatment as an example, the transaction information may include information such as patient registration information, medical records, a list of outpatient expenses, and pre-settlement ID for inter-office payment. In actual applications, consumers may not expect certain part of transaction information to be leaked. Therefore, the transaction information may include private encrypted information, which may also be referred to as a medical insurance transparent transmission structure. The privacy encrypted information is information obtained by encrypting a specified type of privacy information generated during a transaction, and the privacy information is information required by the medical insurance system for settlement. The toll collector and the medical insurance system can pre-determine the type of private information to be encrypted and the encryption algorithm. The information required for settlement may include relevant information used to determine whether the transaction fee is a medical insurance fee. Some information in the transaction information does not need to be encrypted, for example, business serial number, business receipt number, etc., such transaction information can be directly carried in the transaction payment request.
The charging end may be a hospital, a sales end of products that can be consumed with a medical insurance payment card (such as a drug sales end, a medical insurance sales end), and the like. The toll-end information may be an identification of the toll-end, for example, it may be an organization name, an organization code, and so on.
After obtaining the transaction payment request, it can be determined whether the payer indicated by the payer information is bound to the medical insurance payment card based on the payer information and the preset binding relationship between the payer and the medical insurance payment card. If the payer is bound to the medical insurance payment Card, obtain the medical insurance payment card information corresponding to the payer information. If the payer does not bind the medical insurance payment card, the transaction failure reminder is output, for example, the transaction failure reminder is sent to the toll terminal and the payment client. Or, if the payer does not bind a medical insurance payment card, output reminder information about whether to make full self-pay. For example, sending reminder information for full self-payment to the payment client, so that the user can choose whether to continue the payment.
In the medical insurance system, the payer and the consumer are often judged to ensure whether they are the same user. However, in practical applications, the phenomenon of hedging may occur due to the fraudulent identity of the consumer. In one embodiment, the owner and the payer of the medical insurance payment card in the binding relationship may be restricted to be the same user, thereby further avoiding hedging. Case.
In order to improve user operability, a binding service between the payer and the medical insurance payment card is also provided. In one embodiment, in order to save research and development costs, taking the interaction between the payment client and the payment server and the payment server as an example, the binding relationship between the payer and the medical insurance payment card can be configured on the payment client, and to ensure the cost The secondary binding is a legal binding, and the identity of the current operator can also be verified to improve the validity of the binding relationship. Specifically, the following steps can be performed on the payment client:
Confirm that the owner and payer of the medical insurance payment card are the same user;
Perform identity verification on the current operator, and if it is determined through verification that the current operator is the user, it is determined that the paying party and the equipment guarantee card have a binding relationship.
Among them, the card owner identity information of the medical insurance payment card can be matched with the payer information, so as to determine whether the card owner and the payer of the medical insurance payment card are the same user. Regarding identity verification, it may include one or more of verifying the biometric information of the current operator, verifying the entered personal privacy information, and verifying the entered mobile phone verification code. The verification of the biometric information of the current operator can be face recognition, fingerprint recognition, etc. The verification of the entered personal privacy information may be to determine whether the entered personal privacy information matches the standard personal privacy information of the user (payer). Personal privacy information can be ID card, mobile phone number, bank card number, etc. Further, when it is determined that the current operator is the user through verification, the payer and the equipment guarantee card have a binding relationship and send to the payment server, and obtain the user's medical insurance payment card information, and store the payer information Mapping relationship with medical insurance payment card information for users to query medical insurance payment card information. If the medical insurance payment card is a physical card, the binding service between the payer and the medical insurance payment card can also be used as the generation service of the electronic medical insurance payment card.
Taking the medical insurance payment card as a social insurance card as an example, as shown in FIG. 3, FIG. 3 is a schematic diagram showing a process of generating an electronic social insurance card according to an exemplary embodiment of the present invention. Add the service of generating electronic social security cards to the payment client. The payment client can be installed on mobile phones, tablets and other client terminals. The user can open the electronic device card through the electronic social security card activation page provided by the payment client. In order to ensure that the current operator, the owner of the social security card, and the payer are the same user, the social security card information can be matched with the payer information, and the current operator can be authenticated. This example uses face recognition, live body detection and other means to verify the identity of the current operator. When it is determined that the collected person image is alive and matches the pre-stored user image, the user’s device card information is obtained and the payment party is established. Mapping relationship with social security card, and generate electronic social security card.
The combined transaction payment request also includes consumer information. When it is determined that the payer is bound to a medical insurance payment card, and the consumer and the payer are determined to be the same user based on the payer information and consumer information, the medical insurance payment card information, transaction The information and toll terminal information are sent to the medical insurance system.
Regarding how to send to the medical insurance system, if there is only one medical insurance system, the medical insurance payment card information, transaction information and toll terminal information will be directly sent to the medical insurance system. In some application scenarios, there may be multiple medical insurance systems. For example, each area can be configured with a corresponding medical insurance system. The division of regions can be divided by prefecture-level cities, etc. Correspondingly, in order to distinguish the medical insurance system, the transaction payment request may also carry the medical insurance system identifier. For example, the medical insurance system identifier may be the structure name, institution code, etc. of the medical insurance system party. Use the medical insurance system identification to distinguish different medical insurance systems. In step 204, the medical insurance payment card information, transaction information, and the toll terminal information are sent to the medical insurance system, which may be the medical insurance payment card information, transaction information, and toll terminal information to the medical insurance system corresponding to the medical insurance system identifier .
In one embodiment, the payment server can send medical insurance payment card information, transaction information, and toll terminal information to the medical insurance system, and the medical insurance system directly performs settlement processing and payment processing of medical insurance fees. For example, a settlement request carrying medical insurance payment card information and the transaction information is sent to the medical insurance system. The medical insurance system settles the transaction based on the received information, and obtains the medical insurance fee and self-paid expenses of the transaction, based on the toll terminal information Execute payment processing for paying medical insurance fees to the toll-end, and return the processing result to the payment server.
In this embodiment, the medical insurance system directly performs settlement processing and payment processing of medical insurance costs, which can improve payment efficiency.
Regarding the payment processing of medical insurance fees implemented by the medical insurance system, taking the medical insurance payment card as a social insurance card as an example, the medical insurance system can perform the payment processing of medical insurance expenses by deducting the corresponding fees from the medical insurance overall account or the medical insurance personal account to the charging end. The specific processing methods are in I will not repeat them one by one. The specific deduction of the medical insurance overall account or the medical insurance personal account can be determined by the medical insurance reimbursement strategy. In one embodiment, in the case of using a medical insurance personal account to pay medical insurance costs, the user can also be reminded to choose whether to use a medical insurance personal account to pay medical insurance costs through the payment client, and then the medical insurance system determines whether to use a medical insurance personal account to pay medical insurance costs according to the selection result. .
In some application scenarios, the user may expect to determine whether to use medical insurance payment according to the settlement result. In view of this, in another embodiment, pre-settlement can also be performed through the medical insurance system first, and the pre-settlement result is notified to the payment server. And only when the payer agrees to pay, the payment processing of the medical insurance system and the payment processing of the payment server are performed, which improves user operability and user experience. For example, after receiving the pre-settlement result, the payment server can send payment reminder information including medical insurance fees and self-paid expenses to the payment client, display the payment reminder information on the payment client, and give feedback to the payment server based on user operations Confirm payment instruction.
Regarding how to distinguish the two tasks of pre-settlement and settlement, in one example, pre-settlement and settlement can be distinguished through different requests. For example, using a pre-settlement request indicates that the medical insurance system is expected to perform pre-settlement processing, and a settlement request indicates that the medical insurance system is expected to perform settlement processing, and the pre-settlement request and the settlement request can be distinguished by different parameters. For example, a request including a preset pre-settlement identification is a pre-settlement request, and a request including a preset settlement identification is a settlement request. Correspondingly, the transaction payment request further includes a medical insurance system identifier, and the method further includes: the payment server sends a pre-settlement request carrying the medical insurance payment card information, transaction information, and toll terminal information to the medical insurance system Identify the corresponding medical insurance system, receive the medical insurance cost and self-paid expenses of this transaction as feedback from the medical insurance system, and send the payment reminder information including medical insurance expenses and self-paid expenses to the payment client;
The sending of the medical insurance payment card information, transaction information, and toll-end information to the medical insurance system includes: when receiving a confirmation payment instruction returned by the payment client, carrying the medical insurance payment card information, transaction information, and charging The settlement request of the terminal information is sent to the medical insurance system corresponding to the medical insurance system identifier.
In this embodiment, the use of the pre-settlement request indicates that the medical insurance system is expected to perform pre-settlement processing, and the settlement request is used to indicate the expectation of the medical insurance system to perform settlement processing, which can realize the interaction between the medical insurance system and the payment server by sharing the same interface.
In another example, pre-settlement and settlement can be distinguished through different interfaces provided by the medical insurance system. For example, the data transmitted through the pre-settlement interface instructs the medical insurance system to perform pre-settlement processing, and the data transmitted through the settlement interface instructs the medical insurance system to perform the settlement processing. For example, the transaction payment request further includes a medical insurance system identifier, and the method further includes: the payment server sends the medical insurance payment card information, transaction information, and toll terminal information to the payment server by calling the pre-settlement interface of the medical insurance system The medical insurance system identifies the corresponding medical insurance system, and receives the medical insurance expenses and self-paid expenses of this transaction as feedback from the medical insurance system, and outputs the payment reminder information including the medical insurance expenses and self-paid expenses to the payment client;
The sending of the medical insurance payment card information, transaction information, and toll terminal information to the medical insurance system includes: upon receiving the payment confirmation instruction returned by the payment client, by calling the settlement interface of the medical insurance system to transfer the medical insurance payment card The information, transaction information, and toll terminal information are sent to the medical insurance system corresponding to the medical insurance system identifier.
The medical insurance system settles the transaction based on the medical insurance payment card information, transaction information, and toll terminal information, and obtains the medical insurance fee and self-paid expenses of this transaction. The specific settlement strategy is determined by the medical insurance system and is not restricted here. If the medical insurance cost is not 0, the medical insurance cost can be deducted, and the payment result and details will be returned to the payment server. If the medical insurance payment is successful, you can decide whether to execute the payment processing of paying out-of-pocket expenses to the charging terminal. Payment processing is the processing of controlling the payment to the tolling terminal to pay its own expenses. The specific processing methods are similar to the payment methods in related technologies, so I will not repeat them here. In one embodiment, the password-free limit set by the payment platform can be obtained. When the out-of-pocket fee is less than the password-free limit, the payment processing of paying the out-of-pocket fee to the toll terminal can be directly executed; if the out-of-pocket fee is greater than the password-free limit, the cashier can be used The desk page reminds the user to complete the payment. In another embodiment, the Social Security Bureau may consider that the security of direct payment is low. Therefore, it can require all amounts to be confirmed by the user before the payment processing can be performed. There is no need to determine the size of the self-paid expenses and directly output whether the self-paid expenses are paid. Payment reminder information, the user decides whether to continue the payment.
In addition, in one embodiment, if the processing result indicates that the medical insurance cannot be used for payment in this transaction, output reminder information about whether to make full self-payment. It can be seen that when it is ensured that the medical insurance cannot be used, directly enter the processing flow of full self-paid payment without the user having to withdraw from the current order, which can improve the payment efficiency.
Correspondingly, the present invention also exemplifies the payment method from the perspective of the payment server. As shown in FIG. 4, it is a flowchart of another payment method according to an exemplary embodiment of the present invention. The method can be applied to payment. On the server side, the method includes:
In step 402, a transaction payment request is received. The transaction payment request includes at least: payment party information, consumer and toll terminal transaction information, and toll terminal information;
In step 404, based on the preset binding relationship between the payer and the medical insurance payment card, the medical insurance payment card information corresponding to the payer information is obtained, and the medical insurance payment card information, transaction information and toll terminal information are sent to The medical insurance system for the medical insurance system to settle the transaction and process the medical insurance fee payment according to the received information;
In step 406, the payment processing of paying the self-paid expenses to the tolling terminal is executed according to the processing result returned by the medical insurance system.
It can be understood that the related technology in FIG. 4 is the same as that in FIG. 2 and will not be repeated here.
In one embodiment, the transaction information includes privacy encrypted information, the privacy encrypted information is information obtained by encrypting the specified type of privacy information generated during the transaction, and the privacy information is used by the medical insurance system for settlement. Required information.
In one embodiment, the transaction payment request further includes consumer information, and before sending the medical insurance payment card information, transaction information, and the toll-end information to the medical insurance system, it further includes: according to the payer information And consumer information determines that the consumer and the payer are the same user.
In one embodiment, the transaction payment request further includes a medical insurance system identification, and the method further includes: sending a pre-settlement request carrying the medical insurance payment card information, transaction information, and toll terminal information to the medical insurance system Identify the corresponding medical insurance system, receive the medical insurance cost and self-paid expenses of this transaction as feedback from the medical insurance system, and send the payment reminder information including medical insurance expenses and self-paid expenses to the payment client. The sending of the medical insurance payment card information, transaction information, and toll-end information to the medical insurance system includes: when receiving a confirmation payment instruction returned by the payment client, carrying the medical insurance payment card information, transaction information, and charging The settlement request of the terminal information is sent to the medical insurance system corresponding to the medical insurance system identifier.
In one embodiment, the transaction payment request further includes a medical insurance system identifier, and the method further includes: sending the medical insurance payment card information, transaction information, and toll terminal information to the company by calling the pre-settlement interface of the medical insurance system. The medical insurance system identifies the corresponding medical insurance system, receives the medical insurance cost and self-paid expenses of this transaction as feedback from the medical insurance system, and outputs payment reminder information including the medical insurance expenses and self-paid expenses to the payment client. The sending of the medical insurance payment card information, transaction information, and toll terminal information to the medical insurance system includes: upon receiving the payment confirmation instruction returned by the payment client, by calling the settlement interface of the medical insurance system to transfer the medical insurance payment card The information, transaction information, and toll terminal information are sent to the medical insurance system corresponding to the medical insurance system identifier.
In one embodiment, the method further includes: if based on the information of the payer and the preset binding relationship between the payer and the medical insurance payment card, it is determined that the payer is not bound to the medical insurance payment card, and outputting reminder information of transaction failure, or , Output reminder information about whether to pay at full self-pay.
In one embodiment, the method further includes: if the processing result indicates that the medical insurance cannot be used for payment in this transaction, outputting reminder information about whether to perform full self-payment.
The various technical features in the above embodiments can be combined arbitrarily, as long as there is no conflict or contradiction between the combinations of features, but due to space limitations, they are not described one by one. Therefore, any combination of the various technical features in the above embodiments also belongs to The scope of the present invention.
The following is an example of one of the combinations, where the medical insurance payment card is a social insurance card as an example.
As shown in FIG. 5A, it is a flowchart of another payment method according to an exemplary embodiment of the present invention. The method involves a payment user terminal, a payment server terminal, a toll terminal, and a medical insurance system. The method includes:
The payment user terminal provides the payment code to the toll terminal (step 501).
The toll terminal obtains the payment code of the payment client, obtains the payer information based on the payment code (step 502), and sends a transaction payment request to the payment server (step 503). Wherein, the transaction payment request may include: payer information, transaction information between the consumer and the toll terminal, the toll terminal information, the medical insurance system identifier, and the medical insurance payment identifier used to indicate the use of medical insurance for payment.
If the payment server determines that the payer is bound to the social security card based on the preset binding relationship between the payer and the social security card, and the consumer and the payer are the same user based on the payer information and consumer information, the acquisition and payment The social security card information corresponding to the party information (step 504), and the social security card information, transaction information, and toll terminal information are sent to the medical insurance system corresponding to the medical insurance system identifier by calling the pre-settlement interface of the medical insurance system (step 505). In addition, if the payer does not bind a social security card, or the consumer and the payer are not the same user, a reminder of transaction failure is sent to the receiving terminal and the paying client.
The medical insurance system settles the transaction according to the received information, obtains the medical insurance fee and self-paid expenses of this transaction, and returns the medical insurance fee and self-paid expenses to the payment server (step 506).
The payment server outputs the payment reminder information including the medical insurance fee and out-of-pocket expenses to the payment client (step 507), and when receiving the payment confirmation instruction returned by the payment client, it transfers the social security card information, The transaction information and the toll terminal information are sent to the medical insurance system corresponding to the medical insurance system identifier (step 508).
The medical insurance system performs settlement processing and medical insurance fee payment processing for this transaction based on the received information, and returns the processing result to the payment server (step 509).
At the payment server end, if it is determined that the medical insurance payment is successful according to the processing result, the payment processing of paying the self-paid expenses to the charging end is executed (step 510).
Correspondingly, if the out-of-pocket payment is successful, the payment server will return the toll-end order payment result and the medical insurance payment result to the payment client. At the same time, you can also display the total amount of the order, the amount of self-pay, and the amount of medical insurance on the payment success page of the payment client, and the amount of discounts (if there is a discount, if there is no discount, do not display it), etc. If the payment of the self-paid expenses fails, the refund interface of the medical insurance system is called, the medical insurance system is notified to perform the refund operation, and the payment client and the toll terminal are notified that the payment has failed.
As shown in FIG. 5B, it is an application scenario diagram of another payment method according to an exemplary embodiment of the present invention. As shown in FIG. 5C, it is a schematic diagram of a payment client page according to an exemplary embodiment of the present invention. In this application scenario, binding services and medical insurance payment servers can be added to the original payment client. The user can enter the page that includes the payment code by clicking the "Go Swipe Code" button on the electronic social security card page. In other embodiments, the payment code button on the homepage of the payment client can also be used to enter the page that includes the payment code. The code scanner scans the payment code and transmits the scanned information to the toll terminal. After receiving the payment code, the toll terminal can call the payment interface, and input the payment barcode, the identification indicating whether or not to pay for medical insurance, the identity information of the patient (including name, certificate type, certificate number), hospital institution name, hospital institution code, and medical insurance pending Settlement organization name and code, business serial number, business document number, medical insurance transparent transmission structure (mainly information such as user registration information or pre-settlement ID for inter-office payment). The payment server judges whether the user is bound with a social security card. If the user is not bound with a social security card, it will return the transaction failure and give the corresponding error code. If the social security card has been bound, it is determined whether the patient's identity information is consistent with the payment client's real-name information, and if they are consistent, the medical insurance payment transaction establishment step is entered. If they are inconsistent, it will return the transaction failure and give the corresponding error code. Regarding the creation of medical insurance payment transactions, the payment server calls the pre-settlement interface of the medical insurance system, and sends information such as the institution code, medical insurance transparent transmission structure (registered details information, pre-settlement ID in the clinic) to the medical insurance system for pre-settlement. The medical insurance system performs pre-settlement and returns the required medical insurance payment amount and self-pay amount to the payment server. After the pre-settlement is completed, the payment server calls the settlement interface of the medical insurance system, and sends information such as the institution code and the medical insurance transparent transmission structure (registered detail list or clinic detail ID) to the medical insurance system for settlement. The medical insurance system performs settlement, deducts the amount of the medical insurance account, and returns the medical insurance payment result and details to the payment server. If the medical insurance payment is successful, the out-of-pocket amount will be paid and the agreement will be initiated for payment withholding. The amount paid in person is judged according to the total order amount, if it exceeds the amount, it will jump out of the cashier to complete the payment according to the rules of in-person payment. If the self-paid payment is successful, the order payment is successful, and the hospital system order payment result and medical insurance payment result are returned. At the same time, the payment success page of the payment client displays the total amount of this order, the amount of self-pay, the amount of medical insurance, and the amount of discounts (if there is a discount, if there is no discount, it is not displayed).
Corresponding to the embodiments of the aforementioned payment method, the present invention also provides embodiments of the payment device and the electronic equipment to which it is applied.
The embodiments of the payment device of the present invention can be applied to computer equipment. The device embodiments can be implemented through software, or through hardware or a combination of software and hardware. Take software implementation as an example. As a logical device, it is formed by reading the corresponding computer program instructions in the non-volatile memory into the memory through the processor of the computer equipment where it is located. From the perspective of hardware, as shown in FIG. 6, it is a hardware structure diagram of the computer device where the payment device of the present invention is located, except for the processor 610, network interface 620, memory 630, and non-volatile memory shown in FIG. In addition to the sexual memory 640, the computer device in which the payment device 631 is located in the embodiment may also include other hardware according to the actual function of the device, which will not be repeated here.
As shown in FIG. 7, it is a block diagram of a payment device according to an exemplary embodiment of the present invention. The device includes:
The request receiving module 72 is configured to receive a transaction payment request, the transaction payment request including at least: payment party information, consumer and toll terminal transaction information, and toll terminal information;
The information sending module 74 is used to: obtain the medical insurance payment card information corresponding to the payer information based on the preset binding relationship between the payer and the medical insurance payment card, and transfer the medical insurance payment card information, transaction information and charge The terminal information is sent to the medical insurance system for the medical insurance system to settle the transaction and process the medical insurance fee payment based on the received information;
The fee payment module 76 is used to execute payment processing of paying self-paid expenses to the toll terminal according to the processing result returned by the medical insurance system.
In one embodiment, the transaction information includes privacy encrypted information, the privacy encrypted information is information obtained by encrypting the specified type of privacy information generated during the transaction, and the privacy information is used by the medical insurance system for settlement. Required information.
In one embodiment, the transaction payment request further includes consumer information, and the information sending module is also used to: before sending the medical insurance payment card information, transaction information, and toll terminal information to the medical insurance system, according to The payer information and the consumer information determine that the consumer and the payer are the same user.
In one embodiment, the transaction payment request further includes a medical insurance system identification, and the information sending module 74 is specifically configured to:
Send the pre-settlement request carrying the medical insurance payment card information, transaction information and toll terminal information to the medical insurance system corresponding to the medical insurance system identifier, and receive the medical insurance fee and self-paid expenses of this transaction as feedback from the medical insurance system, and send it to The payment client sends payment reminders including medical insurance costs and self-paid expenses;
When receiving the payment confirmation instruction returned by the payment client, the settlement request carrying the medical insurance payment card information, transaction information and toll terminal information is sent to the medical insurance system corresponding to the medical insurance system identifier.
In one embodiment, the transaction payment request further includes a medical insurance system identification, and the information sending module 74 is specifically configured to:
By calling the pre-settlement interface of the medical insurance system, send the medical insurance payment card information, transaction information, and toll terminal information to the medical insurance system corresponding to the medical insurance system identifier, and receive the medical insurance fee and self-pay of this transaction as feedback from the medical insurance system Expenses, output payment reminder information including medical insurance expenses and self-paid expenses to the payment client;
Upon receiving the payment confirmation instruction returned by the payment client, by calling the settlement interface of the medical insurance system, the medical insurance payment card information, transaction information, and toll terminal information are sent to the medical insurance system corresponding to the medical insurance system identifier.
In one embodiment, the information sending module 74 is also used for:
If based on the information of the payer and the preset binding relationship between the payer and the medical insurance payment card, it is determined that the payer is not bound to the medical insurance payment card, and the reminder information of transaction failure is output, or the reminder information of whether the payment is fully paid is output.
In one embodiment, the information sending module 74 is also used for:
If the processing result indicates that the medical insurance cannot be used for payment in this transaction, output reminder information about whether to make full self-payment.
As for the device embodiment, since it basically corresponds to the method embodiment, the relevant part can refer to the part of the description of the method embodiment. The device embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate, and the components displayed as modules may or may not be physical modules. It can be located in one place, or it can be distributed to multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the objectives of the solution of the present invention. Those of ordinary skill in the art can understand and implement without paying creative labor.
Correspondingly, an embodiment of the present invention also provides a computer device, including a memory, a processor, and a computer program stored on the memory and running on the processor, wherein the processor implements the following method when the program is executed :
The payment server receives a transaction payment request, and the transaction payment request includes at least: payment party information, consumer and toll terminal transaction information, and toll terminal information;
Based on the preset binding relationship between the payer and the medical insurance payment card, the payment server obtains the medical insurance payment card information corresponding to the payer information, and sends the medical insurance payment card information, transaction information and toll terminal information to the medical insurance system ；
The medical insurance system settles the transaction based on the received information, obtains the medical insurance fee and self-paid expenses of the transaction, executes the payment processing of the medical insurance fee to the toller based on the toller information, and returns the processing result to the payment server;
The payment server executes payment processing of paying the self-paid expenses to the tolling terminal according to the processing result.
The various embodiments of the present invention are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, as for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for related parts, please refer to the partial description of the method embodiment.
Correspondingly, an embodiment of the present invention also provides a computer storage medium, the storage medium stores program instructions, and the program instructions include:
The payment server receives a transaction payment request, and the transaction payment request includes at least: payment party information, consumer and toll terminal transaction information, and toll terminal information;
Based on the preset binding relationship between the payer and the medical insurance payment card, the payment server obtains the medical insurance payment card information corresponding to the payer information, and sends the medical insurance payment card information, transaction information and toll terminal information to the medical insurance system ；
The medical insurance system settles the transaction based on the received information, obtains the medical insurance fee and self-paid expenses of the transaction, executes the payment processing of the medical insurance fee to the toller based on the toller information, and returns the processing result to the payment server;
The payment server executes payment processing of paying the self-paid expenses to the tolling terminal according to the processing result.
The embodiments of the present invention may adopt the form of a computer program product implemented on one or more storage media (including but not limited to magnetic disk memory, CD-ROM, optical memory, etc.) containing program codes. Computer usable storage media include permanent and non-permanent, removable and non-removable media, and information storage can be realized 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 programmable read-only memory (EEPROM), flash memory or other memory technologies, read-only CD-ROM (CD-ROM), digital multi-function Optical discs (DVD) or other optical storage, magnetic cassettes, 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.
Those skilled in the art will easily think of other embodiments of the present invention after considering the specification and practicing the invention applied here. The present invention is intended to cover any variations, uses, or adaptive changes of the present invention. These variations, uses or adaptive changes follow the general principles of the present invention and include common knowledge or conventional technical means in the technical field not applied for by the present invention. . The description and the embodiments are only regarded as exemplary, and the true scope and spirit of the present invention are pointed out by the following patent scope.
It should be understood that the present invention is not limited to the precise structure described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present invention is only limited by the scope of the attached patent application.
The above descriptions are only the preferred embodiments of the present invention and are not intended to limit the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the present invention Within the scope of protection.
