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.
Claims
exact text as granted — not AI-modified1 .- 20 . (canceled)
21 . A computer-implemented method, comprising:
sending, by a mobile computing device, an application authorization request to a predetermined server by using a credit authorization system application on the mobile computing device; receiving, by the mobile computing device, an application public key certificate and an application private key that are sent by the predetermined server; storing, by the mobile computing device, the application public key certificate and the application private key in a credit payment application on the mobile computing device, wherein the application public key certificate and the application private key are used to complete a credit payment transaction; sending, by the mobile computing device, a credit payment data acquisition request to the predetermined server; receiving, by the mobile computing device, credit payment data sent by the predetermined server; and enabling, by the mobile computing device, a credit payment function of the mobile computing device based on the credit payment data.
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 before sending the application authorization request, the method comprises:
obtaining device parameter information of the mobile computing device; sending the device parameter information to the predetermined server; receiving credit payment enabling information sent by the predetermined server; and determining that the mobile computing device meets a hardware condition for enabling credit payment.
24 . The computer-implemented method of claim 23 , 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.
25 . The computer-implemented method of claim 21 , wherein before sending the application authorization request, the method comprises:
obtaining user identity information corresponding to the mobile computing device; sending the user identity information to the predetermined server; receiving security authentication success information sent by the predetermined server; and determining that the mobile computing device meets a security authentication condition for enabling credit payment.
26 . The computer-implemented method of claim 25 , wherein the user identity information includes at least one of an ID card number, a name, a bank card number, or an email address.
27 . The computer-implemented method of claim 21 , wherein before sending the application authorization request, the method comprises:
sending a request for predetermined installation files to the predetermined server, wherein the predetermined installation files include the credit payment application; receiving the predetermined installation files sent by the predetermined server; and installing the predetermined installation files on the mobile computing device.
28 . A non-transitory, computer-readable medium storing instructions executable by a computer system to perform operations comprising:
sending an application authorization request to a predetermined server by using a credit authorization system application on the computer system; receiving an application public key certificate and an application private key that are sent by the predetermined server; storing the application public key certificate and the application private key in a credit payment application on the computer system, wherein the application public key certificate and the application private key are used to complete a credit payment transaction; sending a credit payment data acquisition request to the predetermined server; receiving credit payment data sent by the predetermined server; and enabling a credit payment function of the computer system based on the credit payment data.
29 . The non-transitory, computer-readable medium of claim 28 , wherein the credit payment data includes a payment card number, a credit limit, an available limit, and a transaction authentication code (TAC) sub-key.
30 . The non-transitory, computer-readable medium of claim 28 , wherein before sending the application authorization request, the operations comprise:
obtaining device parameter information of the computer system; sending the device parameter information to the predetermined server; receiving credit payment enabling information sent by the predetermined server; and determining that the computer system meets a hardware condition for enabling credit payment.
31 . The non-transitory, computer-readable medium of claim 30 , 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.
32 . The non-transitory, computer-readable medium of claim 28 , wherein before sending the application authorization request, the operations comprise:
obtaining user identity information corresponding to the computer system; sending the user identity information to the predetermined server; receiving security authentication success information sent by the predetermined server; and determining that the computer system meets a security authentication condition for enabling credit payment.
33 . The non-transitory, computer-readable medium of claim 32 , wherein the user identity information includes at least one of an ID card number, a name, a bank card number, or an email address.
34 . The non-transitory, computer-readable medium of claim 28 , wherein before sending the application authorization request, the operations comprise:
sending a request for predetermined installation files to the predetermined server, wherein the predetermined installation files include the credit payment application; receiving the predetermined installation files sent by the predetermined server; and installing the predetermined installation files on the computer system.
35 . 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:
sending, by a computer, an application authorization request to a predetermined server by using a credit authorization system application on the computer;
receiving, by the computer, an application public key certificate and an application private key that are sent by the predetermined server;
storing, by the computer, the application public key certificate and the application private key in a credit payment application on the computer, wherein the application public key certificate and the application private key are used to complete a credit payment transaction;
sending, by the computer, a credit payment data acquisition request to the predetermined server;
receiving, by the computer, credit payment data sent by the predetermined server; and
enabling, by the computer, a credit payment function of the computer based on the credit payment data.
36 . The computer-implemented system of claim 35 , wherein the credit payment data includes a payment card number, a credit limit, an available limit, and a transaction authentication code (TAC) sub-key.
37 . The computer-implemented system of claim 35 , wherein before sending the application authorization request, the operations comprise:
obtaining device parameter information of the computer; sending the device parameter information to the predetermined server; receiving credit payment enabling information sent by the predetermined server; and determining that the computer meets a hardware condition for enabling credit payment.
38 . The computer-implemented system of claim 37 , 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.
39 . The computer-implemented system of claim 35 , wherein before sending the application authorization request, the operations comprise:
obtaining user identity information corresponding to the computer; sending the user identity information to the predetermined server; receiving security authentication success information sent by the predetermined server; and determining that the computer meets a security authentication condition for enabling credit payment.
40 . The computer-implemented system of claim 39 , wherein the user identity information includes at least one of an ID card number, a name, a bank card number, or an email address.Join the waitlist — get patent alerts
Track US2022156741A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.