Method and Apparatus for Secure Transaction Management

• US 20110071914A1
• Filed: 09/22/2009
• Published: 03/24/2011
• Est. Priority Date: 09/22/2009
• Status: Active Grant

• Current Assignee: Murphy Oil USA Incorporated (Murphy Oil Corporation)
• Original Assignee: Murphy Oil USA Incorporated (Murphy Oil Corporation)
• Inventors: Beasley, Garland B., Dalton, Raymond, Jarrett, Charles, Jacobson, Jay, Anderson, Alan, Bates, Brian
• Granted Patent: US 9,864,991 B2
• Time in Patent Office: Days
• US Class Current: 705/21
• CPC Class Codes: G06Q 20/105 involving programming of a portable memory device, e.g. IC cards, "electronic purses"
• CPC Class Codes: G06Q 20/202 Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR
• CPC Class Codes: G06Q 20/3223 Realising banking transactions through M-devices
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: G06Q 40/08 Insurance

Abstract

Methods and apparatuses for secure transaction management are provided. An example method may include verifying that a mobile terminal identifier is registered with an account, generating an authorization code, and verifying that the received authorization code matches the authorization code stored in association with the account, and the received customer verification number matches the customer verification number associated with the account. The example method may also include providing for transmission of a verification reply to authorize the transaction.

Claims

1. A method comprising:

receiving an authorization code request and a mobile terminal identifier to initiate a transaction, the received mobile terminal identifier being associated with a mobile terminal;

verifying, by a processor, that the mobile terminal identifier is registered with an account, the mobile terminal identifier and a customer verification number being associated with the account, the customer verification number having not been included in the authorization code request;

generating an authorization code in response to verifying that the mobile terminal identifier is registered;

storing the authorization code in association with the account;

providing for transmission of the authorization code to the mobile terminal;

receiving a verification request from a point of sale terminal, the verification request including a received authorization code, and a received customer verification number provided to the point of sale terminal by a user;

verifying that the received authorization code matches the authorization code stored in association with the account, and the received customer verification number matches the customer verification number associated with the account; and

providing for transmission of a verification reply to the point of sale terminal to authorize the transaction in response to verifying that the received authorization code matches the authorization code stored in association with the account, and the received customer verification number matches the customer verification number associated with the account.

2. The method of claim 1, wherein receiving the authorization code request includes receiving the authorization code request, the authorization code request including price lock parameters.

3. The method of claim 1, wherein receiving the verification request includes receiving an indication of purchase parameters;

and wherein verifying the received authorization code and the received customer verification number includes verifying that the purchase parameters do not violate one or more of a location restriction, a type of good or service restriction, a currency amount limit, an account frequency restriction, a minimum account balance restriction, or a probation period restriction.

4. The method of claim 1, wherein verifying the received authorization code and the received customer verification number includes verifying that the received authorization code matches the authorization code stored in association with the account, and the received customer verification number matches the customer verification number associated with the account, the account being a sub-account of a master account, and wherein the customer verification number is associated with the sub-account.

5. The method of claim 4 further comprising providing for transmission of a notification message indicating transaction activity of the sub-account to a mobile terminal associated with the master account.

6. The method of claim 1, wherein verifying the received authorization code and the received customer verification number includes verifying that the received authorization code matches the authorization code stored in association with the account, and the received customer verification number matches the customer verification number associated with the account, the account being a sub-account of a master account, wherein the mobile terminal identifier is associated with both the master account and the sub-account.

7. The method of claim 1, wherein receiving the authorization code request includes receiving authorization parameters, the authorization parameters including a requested currency amount;

wherein verifying that the mobile terminal identifier is registered includes verifying that the authorization parameters do not violate a transaction restriction; and

wherein generating the authorization code includes generating the authorization code in response to verifying that the authorization parameters do not violate an account rule or transaction restriction.

8. An apparatus comprising a processor, the processor configured to:

receive an authorization code request and a mobile terminal identifier to initiate a transaction, the mobile terminal identifier being associated with a mobile terminal;

verify that the mobile terminal identifier is registered with an account, the mobile terminal identifier and a customer verification number being associated with the account, the customer verification number having not been included in the authorization code request;

generate an authorization code, in response to verifying that the mobile terminal identifier is registered;

store the authorization code in association with the account;

provide for transmission of the authorization code to the mobile terminal;

receive a verification request from a point of sale terminal, the verification request including a received authorization code, and a received customer verification number provided to the point of sale terminal by a user;

verify that the received authorization code matches the authorization code stored in association with the account, and the received customer verification number matches the customer verification number associated with the account; and

provide for transmission of a verification reply to the point of sale terminal to authorize the transaction in response to verifying that the received authorization code matches the authorization code stored in association with the account, and the received customer verification number matches the customer verification number associated with the account.

9. The apparatus of claim 8, wherein the processor configured to receive the authorization code request includes being configured to receive the authorization code request via a short message service transmission, and wherein the processor configured to provide for transmission of the authorization code includes being configured to provide for transmission of the authorization code via a short message service transmission.

10. The apparatus of claim 8, wherein the processor configured to receive the verification request includes being configured to receive an indication of purchase parameters;

and wherein the processor configured to verify the received authorization code and the received customer verification number includes being configured to verify that the purchase parameters do not violate one or more of a location restriction, a type of good or service restriction, a currency amount limit, an account frequency restriction, a minimum account balance restriction, or a probation period restriction.

11. The apparatus of claim 8, wherein the processor configured to verify the received authorization code and the received customer verification number includes being configured to verify that the received authorization code matches the authorization code stored in association with the account, and the received customer verification number matches the customer verification number associated with the account, the account being a sub-account of a master account, and wherein the customer verification number is associated with the sub-account.

12. The apparatus of claim 11, wherein the processor is further configured to provide for transmission of a notification message indicating transaction activity of the sub-account to a mobile terminal associated with the master account.

13. The apparatus of claim 8, wherein the processor configured to verify the received authorization code and the received customer verification number includes being configured to verify that the received authorization code matches the authorization code stored in association with the account, and the received customer verification number matches the customer verification number associated with the account, the account being a sub-account of a master account, wherein the mobile terminal identifier is associated with both the master account and the sub-account.

14. The apparatus of claim 8, wherein the processor configured to receive the authorization code request includes being configured to receive authorization parameters, the authorization parameters including a requested currency amount;

wherein the processor configured to verify that the mobile terminal identifier is registered includes being configured to verify that the authorization parameters do not violate a transaction restriction; and

wherein the processor configured to generate the authorization code includes being configured to generate the authorization code in response to verifying that the authorization parameters do not violate an account rule or transaction restriction.

15. The apparatus of claim 8, wherein the processor configured to receive the authorization code request includes being configured to receive the authorization code request, the authorization code request including price lock parameters.

16. A computer-readable storage medium having executable computer-readable program code instructions stored therein, the computer-readable program code instructions configured to cause an apparatus to:

receive an authorization code request and a mobile terminal identifier to initiate a transaction and request generation of an authorization code, the mobile terminal identifier being associated with a mobile terminal;

verify that the mobile terminal identifier is registered with an account, the mobile terminal identifier and a customer verification number being associated with the account, the customer verification number having not been included in the authorization code request;

receive a verification request from a point of sale terminal, the verification request including a received authorization code, and a received customer verification number provided to the point of sale terminal by a user;

verify that the received authorization code matches an authorization code stored in association with the account, and the received customer verification number matches the customer verification number associated with the account; and

provide for transmission of a verification reply to the point of sale terminal to thereby authorize the transaction in response to verifying that the received authorization code matches the authorization code stored in association with the account, and the received customer verification number matches the customer verification number associated with the account.

17. The computer-readable storage medium of claim 16, wherein the instructions configured to cause the apparatus to receive the authorization code request includes being configured to cause the apparatus to receive the authorization code request via a short message service transmission and wherein providing for transmission of the authorization code includes providing for transmission of the authorization code via a short message service transmission.

18. The computer-readable storage medium of claim 16, wherein the instructions configured to cause the apparatus to receive the verification request include being configured to cause the apparatus to receive an indication of purchase parameters;

and wherein the instructions configured to cause the apparatus to verify the received authorization code and the received customer verification number include being configured to cause the apparatus to verify that the purchase parameters do not violate one or more of a location restriction, a type of good or service restriction, a currency amount limit, an account frequency restriction, a minimum account balance restriction, or a probation period restriction.

19. The computer-readable storage medium of claim 16, wherein the instructions configured to cause the apparatus to verify the received authorization code and the received customer verification number include being configured to cause the apparatus to verify that the received authorization code matches the authorization code stored in association with the account, and the received customer verification number matches the customer verification number associated with the account, the account being a sub-account of a master account, and wherein the customer verification number is associated with the sub-account.

20. The computer-readable storage medium of claim 19, wherein the instructions are further configured to cause the apparatus to provide for transmission of a notification message indicating transaction activity of the sub-account to a mobile terminal associated with the master account.

21. The computer-readable storage medium of claim 16, wherein the instructions configured to cause the apparatus to verify the received authorization code and the received customer verification number include being configured to cause the apparatus to verify that the received authorization code matches the authorization code stored in association with the account, and the received customer verification number matches the customer verification number associated with the account, the account being a sub-account of a master account, wherein the mobile terminal identifier is associated with both the master account and the sub-account.

22. The computer-readable storage medium of claim 16, wherein the instructions configured to cause the apparatus to receive the authorization code request include being configured to cause the apparatus to receive authorization parameters, the authorization parameters including a requested currency amount;

wherein the instructions configured to cause the apparatus to verify that the mobile terminal identifier is registered include being configured to cause the apparatus to verify that the authorization parameters do not violate a transaction restriction; and

wherein the instructions configured cause the apparatus to generate the authorization code include being configured to cause the apparatus to generate the authorization code in response to verifying that the authorization parameters do not violate an account rule or transaction restriction.

23. The computer-readable storage medium of claim 16, wherein the instructions configured to cause the apparatus to receive the authorization code request include being configured to cause the apparatus to receive the authorization code request, the authorization code request including price lock parameters.