Systems and methods for distributed enhanced payment processing
A distributed enhanced payment processing system includes a merchant point of sale (POS) terminal system and a remote payment management system. The POS terminal system initiates a transaction that includes receiving a payment amount, a purchaser account identifier, a virtual electronic payment indicator, and a merchant ID via a payment client. Subsequently, the POS terminal system outputs the transaction to the remote payment management system which generates a token for the transaction. The payment management system then provides the purchaser account identifier, a merchant account identifier, and the payment amount to a remote virtual electronic payment (VEP) entity system. Upon receiving a VEP entity system response, the payment management system outputs the response and token to the POS terminal system.
1. In a distributed enhanced payment processing system, a method for electronic payment processing comprising:
receiving, by a point of sale terminal, selection of a first payer system via a graphical user interface of the point of sale terminal;
reading, by the point of sale terminal, a primary account number from a payment vehicle via a payment vehicle reader of the point of sale terminal;
generating, by the point of sale terminal, a transaction comprising i) a payment amount, ii) purchaser payment credentials comprising the read primary account number, iii) a payer ID associated with the selected first payer system, iv) a payment type, and v) a merchant ID, wherein the payment type is either a virtual electronic payment or a traditional card brand payment;
receiving, at a remote payment management system, the transaction from the point of sale terminal;
determining, by the remote payment management system, the selected first payer system based on the payer ID, wherein the selected first payer system is either a remote virtual electronic payment (VEP) entity system or a card processor;
determining, by the remote payment management system, that the read primary account number is associated with a second payer system that is different from the selected first payer system;
based on the determining that the read primary account number is associated with the second payer system that is different from the selected first payer system, translating, by the remote payment management system, the read primary account number to a primary account number corresponding to the payer ID;
determining, by the remote payment management system, that communication with the selected first payer system cannot be established; and
based on the determining that communication with the selected first payer system cannot be established:
generating, by the remote payment management system, an approval response for the transaction;
outputting, by the remote payment management system at a first time, the generated approval response to the point of sale terminal; and
routing, by the remote payment management system at a second time later than the first time, the primary account number corresponding to the payer ID, a merchant account identifier, and the payment amount to the selected first payer system, wherein communication with the selected first payer system is established at the second time.
2. The method of claim 1 , wherein the transaction is encrypted.
3. The method of claim 1 , further comprising:
validating the merchant ID against merchant logs to ensure a corresponding merchant is configured for tokenization;
generating a token for the transaction, wherein the token includes the primary account number corresponding to the payer ID, an expiration date, and a group ID, wherein the group ID is generated in a database to correlate with more than one merchant ID, wherein the token is encrypted.
4. The method of claim 3 , wherein the group ID enables particular merchants to redeem the token.
5. The method of claim 4 , further comprising associating merchants to the group ID.
6. The method of claim 3 , further comprising:
receiving the token from the point of sale terminal;
validating the merchant ID against merchant logs to ensure the merchant is configured for tokenization;
decrypting the token;
determining if the group ID corresponds to the merchant ID in the database; and if the merchant ID corresponds to the group ID, then:
providing the primary account number corresponding to the payer ID, the merchant account identifier, and the payment amount to the remote VEP entity system;
receiving a second response from the remote VEP entity system; and
outputting the second response to the point of sale terminal.
7. The method of claim 1 , further comprising querying a database for merchant configuration.
8. The method of claim 7 , further comprising declining the transaction if the merchant configuration does not match the transaction.
9. The method of claim 7 , further comprising updating the database for changes in merchant configuration.
10. The method of claim 1 , further comprising upon a verification of the primary account number corresponding to the payer ID, providing an electronic coupon as partial payment for the transaction.
11. The method of claim 1 , further comprising:
upon determining that communication with the selected first payer system is established:
routing, by the remote payment management system, the primary account number corresponding to the payer ID, the merchant account identifier, and the payment amount to the selected first payer system;
receiving, by the remote payment management system, an approval response approving the transaction from the selected first payer system; and
outputting, by the remote payment management system, the received approval response to the point of sale terminal.
12. A distributed enhanced payment processing system configured to process electronic payments, the system comprising:
a point of sale terminal configured to:
receive selection of a first payer system via a graphical user interface of the point of sale terminal;
read a primary account number from a payment vehicle via a payment vehicle reader of the point of sale terminal; and
generate a transaction comprising i) a payment amount, ii) purchaser payment credentials comprising the read primary account number, iii) a payer ID associated with the selected first payer system, iv) a payment type, and v) a merchant ID, wherein the payment type is either a virtual electronic payment or a traditional card brand payment;
a remote payment management system configured to:
receive the transaction from the point of sale terminal;
determine the selected first payer system based on the payer ID, wherein the selected first payer system is either a remote virtual electronic payment (VEP) entity system or a card processor;
determine that the read primary account number is associated with a second payer system that is different from the selected first payer system;
based on the determining that the read primary account number is associated with the second payer system that is different from the selected first payer system, translate the read primary account number to a primary account number corresponding to the payer ID;
determine that communication with the selected first payer system cannot-be established; and
based on the determining that communication with the selected first payer system cannot be established:
generate an approval response for the transaction;
output, at a first time, the generated approval response to the point of sale terminal; and
route, at a second time later than the first time, the primary account number corresponding to the payer ID, a merchant account identifier, and the payment amount to the selected first payer system, wherein communication with the selected first payer system is established at the second time.
13. The system of claim 12 , wherein the transaction is encrypted.
14. The system of claim 13 , wherein the remote payment management system is further configured to decrypt the transaction.
15. The system of claim 12 , wherein the remote payment management system is further configured to:
validate the merchant ID against merchant logs to ensure a corresponding merchant is configured for tokenization;
generate a token for the transaction, wherein the token includes the primary account number, an expiration date, and a group ID, wherein the group ID is generated in a database to correlate with more than one merchant ID, wherein the token is encrypted.
16. The system of claim 15 , wherein the group ID enables particular merchants to redeem the token.
17. The system of claim 16 , wherein the remote payment management system is further configured to associate merchants to the group ID.
18. The system of claim 12 , wherein the remote payment management system is further configured to query a database for merchant configuration.
19. The system of claim 18 , wherein the remote payment management system is further configured to decline the transaction if the merchant configuration does not match the transaction.
20. The system of claim 18 , wherein the remote payment management system is further configured to update the database for changes in merchant configuration.
21. The system of claim 12 wherein the point of sale terminal is further configured to, upon a verification of the translated primary account number, provide an electronic coupon as partial payment for the transaction.
22. The system of claim 15 , wherein the remote payment management system is further configured to:
receive the token from the point of sale terminal;
validate the merchant ID against merchant logs to ensure the merchant is configured for tokenization;
decrypt the token;
determine if the group ID corresponds to the merchant ID in the database; and if the merchant ID corresponds to the group ID, then:
provide the primary account number, the merchant account identifier, and the payment amount to the remote VEP entity system;
receive a second response from the remote VEP entity system; and
output the second response to the point of sale terminal.
23. The system of claim 12 , wherein a payment client at the point of sale terminal is configured to display merchant selected VEP payer choices.
24. The system of claim 12 , wherein a payment client at the point of sale terminal is pre-configured to display payment control subscreens in a manner consistent with control screens of the point of sale terminal.
25. The system of claim 12 , wherein the remote payment management system is further configured to:
upon determining that communication with the selected first payer system is established:
route the primary account number corresponding to the payer ID, the merchant account identifier, and the payment amount to the selected first payer system;
receive, at the remote payment management system, an approval response approving the transaction from the selected first payer system; and
output the received approval response to the point of sale terminal.