Credit payment method and apparatus based on mobile terminal peer-to-peer

Abstract

Technologies related to mobile credit payment are disclosed. In an implementation, a first SNEP Get Request Message is generated and sent to a mobile computing device, in response to a NFC signal received from the mobile computing device. A first SNEP Response Message is received from the mobile computing device and parsed to identify an APP public key license. A pre-stored credit authorization public key is used to verify the APP public key license and an APP public key is retrieved from the APP public key license if the verification is successful. A second SNEP Get Request Message is sent to the mobile computing device and a second SNEP Response Message is received from the mobile computing device. The APP public key is then used to decrypt the second SNEP Response Message, and a transaction log is recorded if the second SNEP Response Message is successfully decrypted.

1 .- 20 . (canceled) 
     
     
         21 . A computer-implemented method, comprising:
 receiving, by a server, an application authorization request sent by a mobile computing device;   generating, by the server, an application public key and an application private key based on the application authorization request;   signing, by the server, the application public key by using a locally stored authorization private key to generate an application public key certificate;   sending, by the server, the application public key certificate and the application private key to the mobile computing device;   receiving, by the server, a credit payment data acquisition request sent by the mobile computing device;   generating, by the server, credit payment data corresponding to the mobile computing device based on the credit payment data acquisition request; and   sending, by the server, the credit payment data to the mobile computing device.   
     
     
         22 . The computer-implemented method of  claim 21 , wherein the credit payment data includes a payment card number, a credit limit, an available limit, and a transaction authentication code (TAC) sub-key. 
     
     
         23 . The computer-implemented method of  claim 21 , wherein the credit payment data is used by the mobile computing device to enable a credit payment function. 
     
     
         24 . The computer-implemented method of  claim 21 , wherein before receiving the application authorization request, the method comprises:
 receiving device parameter information sent by the mobile computing device;   determining, based on the device parameter information, that the mobile computing device meets a hardware condition for enabling credit payment; and   sending credit payment enabling information to the mobile computing device.   
     
     
         25 . The computer-implemented method of  claim 24 , wherein the device parameter information includes at least one of a device model, a read-only memory (ROM) version, a system model, or an application version, and wherein the credit payment enabling information includes a credit payment application enabling page. 
     
     
         26 . The computer-implemented method of  claim 21 , wherein before receiving the application authorization request, the method comprises:
 receiving user identity information sent by the mobile computing device;   determining that the mobile computing device meets a security authentication condition for enabling credit payment; and   sending security authentication success information to the mobile computing device.   
     
     
         27 . The computer-implemented method of  claim 26 , wherein the user identity information includes at least one of an ID card number, a name, a bank card number, or an email address. 
     
     
         28 . The computer-implemented method of  claim 21 , wherein before receiving the application authorization request, the method comprises:
 receiving a request for predetermined installation files sent by the mobile computing device, wherein the predetermined installation files include a credit payment application; and   sending the predetermined installation files to the mobile computing device.   
     
     
         29 . A non-transitory, computer-readable medium storing instructions executable by a computer system to perform operations comprising:
 receiving, by a server, an application authorization request sent by a mobile computing device;   generating, by the server, an application public key and an application private key based on the application authorization request;   signing, by the server, the application public key by using a locally stored authorization private key to generate an application public key certificate;   sending, by the server, the application public key certificate and the application private key to the mobile computing device;   receiving, by the server, a credit payment data acquisition request sent by the mobile computing device;   generating, by the server, credit payment data corresponding to the mobile computing device based on the credit payment data acquisition request; and   sending, by the server, the credit payment data to the mobile computing device.   
     
     
         30 . The non-transitory, computer-readable medium of  claim 29 , wherein the credit payment data includes a payment card number, a credit limit, an available limit, and a transaction authentication code (TAC) sub-key. 
     
     
         31 . The non-transitory, computer-readable medium of  claim 29 , wherein the credit payment data is used by the mobile computing device to enable a credit payment function. 
     
     
         32 . The non-transitory, computer-readable medium of  claim 29 , wherein before receiving the application authorization request, the operations comprise:
 receiving device parameter information sent by the mobile computing device;   determining, based on the device parameter information, that the mobile computing device meets a hardware condition for enabling credit payment; and   sending credit payment enabling information to the mobile computing device.   
     
     
         33 . The non-transitory, computer-readable medium of  claim 32 , wherein the device parameter information includes at least one of a device model, a read-only memory (ROM) version, a system model, or an application version, and wherein the credit payment enabling information includes a credit payment application enabling page. 
     
     
         34 . The non-transitory, computer-readable medium of  claim 29 , wherein before receiving the application authorization request, the operations comprise:
 receiving user identity information sent by the mobile computing device;   determining that the mobile computing device meets a security authentication condition for enabling credit payment; and   sending security authentication success information to the mobile computing device.   
     
     
         35 . The non-transitory, computer-readable medium of  claim 34 , wherein the user identity information includes at least one of an ID card number, a name, a bank card number, or an email address. 
     
     
         36 . The non-transitory, computer-readable medium of  claim 29 , wherein before receiving the application authorization request, the operations comprise:
 receiving a request for predetermined installation files sent by the mobile computing device, wherein the predetermined installation files include a credit payment application; and   sending the predetermined installation files to the mobile computing device.   
     
     
         37 . A computer-implemented system, comprising:
 one or more computers; and   one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing instructions that, when executed by the one or more computers, perform operations comprising:
 receiving, by a server, an application authorization request sent by a mobile computing device; 
 generating, by the server, an application public key and an application private key based on the application authorization request; 
 signing, by the server, the application public key by using a locally stored authorization private key to generate an application public key certificate; 
 sending, by the server, the application public key certificate and the application private key to the mobile computing device; 
 receiving, by the server, a credit payment data acquisition request sent by the mobile computing device; 
 generating, by the server, credit payment data corresponding to the mobile computing device based on the credit payment data acquisition request; and 
 sending, by the server, the credit payment data to the mobile computing device. 
   
     
     
         38 . The computer-implemented system of  claim 37 , wherein the credit payment data includes a payment card number, a credit limit, an available limit, and a transaction authentication code (TAC) sub-key. 
     
     
         39 . The computer-implemented system of  claim 37 , wherein the credit payment data is used by the mobile computing device to enable a credit payment function. 
     
     
         40 . The computer-implemented system of  claim 37 , wherein before receiving the application authorization request, the operations comprise:
 receiving device parameter information sent by the mobile computing device;   determining, based on the device parameter information, that the mobile computing device meets a hardware condition for enabling credit payment; and   sending credit payment enabling information to the mobile computing device.