Exhibit 2004
`
`Exhibit 2004
`
`
`
`Exhibit 2004
`
`
`
`Case 1:18-cv-03696 Document 1-2 Filed 04/26/18 Page 2 of 7
`U.S. Patent No. 8,887,308: Chase Quickpay Zelle
`Analysis
`Select Evidence
`Chase Quickpay ZELLE
`(CQZ) apparatus performs
`the ‘308 patent process of
`transforming.
`
`Claim 1
`A process for
`transforming a user
`access request for cloud
`digital content into a
`computer readable
`authorization object, the
`process for transforming
`comprising:
`
`Source: https://www.chase.com/personal/quickpay/login-quickpay
`
`US Pat. No. 8,887,308: Chase Quickpay Zelle
`
`Page 1
`
`
`
`Case 1:18-cv-03696 Document 1-2 Filed 04/26/18 Page 3 of 7
`
`
`
`CQZ receives a write request
`a) receiving an access
`for access to Zelle privy cloud
`request for cloud digital
`digital financial data through
`content through an
`a CPU apparatus to write a
`apparatus in process with
`Zelle “token” to storage (see
`at least one CPU, the
`page 6).
`access request being a
`
`write request to a data
`The verification token is the
`store, wherein the data
`user email and mobile
`store is at least one of:
`number.
`a memory connected to
`
`the at least one CPU;
`
`a storage connected to
`
`the at least one CPU;and
`
`a database connected to
`
`the at least one CPU
`
`through the Internet;
`
`wherein the access
`
`request further comprises
`
`verification data provided
`
`by at least one user,
`
`wherein the verification
`
`data is recognized by the
`
`apparatus as a
`
`verification token; then
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`US Pat. No. 8,887,308: Chase Quickpay Zelle
`
`
`Source: https://www.chase.com/content/dam/chasecom/en/personal-banking/documents/Guide_QuickPay.pdf
`Wayback:
`https://web.archive.org/web/20180426111215/https://www.chase.com/content/dam/chasecom/en/personal-
`banking/documents/Guide_QuickPay.pdf
`
`
`
`Source: https://www.zellepay.com/go/chase
`
`
`
`
`
`
`
`
`
`
`Page 2
`
`
`
`Case 1:18-cv-03696 Document 1-2 Filed 04/26/18 Page 4 of 7
`
`CQZ authenticates the
`verification token using a
`verification token database.
`
`b) authenticating the
`verification token of (a)
`using a database
`recognized by the
`apparatus of (a) as a
`verification token
`database; then
`
`Source: https://www.chase.com/content/dam/chasecom/en/personal-banking/documents/Guide_QuickPay.pdf
`Wayback:
`https://web.archive.org/web/20180426111215/https://www.chase.com/content/dam/chasecom/en/personal-
`banking/documents/Guide_QuickPay.pdf
`
`
`
`
`
`
`US Pat. No. 8,887,308: Chase Quickpay Zelle
`
`Page 3
`
`
`
`Case 1:18-cv-03696 Document 1-2 Filed 04/26/18 Page 5 of 7
`
`CQZ establishes a
`connection to the Zelle
`service database related to
`the Zelle services API with an
`assigned credential (e.g.,
`Participant ID, Partner ID).
`
`
`
`Source: https://letstalkpayments.com/interview-with-early-warning-and-clearxchange-the-most-
`powerful-bank-focused-alliance-in-the-authentication-and-digital-payments-industry/
`
`
`
`Source: http://www-01.ibm.com/support/docview.wss?uid=swg27050366&aid=1
`Wayback: https://web.archive.org/web/20180214204352/http://www-
`01.ibm.com/support/docview.wss?uid=swg27050366&aid=1
`
`
`
`
`
`
`
`c) establishing an API
`communication between
`the apparatus of (a) and
`a database apparatus,
`the database apparatus
`being a different
`database from the
`verification token
`database of (b) wherein
`the API is related to a
`verified web service,
`wherein the verified web
`service is a part of the
`database apparatus,
`wherein establishing the
`API communication
`requires a credential
`assigned to the
`apparatus of (a), wherein
`the apparatus assigned
`credential is recognized
`as a permission to
`conduct a data exchange
`session between the
`apparatus of (a) and the
`database apparatus to
`complete the verification
`process, wherein the
`data exchange session is
`also capable of an
`exchange of query data,
`wherein the query data
`comprises at least one
`verified web service
`account identifier; then
`
`
`
`
`
`
`
`
`US Pat. No. 8,887,308: Chase Quickpay Zelle
`
`Page 4
`
`
`
`Case 1:18-cv-03696 Document 1-2 Filed 04/26/18 Page 6 of 7
`
`
`
`
`
`Page 5
`
`
`
`
`
`^Page 24:
`Source: http://www-01.ibm.com/support/docview.wss?uid=swg27050366&aid=1
`Wayback: https://web.archive.org/web/20180214204352/http://www-
`01.ibm.com/support/docview.wss?uid=swg27050366&aid=1
`
`^Page 21
`
`^Page 7, definition of “Token”
`
`
`
`CQZ requests and receives
`query data (computational
`code logic query example:
`what is this user’s Zelle token
`ID for the user’s verified email
`or mobile number?)
`
`The query data request is for
`at least one Zelle web service
`identifier
`(e.g. CXCToken.Create
`register and return a Zelle
`token).
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`d) requesting the query
`data, from the apparatus
`of (a), from the API
`communication data
`exchange session of (c),
`wherein the query data
`request is a request for
`the at least one verified
`web service identifier;
`then
`
`e) receiving the query
`data requested in (d)
`from the API
`communication data
`exchange session of (c);
`and
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`US Pat. No. 8,887,308: Chase Quickpay Zelle
`
` .
`
`
`
`
`
`Case 1:18-cv-03696 Document 1-2 Filed 04/26/18 Page 7 of 7
`
`CQZ creates a computer
`readable Zelle authorization
`object by writing the received
`verification data (e.g., verified
`email or mobile number) and
`the received query data (e.g.,
`A CXCToken entity
`represents a Zelle token) to
`the CQZ apparatus storage
`(e.g., data store).
`
`The Zelle token is used in
`subsequent requests for
`access to Zelle privileged
`cloud financial data to “send
`money” using a cross
`reference action between the
`Zelle token data saved to the
`CQZ data store, and the Zelle
`web service to determine an
`access permission to Zelle
`privy cloud financial data.
`
`f) creating a computer
`readable authorization
`object by writing into the
`data store of (a) at least
`one of:
`the received verification
`data of (a); and
`the received query data
`of (e); wherein
`the created computer
`readable authorization
`object is recognized by
`the apparatus of (a) as
`user access rights
`associated to the cloud
`digital content, wherein
`the computer readable
`authorization object is
`processed by the
`apparatus of (a) using a
`cross-referencing action
`during subsequent user
`access requests to
`determine one or more of
`a user access permission
`for the cloud digital
`content.
`
`US Pat. No. 8,887,308: Chase Quickpay Zelle
`
`Page 6
`
`Source: https://www.zellepay.com/how-it-works
`
`
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
Still Working On It
This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.
Give it another minute or two to complete, and then try the refresh button.
A few More Minutes ... Still Working
It can take up to 5 minutes for us to download a document if the court servers are running slowly.
Thank you for your continued patience.
This document could not be displayed.
We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.
Your account does not support viewing this document.
You need a Paid Account to view this document. Click here to change your account type.
Your account does not support viewing this document.
Set your membership
status to view this document.
With a Docket Alarm membership, you'll
get a whole lot more, including:
- Up-to-date information for this case.
- Email alerts whenever there is an update.
- Full text search for other cases.
- Get email alerts whenever a new case matches your search.
One Moment Please
The filing “” is large (MB) and is being downloaded.
Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.
Your document is on its way!
If you do not receive the document in five minutes, contact support at support@docketalarm.com.
Sealed Document
We are unable to display this document, it may be under a court ordered seal.
If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.
Access Government Site
