Payment verification method and apparatus

Patent metadata

Field	Value
Publication number	US-11055720-B2
Application number	US-201616312917-A
Country	US
Kind code	B2
Filing date	Jun 29, 2016
Priority date	Jun 29, 2016
Publication date	Jul 6, 2021
Grant date	Jul 6, 2021

Abstract

A payment verification method and apparatus are disclosed. The method includes: if a payment terminal detects that there is valid verification information in a secure storage of the payment terminal, changing, by the payment terminal, a cardholder verification method (CVM) supported by a currently used payment card to “no CVM required”, where the payment card is a preset card or a card selected by a user, and the secure storage of the payment terminal is a trusted storage area in a trusted execution environment (TEE) or a secure storage area in a rich execution environment (REE); and notifying, by the payment terminal, the settlement terminal that the CVM supported by the payment card is “no CVM required”, so that the settlement terminal performs verification on the user and completes a transaction according to “no CVM required”.

First claim

What is claimed is:

1. A method, comprising:
detecting, by a payment terminal, first verification information in a secure storage of the payment terminal, the first verification information comprising a quantity of payment transactions, and the secure storage of the payment terminal being a trusted storage area in a trusted execution environment (TEE) or a secure storage area in a rich execution environment (REE);
determining, by the payment terminal, whether the first verification information is valid, wherein determining whether the first verification information is valid comprises determining whether the quantity of payment transactions exceeds a threshold;
sending, by the payment terminal to a cloud verification server, in response to determining that the first verification information is invalid, a verification request that comprises a verification parameter, wherein the verification parameter comprises a cardholder telephone number of a card bound to a user program of the payment terminal;
receiving, by the payment terminal from the cloud verification server, second verification information, the second verification information having been generated and sent based on successful verification of the verification parameter;
changing, by the payment terminal in response to determining that the second verification information is valid, a cardholder verification method (CVM) supported by a currently-used payment card to a no CVM required payment method, the currently-used payment card having been preset or selected by a user; and
notifying, by the payment terminal, a settlement terminal that the CVM supported by the currently-used payment card is the no CVM required payment method, causing the settlement terminal to perform verification on the user and to complete a payment transaction according to the no CVM required payment method.

2. The method according to claim 1 , further comprising:
receiving, by the payment terminal, first identity verification data; and
determining, by the payment terminal, that the first identity verification data matches second identity verification data stored in the secure storage of the payment terminal.

3. The method according to claim 1 , wherein:
the first verification information further comprises a validity period parameter indicating a time period during which the first verification information is valid;
the validity period parameter is a preset validity time set by the cloud verification server; and
determining whether the first verification information is valid further comprises:
determining, by the payment terminal, whether the preset validity time corresponding to the first verification information has not expired.

4. The method according to claim 1 , wherein:
the quantity of payment transactions has been set by the cloud verification server;
the threshold is equal to zero; and
the method further comprises:
decrementing, by the payment terminal in response to the payment terminal performing a successful payment transaction using the currently-used payment card, the quantity of payment transactions by one.

5. The method according to claim 1 , further comprising:
obtaining, by the payment terminal, a terminal transaction attribute of the settlement terminal, the terminal transaction attribute indicating a CVM method supported by the settlement terminal; and
determining, by the payment terminal according to the terminal transaction attribute, that the settlement terminal does not support a consumer device cardholder verification method (CD-CVM).

6. The method according to claim 5 , wherein obtaining the terminal transaction attribute of the settlement terminal comprises:
receiving, by the payment terminal from the settlement terminal, a select application identifier (SELECT AID) command; and
sending, by the payment terminal to the settlement terminal, a processing options data object list (PDOL) requesting the terminal transaction attribute of the settlement terminal.

7. The method according to claim 1 , further comprising:
receiving, by the payment terminal, a transaction success notification pushed by the cloud verification server;
marking, by the payment terminal in a transaction log, a type of the payment transaction as a downgraded CVM transaction; and
synchronizing, by the payment terminal, the transaction log to the cloud verification server.

8. A payment terminal, comprising:
a near field communication (NFC) module;
a processor; and
a non-transitory computer readable storage medium storing instructions that, when executed by the processor, cause the processor to:
detect first verification information in a secure storage of the payment terminal, the first verification information comprising a quantity of payment transactions, wherein the secure storage of the payment terminal is a trusted storage area in a trusted execution environment (TEE) or a secure storage area in a rich execution environment (REE);
determine whether the first verification information is valid, wherein determining whether the first verification information is valid comprises determining whether the quantity of payment transactions exceeds a threshold; and

send, to a cloud verification server, in response to determining that the first verification information is invalid, a verification request that comprises a verification parameter, wherein the verification parameter comprises a cardholder telephone number of a card bound to a user Program of the payment terminal;
receive, from the cloud verification server, second verification information, the second verification information having been generated and sent based on successful verification of the verification parameter;
change, in response to determining that the second verification information is valid, a cardholder verification method (CVM) supported by a currently-used payment card to a no CVM required payment method, wherein the currently-used payment card has been preset card or selected by a user; and

wherein the NFC module is configured to notify a settlement terminal that the CVM supported by the currently-used payment card is the no CVM required payment method, causing the settlement terminal to perform a verification on the user and to complete a payment transaction according to the no CVM required payment method.

9. The payment terminal according to claim 8 , wherein the payment terminal further comprises a transceiver and a Wi-Fi module;
wherein the transceiver or the Wi-Fi module is configured to receive first identity verification data; and
wherein the processor is configured to determine that the first identity verification data matches second identity verification data that is stored in the secure storage.

10. The payment terminal according to claim 8 , wherein:
the first verification information further comprises a validity period parameter indicating a time period during which the first verification information is valid;
the validity period parameter is a preset validity time set by the cloud verification server; and
determining whether the first verification information is valid further comprises determining whether the preset validity time corresponding to the first verification information has not expired.

11. The payment terminal according to claim 8 , wherein:
the quantity of payment transactions has been set by the cloud verification server;
the threshold is equal to zero; and
the processor is further configured to decrement, in response to the payment terminal performing a successful payment transaction using the currently-used payment card, the quantity of payment transactions by one.

12. The payment terminal according to clai

Assignees

• Huawei Tech Co Ltd
• Huawei Tech Co Lid

Inventors

• Li Guoqing
• Mei Jingqing

Classifications

• G06Q20/3278 Primary

  RFID or NFC payments by means of M-devices · CPC title

• G06Q20/386

  using messaging services or messaging apps (using mobile network messaging services for payment, e.g. SMS G06Q20/3255) · CPC title

• G06Q20/409 Primary

  Device specific authentication in transaction processing · CPC title

• G06Q20/4014

  Identity check for transactions · CPC title

• G06Q20/3227

  using secure elements embedded in M-devices · CPC title