System and method for single page banner integration

Abstract

A dynamic banner may be displayed in a merchant check out page sourced from a merchant server that may be customized to a particular user and/or merchant. The dynamic banner may be provided by a transaction account provider server and may invite the user to select an offer. In response to the user's interaction with the offer, the characteristics of the merchant check out page may be changed, for example, a product may be discounted, and/or a new transaction account may be issued to the user by the transaction account provider server and used to complete the checkout process via cross document messaging and cross domain scripting. In this manner, the merchant server and the transaction account provider server may interact with a user within a single web page.

What is claimed is: 
     
         1 . A method comprising:
 receiving, by a web browser, a navigation command from a merchant server directing the web browser to navigate to a merchant check out page;   receiving, by the web browser, the merchant check out page comprising returned webpage content; and   instantiating, by the web browser, a service call comprising a portion of the returned webpage content,   wherein the service call is configured to be transmitted to a transaction account provider server.   
     
     
         2 . The method according to  claim 1 , wherein the merchant check out page further comprises:
 a digital signature signed on a current timestamp using a merchant SSL certificate private key; and   personally identifiable information receiver fields of the merchant check out page.   
     
     
         3 . The method according to  claim 1 , wherein the service call comprises a secured CORS HTTPS RESTful service call. 
     
     
         4 . A method according to  claim 1 ,
 wherein the service call comprising a portion of returned webpage content is configured to be received by the transaction account provider server,   wherein an originating domain of returned webpage content is configured to be validated by the transaction account provider server,   wherein a time stamp of the returned webpage content is configured to be compared against a time constraint by the transaction account provider server,   wherein a dynamic banner is configured to be prepared in response to the validating by the transaction account provider server, and   wherein the dynamic banner is configured to be transmitted by the transaction account provider server.   
     
     
         5 . The method according to  claim 4 , wherein a digital signature of the merchant is configured to be validated by the transaction account provider server. 
     
     
         6 . The method according to  claim 4 , wherein a banner request ID of the returned webpage content is configured to be validated by the transaction account provider server. 
     
     
         7 . The method according to  claim 6 , wherein the banner request ID uniquely identifies a request for the dynamic banner. 
     
     
         8 . The method according to  claim 4 , wherein the returned webpage content comprises a merchant-id. 
     
     
         9 . The method according to  claim 4 , wherein the dynamic banner comprises at least one of an iFrame configured to host a landing page URL, a browser tab configured to host a landing page URL, and a browser window configured to host a landing page URL. 
     
     
         10 . The method according to  claim 9 , wherein the dynamic banner further comprises a secure banner token with an expiration data. 
     
     
         11 . The method according to  claim 9 , wherein the dynamic banner further comprises a secure URL linked to a portion of the dynamic banner configured to accept a user interaction. 
     
     
         12 . A customer application method comprising:
 receiving, by a transaction account provider server, an instruction to the transaction account provider server from a web browser to open a landing page within the web browser;   validating, by the transaction account provider server, a secure URL linked to a portion of a dynamic banner corresponding to a user-banner interaction;   opening, by the transaction account provider server, the landing page within the web browser in response to the validating; and   wherein the landing page is configured to transmit a cross document message to a merchant check out page.   
     
     
         13 . The customer application method of  claim 12 , wherein the instruction to the transaction account provider server from the web browser to open the landing page within a web page further comprises an instruction to open the landing page within an iFrame. 
     
     
         14 . The customer application method of  claim 12 , wherein the validating step further comprises validating, by the transaction account provider server, a secure banner token. 
     
     
         15 . The customer application method of  claim 12 , wherein the landing page is configured to close in response to a cross document message from a merchant server. 
     
     
         16 . A method of IAN to checkout return comprising:
 receiving, by a web browser from a transaction account provider server, an IAN details;   transmitting, by the web browser, a cross document message comprising the IAN details to a merchant page; and   pre-filling a purchase payment information in response to the IAN details by the merchant page into a shopping card experience of the web browser.   
     
     
         17 . The method of IAN to checkout return according to  claim 16 , wherein the IAN details are displayed by the web browser in an iFrame. 
     
     
         18 . The method of IAN to checkout return according to  claim 16 , wherein the web browser forwards the IAN details to a merchant server to complete a transaction. 
     
     
         19 . The method of IAN to checkout return according to  claim 16 ,
 wherein the IAN details are provided in a format comprising an encrypted variable encrypted using a public key of a merchant server.   
     
     
         20 . The method of IAN to checkout return according to  claim 19 ,
 wherein the merchant server is configured to decrypt the IAN details with a private key of the merchant server.