Menu

User Tools

Create PDF

Site Tools


Differences

This shows you the differences between two versions of the page.

Go

Link to this comparison view

payment_methods:invoice:wirecard [2017-07-19 10:17]
lkn [Required request parameters]
payment_methods:invoice:wirecard [2020-10-28 07:31] (current)
Line 40: Line 40:
 In order to use the parameter ''consumerDeviceId'' you first need to generate a **unique token** and **run a JavaScript** as described in the following sections. In order to use the parameter ''consumerDeviceId'' you first need to generate a **unique token** and **run a JavaScript** as described in the following sections.
  
-The request parameter ''consumerDeviceId'' is transmitted to Wirecard at the **initiation** of Wirecard Checkout Page or Wirecard Checkout Seamless front-end.+The request parameter ''consumerDeviceId'' is transmitted to Wirecard at the **initiation** of Wirecard Checkout Page or Wirecard Checkout Seamless front-end. The value of the parameter needs to be the **unique token**.  
 + 
 +The unique token, identifying your consumer during the process of ordering, is thus transmitted via JavaScript **and** via the request parameter ''consumerDeviceId''.
  
 **Generating a unique token** **Generating a unique token**
Line 67: Line 69:
     var di = {t:'<?php echo $consumerDeviceId ?>',v:'WDWL',l:'Checkout'};     var di = {t:'<?php echo $consumerDeviceId ?>',v:'WDWL',l:'Checkout'};
 </script> </script>
-<script type="text/javascript" src="//d.ratepay.com/<?php echo $deviceIdentSId ?>/di.js"></script>+<script type="text/javascript" src="//d.ratepay.com/<?php echo $consumerDeviceId?>/di.js"></script>
 <noscript> <noscript>
     <link rel="stylesheet" type="text/css" href="//d.ratepay.com/di.css?t=<?php echo $consumerDeviceId ?>&v=WDWL&l=Checkout">     <link rel="stylesheet" type="text/css" href="//d.ratepay.com/di.css?t=<?php echo $consumerDeviceId ?>&v=WDWL&l=Checkout">

This website uses cookies to deliver the best service to you. By continuing to browse the site, you are agreeing to our use of cookies.