Prototype message service
Described herein are systems and techniques in which a service provider may determine one or more capabilities of an authorization provider. To do this, the service provider may, upon receiving a request to determine authorization provider capabilities that includes at least an account identifier and an indication of a transaction type, identify a prototype message template associated with the indicated transaction type from a plurality of prototype transaction templates. The service provider may then overwrite a number of default data values with data values specific to the transaction to generate a prototype message for the transaction, which it may then send to the authorization provider. Upon receiving a response from the authorization provider, the service provider may determine whether the authorization provider is capable of conducting a transaction of the indicated transaction type based on information included within the received response.
1 . A method comprising:
receiving, by an access device, a transaction request including an account identifier that is to be used for a transaction;
determining, by the access device, a type of the transaction and an authorization computer associated with the transaction;
determining, by the access device, whether the authorization computer associated with the transaction is capable of conducting the type of the transaction;
responsive to an unsuccessful determination, transmitting, by the access device, a request including a subset of transaction details comprising the account identifier and the type of the transaction to a service provider computer, wherein the service provider computer is configured to:
identify an appropriate prototype message template of a plurality of prototype message templates based on the type of the transaction, the appropriate prototype message template being populated with default data values in data fields, wherein each prototype message template of the plurality of prototype message templates is unique;
retrieve from an account information database associated with the access device, first information associated with the account identifier included within the subset of transaction details and second information associated with the access device;
generate a populated prototype message by: (1) overwriting a first portion of data fields and a corresponding default data values in the appropriate prototype message template with the subset of transaction details comprising the account identifier, and (2) overwriting a second portion of the data fields to include the first information and the second information, wherein the populated prototype message is transmitted by the service provider computer to the authorization computer and represents a test transaction that is different from the transaction; and
responsive to receiving a response message from the authorization computer, (i) parse the response message to determine whether the authorization computer is capable of conducting the transaction request, and (ii) transmit to the access device, a transaction indicator indicating whether the authorization computer is capable of conducting the transaction and an identification of additional data fields needed to process the type of the transaction;
responsive to receiving the transaction indicator, obtaining, by the access device, input associated with additional data values for additional data fields needed to process the type of the transaction;
in response to receiving the transaction indicator and input corresponding to the additional data fields obtained from a user device, generating by the access device, an authorization request message comprising the account identifier and additional data fields comprising additional data values;
transmitting, by the access device, the authorization request message to the service provider computer; and
responsive to receiving an authorization response message from the service provider computer, processing, by the access device the transaction request.
2 . The method of claim 1 , wherein the type of the transaction is a debit transaction, a credit transaction, or a cash-back transaction.
3 . The method of claim 1 , wherein the access device determines the authorization computer associated with the transaction based on a banking identification number included in the account identifier.
4 . The method of claim 1 , wherein each prototype message template of the plurality of prototype message templates corresponds to a particular type of transaction.
5 . The method of claim 1 , wherein the populated prototype message represents the test transaction that is different from the request, and wherein the authorization computer configured to respond to the populated prototype message as a non-test transaction.
6 . The method of claim 1 , wherein the authorization computer is determined to be capable of conducting the type of the transaction upon determining that the response message received from the authorization computer includes an approval.
7 . The method of claim 1 , wherein the account identifier is a credit card number.
8 . The method of claim 1 , wherein the access device is a POS terminal.
9 . The method of claim 1 , wherein the access device is operated on behalf of a resource provider.
10 . The method of claim 1 , wherein the authorization computer is an issuer computer.
11 . An access device comprising:
a processor; and
a memory including instructions that, when executed with the processor, cause the access device to, at least:
receive a transaction request including an account identifier that is to be used for a transaction;
determine a type of the transaction and an authorization computer associated with the transaction;
determine whether the authorization computer associated with the transaction is capable of conducting the type of the transaction;
responsive to an unsuccessful determination, transmit a request including a subset of transaction details comprising the account identifier and the type of the transaction to a service provider computer, wherein the service provider computer is configured to:
identify an appropriate prototype message template of a plurality of prototype message templates based on the type of the transaction, the appropriate prototype message template being populated with default data values in data fields, wherein each prototype message template of the plurality of prototype message templates is unique;
retrieve from an account information database associated with the access device, first information associated with the account identifier included within the subset of transaction details and second information associated with the access device;
generate a populated prototype message by: (1) overwriting a first portion of data fields and a corresponding default data values in the appropriate prototype message template with the subset of transaction details comprising the account identifier, and (2) overwriting a second portion of the data fields to include the first information and the second information, wherein the populated prototype message is transmitted by the service provider computer to the authorization computer and represents a test transaction that is different from the transaction; and
responsive to receiving a response message from the authorization computer, (i) parse the response message to determine whether the authorization computer is capable of conducting the transaction request, and (ii) transmit to the access device, a transaction indicator indicating whether the authorization computer is capable of conducting the transaction and an identification of additional data fields needed to process the type of the transaction;
responsive to receiving the transaction indicator, obtaining, by the access device, input associated with additional data values for additional data fields needed to process the type of the transaction;
in response to receiving the transaction indicator and input corresponding to the additional data fields obtained from a user device, generate an authorization request message comprising the account identifier and additional data fields comprising additional data values;
transmit the authorization request message to the service provider computer; and
responsive to receiving an authorization response message from the service provider computer, process the transaction request.
12 . The access device of claim 11 , wherein the type of the transaction is a debit transaction, a credit transaction, or a cash-back transaction.
13 . The access device of claim 11 , wherein the access device determines the authorization computer associated with the transaction based on a banking identification number included in the account identifier.
14 . The access device of claim 11 , wherein each prototype message template of the plurality of prototype message templates corresponds to a particular type of transaction.
15 . The access device of claim 11 , wherein the populated prototype message represents the test transaction that is different from the request, and wherein the authorization computer configured to respond to the populated prototype message as a non-test transaction.
16 . The access device of claim 11 , wherein the authorization computer is determined to be capable of conducting the type of the transaction upon determining that the response message received from the authorization computer includes an approval.
17 . The access device of claim 11 , wherein the account identifier is a credit card number.
18 . The access device of claim 11 , wherein the access device is a POS terminal.
19 . The access device of claim 11 , wherein the access device is operated on behalf of a resource provider.
20 . The access device of claim 11 , wherein the authorization computer is an issuer computer.