METHODS AND SYSTEMS FOR USING A CO-LOCATED GROUP AS AN AUTHORIZATION MECHANISM

• US 20130173467A1
• Filed: 12/29/2011
• Published: 07/04/2013
• Est. Priority Date: 12/29/2011
• Status: Abandoned Application

• Current Assignee: PayPal, Inc. (PayPal Holdings, Inc.)
• Original Assignee: eBay Inc.
• Inventors: Nuzzi, Frank Anthony, Sowder, James Brett
• Application Number:
  US13/340,626
• Publication Number:
  US 20130173467A1
• Time in Patent Office: Days
• US Class Current: 705/44
• CPC Class Codes: G06Q 20/3224 Transactions dependent on location of M-devices
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules

Abstract

Systems and methods to enable a co-located group to be used as an authorization mechanism are discussed. For example, a method to receive a group account configuration, define a group account according to the group account configuration, receive a transaction authorization request associated with the group account, and authorize payment from the group account. The account configuration including a membership list and a target location. The method further including determining whether the transaction authorization request includes data identifying an identified user on the membership list. The method also including determining whether the identified user on the membership list is physically proximate to the target location. The authorizing payment from the group account including verifying that the identified user is determined to be physically proximate to the target location.

Claims

1. A method comprising:

receiving, at a central payment processing server, a group account configuration to define a group account to be hosted on the central payment processing server, the group account configuration including a membership list and a co-location requirement;

defining, on the central payment processing server, a group account according to the group account configuration;

receiving, at the central payment processing server from a mobile device, a transaction authorization request associated with the group account;

determining, on the central payment processing server, whether the transaction authorization request includes data identifying an identified user included in the membership list;

determining, on the central payment processing server, whether the identified user on the membership list satisfies the co-location requirement based at least in part on location data from the mobile device included in the transaction authorization request; and

authorizing, on the central payment processing server, payment from the group account in response to the identified user satisfying the co-location requirement.

2. The method of claim 1, wherein the receiving the group account configuration includes receiving a time period limitation associated with the group account;

and

wherein the authorizing the payment validates that the transaction authorization request is received within the time period limitation.

3. The method of claim 2, wherein the receiving the time period limitation includes receiving a list of dates when the group account is available for paying for transactions initiated by a user included in the membership list.

4. The method of claim 1, wherein receiving the group account configuration includes receiving an authorization limit threshold associated with the group account.

5. The method of claim 4, wherein the authorizing payment from the group account includes validating that the payment amount does not transgress the authorization limit threshold.

6. The method of claim 4, wherein the authorizing payment from the group account includes requesting a secondary authentication when the payment amount transgresses the authorization limit threshold.

7. The method of claim 1, wherein receiving the group account configuration includes receiving a funding rule to govern a source of funds to cover payments authorized against the group account.

8. The method of claim 7, wherein receiving the funding rule includes receiving a funding rule associated with each funding account associated with the group account.

9. The method of claim 8, wherein each member in membership list owns a funding account associated with the group account.

10. The method of claim 7, wherein receiving the funding rule includes receiving a rule to govern a source and amount of a starting balance of funds for the group account.

11. The method of claim 1, wherein the determining whether the identified user satisfies the co-location requirement includes verifying location data received from a mobile device associated with the identified user.

12. The method of claim 11, wherein the determining whether the identified user satisfies the co-location requirement includes verifying a secondary authentication factor.

13. The method of claim 12, wherein the verifying the secondary authentication factor includes receiving and verifying at least one of the following secondary authentication factors:

a password;

a wireless signal; and

a code or PIN entered into the mobile device associated with the identified user.

14. The method of claim 1, wherein the receiving the group account configuration includes receiving data identifying a primary source account and a failover source account;

and

wherein the authorizing payment from the group account includes authorizing payment from the primary source account in response to the primary source account containing sufficient funds.

15. The method of claim 14, wherein the receiving the group account configuration includes receiving a failover source account authorization threshold;

and

wherein authorizing payment from the group account includes authorizing backup funding from the failover source account up to the failover source account authorization threshold in the event the primary source account contains insufficient funds.

21. The method of claim 1, wherein determining whether the identified user satisfies the co-location requirement includes determining whether the identified user is within a pre-defined distance of another user on the membership list.

16. A system comprising:

a central payment processing server coupled to a network to enable communication with a mobile device, the central payment processing server including;

a communication module configured to;

receive, over the network, a group account configuration to define a group account hosted on the central payment processing server, the group account configuration including a membership list and a co-location requirement; and

receive, over the network, a transaction authorization request associated with the group account;

an account module configured to provision a group account according to the group account configuration;

a location module configured to determine whether an identified user on the membership list satisfies the co-location requirement based at least in part on location data from the mobile device included in the transaction authorization request; and

a validation module configured to;

determine whether the transaction authorization request includes data identifying the identified user included in the membership list; and

authorize payment from the group account if the identified user satisfies the co-location requirement.

17. The system of claim 16, wherein the communication module is further configured to receive a time period limitation associated with the group account;

and

wherein the validation module is further configured to authorize payment only if the transaction authorization request is received within the time period limitation.

18. The system of claim 16, wherein the communication module is further configured to receive an authorization limit threshold associated with the group account;

and

wherein the validation module is configured to deny authorization of payment from the group account if the payment amount transgresses the authorization limit threshold.

19. The system of claim 16, wherein the central payment server further includes a rules engine configured to apply a set of group account rules to provisioning of a new group account and to decommissioning an established group account.

20. A non-transitory machine-readable storage medium including instructions that, when executed on a machine, cause the machine to:

receive a group account configuration to define a group account hosted on the central payment processing server, the group account configuration including a membership list and a co-location requirement;

define a group account according to the group account configuration;

receive a transaction authorization request associated with the group account from a mobile device;

determine whether the transaction authorization request includes data identifying an identified user included in the membership list;

determine whether the identified user on the membership list satisfies the co-location requirement based at least in part on location data from the mobile device included in the transaction authorization request; and

authorize payment from the group account in response to the identified user satisfying the co-location requirement.