Access denied | nyaso.com used Cloudflare to restrict access
Please enable cookies.
What happened?
The owner of this website (nyaso.com) has banned your access based on your browser's signature (44cc7-ua98).Follow us on Twitter
Browse patents:
Dynamic account identifier with return real account identifier
Title: Dynamic account identifier with return real account identifier.Abstract: Embodiments of the invention are directed to systems, apparatus, and methods for receiving an account token for a transaction, and returning an associated real account identifier if the transaction is approved. In one embodiment, an authorization request message for a transaction is received by a server computer, the authorization request message including an account token associated with a real account identifier. The server computer determines the real account identifier associated with the account token. If the transaction is approved, an authorization response message including the real account identifier is transmitted. ...
USPTO Applicaton #: #
Inventors: ,
The Patent Description & Claims data below is from USPTO Patent Application , Dynamic account identifier with return real account identifier.
CROSS-REFERENCES TO RELATED APPLICATIONS
The present application is a non-provisional application of and claims priority to U.S. Provisional Application No. 61/734,863, filed on Dec. 7, 2012, the entire contents of which are herein incorporated by reference for all purposes.
BACKGROUND
The use of tokenization is becoming increasingly popular in the context of electronic payment transactions using credit card accounts, debit card accounts, prepaid accounts, checking accounts, and the like. Tokenization refers to the process of converting financial account information, such as a primary account number (PAN) or other real account identifier into an account token, which may be used in lieu of the real account identifier to conduct an electronic payment transaction with a merchant for goods or services. For instance, a tokenization algorithm can be used to transform a real account identifier into an account token by replacing all or a portion of the real account identifier with one or more valueless stand-in numbers, letters, symbols, or other characters, or the real account identifier can be replaced altogether by a different static or dynamic value.
Account tokens may be stored and utilized by merchants and acquirers (e.g., in customer “cards on file” databases), by users (e.g., on a payment card or accessible via an electronic wallet client facilitated by a mobile device), issuers, processors, and other entities that participate in electronic payment transactions. Although the use of account tokens can provide advantages such as improved security and convenience, such tokens may also introduce a number of disadvantages. For instance, merchants or acquirers may need access to real account identifiers to facilitate returns, refunds, and other post-transaction activity. Similarly, since the relationship between an account token and a specific user may not be readily ascertainable, real account identifiers may be needed by merchants or acquirers to perform services such as customer loyalty programs, analytics, targeted marketing, and the like. Moreover, account token formats may be incompatible with existing clearing and settlement processes and infrastructure utilized by acquirers, issuers, payment processing networks, and the like.
Some of the aforementioned disadvantages may be remedied by real account identifiers being provided to merchants and their acquirers as part of the electronic payment transaction flow. However, providing such sensitive information for all transactions may negate many of the advantages provided by account tokens, such as the ability to protect the customer's privacy from hackers, fraudsters, and unscrupulous merchants.
Embodiments of the present invention address these problems and other problems individually and collectively.
BRIEF SUMMARY
Embodiments of the invention are directed to systems, apparatus, and methods for receiving an account token for a transaction, and returning an associated real account identifier if the transaction is approved.
One embodiment of the invention is directed to a method. The method comprises receiving, by a server computer, an authorization request message for a transaction, the authorization request message including an account token associated with a real account identifier. The server computer determines the real account identifier associated with the account token. If the transaction is approved, an authorization response message including the real account identifier is transmitted.
Another embodiment of the invention is directed to a server computer comprising a processor and a computer-readable medium coupled to the processor. The computer-readable medium includes code executable by a processor for performing a method. The method comprises receiving an authorization request message for a transaction, the authorization request message including an account token associated with a real account identifier. The real account identifier associated with the account token is determined. If the transaction is approved, an authorization response message including the real account identifier is transmitted.
Another embodiment of the invention is directed to a method comprising receiving, by a merchant computer, an account token from a payment device, the account token being associated with a real account identifier. The merchant computer transmits an authorization request message for a transaction to a server computer, the authorization request message including the account token. The server computer determines the real account identifier associated with the account token and, if the transaction is approved, transmits an authorization response message including the real account identifier.
Another embodiment of the invention is directed to a system comprising a payment device, a merchant computer, and a server computer. The payment device is configured to store an account token associated with a real account identifier. The merchant computer is configured to receive the account token from the payment device, and transmit an authorization request message for a transaction including the account token. The server computer is configured to receive the authorization request message including the account token from the merchant computer, determine the real account identifier associated with the account token, and transmit an authorization response message including the real account identifier if the transaction is approved.
These and other embodiments of the invention are described in detail below.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 illustrates a block diagram of an exemplary payment processing system in accordance with some embodiments.
FIG. 2 illustrates a block diagram of an exemplary payment processing network including a server computer in accordance with some embodiments.
FIG. 3 shows a flowchart illustrating an exemplary method of processing payment transactions by a payment processing network in accordance with some embodiments.
FIG. 4 shows a flowchart illustrating an exemplary method of processing payment transactions by an issuer computer in accordance with some embodiments.
FIG. 5 illustrates a block diagram of an exemplary computer system.
DETAILED DESCRIPTION
Embodiments of the invention are directed to systems, apparatus, and methods for receiving an account token for a transaction, and returning an associated real account identifier if the transaction is approved.
Prior to discussing embodiments of the invention, a further description of some terms may be helpful in understanding embodiments of the invention.
An “authorization request message” may be an electronic message that is sent to a payment processing network and/or an issuer of a payment card to request authorization for a transaction. An authorization request message according to some embodiments may comply with ISO 8583, which is a standard for systems that exchange electronic transaction information associated with a payment made by a consumer using a payment device or payment account. The authorization request message may include an issuer account identifier that may be associated with a payment device or payment account. An authorization request message may also comprise additional data elements corresponding to “identification information” including, by way of example only: a service code, a CVV/iCVV (card verification value), a dCVV (dynamic card verification value), a cryptogram (e.g., a unique cryptographic value for the transaction), an expiration date, etc. An authorization request message may also comprise “transaction information,” such as any information associated with a current transaction, such as the transaction amount, merchant identifier (e.g., MVV), merchant location, merchant category code, etc., as well as any other information that may be utilized in determining whether to authorize a transaction.
An “authorization response message” may be an electronic message reply to an authorization request message generated by an issuing financial institution or a payment processing network. The authorization response message may include, by way of example only, one or more of the following status indicators: Approval—tran Decline—transact or Call Center—response pending more information, merchant must call the toll-free authorization phone number. The authorization may also include “identification information” as described in further detail below. The authorization response message may also include an authorization code, which may be a code that a credit card issuing bank returns in response to an authorization request message in an electronic message (either directly or through the payment processing network) to the merchant\'s access device (e.g., POS equipment) that indicates approval of the transaction. The code may serve as proof of authorization. As described below, in some embodiments, a payment processing network may generate or forward the authorization response message to the merchant or an acquirer of the merchant.
“Identification information” may include any suitable information associated with an account (e.g., a payment account and/or payment device associated with the account). Such information may be directly related to the account or may be derived from information related to the account. Examples of account information may include a “real account identifier” such as a PAN (primary account number), “account token,” user name, expiration date, CVV/iCVV (card verification value), dCVV (dynamic card verification value), CVV2 (card verification value 2), CVC3 card verification values, cryptograms, etc. CVV/iCVV and CVV2 are generally understood to be static verification values associated with a payment device, whereas dCVV and cryptograms are generally understood to be dynamic verification values. CVV2 values are generally visible to a user (e.g., a consumer), whereas CVV/iCVV, dCVV, and cryprogram values are typically embedded in memory or authorization request messages and are not readily known to the user (although they are known to the issuer and payment processors).
A “payment device” may include any device that may be used to conduct a financial transaction, such as to provide payment information to a merchant. A payment device may be in any suitable form. For example, suitable payment devices can be hand-held and compact so that they can fit into a consumer\'s wallet and/or pocket (e.g., pocket-sized). They may include smart cards, magnetic stripe cards, keychain devices (such as the Speedpass™ commercially available from Exxon-Mobil Corp.), etc. Other examples of payment devices include security cards, access cards, smart media, transponders, 2-D barcodes, an “electronic” or “digital wallet,” and the like. If the payment device is in the form of a debit, credit, smartcard, or other payment card, the payment device may also optionally have features such as magnetic stripes. Payment devices can operate in a contact mode (e.g., with magnetic stripe data being read by a contact-based access device) and/or in contactless mode (e.g., by transmitting data to a contactless access device using radio frequency (RF) communication or other wireless protocol). Suitable payment devices may also include “stationary” devices such as desktop computers and the like.
In some embodiments, exemplary payment devices can include “mobile devices.” A “mobile device” may comprise any electronic device that may be transported and operated by a user, which may also provide remote communication capabilities to a network. Examples of remote communication capabilities include using a mobile phone (wireless) network, wireless data network (e.g., 3G, 4G, or similar networks), Wi-Fi, Wi-Max, or any other communication medium that may provide access to a network such as the Internet or a private network. Examples of mobile devices include mobile phones (e.g., cellular phones), PDAs, tablet computers, net books, laptop computers, personal music players, hand-held specialized readers, etc. Mobile devices may facilitate an “electronic” or “digital wallet.” A mobile device may comprise any suitable hardware and software for performing such functions, and may also include multiple devices or components (e.g., when a device has remote access to a network by tethering to another device—i.e. using the other device as a modem—both devices taken together may be considered a single mobile device).
An “electronic wallet” or “digital wallet” can store user profile information, payment information, bank account information, and/or the like and can be used in a variety of transactions, such as but not limited to eCommerce, social networks, money transfer/personal payments, mobile commerce, proximity payments, gaming, and/or the like for retail purchases, digital goods purchases, utility payments, purchasing games or gaming credits from gaming websites, transferring funds between users, and/or the like. As described in further detail below, an electronic or digital wallet can store “real account identifiers” and/or “account tokens.”
A “real account identifier” may include any information that directly identifies a payment account such as a credit card account, a checking account, a prepaid account, and the like. A real account identifier can be represented as a sequence of characters or symbols (e.g., a 16 digit PAN). Exemplary real account identifiers include, but are not limited to, credit card account numbers, debit card numbers, checking and savings account numbers, prepaid account numbers, and the like.
You can also Monitor Keywords and Search for tracking patents relating to this Dynamic account identifier with return real account identifier patent application.
How KEYWORD MONITOR works... a FREE service from FreshPatents1.
(takes 30 seconds). 2.
to be monitored.
3. Each week you receive an email with patent applications related to your keywords.&& - Receive info on patent apps like Dynamic account identifier with return real account identifier or other areas of interest.###
Previous Patent Application:Next Patent Application:Industry Class:Thank you for viewing the Dynamic account identifier with return real account identifier patent info.- -
Results in 0.01479 seconds###Data source: patent applications published in the public domain by the United States Patent and Trademark Office (USPTO). Information published here is for research/educational purposes only.
FreshPatents is not affiliated with the USPTO, assignee companies, inventors, law firms or other assignees. Patent applications, documents and images may contain trademarks of the respective companies/authors. FreshPatents is not responsible for the accuracy, validity or otherwise contents of these public document patent application filings. When possible a complete PDF is provided, however, in some cases the presented document/images is an abstract or sampling of the full patent application for display purposes.
-g2-0.24766.232.115.224
Browse patents:
Patent InfoApplication # US
Publish Date
06/12/2014
Document #
12/09/2013 USPTO Class
705 44 Other USPTO Classes
n/a International Class
n/a Drawings
Follow us on Twitter
Patent assigned to&&
&& && && && Browse patents:
|dynamic account identifier with return real account identifier|Embodiments of the invention are directed to systems, apparatus, and methods for receiving an account token for a transaction, and returning an associated real account identifier if the transaction is approved. In one embodiment, an authorization request message for a transaction is received by a server computer, the authorization request |大图自动缩小
汉化/扫图：王样汉化组
本页Real Account漫画内容均来自互联网，动漫之家与内容的出处无关，如有违反您的权益，或您发现有任何不良内容或图片错误，【】，我们将修正该漫画图片
作者：otosama　　类型：欢乐向|节操
推荐理由：物理系等级999(无队友时攻击力翻十倍)的唐僧与虎皮裙抹胸飞机场孙猴子、大波变态三到九十九岁通吃的母猪八戒和死库水无口电波沙僧，穿着娇羞可人清纯羞涩的小白龙牌布鞋去西天取经的无厘头掉节操搞笑故事
万能的小编
作者：浅井莲次 沢田新　　类型：悬疑
推荐理由：“软滑滑天然娘”的头牌花魁，巨乳少女杀手『小景』，在与完全绝望的黑医、寻求新生的黑帮奴隶、从小被变态黑帮圈养的杀手少女等各种委托人及目标激烈碰撞之间，追求自己小小幸福的，超乎预期的黑暗故事。
汉化组卖瓜
本章节已经浏览完毕，您可以：大图自动缩小
本页Real Account漫画内容均来自互联网，动漫之家与内容的出处无关，如有违反您的权益，或您发现有任何不良内容或图片错误，【】，我们将修正该漫画图片
作者：otosama　　类型：欢乐向|节操
推荐理由：物理系等级999(无队友时攻击力翻十倍)的唐僧与虎皮裙抹胸飞机场孙猴子、大波变态三到九十九岁通吃的母猪八戒和死库水无口电波沙僧，穿着娇羞可人清纯羞涩的小白龙牌布鞋去西天取经的无厘头掉节操搞笑故事
万能的小编
作者：浅井莲次 沢田新　　类型：悬疑
推荐理由：“软滑滑天然娘”的头牌花魁，巨乳少女杀手『小景』，在与完全绝望的黑医、寻求新生的黑帮奴隶、从小被变态黑帮圈养的杀手少女等各种委托人及目标激烈碰撞之间，追求自己小小幸福的，超乎预期的黑暗故事。
汉化组卖瓜
本章节已经浏览完毕，您可以：}