Systems communications with non-sensitive identifiers

US10325261B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10325261-B2
Application numberUS-201514952514-A
CountryUS
Kind codeB2
Filing dateNov 25, 2015
Priority dateNov 25, 2014
Publication dateJun 18, 2019
Grant dateJun 18, 2019

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A method is disclosed for enabling transaction reversal processes without utilizing sensitive information. Instead of being identified by sensitive information, the transaction associated with a reversal can be identified by a transaction identifier that is generated by a resource provider.

First claim

Opening claim text (preview).

What is claimed is: 1. A method comprising: receiving, by a transaction processing computer, from a resource provider computer associated with a resource provider, an authorization request message for a transaction between a user and the resource provider, the authorization request message including, a transaction identifier that was generated by the resource provider computer, a resource provider identifier that was generated by the transaction processing computer, a primary account number associated with an account of the user, and at least one of a timestamp, a transaction amount, information about purchased items, geo-location information associated with the transaction, or a digital certificate associated with the resource provider; determining, by the transaction processing computer, an authorizing entity identifier associated with an authorizing entity based on the authorization request message; storing, by the transaction processing computer, a transaction record including the resource provider identifier, the transaction identifier, the authorizing entity identifier, and at least one of the timestamp, the transaction amount, the information about purchased items, the geo-location information associated with the transaction, or the digital certificate associated with the resource provider, wherein the primary account number is not stored; transmitting, by the transaction processing computer, the authorization request message to an authorizing entity computer associated with the authorizing entity identifier, wherein the authorizing entity computer authorizes the transaction based on the primary account number; receiving, by the transaction processing computer, an authorization response message including the resource provider identifier and the transaction identifier, and not including the primary account number; transmitting, by the transaction processing computer, the authorization response message to the resource provider computer; receiving, by the transaction processing computer, from the resource provider computer, a request for reversing the transaction, the request including the resource provider identifier, the transaction identifier, and at least one of the timestamp, the transaction amount, the information about purchased items, the geo-location information associated with the transaction, or the digital certificate associated with the resource provider, the request not including the primary account number, wherein the transaction is uniquely identified by a combination of the resource provider identifier and the transaction identifier; identifying, by the transaction processing computer, the transaction record based on the resource provider identifier and the transaction identifier; obtaining, by the transaction processing computer, the authorizing entity identifier from the transaction record; and forwarding, by the transaction processing computer, the request to the authorizing entity computer associated with the authorizing entity identifier, wherein the authorizing entity computer determines the primary account number based on the resource provider identifier and the transaction identifier, and wherein the authorizing entity computer approves of the transaction reversal. 2. The method of claim 1 , wherein the resource provider computer sent the transaction reversal request in response to receiving the transaction identifier and the resource provider identifier from a user device. 3. The method of claim 1 , further comprising: receiving, by the transaction processing computer, from a user device, a request for transaction data, the request including a time, user information, and resource provider information; identifying, by the transaction processing computer, based on the request, the transaction identifier and the resource provider identifier; and providing, by the transaction processing computer, the transaction identifier and the resource provider identifier to the user device. 4. The method of claim 1 , wherein the request for reversing the transaction between the user and the resource provider also does not include a user name, an expiration date, a payment token, or a card verification value. 5. The method of claim 1 , further comprising: generating, by the transaction processing computer, the resource provider identifier for the resource provider; and transmitting, by the transaction processing computer, the resource provider identifier to the resource provider computer. 6. The method of claim 1 , wherein the authorizing entity identifier is an issuer bank identification number. 7. The method of claim 1 , wherein the transaction processing computer is associated with a transaction processing network, wherein the resource provider is a merchant, and wherein the authorizing entity is an issuer. 8. A transaction processing computer comprising: a processor; and a computer readable medium, the computer readable medium comprising code, executable by the processor, for implementing a method comprising: receiving, from a resource provider computer associated with a resource provider, an authorization request message for a transaction between a user and the resource provider, the authorization request message including a transaction identifier that was generated by the resource provider computer, a resource provider identifier that was generated by the transaction processing computer, a primary account number associated with an account of the user, and at least one of a timestamp, a transaction amount, information about purchased items, geo-location information associated with the transaction, or a digital certificate associated with the resource provider; determining an authorizing entity identifier associated with an authorizing entity based on the authorization request message; storing a transaction record including the resource provider identifier, the transaction identifier, the authorizing entity identifier, and at least one of the timestamp, the transaction amount, the information about purchased items, the geo-location information associated with the transaction, or the digital certificate associated with the resource provider, wherein the primary account number is not stored; transmitting the authorization request message to an authorizing entity computer associated with the authorizing entity identifier, wherein the authorizing entity computer authorizes the transaction based on the primary account number; receiving an authorization response message including the resource provider identifier and the transaction identifier, and not including the primary account number; transmitting the authorization response message to the resource provider computer; receiving, from the resource provider computer, a request for reversing the transaction, the request including the resource provider identifier, the transaction identifier, and at least one of the timestamp, the transaction amount, the information about purchased items, the geo-location information associated with the transaction, or the digital certificate associated with the resource provider, the request not including the primary account number, wherein the transaction is uniquely identified by a combination of the resource provider identifier and the transaction identifier; identifying the transaction record based on the resource provider identifier and the transaction identifier; obtaining the authorizing entity identifier from the transaction record; and forwarding the request to the authorizing entity computer associated with the authorizing entity identifier, wherein the authorizing entity computer determines the primary account number based on the resource provider identifier and the transaction identifier, and wherein the authorizing entity computer

Assignees

Inventors

Classifications

  • using an alias or single-use codes · CPC title

  • Business processing using cryptography · CPC title

  • Cancellation of a transaction · CPC title

  • Protecting personal data, e.g. for financial or medical purposes · CPC title

  • Identity check for transactions · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10325261B2 cover?
A method is disclosed for enabling transaction reversal processes without utilizing sensitive information. Instead of being identified by sensitive information, the transaction associated with a reversal can be identified by a transaction identifier that is generated by a resource provider.
Who is the assignee on this patent?
Visa Int Service Ass
What technology area does this patent fall under?
Primary CPC classification G06Q20/4014. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Jun 18 2019 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 2 related publications on this page (citations in our corpus or others sharing the same primary CPC).