Point of interaction device emulation for payment transaction simulation
Technologies for emulating payment transaction messaging for electronic payment transaction include a transaction management controller for receiving a transaction amount for a payment transaction from a business management engine and simulated payment card data for the payment transaction from a point of interaction emulator. The transaction management controller inserts the transaction amount and the payment card data into a test payment authorization request message, which is transmitted to a null host. A payment authorization response message is received from the null host and transmitted by the transaction management controller the business management engine Other embodiments are described and claimed.
1 . A computer-implemented method for simulating a payment transaction using a payment transaction simulation system, the method comprising:
receiving, by a point of interaction emulator of the payment transaction simulation system and from a transaction management controller installed on a merchant computing device, a request for simulated payment card data for a test payment transaction according to a predetermined transaction scenario, wherein the test payment transaction is initiated by the transaction management controller installed on the merchant computing device;
generating, by the point of interaction emulator, the simulated payment card data according to the predetermined transaction scenario and using one or more payment processing features;
transmitting, by the point of interaction emulator and to the transaction management controller, the simulated payment card data;
receiving, by a null host of the payment transaction simulation system, a simulated authorization request for the test payment transaction;
processing, by the null host, the test payment transaction;
transmitting, by the null host and to the transaction management controller, a simulated authorization response based on processing the test payment transaction;
receiving, by the point of interaction emulator and from the transaction management controller, an instruction to finalize the test payment transaction;
generating, by the point of interaction emulator, simulated captured finalized data for the test payment transaction; and
transmitting, by the point of interaction emulator and to the transaction management controller, the simulated captured finalized data.
2 . The computer-implemented method of claim 1 , further comprising:
transmitting, by the point of interaction emulator and to the transaction management controller, additional transaction data for the test payment transaction, the additional transaction data comprising a tip amount or a cashback amount.
3 . The computer-implemented method of claim 1 , further comprising:
transmitting, by the point of interaction emulator and to the transaction management controller, one or more transaction messages according to a payment vehicle type and/or a transaction type of the test payment transaction.
4 . The computer-implemented method of claim 3 , wherein the transaction type is one of a swiped card entry, a contactless payment card entry, or a keyed entry.
5 . The computer-implemented method of claim 1 , further comprising:
receiving, by the point of interaction emulator and from a remote configuration device, a feature modification message, the feature modification message including configuration data to modify one or more features of the point of interaction emulator, wherein the one or more features having been modified includes one or more of signature prompting features, personal identification number (PIN) entry features, loyalty card reading, and driver license number input.
6 . The computer-implemented method of claim 1 , wherein the one or more payment processing features include one or more of listening port settings, security settings, user settings, partial approval features, transaction amount confirmation features, cashback features, accepted payment card settings, supported language settings, transaction gratuity features, signature requirement features, transaction store and forward features, lane identification features, lane initialization settings, terminal type settings, driver configurations, and communication settings.
7 . The computer-implemented method of claim 1 , wherein a point of interaction device emulated by the point of interaction emulator is one of a card reader or a personal identification number (PIN) pad.
8 . The computer-implemented method of claim 1 , wherein the simulated captured finalized data for the test payment transaction includes a simulated captured signature for the test payment transaction.
9 . A payment transaction simulation system for simulating a payment transaction, the system comprising:
a data storage device storing instructions in one or more electronic storage mediums; and
one or more processors configured to execute the instructions to perform a computer-implemented method including:
receiving, by a point of interaction emulator, executed by the one or more processors, of the payment transaction simulation system and from a transaction management controller installed on a merchant computing device, a request for simulated payment card data for a test payment transaction according to a predetermined transaction scenario, wherein the test payment transaction is initiated by the transaction management controller installed on the merchant computing device;
generating, by the point of interaction emulator, executed by the one or more processors, the simulated payment card data according to the predetermined transaction scenario and using one or more payment processing features;
transmitting, by the point of interaction emulator, executed by the one or more processors, and to the transaction management controller, the simulated payment card data;
receiving, by a null host, executed by the one or more processors, of the payment transaction simulation system, a simulated authorization request for the test payment transaction;
processing, by the null host, executed by the one or more processors, the test payment transaction;
transmitting, by the null host, executed by the one or more processors, and to the transaction management controller, a simulated authorization response based on processing the test payment transaction;
receiving, by the point of interaction emulator, executed by the one or more processors, and from the transaction management controller, an instruction to finalize the test payment transaction;
generating, by the point of interaction emulator, executed by the one or more processors, simulated captured finalized data for the test payment transaction; and
transmitting, by the point of interaction emulator, executed by the one or more processors, and to the transaction management controller, the simulated captured finalized data.
10 . The payment transaction simulation system of claim 9 , wherein the system is further configured for:
transmitting, by the point of interaction emulator, executed by the one or more processors, and to the transaction management controller, additional transaction data for the test payment transaction, the additional transaction data comprising a tip amount or a cashback amount.
11 . The payment transaction simulation system of claim 9 , wherein the system is further configured for:
transmitting, by the point of interaction emulator, executed by the one or more processors, and to the transaction management controller, one or more transaction messages according to a payment vehicle type and/or a transaction type of the test payment transaction.
12 . The payment transaction simulation system of claim 9 , wherein the system is further configured for:
receiving, by the point of interaction emulator, executed by the one or more processors, and from a remote configuration device, a feature modification message, the feature modification message including configuration data to modify one or more features of the point of interaction emulator, wherein the one or more features having been modified includes one or more of signature prompting features, personal identification number (PIN) entry features, loyalty card reading, and driver license number input.
13 . The payment transaction simulation system of claim 9 , wherein the one or more payment processing features include one or more of listening port settings, security settings, user settings, partial approval features, transaction amount confirmation features, cashback features, accepted payment card settings, supported language settings, transaction gratuity features, signature requirement features, transaction store and forward features, lane identification features, lane initialization settings, terminal type settings, driver configurations, and communication settings.
14 . The payment transaction simulation system of claim 9 , wherein the simulated captured finalized data for the test payment transaction includes a simulated captured signature for the test payment transaction.
15 . One or more non-transitory machine-readable mediums storing instructions that, when executed by one or more processors of a computing system, causes the one or more processors of the computing system to perform a computer-implemented method for simulating a payment transaction using a payment transaction simulation system, the method comprising:
receiving, by a point of interaction emulator, executed by the one or more processors, of the payment transaction simulation system and from a transaction management controller installed on a merchant computing device, a request for simulated payment card data for a test payment transaction according to a predetermined transaction scenario, wherein the test payment transaction is initiated by the transaction management controller installed on the merchant computing device;
generating, by the point of interaction emulator, executed by the one or more processors, the simulated payment card data according to the predetermined transaction scenario and using one or more payment processing features;
transmitting, by the point of interaction emulator, executed by the one or more processors, and to the transaction management controller, the simulated payment card data;
receiving, by a null host, executed by the one or more processors, of the payment transaction simulation system, a simulated authorization request for the test payment transaction;
processing, by the null host, executed by the one or more processors, the test payment transaction;
transmitting, by the null host, executed by the one or more processors, and to the transaction management controller, a simulated authorization response based on processing the test payment transaction;
receiving, by the point of interaction emulator, executed by the one or more processors, and from the transaction management controller, an instruction to finalize the test payment transaction;
generating, by the point of interaction emulator, executed by the one or more processors, simulated captured finalized data for the test payment transaction; and
transmitting, by the point of interaction emulator, executed by the one or more processors, and to the transaction management controller, the simulated captured finalized data.
16 . The one or more non-transitory machine-readable mediums of claim 15 , the method further comprising:
transmitting, by the point of interaction emulator, executed by the one or more processors, and to the transaction management controller, additional transaction data for the test payment transaction, the additional transaction data comprising a tip amount or a cashback amount.
17 . The one or more non-transitory machine-readable mediums of claim 15 , the method further comprising:
transmitting, by the point of interaction emulator, executed by the one or more processors, and to the transaction management controller, one or more transaction messages according to a payment vehicle type and/or a transaction type of the test payment transaction.
18 . The one or more non-transitory machine-readable mediums of claim 15 , the method further comprising:
receiving, by the point of interaction emulator, executed by the one or more processors, and from a remote configuration device, a feature modification message, the feature modification message including configuration data to modify one or more features of the point of interaction emulator, wherein the one or more features having been modified includes one or more of signature prompting features, personal identification number (PIN) entry features, loyalty card reading, and driver license number input.
19 . The one or more non-transitory machine-readable mediums of claim 15 , wherein the one or more payment processing features include one or more of listening port settings, security settings, user settings, partial approval features, transaction amount confirmation features, cashback features, accepted payment card settings, supported language settings, transaction gratuity features, signature requirement features, transaction store and forward features, lane identification features, lane initialization settings, terminal type settings, driver configurations, and communication settings.
20 . The one or more non-transitory machine-readable mediums of claim 15 , wherein the simulated captured finalized data for the test payment transaction includes a simulated captured signature for the test payment transaction.