SYSTEMS AND METHODS FOR ONLINE PAYMENT PROCESSING USING SECURE INLINE FRAMES
Systems and methods for facilitating online payments via an HTML document embedded inside another HTML document on a payee website (e.g., an “inline frame” or “iFrame”). Generally, the iFrame permits a payor (e.g., customer, constituent, donor, etc.) to pay for a transaction (e.g., purchase, utilities payment, fine, donation, dues, etc.) on the payee's web site without requiring the payee (e.g., merchant, utilities provider, government entity, non-profit, etc.) to handle the payor's payment data (e.g., credit card information, bank account information, blockchain-based transaction information, etc.). Further, the iFrame permits the payor to pay for a transaction on the payee's website without requiring the payor to leave the payee's website.
1 . A system, comprising:
an iFrame controller that:
produces an iFrame on a merchant website hosted on a server;
receives payment data from the iFrame corresponding to a transaction on the merchant website;
generates an eToken corresponding to the received payment data; and
transmits the eToken to the server; and
an eToken transaction processor that:
receives, from the server, transaction data, comprising the eToken and non-sensitive payment data, corresponding to the transaction;
authenticates the eToken to determine the received payment data to which it corresponds; and
processes the transaction, according to the received transaction data, using the received payment data.
2 . The system of claim 1 , wherein the iFrame comprises a first HTML document embedded within a second HTML document.
3 . The system of claim 1 , wherein the received payment data comprises at least one of the following: a credit card number, a credit card expiration date, a credit card verification value, a bank account routing number, a debit card number, a debit card expiration date, or a PIN number.
4 . The system of claim 3 , wherein the payment data is not accessible by the merchant website or the server.
5 . The system of claim 1 , wherein the non-sensitive payment data comprises at least one of the following: a transaction identifier, a transaction price, or contact information.
6 . The system of claim 1 , wherein the iFrame controller encrypts the eToken prior to transmitting the eToken to the server.
7 . The system of claim 6 , wherein the eToken transaction processor decrypts the eToken prior to authenticating the eToken.
8 . The system of claim 1 , wherein the eToken transaction processor, to process the transaction, transmits the payment data and at least some of the transaction data to a payment network.
9 . A method, comprising the steps of:
producing an iFrame on a merchant web site hosted on a server;
receiving payment data from the iFrame corresponding to a transaction on the merchant web site;
generating an eToken corresponding to the received payment data;
transmitting the eToken to the server;
receiving, from the server, transaction data, comprising the eToken and non-sensitive payment data, corresponding to the transaction;
authenticating the eToken to determine the received payment data to which it corresponds; and
processing the transaction, according to the received transaction data, using the received payment data.
10 . The method of claim 9 , wherein the iFrame comprises a first HTML document embedded within a second HTML document.
11 . The method of claim 9 , wherein the received payment data comprises at least one of the following: a credit card number, a credit card expiration date, a credit card verification value, a bank account routing number, a debit card number, a debit card expiration date, or a PIN number.
12 . The method of claim 11 , wherein the payment data is not accessible by the merchant web site or the server.
13 . The method of claim 9 , wherein the non-sensitive payment data comprises at least one of the following: a transaction identifier, a transaction price, or contact information.
14 . The method of claim 9 , further comprising the step of encrypting the eToken prior to transmitting the eToken to the server.
15 . The method of claim 14 , further comprising the step of decrypting the eToken prior to authenticating the eToken.
16 . The method of claim 9 , wherein processing the transaction further comprising the step of transmitting the payment data and at least some of the transaction data to a payment network.
17 . A system, comprising:
a website hosted on a server, wherein the website comprises an iFrame, wherein the iFrame receives payment data corresponding to a transaction on the website and is produced by an iFrame controller; and
the server that:
receives an eToken corresponding to the received payment data from the iFrame controller;
generates transaction data, corresponding to the transaction, comprising the eToken and non-sensitive payment data;
transmits the transaction data to an eToken transaction processor for processing of the transaction; and
receives at least one result of the processing from the eToken transaction processor.
18 . The system of claim 17 , wherein the iFrame comprises a first HTML document embedded within a second HTML document.
19 . The system of claim 17 , wherein the received payment data comprises at least one of the following: a credit card number, a credit card expiration date, a credit card verification value, a bank account routing number, a debit card number, a debit card expiration date, or a PIN number.
20 . The system of claim 19 , wherein the payment data is not accessible by the website or the server.
21 . The system of claim 17 , wherein the non-sensitive payment data comprises at least one of the following: a transaction identifier, a transaction price, or contact information.
22 . A method, comprising the steps of:
hosting a website that comprises an iFrame, wherein the iFrame receives payment data corresponding to a transaction on the website;
receiving an eToken corresponding to the received payment data;
generating transaction data, corresponding to the transaction, comprising the eToken and non-sensitive payment data;
transmitting the transaction data for processing of the transaction; and
receiving at least one result of the processing.
23 . The method of claim 22 , wherein the iFrame comprises a first HTML document embedded within a second HTML document.
24 . The method of claim 22 , wherein the received payment data comprises at least one of the following: a credit card number, a credit card expiration date, a credit card verification value, a bank account routing number, a debit card number, a debit card expiration date, or a PIN number.
25 . The method of claim 24 , wherein the payment data is not accessible by the website.
26 . The method of claim 22 , wherein the non-sensitive payment data comprises at least one of the following: a transaction identifier, a transaction price, or contact information.