Secure payment capture processes

• US 8,812,401 B2
• Filed: 11/20/2007
• Issued: 08/19/2014
• 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
• Primary Examiner(s): Hewitt, II, Calvin L
• Assistant Examiner(s): Nilforoush, Mohammad A
• Application Number:
  US11/943,477
• Publication Number:
  US 20090132424A1
• Time in Patent Office: 2,464 Days
• Field of Search: None
• US Class Current: 705/65
• 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 postage metering system using cryptography G06Q2250/05
• 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 with a secure device configured to securely store the payment device information;

storing, by the secure device, 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 retrieve the stored payment device information from the secure device such that the retrieved payment device information is not required to be displayed;

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

receiving, by the client device, status from the payment authorization service that the payment authorization request is approved or declined; and

deleting the stored payment device information from the secure device.

2. The method as recited in claim 1, wherein capturing payment device information with a secure device configured to securely store the 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 with a secure device configured to securely store the 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 retrieve the stored payment device information from the secure device comprises using at least one of a push or pull method to retrieve 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:

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

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

or

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