為了提高跨應用之間支付業務處理的便捷性，本說明書實施例提供了一種業務處理方法及設備，通過根據設定的資訊提取方式，從第一應用用戶端中提取設定格式的、用於支付的業務資訊；運行與所述設定格式相匹配的第二應用用戶端，並在所述第二應用用戶端中對所述業務資訊進行處理，以完成付款。這樣，能夠有效打破不同應用之間對支付業務處理的禁錮，實現跨應用對支付業務的處理，有效提升支付業務處理的便捷性。 需要說明的是，本說明書實施例中記載的“第一應用用戶端”和“第二應用用戶端”中的“第一”和“第二”沒有特殊含義，僅用來區分不同的應用用戶端。這兩個應用用戶端在實際應用中可以屬於互為競爭對手的不同開發者開發的，也可以是同一個開發者開發的，但是這兩個應用用戶端之間存在禁止直接通信的問題，在本說明書實施例中不做具體限定。 為使本說明書的目的、技術方案和優點更加清楚，下面將結合本說明書具體實施例及相應的附圖對本說明書技術方案進行清楚、完整地描述。顯然，所描述的實施例僅是本說明書一部分實施例，而不是全部的實施例。基於本說明書中的實施例，在該技術領域中具有通常知識者在沒有做出創造性勞動前提下所獲得的所有其他實施例，都屬於本說明書保護的範圍。 以下結合附圖，詳細說明本說明書各實施例提供的技術方案。 圖1為本說明書實施例提供的一種業務處理方法的流程示意圖。所述方法可以如下所示。本說明書實施例的執行主體可以為終端設備，在該終端設備中安裝了第一應用用戶端和第二應用用戶端，但是這兩個用戶端之間禁止直接資料交互作用。 步驟101：根據設定的資訊提取方式，從第一應用用戶端中提取設定格式的、用於支付的業務資訊。 在本說明書實施例中，在第一應用用戶端的指定區域發佈設定格式的、用於支付的業務資訊。一旦使用者需要該業務資訊，可以按照步驟101的方式從第一應用用戶端中提取該業務資訊。 這裡所記載的設定格式可以是指滿足第二應用用戶端運行需求的格式，也可以理解為該設定格式根據第二應用用戶端所支援的格式確定，這裡不做具體限定。 具體地，通過複製的方式從第一應用用戶端中提取設定格式的、用於支付的業務資訊；並將提取到的所述業務資訊儲存在系統的剪輯板中。 例如：對該業務資訊執行“長按”操作，在顯示的操作類型中可以選擇複製操作，這樣可以從第一應用戶端中提取該業務資訊。 需要說明的是，該業務資訊中包含收款物件的標識，還可以包含收款金額等其他資訊，這裡不做具體限定。這裡業務資訊的顯示形式可以是二維碼圖片，也可以是設定格式的文本資訊，還可以是具備可識別特徵的內容，還可以是聲波，這裡不做具體限定。 步驟103：運行與所述設定格式相匹配的第二應用用戶端，並在所述第二應用用戶端中對所述業務資訊進行處理，以完成付款。 在本說明書實施例中，首先，在檢測到所述設定格式的所述業務資訊的情況下，推送提示資訊，所述提示資訊用於提示使用者是否跳轉運行於所述設定格式匹配的第二應用用戶端。 具體地，在檢測到所述設定格式的所述業務資訊的情況下，檢測是否安裝與所述設定格式相匹配的第二應用用戶端； 若檢測結果為已安裝，則推送提示資訊。 若檢測結果為未安裝，則推送安裝提示資訊，以提示使用者是否安裝第二應用用戶端。 其次，在接收到確認資訊的情況下，運行與所述設定格式相匹配的第二應用用戶端。 最後，在所述第二應用用戶端中對所述業務資訊進行處理。 具體地，將所述業務資訊發送給伺服器，使所述伺服器對所述業務資訊進行解析； 接收所述伺服器返回的支付頁面，所述支付頁面是所述伺服器對所述業務資訊進行解析後產生的； 基於所述支付頁面，向所述業務資訊中包含收款物件付款。 較優地，在得到付款結果的情況下，按照所述設定的資訊提取方式，提取得到所述付款結果，並將所述付款結果跳轉顯示在所述第一應用用戶端中。 例如：通過複製的方式提取付款結果，並將得到的付款結果儲存在系統的剪輯板上，在確定返回第一應用用戶端的情況下，將該付款結果顯示在所述第一應用用戶端中。 或者，還可以通過RPC介面向第二應用用戶端發送付款結果查詢消息，並根據第二應用用戶端回饋的結果，確定支付業務處理完成。 較優地，在確認支付完成的情況下，觸發第一應用用戶端跳轉至支付完成頁面，以示該業務資訊處理結束。 通過本說明書實施例提供的技術方案，根據設定的資訊提取方式，從第一應用用戶端中提取設定格式的、用於支付的業務資訊；運行與所述設定格式相匹配的第二應用用戶端，並在所述第二應用用戶端中對所述業務資訊進行處理，以完成付款。這樣，能夠有效打破不同應用之間對支付業務處理的禁錮，實現跨應用對支付業務的處理，有效提升支付業務處理的便捷性。 圖2為本說明書實施例提供的一種業務處理方法的流程示意圖。所述方法可以如下所示。 步驟201：使用者A在第二應用用戶端中產生用於支付的業務資訊。 在本說明書實施例中，這裡記載的業務資訊中包含用於支付的帳戶標識(例如：用於收款的帳戶標識，或者用於付款的帳戶標識)、支付金額(這個支付金額可以作為選擇項，可以任意設置金額的大小，也可以設置固定金額的大小，這裡不做限定)等等。 步驟203：使用者A通過第二應用用戶端將該業務資訊發送給第二應用用戶端對應的伺服器。 步驟205：伺服器在接收到該業務資訊時，按照設定的資訊格式對該業務資訊進行處理，並將處理後的該業務資訊發送給第二應用用戶端所在終端設備，使所述終端設備將該處理後的業務資訊儲存在剪輯板中。 步驟207：使用者A啟動終端設備中安裝的第一應用用戶端，並將剪輯板中的業務資訊發佈在第一應用用戶端的指定區域中。 在本說明書實施例中，這裡的指定區域可以是公共資訊發佈區域，也可以是某一個頁面中的指定位置，例如：某個頁面的底部等。 圖3為本說明書實施例提供的業務資訊的示意圖。 從圖3中可以看出，業務資訊顯示在頁面的底部指定位置。看到該業務資訊的其他使用者可以對該業務資訊執行指定操作，以獲取該業務資訊的內容。 步驟209：使用者B根據設定的資訊提取方式，從第一應用用戶端中提取設定格式的、用於支付的業務資訊。 步驟211：檢測是否安裝與所述設定格式相匹配的第二應用用戶端；若檢測結果為已安裝，則執行步驟213。 若檢測結果為未安裝，則推送安裝提示資訊，以提示使用者是否安裝第二應用用戶端。 步驟213：運行與所述設定格式相匹配的第二應用用戶端。 步驟215：通過第二應用用戶端將所述業務資訊發送給伺服器，使所述伺服器對所述業務資訊進行解析。 步驟217：接收所述伺服器返回的支付頁面，所述支付頁面是所述伺服器對所述業務資訊進行解析後產生的。 步驟219：基於所述支付頁面，向所述業務資訊中包含收款物件付款。 步驟221：在得到付款結果的情況下，按照所述設定的資訊提取方式，提取得到所述付款結果，並將所述付款結果跳轉顯示在所述第一應用用戶端中。 需要說明的是，本說明書實施例記載的技術方案可以應用在“獎賞”場景中，被獎賞者可以將業務資訊發佈在獎賞區域，這樣，獎賞者可以在獎賞區域獲取該業務資訊，以實現對被獎賞者的獎賞(即付款)。 圖4為本說明書實施例提供的一種業務處理方法的場景示意圖。 從圖4中可以看出，在第一應用用戶端與第二應用用戶端之間存在禁止直接通信的問題時，通過根據設定的資訊提取方式，從第一應用用戶端中提取設定格式的、用於支付的業務資訊；運行與所述設定格式相匹配的第二應用用戶端，並在所述第二應用用戶端中對所述業務資訊進行處理，以完成付款，這樣採用本說明書實施例提供的技術方案可以實現第一應用用戶端與第二應用用戶端之間跨應用的支付業務的處理，有效提升支付業務處理的便捷性。 圖5為本說明書實施例提供的一種業務處理設備的結構示意圖。所述業務處理設備包括：提取單元501和處理單元502，其中： 提取單元501，根據設定的資訊提取方式，從第一應用用戶端中提取設定格式的、用於支付的業務資訊； 處理單元502，運行與所述設定格式相匹配的第二應用用戶端，並在所述第二應用用戶端中對所述業務資訊進行處理，以完成付款。 在本說明書的另一個實施例中，所述業務處理設備還包括：跳轉顯示單元503，其中： 跳轉顯示單元503，在得到付款結果的情況下，按照所述設定的資訊提取方式，提取得到所述付款結果，並將所述付款結果跳轉顯示在所述第一應用用戶端中。 在本說明書的另一個實施例中，所述提取單元501根據設定的資訊提取方式，從第一應用用戶端中提取設定格式的、用於支付的業務資訊，包括： 通過複製的方式從第一應用用戶端中提取設定格式的、用於支付的業務資訊； 將提取到的所述業務資訊儲存在系統的剪輯板中。 在本說明書的另一個實施例中，所述業務處理設備還包括：發佈單元504，其中： 所述發佈單元504，在第一應用用戶端的指定區域發佈設定格式的、用於支付的業務資訊。 在本說明書的另一個實施例中，所述處理單元502運行與所述設定格式相匹配的第二應用用戶端，包括： 在檢測到所述設定格式的所述業務資訊的情況下，推送提示資訊，所述提示資訊用於提示使用者是否跳轉運行於所述設定格式匹配的第二應用用戶端； 在接收到確認資訊的情況下，運行與所述設定格式相匹配的第二應用用戶端。 在本說明書的另一個實施例中，所述處理單元502在檢測到所述設定格式的所述業務資訊的情況下，推送提示資訊，包括： 在檢測到所述設定格式的所述業務資訊的情況下，檢測是否安裝與所述設定格式相匹配的第二應用用戶端； 若檢測結果為已安裝，則推送提示資訊。 在本說明書的另一個實施例中，所述處理單元502在所述第二應用用戶端中對所述業務資訊進行處理，包括： 將所述業務資訊發送給伺服器，使所述伺服器對所述業務資訊進行解析； 接收所述伺服器返回的支付頁面，所述支付頁面是所述伺服器對所述業務資訊進行解析後產生的； 基於所述支付頁面，向所述業務資訊中包含收款物件付款。 需要說明的是，本說明書實施例中記載的業務處理設備可以通過軟體方式實現，也可以通過硬體方式實現，這裡不做具體限定。業務處理設備根據設定的資訊提取方式，從第一應用用戶端中提取設定格式的、用於支付的業務資訊；運行與所述設定格式相匹配的第二應用用戶端，並在所述第二應用用戶端中對所述業務資訊進行處理，以完成付款。這樣，能夠有效打破不同應用之間對支付業務處理的禁錮，實現跨應用對支付業務的處理，有效提升支付業務處理的便捷性。 基於同一個發明概念，本說明書實施例還提供了一種業務處理設備，包括：至少一個記憶體和至少一個處理器，其中，所述記憶體中儲存有程式，並被配置成由所述處理器執行以下步驟： 根據設定的資訊提取方式，從第一應用用戶端中提取設定格式的、用於支付的業務資訊； 運行與所述設定格式相匹配的第二應用用戶端，並在所述第二應用用戶端中對所述業務資訊進行處理，以完成付款。 其中，所述處理器可以按照上述實施例中記載的方式實施，這裡不再一一贅述。 在20世紀90年代，對於一個技術的改進可以很明顯地區分是硬體上的改進(例如，對二極體、電晶體、開關等電路結構的改進)還是軟體上的改進(對於方法流程的改進)。然而，隨著技術的發展，當今的很多方法流程的改進已經可以視為硬體電路結構的直接改進。設計人員幾乎都通過將改進的方法流程程式設計到硬體電路中來得到相應的硬體電路結構。因此，不能說一個方法流程的改進就不能用硬體實體模組來實現。例如，可程式設計邏輯裝置(Programmable Logic Device, PLD)(例如現場可程式設計閘陣列(Field Programmable Gate Array, FPGA))就是這樣一種積體電路，其邏輯功能由使用者對器件程式設計來確定。由設計人員自行程式設計來把一個數位系統“整合”在一片PLD上，而不需要請晶片製造廠商來設計和製作專用的積體電路晶片。而且，如今，取代手工地製作積體電路晶片，這種程式設計也多改用“邏輯編譯器(logic compiler)”軟體來實現，它與程式開發撰寫時所用的軟體編譯器相類似，而要編譯之前的原始碼也得用特定的程式設計語言來撰寫，此稱之為硬體描述語言(Hardware Description Language, HDL)，而HDL也並非僅有一種，而是有許多種，如ABEL(Advanced Boolean Expression Language)、AHDL(Altera Hardware Description Language)、Confluence、CUPL(Cornell University Programming Language)、HDCal、JHDL(Java Hardware Description Language)、Lava、Lola、MyHDL、PALASM、RHDL(Ruby Hardware Description Language)等，目前最普遍使用的是VHDL (Very-High-Speed Integrated Circuit Hardware Description Language)與Verilog。在該技術領域中具有通常知識者也應該清楚，只需要將方法流程用上述幾種硬體描述語言稍作邏輯程式設計並程式設計到積體電路中，就可以很容易得到實現該邏輯方法流程的硬體電路。 控制器可以按任何適當的方式實現，例如，控制器可以採取例如微處理器或處理器以及儲存可由該(微)處理器執行的電腦可讀程式碼(例如軟體或韌體)的電腦可讀媒體、邏輯閘、開關、專用積體電路(Application Specific Integrated Circuit, ASIC)、可程式設計邏輯控制器和嵌入微控制器的形式，控制器的例子包括但不限於以下微控制器：ARC 625D、Atmel AT91SAM、Microchip PIC18F26K20以及Silicone Labs C8051F320，記憶體控制器還可以被實現為記憶體的控制邏輯的一部分。在該技術領域中具有通常知識者也知道，除了以純電腦可讀程式碼方式實現控制器以外，完全可以通過將方法步驟進行邏輯程式設計來使得控制器以邏輯閘、開關、專用積體電路、可程式設計邏輯控制器和嵌入微控制器等的形式來實現相同功能。因此這種控制器可以被認為是一種硬體部件，而對其內包括的用於實現各種功能的裝置也可以視為硬體部件內的結構。或者甚至，可以將用於實現各種功能的裝置視為既可以是實現方法的軟體模組又可以是硬體部件內的結構。 上述實施例闡明的系統、裝置、模組或單元，具體可以由電腦晶片或實體實現，或者由具有某種功能的產品來實現。一種典型的實現設備為電腦。具體的，電腦例如可以為個人電腦、膝上型電腦、蜂巢式電話、相機電話、智慧型電話、個人數位助理、媒體播放器、導航設備、電子郵件設備、遊戲主機、平板電腦、可穿戴設備或者這些設備中的任何設備的組合。 為了描述的方便，描述以上裝置時以功能分為各種單元分別描述。當然，在實施本說明書時可以把各單元的功能在同一個或多個軟體和/或硬體中實現。 在該技術領域中具有通常知識者應明白，本發明的實施例可提供為方法、系統、或電腦程式產品。因此，本發明可採用完全硬體實施例、完全軟體實施例、或結合軟體和硬體方面的實施例的形式。而且，本發明可採用在一個或多個其中包含有電腦可用程式碼的電腦可用儲存媒體(包括但不限於磁碟記憶體、CD-ROM、光學記憶體等)上實施的電腦程式產品的形式。 本發明是參照根據本發明實施例的方法、設備(系統)、和電腦程式產品的流程圖和／或方塊圖來描述的。應理解可由電腦程式指令實現流程圖和／或方塊圖中的每一流程和／或方塊、以及流程圖和／或方塊圖中的流程和／或方塊的結合。可提供這些電腦程式指令到通用電腦、專用電腦、嵌入式處理機或其他可程式設計資料處理設備的處理器以產生一個機器，使得通過電腦或其他可程式設計資料處理設備的處理器執行的指令產生用於實現在流程圖一個流程或多個流程和／或方塊圖一個方塊或多個方塊中指定的功能的裝置。 這些電腦程式指令也可儲存在能引導電腦或其他可程式設計資料處理設備以特定方式工作的電腦可讀記憶體中，使得儲存在該電腦可讀記憶體中的指令產生包括指令裝置的製造品，該指令裝置實現在流程圖一個流程或多個流程和／或方塊圖一個方塊或多個方塊中指定的功能。 這些電腦程式指令也可裝載到電腦或其他可程式設計資料處理設備上，使得在電腦或其他可程式設計設備上執行一系列操作步驟以產生電腦實現的處理，從而在電腦或其他可程式設計設備上執行的指令提供用於實現在流程圖一個流程或多個流程和／或方塊圖一個方塊或多個方塊中指定的功能的步驟。 在一個典型的配置中，計算設備包括一個或多個處理器(CPU)、輸入/輸出介面、網路介面和內部記憶體。 內部記憶體可能包括電腦可讀媒體中的非永久性記憶體，隨機存取記憶體(RAM)和/或揮發失性內部記憶體等形式，如唯讀記憶體(ROM)或快閃記憶體(flash RAM)。內部記憶體是電腦可讀媒體的示例。 電腦可讀媒體包括永久性和非永久性、可移動和非可移動媒體可以由任何方法或技術來實現資訊儲存。資訊可以是電腦可讀指令、資料結構、程式的模組或其他資料。電腦的儲存媒體的例子包括，但不限於相變記憶體(PRAM)、靜態隨機存取記憶體(SRAM)、動態隨機存取記憶體(DRAM)、其他類型的隨機存取記憶體(RAM)、唯讀記憶體(ROM)、電可抹除可程式設計唯讀記憶體(EEPROM)、快閃記憶體或其他內部記憶體技術、唯讀光碟唯讀記憶體(CD-ROM)、數位多功能光碟(DVD)或其他光學儲存、磁盒式磁帶、磁帶磁碟儲存或其他磁性儲存裝置或任何其他非傳輸媒體，可用於儲存可以被計算設備訪問的資訊。按照本文中的界定，電腦可讀媒體不包括暫態媒體(transitory media)，如調變的資料訊號和載波。 還需要說明的是，術語“包括”、“包含”或者其任何其他變體意在涵蓋非排他性的包含，從而使得包括一系列要素的過程、方法、商品或者設備不僅包括那些要素，而且還包括沒有明確列出的其他要素，或者是還包括為這種過程、方法、商品或者設備所固有的要素。在沒有更多限制的情況下，由語句“包括一個……”限定的要素，並不排除在包括所述要素的過程、方法、商品或者設備中還存在另外的相同要素。 本說明書可以在由電腦執行的電腦可執行指令的一般上下文中描述，例如程式模組。一般地，程式模組包括執行特定任務或實現特定抽象資料類型的常式、程式、物件、元件、資料結構等等。也可以在分散式運算環境中實踐本說明書，在這些分散式運算環境中，由通過通信網路而被連接的遠端處理設備來執行任務。在分散式運算環境中，程式模組可以位於包括存放裝置在內的本地和遠端電腦儲存媒體中。 本說明書中的各個實施例均採用循序的方式描述，各個實施例之間相同相似的部分互相參見即可，每個實施例重點說明的都是與其他實施例的不同之處。尤其，對於系統實施例而言，由於其基本相似於方法實施例，所以描述的比較簡單，相關之處參見方法實施例的部分說明即可。 以上所述僅為本說明書的實施例而已，並不用於限制本說明書。對在該技術領域中具有通常知識者而言，本說明書可以有各種更改和變化。凡在本說明書的精神和原理之內所作的任何修改、等同替換、改進等，均應包含在本說明書的申請專利範圍的範疇之內。In order to improve the convenience of payment business processing between applications, the embodiments of this specification provide a business processing method and device, which extracts the set format for payment from the first application client according to the set information extraction method. Business information; run a second application client that matches the set format, and process the business information in the second application client to complete payment. In this way, it is possible to effectively break the barriers of payment service processing between different applications, realize cross-application processing of payment services, and effectively improve the convenience of payment service processing. It should be noted that the "first" and "second" in the "first application client" and "second application client" described in the embodiments of this specification have no special meaning and are only used to distinguish different application users. end. In actual applications, the two application clients can be developed by different developers who are competitors, or they can be developed by the same developer. However, there is a problem of prohibiting direct communication between the two application clients. There is no specific limitation in the embodiments of this specification. "In order to make the purpose, technical solution and advantages of this specification clearer, the technical solution of this specification will be clearly and completely described below in conjunction with the specific embodiments of this specification and the corresponding drawings. Obviously, the described embodiments are only a part of the embodiments in this specification, rather than all the embodiments. Based on the embodiments in this specification, all other embodiments obtained by persons with ordinary knowledge in the technical field without creative work shall fall within the protection scope of this specification. The following describes in detail the technical solutions provided by each embodiment of this specification with reference to the accompanying drawings. Figure 1 is a schematic flowchart of a service processing method provided by an embodiment of this specification. The method can be as follows. The execution subject of the embodiments of this specification may be a terminal device, in which the first application client and the second application client are installed, but direct data interaction between the two client terminals is prohibited. Step 101: According to the set information extraction method, extract business information for payment in a set format from the first application client. In the embodiment of this specification, the business information for payment in a set format is published in the designated area of the first application client. Once the user needs the business information, the business information can be extracted from the first application client in step 101. The setting format described here may refer to a format that meets the operating requirements of the second application client, or it can be understood that the setting format is determined according to the format supported by the second application client, and there is no specific limitation here. Specifically, the business information for payment in a set format is extracted from the first application client by copying; and the extracted business information is stored in the clip board of the system. For example: perform a "long press" operation on the business information, and select the copy operation in the displayed operation type, so that the business information can be extracted from the first application client. It should be noted that the business information includes the identification of the payment object, and can also include other information such as the payment amount, and there is no specific limitation here. The display form of the business information here can be a two-dimensional code picture, or text information in a set format, or content with identifiable characteristics, or sound waves, which is not specifically limited here. Step 103: Run a second application client that matches the set format, and process the business information in the second application client to complete payment. In the embodiment of this specification, firstly, when the business information in the set format is detected, prompt information is pushed, and the prompt information is used to prompt the user whether to jump and run on the second matching format in the set format. Application client. Specifically, in the case of detecting the business information in the setting format, detecting whether to install a second application client that matches the setting format; if the detection result is that it has been installed, then pushing prompt information. If the detection result is that it is not installed, the installation prompt information is pushed to prompt the user whether to install the second application client. Secondly, when the confirmation information is received, the second application client that matches the setting format is run. Finally, the business information is processed in the second application client. Specifically, sending the business information to a server, so that the server can analyze the business information; receiving a payment page returned by the server, the payment page being the server’s response to the business information Generated after parsing; Based on the payment page, payment is made to the business information including the receivable item. Preferably, when the payment result is obtained, the payment result is extracted according to the set information extraction method, and the payment result is redirected and displayed in the first application client. For example: extract the payment result by copying, and store the obtained payment result on the clip board of the system, and display the payment result in the first application client when it is determined to return to the first application client. Alternatively, it is also possible to send a payment result query message to the second application client through the RPC interface, and determine that the payment service processing is completed based on the result returned by the second application client. Preferably, in the case of confirming that the payment is completed, the first application client is triggered to jump to the payment completion page to indicate the end of the business information processing. According to the technical solution provided by the embodiment of this specification, according to the set information extraction method, extract the business information for payment in the set format from the first application client; run the second application client that matches the set format , And process the business information in the second application client to complete the payment. In this way, it is possible to effectively break the barriers of payment service processing between different applications, realize cross-application processing of payment services, and effectively improve the convenience of payment service processing. Figure 2 is a schematic flowchart of a service processing method provided by an embodiment of this specification. The method can be as follows. Step 201: User A generates business information for payment in the second application client. In the embodiment of this specification, the business information recorded here includes the account identification used for payment (for example: the account identification used for collection, or the account identification used for payment), payment amount (this payment amount can be used as an option) , You can set the size of the amount arbitrarily, or you can set the size of a fixed amount, there is no limit here) and so on. Step 203: User A sends the service information to the server corresponding to the second application client through the second application client. Step 205: When the server receives the business information, it processes the business information according to the set information format, and sends the processed business information to the terminal device where the second application client is located, so that the terminal device will The processed business information is stored in the clip board. Step 207: User A activates the first application client installed in the terminal device, and publishes the business information in the clip board in the designated area of the first application client. In the embodiment of this specification, the designated area here can be a public information release area, or a designated location on a certain page, such as the bottom of a certain page. Figure 3 is a schematic diagram of the business information provided by the embodiment of this specification. It can be seen from Figure 3 that the business information is displayed at the designated position at the bottom of the page. Other users who see the business information can perform specified operations on the business information to obtain the content of the business information. Step 209: User B extracts the business information for payment in the set format from the first application client according to the set information extraction method. Step 211: Detect whether the second application client that matches the set format is installed; if the detection result is that it has been installed, go to step 213. If the detection result is that it is not installed, the installation prompt information is pushed to prompt the user whether to install the second application client. Step 213: Run a second application client that matches the set format. Step 215: Send the business information to the server through the second application client, so that the server parses the business information. Step 217: Receive a payment page returned by the server, where the payment page is generated after the server analyzes the business information. Step 219: Based on the payment page, make payment to the business information including the collection item. Step 221: In the case of obtaining the payment result, extract the payment result according to the set information extraction method, and display the payment result in the first application client. It should be noted that the technical solutions recorded in the embodiments of this specification can be applied in the "reward" scenario, and the rewardee can post business information in the reward area. In this way, the rewarder can obtain the business information in the reward area to achieve The reward (ie payment) of the rewarded person. Figure 4 is a schematic diagram of a scenario of a service processing method provided by an embodiment of this specification. It can be seen from Figure 4 that when there is a problem of prohibiting direct communication between the first application client and the second application client, the set format, Business information used for payment; run a second application client that matches the set format, and process the business information in the second application client to complete the payment. In this way, the embodiment of this specification is used The provided technical solution can realize the processing of cross-application payment services between the first application client and the second application client, and effectively improve the convenience of payment service processing. Figure 5 is a schematic structural diagram of a service processing device provided by an embodiment of this specification. The service processing equipment includes: an extraction unit 501 and a processing unit 502, wherein: an extraction unit 501 extracts business information for payment in a set format from the first application client according to a set information extraction method; and a processing unit 502 , Run a second application client that matches the set format, and process the business information in the second application client to complete payment. In another embodiment of the present specification, the service processing device further includes: a jump display unit 503, wherein: a jump display unit 503, in the case of obtaining the payment result, extracts all information according to the set information extraction method The payment result is described, and the payment result is redirected and displayed in the first application client. In another embodiment of this specification, the extraction unit 501 extracts business information for payment in a set format from the first application client according to the set information extraction method, including: from the first application client by copying The application client extracts the business information used for payment in a set format; stores the extracted business information in the clip board of the system. In another embodiment of this specification, the service processing device further includes: a publishing unit 504, wherein: the publishing unit 504 publishes business information for payment in a set format in a designated area of the first application client. In another embodiment of the present specification, the processing unit 502 runs the second application client that matches the set format, including: in the case of detecting the business information in the set format, push notification Information, the prompt information is used to prompt the user whether to jump to the second application client that matches the set format; upon receiving the confirmation information, run the second application client that matches the set format . In another embodiment of this specification, when the processing unit 502 detects the business information in the set format, push notification information, including: when the business information in the set format is detected In this case, it is detected whether the second application client that matches the setting format is installed; if the detection result is that it has been installed, a prompt message is pushed. In another embodiment of this specification, the processing unit 502 processing the business information in the second application client includes: sending the business information to a server, so that the server can Analyzing the business information; receiving a payment page returned by the server, the payment page being generated after the server analysing the business information; based on the payment page, sending the business information to Receiving items payment. It should be noted that the business processing equipment described in the embodiments of this specification can be implemented in software or hardware, and there is no specific limitation here. The business processing device extracts the business information used for payment in the set format from the first application client according to the set information extraction method; runs the second application client that matches the set format, and executes the payment in the second application client. The business information is processed in the application client to complete the payment. In this way, it is possible to effectively break the barriers of payment service processing between different applications, realize cross-application processing of payment services, and effectively improve the convenience of payment service processing. Based on the same inventive concept, an embodiment of this specification also provides a business processing device, including: at least one memory and at least one processor, wherein the memory is stored with a program and is configured to be used by the processor Perform the following steps: extract business information for payment in a set format from the first application client according to the set information extraction method; run a second application client that matches the set format, and run the 2. The business information is processed in the application client to complete the payment. Wherein, the processor can be implemented in the manner recorded in the above-mentioned embodiment, which will not be repeated here. In the 1990s, the improvement of a technology can be clearly distinguished from the improvement of the hardware (for example, the improvement of the circuit structure of diodes, transistors, switches, etc.) or the improvement of the software (for the process of the method). Improve). However, with the development of technology, the improvement of many methods and processes of today can be regarded as a direct improvement of the hardware circuit structure. Designers almost always get the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be realized by the hardware entity module. For example, Programmable Logic Device (PLD) (such as Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user’s programming of the device . It is designed by the designer to "integrate" a digital system on a PLD without having to ask the chip manufacturer to design and produce a dedicated integrated circuit chip. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is often implemented by using "logic compiler" software, which is similar to the software compiler used in programming and writing, but requires The source code before compilation must also be written in a specific programming language, which is called Hardware Description Language (HDL), and there is not only one HDL, but many, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., Currently the most commonly used are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those with ordinary knowledge in this technical field should also be aware that only need to use the above-mentioned hardware description language to design the method flow with a little logic programming and program it into the integrated circuit, then the flow of the logic method can be easily obtained. The hardware circuit. The controller can be implemented in any suitable manner. For example, the controller can take the form of, for example, a microprocessor or a processor and a computer readable program code (such as software or firmware) that can be executed by the (micro) processor. Media, logic gates, switches, application specific integrated circuits (ASIC), programmable logic controllers and embedded microcontrollers. Examples of controllers include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicon Labs C8051F320, the memory controller can also be implemented as part of the memory control logic. Those with ordinary knowledge in this technical field also know that in addition to implementing the controller in a purely computer-readable program code, it is entirely possible to design the method steps by logic programming to make the controller use logic gates, switches, dedicated integrated circuits, Programmable logic controllers and embedded microcontrollers can be used to achieve the same functions. Therefore, such a controller can be regarded as a hardware component, and the devices included in it for realizing various functions can also be regarded as a structure within the hardware component. Or even, the device for realizing various functions can be regarded as both a software module for realizing the method and a structure within a hardware component. The system, device, module or unit explained in the above embodiments can be implemented by a computer chip or entity, or by a product with a certain function. A typical implementation device is a computer. Specifically, the computer can be, for example, 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 device, a game console, a tablet computer, and a wearable device. Or a combination of any of these devices. For the convenience of description, when describing the above device, the functions are divided into various units and described separately. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and/or hardware. "A person with ordinary knowledge in the technical field should understand that the embodiments of the present invention can be provided as a method, a system, or a computer program product. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware. Moreover, the present invention can be in the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memory, CD-ROM, optical memory, etc.) containing computer-usable program codes. . "The present invention is described with reference to flowcharts and/or block diagrams of methods, equipment (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and/or block in the flowchart and/or block diagram, and the combination of processes and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions can be provided to the processors of general-purpose computers, dedicated computers, embedded processors, or other programmable data processing equipment to generate a machine that can be executed by the processors of the computer or other programmable data processing equipment A device for realizing the functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram is generated. These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory generate a manufactured product including the instruction device , The instruction device realizes the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram. These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to generate computer-implemented processing, so that the computer or other programmable equipment The instructions executed above provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram. In a typical configuration, the computing device includes one or more processors (CPU), input/output interfaces, network interfaces, and internal memory. Internal memory may include non-permanent memory in computer-readable media, random access memory (RAM), and/or volatile internal memory, such as read-only memory (ROM) or flash memory. (flash RAM). Internal memory is an example of computer-readable media. Computer-readable media includes permanent and non-permanent, removable and non-removable media, and information storage can be realized by any method or technology. Information can be computer-readable instructions, data structures, program modules, 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 internal memory technology, read-only CD-ROM (CD-ROM), digital multi Functional discs (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that 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 transitory media, such as modulated data signals and carrier waves. It should also be noted that the terms "include", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or equipment including a series of elements not only includes those elements, but also includes Other elements that are not explicitly listed, or they also include elements inherent to such processes, methods, commodities, or equipment. If there are no more restrictions, the element defined by the sentence "including a..." does not exclude the existence of other identical elements in the process, method, commodity, or equipment that includes the element. This manual can be described in the general context of computer-executable instructions executed by a computer, such as a program module. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. This specification can also be practiced in a distributed computing environment. In these distributed computing environments, remote processing devices connected through a communication network perform tasks. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices. Each embodiment in this specification is described in a sequential manner, and the same or similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the difference from other embodiments. In particular, as for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for related parts, please refer to the part of the description of the method embodiment. The above descriptions are only examples of this specification, and are not intended to limit this specification. For those who have general knowledge in this technical field, this specification can have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this specification shall be included in the scope of the patent application of this specification.
