Secure payment capture processes
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
exact text as granted — not AI-modified1 - 5 . (canceled)
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 - 19 . (canceled)
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.Join the waitlist — get patent alerts
Track US2014358795A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.