SECURE DIGITAL INVOICE PROCESSING

• US 20130246280A1
• Filed: 03/12/2013
• Published: 09/19/2013
• Est. Priority Date: 03/12/2012
• Status: Abandoned Application

• Current Assignee: OneID Inc.
• Original Assignee: OneID Inc.
• Inventors: KIRSCH, STEVEN TODD
• Application Number:
  US13/796,870
• Publication Number:
  US 20130246280A1
• Time in Patent Office: Days
• US Class Current: 705/71
• CPC Class Codes: G06Q 20/023 the neutral party being a clearing house
• CPC Class Codes: G06Q 20/047 using payment protocols involving electronic receipts
• CPC Class Codes: G06Q 20/14 specially adapted for billing systems
• CPC Class Codes: G06Q 20/3825 Use of electronic signatures

Abstract

A method of processing a digital invoice may include receiving, at the access device, a digital invoice for the transaction; sending, from the access device to an identity repository, information associated with the digital invoice; receiving, from the identity repository, a first signature for the digital invoice; providing, by the access device, a second signature for the digital invoice; and sending, from the access device, the first signature and the second signature for use in the transaction.

Claims

1. A method of processing a digital invoice using an access device for a transaction between the access device and a merchant device, the method comprising:

receiving, at the access device, a digital invoice for the transaction;

sending, from the access device to an identity repository, information associated with the digital invoice;

receiving, from the identity repository, a first signature for the digital invoice;

providing, by the access device, a second signature for the digital invoice; and

sending, from the access device, the first signature and the second signature for use in the transaction.

2. The method of claim 1 wherein the digital invoice comprises a transaction price.

3. The method of claim 1 wherein the first signature is associated with a particular payment method.

4. The method of claim 3 wherein the first signature and the second signature are associated with a particular bank or credit card company.

5. The method of claim 1 wherein the first signature and the second signature are associated with corresponding cryptographic keys stored at a payment processing device.

6. The method of claim 1 wherein:

the first signature is generated using a private key; and

a public key corresponding to the private key is stored by a payment processing device.

7. The method of claim 1 further comprising receiving, by the access device, an input comprising a selection of a payment method.

8. The method of claim 1 further comprising:

receiving, from the identity repository, a third signature for the digital invoice, wherein the third signature is provided by a control device; and

sending, from the access device, the third signature for use in the transaction.

9. The method of claim 1 wherein the first and second signatures are configured to be verified by a payment processing device such that the payment processing device can provide a credit card number.

10. The method of claim 1 further comprising:

providing, by the access device, an output comprising a request for a passcode to verify an identity of a user;

receiving, by the access device, an input comprising the passcode; and

sending, from the access device to the identity repository, the information associated with the passcode for the identity repository to verify the identity of the user.

11. The method of claim 1 further comprising:

providing, by the access device, a first identifier that identifies a payment provider;

providing, by the access device, a second identifier that identifies an account at the payment provider; and

sending, from the access device, the first identifier and the second identifier with the first signature and the second signature, wherein;

the first digital signature and the second digital signature are generated using private keys;

the private keys are associated with public keys at the payment provider; and

the public keys are associated with the account or a user of the access device at the payment provider.

12. A method of processing a digital invoice for a transaction between an access device and a merchant device by an identity repository, the method comprising:

receiving, at the identity repository from the access device, information associated with a digital invoice for the transaction;

associating the access device with a virtual identity;

determining that the access device is authorized to participate in the transaction;

providing, by the identity repository, a first signature for the digital invoice; and

sending, from the identity repository to the access device, the first signature.

13. The method of claim 12 wherein the first signature is associated with a selected payment method.

14. The method of claim 12 wherein the first signature is generated by encrypting at least part of the information associated with the digital invoice using a cryptographic key.

15. The method of claim 12 further comprising pre-registering a public key to be stored by a payment processing device, wherein the public corresponds to a private key associated with the virtual identity.

16. The method of claim 12 further comprising:

receiving a selection of a payment method;

retrieving an account identifier associated with the payment method from the virtual identity; and

encrypting the account number to generate the first signature.

17. The method of claim 12 further comprising:

sending, from the identity repository to a control device, request for a second signature; and

receiving, by the identity repository from the control device, a second signature for the digital invoice.

18. An identity repository for providing secure information for a transaction between an access device and a relying party device, the identity repository comprising:

one or more processors; and

a memory communicatively coupled with and readable by the one or more processors and comprising a sequence of instructions which, when executed by the one or more processors, cause the one or more processors to facilitate the transaction by;

receiving, at the identity repository, information associated with a digital invoice for the transaction;

associating the access device with a virtual identity;

determining that the access device is authorized to participate in the transaction;

providing, by the identity repository, a first signature for the digital invoice; and

sending, from the identity repository to the access device, the first signature, wherein the access device provides a second signature for the digital invoice.

19. The identity repository of claim 18 wherein the identity repository is geographically remote from the access device.

20. The identity repository of claim 18 further comprising a fully encrypted repository storing encrypted field/value pairs, wherein:

an account identifier is stored as an encrypted value; and

the account number is associated with a selected payment method.