System and method for facilitating a financial transaction with a dynamically generated identifier
View Patent ↗Instead of a PIN which is associated with an account and provides access to an account, a dynamically generated card identifier (dynamic CID) is used to verify that the consumer currently possesses the transaction card at the time of purchase and/or is the true card owner. At the time of purchase, a token generates a dynamic CID, which changes with each transaction. A consumer enters the dynamic CID into a pre-existing CID field in an electronic order form. The merchant then sends the dynamic CID to a card authorization system within an authorization request. The card authorization system issues a response to a merchant system via a pre-existing authorization message indicating that the transaction card and dynamic CID have been validated, thereby adjusting the fraud risk associated with the transaction.
1. A computer-implemented method comprising:
transmitting, by a merchant transaction computer system, at least a portion of a request message including a code to an authorization system in a data message, wherein said authorization system authenticates said code; and
receiving, by said merchant transaction computer system, a response from said authorization system in a data message indicating that said code is a valid dynamically generated code comprising four digit batch code (4DBC), wherein said response includes an authorization code related to said transaction and indicative of said authorization being based on validation of said dynamically generated code, and wherein said response is indicative of an allocation to an issuer of a fraud risk associated with said transaction.
2. The method of claim 1 , further comprising completing, by said merchant computer system, said transaction.
3. The method of claim 1 , wherein said data message is at least one of: a four digit card security code (4CSC), or a three digit card security code (3CSC).
4. The method of claim 1 , wherein said code is entered into a card identifier (CID) field of an electronic payment form.
5. The method of claim 1 , wherein said merchant computer system does not know a type of said code within said request message upon the receiving of said request message.
6. The method of claim 1 , wherein said code is generated by using a token.
7. The method of claim 1 , wherein said code is generated using a token, wherein said token includes at least one of: software, a USB device, fob, transaction card reader or pinpad.
8. The method of claim 1 , wherein said code is generated based on interaction between at least one of a transaction card, biometric and a token.
9. The method of claim 8 , wherein said code is automatically captured by a point of sale system.
10. The method of claim 9 , wherein said code is created based on at least one of:
transaction account data, entered Personal Identification Number (PIN), private key, password, profile data, card reader data, and time.
11. The method of claim 1 , wherein said code is retrieved from a preexisting field of said electronic payment form.
12. A computer-implemented method for authorizing a dynamically generated code, said method comprising:
receiving, by an authorization computer having a processor and non-transitory memory, at least a portion of a request message to authorize a transaction from a merchant server, wherein said request message includes a code, and wherein said code is in a data message;
authorizing, by said authorization computer, said code as a valid dynamically generated code comprising a four digit batch code (4DBC); and
transmitting, by said authorization computer, said authorization of said dynamically generated code to said merchant server in a data message, wherein said authorization includes an authorization code related to said transaction and based on said dynamically generated code being valid, and wherein said authorization code is indicative of an allocation to an issuer of a fraud risk associated with said transaction,
13. The method of claim 12 , wherein said code is retrieved from a preexisting field of an electronic payment form.
14. The method of claim 12 , wherein said code is entered into a card identifier (CID) field of an electronic payment form.
15. The method of claim 12 , wherein said data message is a pre-existing data message.
16. The method of claim 12 , wherein said merchant computer system does not know a type of said code within said request message upon the receiving of said request message.
17. The method of claim 12 , wherein said authorization code confirms allocation to an issuer of a fraud risk associated with said transaction.
18. A computer-implemented method for conducting a transaction, said method comprising:
generating a code, by a computing device for completing a transaction, wherein said computing device includes a processor and non-transitory memory; and
sending, by said personal computing device, a request message in a data message to a merchant computer system for a transaction, wherein said request message includes said code, and wherein said merchant computer system transmits at least a portion of said request message to an authorization system in a data message and receives a response from said authorization system in a data message indicating that said code is valid dynamically generated code comprising a four digit batch code (4DBC) before completing said transaction, and wherein said response includes an authorization code related to said transaction and said dynamically generated code being valid, and indicative of said authorization being based on said dynamically generated code and wherein said authorization code is indicative of an allocation to an issuer of a fraud risk associated with said transaction.
19. The method of claim 18 , wherein said generating comprises generating said code via at least one of: a hardware token and a software token.
20. The method of claim 18 , wherein said code is entered into a card identifier (CID) field of an electronic payment form.
21. The method of claim 18 , wherein said merchant computer system does not know a type of said code within said request message upon the receiving of said request message.