Payment card binding method, trust evaluation method, apparatus, and electronic device

• US 10,902,415 B2
• Filed: 05/21/2020
• Issued: 01/26/2021
• Est. Priority Date: 01/23/2018
• Status: Active Grant

• Current Assignee: Advanced New Technologies Company Limited (Ant Group Co., Ltd.)
• Original Assignee: Advanced New Technologies Company Limited (Ant Group Co., Ltd.)
• Inventors: Zhu, Jinbiao
• Primary Examiner(s): Kalinowski, Alexander G
• Assistant Examiner(s): Bunker, William B.
• Application Number:
  US16/880,315
• Publication Number:
  US 20200279248A1
• Time in Patent Office: 250 Days
• CPC Class Codes: G06Q 20/105 involving programming of a portable memory device, e.g. IC cards, "electronic purses"
• CPC Class Codes: G06Q 20/3224 Transactions dependent on location of M-devices
• CPC Class Codes: G06Q 20/34 using cards, e.g. integrated circuit [IC] cards or magnetic cards
• CPC Class Codes: G06Q 20/367 involving electronic purses or money safes
• CPC Class Codes: G06Q 20/4016 involving fraud or risk level assessment in transaction processing
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules
• CPC Class Codes: G06Q 20/409 Device specific authentication in transaction processing

Abstract

A payment card binding method, a trust evaluation method, an apparatus, and an electronic device are provided. The payment card binding method includes: receiving a payment card binding request; sending a payment request to a payment system; in response to the payment request being successfully processed by the payment system, determining (1) an account trust level, (2) a device trust level, and (3) an environment trust level; inputting the account trust level, the device trust level, and the environment trust level into a trained classifier to determine a new card trust level (NCTL); determining a payment limit restriction for the digital wallet account using the payment card on the computing device; and binding, based on the NCTL and the payment limit restriction, the digital wallet account with the payment card for the digital wallet account to use the payment card for future payments.

Claims

1. A computer-implemented method, comprising:

receiving, at a server, a payment card binding request from a digital wallet client installed on a computing device of a user to bind a new payment card of the user with a digital wallet account, wherein the payment card binding request comprises account data of the digital wallet account, device data of the computing device, environment data of the computing device, and account information of the payment card, wherein;

the account data comprises;

an account identifier, a registration time, or personal information of an account owner;

the device data comprises;

a device identifier of the computing device or a media access control (MAC) address of the computing device; and

the environment data comprises;

a name of a wireless network connected to the computing device, an IP address of the computing device, or location information of the computing device;

sending a micro charge payment request from the server to a payment system according to the account information of the payment card, wherein the micro charge payment request is to verify the validity of the payment card;

in response to the micro charge payment request being successfully processed by the payment system, sending from the server to a risk control system associated with the server a request to determine (1) an account trust level based on the account data, (2) a device trust level based on the device data, and (3) an environment trust level based on the environment data, wherein the risk control system is configured to;

input the determined account trust level, the device trust level, and the environment trust level into a trained new card trust level (NCTL) model to determine a NCTL, wherein the NCTL model is trained to provide a plurality of weights respectively corresponding to the account trust level, the device trust level, and the environment trust level, and wherein the NCTL model is trained based on a plurality of historical payment card binding requests of a plurality of wallet accounts, and historical transaction data of the plurality of wallet accounts; and

determine, based on the NCTL, a payment limit restriction for the digital wallet account using the payment card on the computing device;

binding, at the server, based on the NCTL and the payment limit restriction, the digital wallet account with the payment card for the digital wallet account to use the payment card for future payments;

receiving, at the server, a subsequent payment request to make a payment with the digital wallet account using the payment card;

sending, from the server to the risk control system, a verification request to perform verification to determine whether to allow the subsequent payment request, wherein the verification is based on a payment amount of the subsequent payment request and the NCTL and the payment limit restriction at the time of the subsequent payment request;

receiving, at the server, from the risk control system, a response to the verification request; and

wherein the risk control system is configured to adjust the NCTL and the payment limit restriction based on transaction records or payment refusal records generated after the payment card is bound to the digital wallet account.

2. The method according to claim 1, wherein sending the micro charge payment request to the payment system according to the account information of the payment card comprises:

sending a withdrawal request to the payment system to withdraw a randomly generated payment amount from an account associated with the payment card; and

receiving a success response from the payment system after the payment system approves the withdrawal request.

3. The method according to claim 2, further comprising:

recharging the randomly generated payment amount into the account associated with the payment card.

4. The method according to claim 1, further comprising:

adjusting the NCTL based on payment refusal records and transaction records that occurred after the digital wallet account is bound with the payment card.

5. The method according to claim 1, further comprising:

sending the subsequent payment request to the payment system to process;

determining whether the subsequent payment request should be processed by the payment system according to the payment amount and the payment limit restriction; and

if not, sending an offset request to the payment system to revoke the second payment request.

6. The method according to claim 1, further comprising:

determining whether the subsequent payment request should be processed according to the payment amount and the payment limit restriction; and

if yes, sending the subsequent payment request to the payment system to process.

7. The method according to claim 1, wherein sending from the server to the risk control system the request to determine (1) the account trust level based on the account data, (2) the device trust level based on the device data, and (3) the environment trust level based on the environment data comprises:

sending through an API of the risk control system, the account data of the digital wallet account, the device data of the computing device, and the environment data of the computing device to the risk control system.

8. A system comprising one or more processors and one or more non-transitory computer-readable storage mediums storing instructions executable by the one or more processors to cause the system to perform operations comprising:

receiving, at a server, a payment card binding request from a digital wallet client installed on a computing device of a user to bind a new payment card of the user with a digital wallet account, wherein the payment card binding request comprises account data of the digital wallet account, device data of the computing device, environment data of the computing device, and account information of the payment card, wherein;

the account data comprises;

an account identifier, a registration time, or personal information of an account owner;

the device data comprises;

a device identifier of the computing device or a media access control (MAC) address of the computing device; and

the environment data comprises;

a name of a wireless network connected to the computing device, an IP address of the computing device, or location information of the computing device;

sending a micro charge payment request from the server to a payment system according to the account information of the payment card, wherein the micro charge payment request is to verify the validity of the payment card;

in response to the micro charge payment request being successfully processed by the payment system, sending from the server to a risk control system associated with the server a request to determine (1) an account trust level based on the account data, (2) a device trust level based on the device data, and (3) an environment trust level based on the environment data, wherein the risk control system is configured to;

input the determined account trust level, the device trust level, and the environment trust level into a trained new card trust level (NCTL) model to determine a NCTL, wherein the NCTL model is trained to provide a plurality of weights respectively corresponding to the account trust level, the device trust level, and the environment trust level, and wherein the NCTL model is trained based on a plurality of historical payment card binding requests of a plurality of wallet accounts, and historical transaction data of the plurality of wallet accounts; and

determine, based on the NCTL, a payment limit restriction for the digital wallet account using the payment card on the computing device;

binding, at the server, based on the NCTL and the payment limit restriction, the digital wallet account with the payment card for the digital wallet account to use the payment card for future payments;

receiving, at the server, a subsequent payment request to make a payment with the digital wallet account using the payment card;

sending, from the server to the risk control system, a verification request to perform verification to determine whether to allow the subsequent payment request, wherein the verification is based on a payment amount of the subsequent payment request and the NCTL and the payment limit restriction at the time of the subsequent payment request;

receiving, at the server, from the risk control system, a response to the verification request; and

wherein the risk control system is configured to adjust the NCTL and the payment limit restriction based on transaction records or payment refusal records generated after the payment card is bound to the digital wallet account.

9. The system according to claim 8, wherein sending the micro charge payment request to the payment system according to the account information of the payment card comprises:

sending a withdrawal request to the payment system to withdraw a randomly generated payment amount from an account associated with the payment card; and

receiving a success response from the payment system after the payment system approves the withdrawal request.

10. The system according to claim 8, wherein the operations further comprise:

sending the subsequent payment request to the payment system to process;

determining whether the subsequent payment request should be processed by the payment system according to the payment amount and the payment limit restriction; and

if not, sending an offset request to the payment system to revoke the second payment request.

11. The system according to claim 8, wherein the operations further comprise:

determining whether the subsequent payment request should be processed according to the payment amount and the payment limit restriction; and

if yes, sending the subsequent payment request to the payment system to process.

12. One or more non-transitory computer-readable storage mediums configured with instructions executable by one or more processors to cause the one or more processors to perform operations comprising:

receiving, at a server, a payment card binding request from a digital wallet client installed on a computing device of a user to bind a new payment card of the user with a digital wallet account, wherein the payment card binding request comprises account data of the digital wallet account, device data of the computing device, environment data of the computing device, and account information of the payment card, wherein;

the account data comprises;

an account identifier, a registration time, or personal information of an account owner;

the device data comprises;

a device identifier of the computing device or a media access control (MAC) address of the computing device; and

the environment data comprises;

a name of a wireless network connected to the computing device, an IP address of the computing device, or location information of the computing device;

sending a micro charge payment request from the server to a payment system according to the account information of the payment card, wherein the micro charge payment request is to verify the validity of the payment card;

in response to the micro charge payment request being successfully processed by the payment system, sending from the server to a risk control system associated with the server a request to determine (1) an account trust level based on the account data, (2) a device trust level based on the device data, and (3) an environment trust level based on the environment data, wherein the risk control system is configured to;

input the determined account trust level, the device trust level, and the environment trust level into a trained new card trust level (NCTL) model to determine a NCTL, wherein the NCTL model is trained to provide a plurality of weights respectively corresponding to the account trust level, the device trust level, and the environment trust level, and wherein the NCTL model is trained based on a plurality of historical payment card binding requests of a plurality of wallet accounts, and historical transaction data of the plurality of wallet accounts; and

determine, based on the NCTL, a payment limit restriction for the digital wallet account using the payment card on the computing device;

binding, at the server, based on the NCTL and the payment limit restriction, the digital wallet account with the payment card for the digital wallet account to use the payment card for future payments;

receiving, at the server, a subsequent payment request to make a payment with the digital wallet account using the payment card;

sending, from the server to the risk control system, a verification request to perform verification to determine whether to allow the subsequent payment request, wherein the verification is based on a payment amount of the subsequent payment request and the NCTL and the payment limit restriction at the time of the subsequent payment request;

receiving, at the server, from the risk control system, a response to the verification request; and

wherein the risk control system is configured to adjust the NCTL and the payment limit restriction based on transaction records or payment refusal records generated after the payment card is bound to the digital wallet account.

13. The one or more non-transitory computer-readable storage mediums according to claim 12, wherein sending the micro charge payment request to the payment system according to the account information of the payment card comprises:

sending a withdrawal request to the payment system to withdraw a randomly generated payment amount from an account associated with the payment card; and

receiving a success response from the payment system after the payment system approves the withdrawal request.

14. The one or more non-transitory computer-readable storage mediums according to claim 12, wherein the operations further comprise:

sending the subsequent payment request to the payment system to process;

determining whether the subsequent payment request should be processed by the payment system according to the payment amount and the payment limit restriction; and

if not, sending an offset request to the payment system to revoke the second payment request.

15. The one or more non-transitory computer-readable storage mediums according to claim 12, wherein the operations further comprise:

determining whether the subsequent payment request should be processed according to the payment amount and the payment limit restriction; and

if yes, sending the subsequent payment request to the payment system to process.