Techniques for peer entity account management
Techniques and apparatus for providing peer-based management of user accounts are described. In one embodiment, for example, an apparatus may include at least one memory and logic coupled to the at least one memory. The logic may be configured to receive a request from at least one first user account to unlock a second user account locked responsive to a fraud event, determine a safe authentication value for the fraud event, and unlock the second user account responsive to the at least one first user account being a safe authentication account and the safe authentication value being over a safe authentication threshold value. Other embodiments are described.
1. A computing device, comprising:
a storage device; and
logic, at least a portion of the logic implemented in circuitry coupled to the storage device, the logic to:
designate at least one first user account as a safe authentication account based on a safe authentication score, the safe authentication account permitted to unlock other user accounts;
receive a request from at least one first user account to unlock a second user account locked responsive to a fraud event associated with a transaction,
determine a safe authentication value for the fraud event, the safe authentication value to indicate a risk level associated with the transaction,
determine whether the at least one first user account is a safe authentication account,
unlock the second user account responsive to the at least one first user account being the safe authentication account and the safe authentication value being greater than a safe authentication threshold value.
2. The computing device of claim 1 , the logic to unlock the second user account responsive to receiving at least one identifier for the second user account from at least one first computing device associated with the at least one first user account.
3. The computing device of claim 2 , the logic to send the at least one identifier to a second computing device associated with the second user account.
4. The computing device of claim 3 , the at least one identifier comprising a secret code.
5. The computing device of claim 2 , the at least one identifier comprising a profile element of the second user account, the profile element comprising at least one of an email address, a user name, a phone number, a device identifier, or an account identifier.
6. The computing device of claim 1 , the logic to determine the safe authentication score based on transactions associated with the user account.
7. The computing device of claim 1 , the logic to determine the safe authentication score based on a level of risk associated with the user account.
8. The computing device of claim 1 , the at least one first user account and the second user account comprising peer accounts.
9. The computing device of claim 8 , the peer accounts comprising at least one of a consumer credit card account, a business credit card account, a consumer bank account, or a business bank account.
10. The computing device of claim 1 , the logic to unlock the second user account responsive to a plurality of successful requests from a plurality of user accounts if the safe authentication value is greater than a multiple user account threshold.
11. A computing device, comprising:
a storage device; and
logic, at least a portion of the logic implemented in circuitry coupled to the storage device, the logic to:
designate a first user account as a safe authentication account based on a safe authentication score, the safe authentication account permitted to unlock other user accounts,
provide a request to unlock a second user account locked responsive to a fraud event associated with a transaction initiated by the second user account, the fraud event associated with a safe authentication value greater than a save authentication threshold, the safe authentication value to indicate a risk level associated with the transaction,
receive a request for at least one identifier associated with the second user account, and
transmit the at least one identifier to unlock the second user account.
12. The computing device of claim 11 , the at least one identifier comprising at least one of a profile element of the second user account or a secret code transmitted to a second computing device associated with the second computing device.
13. The computing device of claim 11 , the logic to determine the safe authentication score based on transactions associated with the at least one first user account.
14. The computing device of claim 11 , the at least one first user account and the second user account comprising peer accounts.
15. A computer-implemented method, comprising, by a processor of a computing device:
designating at least one first user account as a safe authentication account based on a safe authentication score, the safe authentication account permitted to unlock other user accounts;
receiving a request from at least one first user account to unlock a second user account locked responsive to a fraud event associated with a transaction;
determining a safe authentication value for the fraud event, the safe authentication value to indicate a risk level associated with the transaction;
determining whether the at least one first user account is a safe authentication account; and
unlock the second user account responsive to the at least one first user account being the safe authentication account and the safe authentication value being greater than a safe authentication threshold value.
16. The computer-implemented method of claim 15 , comprising unlocking the second user account responsive to receiving at least one identifier for the second user account from at least one first computing device associated with the at least one first user account.
17. The computer-implemented method of claim 16 , comprising sending the at least one identifier to a second computing device associated with the second user account.
18. The computer-implemented method of claim 15 , further comprising:
unlocking the second user account responsive to receiving at least one identifier for the second user account from at least one first computing device associated with the at least one first user account;
sending the at least one identifier to a second computing device associated with the second user account; and
designating a user account as the safe authentication account based on a safe authentication score, the safe authentication score based on transactions associated with the user account;
wherein the at least one first user account and the second user account comprising peer accounts,
wherein the at least one identifier comprises at least one of a secret code or a profile element of the second user account, the profile element comprising at least one of an email address, a user name, a phone number, a device identifier, or an account identifier.