SECURE PAYMENT CAPTURE PROCESSES

• US 20090132424A1
• Filed: 11/20/2007
• Published: 05/21/2009
• Est. Priority Date: 11/20/2007
• Status: Active Grant

• Current Assignee: Propay USA Incorporated
• Original Assignee: Propay USA Incorporated
• Inventors: Kendrick, Jeff P., Welling, Darrel Grant, Thacker, Bryce Weldon
• Granted Patent: US 8,812,401 B2
• Time in Patent Office: Days
• US Class Current: 705/75
• CPC Class Codes: G06Q 20/105 involving programming of a portable memory device, e.g. IC cards, "electronic purses"
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/401 Transaction verification
• CPC Class Codes: G06Q 2220/00 Business processing using cryptography
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: H04L 9/50 using hash chains, e.g. blockchains or hash trees

Abstract

Methods and processes for securely capturing payment device information and conveying the securely captured payment device information to a client application on a merchant'"'"'s client device in a manner that does not require that the payment device information to be displayed to the merchant. The client application generates and submits a payment authorization request to a payment authorization service in a manner that does not require the payment information to be displayed to the merchant. The merchant receives a status of the payment authorization request as approved, denied, or process failure. Payment capture can be made before an active connection is made with the merchant'"'"'s client device, or can occur in real-time.

Claims

1. A method for a merchant to perform a financial transaction using a secure device, the method comprising:

capturing payment device information using a secure device having a means of securely storing payment device information;

storing the payment device information in an encrypted format while the secure device does not have an active connection to a client device;

establishing a connection between the secure device and the client device;

using a client application on the client device to read the stored payment device information from the secure device such that the read payment device information is not required to be displayed;

submitting a payment authorization request to a payment authorization service, the payment authorization request including at least some of the read payment device information;

receiving status from the payment authorization service that the payment authorization request is approved, declined, or an instance of process failure; and

deleting the stored payment device information from the secure device.

2. The method as recited in claim 1, wherein capturing payment device information using a secure device having a means of securely storing payment device information comprises the payment device being at least one of:

a bank issued credit card;

a debit card;

a prepaid debit card;

a gift card;

a private label card;

a closed loop payment card;

a smart card;

or

a check.

3. The method as recited in claim 1, wherein capturing payment device information using a secure device having a means of securely storing payment device information comprises the secure device having at least one of:

a magnetic reader;

a magnetic check reader;

an RFID tag reader;

a transponder device;

a smart card reader;

or

a magnetic field detector.

4. The method as recited in claim 1, wherein using a client application on the client device to read the stored payment device information from the secure device comprises using at least one of a push or pull method to read the stored payment device information.

5. The method as recited in claim 1, further comprising limiting additional storage of payment device information on the secure device when at least one of the following occurs:

when the secure device reaches a maximum number of transactions within a given time period;

when the secure device reaches a total amount charged within a given time period;

or

a maximum length of time that payment device information can be stored.

6. A method for a merchant to perform a financial transaction using a secure device, the method comprising:

initiating a secure device;

presenting a payment device to the secure device;

receive confirmation that the payment device is successfully recognized by the secure device

encrypting the payment device information; and

storing at least the encrypted payment device information on the secure device.

7. The method as recited in claim 6, wherein storing at least the encrypted payment device information on the secure device occurs while the secure device does not have an active connection with a client device.

8. The method as recited in claim 6, wherein storing at least the encrypted payment device information on the secure device occurs while the secure device has an active connection with a client device.

9. The method as recited in claim 6, further comprising identifying pricing information and storing pricing information on the secure device.

10. The method as recited in claim 6, further comprising receiving security information into the secure device.

11. A method for a merchant to perform a financial transaction using a secure device, the method comprising:

detecting a secure device on which payment device information has been previously stored;

receive authentication information from a merchant;

reading previously stored payment device information from the secure device;

generating a payment authorization request using at least the stored payment device information;

sending the payment authorization request to a payment authorization service; and

receiving status from the payment authorization service that the payment authorization request is approved, declined, or instance of process failure.

12. The method as recited in claim 11, further comprising deleting the stored payment device information from the secure device.

13. The method as recited in claim 11, wherein reading previously stored payment device information from the secure device comprises using at least one of a push or pull method to read the stored payment device information.

14. The method as recited in claim 11, further comprising limiting additional storage of payment device information on the secure device when at least one of the following occurs:

when the secure device reaches a maximum number of transactions within a given time period;

when the secure device reaches a total amount charged within a given time period;

or

a maximum length of time that payment device information can be stored.

15. The method as recited in claim 11, further comprising populating a transaction record with order information and billing information, wherein the billing information uses at least some of the payment device information.

16. A method for a merchant to perform a financial transaction using a secure device, the method comprising:

generating a payment authorization request using payment device information read from a secure device;

submitting the payment authorization request to a payment authorization service;

receiving status from the payment authorization service that the payment authorization request is approved, declined, or instance of process failure; and

deleting the stored payment device information from the secure device.

17. The method as recited in claim 16, wherein the payment device information comprises at least one of:

an account number;

a name of a payment device owner;

an expiration date;

a service code;

discretionary data;

a routing transit number;

a particular check number;

a PIN into the secure device;

or

biometric information.

18. The method as recited in claim 16, wherein the payment authorization request further includes pricing.

19. The method as recited in claim 16, wherein generating a payment authorization request using payment device information read from a secure device and submitting the payment authorization request to a payment authorization service further are performed such that the payment device information is not required to be displayed.

20. A method for a merchant to perform a financial transaction using a secure device, the method comprising:

establishing an active connection between a client application on a client device and a secure device;

capturing payment device information using the secure device;

using the captured payment device information to generate a payment authorization request such that the payment device information is not required to be displayed; and

submitting the payment authorization request to a payment authorization service;

receiving status from the payment authorization service that the payment authorization request is approved, declined, or instance of process failure; and

monitoring the secure device to ensure that the captured payment device information is not stored permanently on the secure device.

21. The method as recited in claim 20, wherein capturing payment device information using the secure device comprises storing the captured payment device information on the secure device in an encrypted manner.

22. The method as recited in claim 20, wherein capturing payment device information using the secure device comprises not storing the captured payment device information on the secure device, and passing the captured payment device information to the client device in an encrypted manner.

23. The method as recited in claim 20, wherein monitoring the secure device to ensure that the captured payment device information is not stored permanently on the secure device comprises deleting one or more transactions from the service device if at least one of the following occurs:

the secure device reaches a maximum number of transactions within a given time period;

the secure device reaches a total amount charged within a given time period;

or

a maximum length of time has occurred that payment device information can be stored.

24. The method as recited in claim 20, further comprising identifying order information and populating a transaction record with the order information.

25. The method as recited in claim 20, wherein the payment device information comprises at least one of:

an account number;

a name of a payment device owner;

an expiration date;

a service code;

discretionary data;

a routing transit number;

a particular check number;

a PIN into the secure device;

or

biometric information.