Vejledning. - Opsætning og layout af tilmeldingslink til Automatisk kortbetaling. Versionnr Nets A/S. Lautrupbjerg 10.

Transkript

1 Vejledning - Opsætning og layout af tilmeldingslink til Automatisk Versionnr. 1.0 Nets A/S Lautrupbjerg Ballerup DK T F

2 Indholdsfortegnelse 1. Formål Forudsætninger Online tilmelding Kundenummer Tekstforslag Pop up vindue for tilmelding, ændring og afmelding Tilmeldingslink Tilmeldingsflow for kunden Redigering/afmelding af aftale Option call back/redirect Interface description Basic integration setup Redirect-on-success feature setup Proxy-page setup Setup Example 1: Only mandate registration Setup Example 2: Mandate registration with first-time payment, callback and redirect Error codes and error text generated from pop up P. 2-31

3 1. Formål Formålet med dette dokument er at give et overblik over, hvordan integrationen mellem virksomhedens hjemmeside og tilmeldingslinket til Automatisk virker. Dokumentet indeholder forudsætninger, beskrivelse af krav til information på hjemmesiden, faciliteter og formater, samt konfigurationseksempler. Dokumentet er henvendt til både web-ansvarlige, web-udviklere og andre tekniske specialister, der skal være med til at integrere tilmeldingslinket til virksomhedens løsning. Formodentligt personer med viden omkring HTML markup, JavaScript og integration til HTML ved brug af e.g. PHP, ASP, JSP eller andre programmeringssprog. 2. Forudsætninger Tjenesten Automatisk indbefatter en række forudsætninger, der skal være opfyldt, herunder bl.a. hvordan virksomhedens kunder skal kunne til- og afmelde sig, og hvordan de kan foretage ændringer på deres aftale for Automatisk. 2.1 Online tilmelding Kunderne skal kunne tilmelde sig aftale om Automatisk online via virksomhedens hjemmeside. På hjemmesiden skal tilmeldingslink til Automatisk betaling implementeres, og hvorfra kunden kan registrere, tilmelde og afmelde sig, samt hvorfra der kan foretages ændringer (ændre kortoplysninger). Virksomheden skal i den forbindelse vedligeholde forskellige stamdata om kunden, bl.a. navn, adresse og kundenummer, som skal overføres til linket for at aktivere pop up vinduet. Virksomheden har ansvar for at følge gældende regler for internethandel for henholdsvis nationale som internationale kort i henhold til de betalingskortaftaler virksomheden har indgået med indløser. Herunder at tilsikre den nødvendige information er til rådighed på hjemmesiden for kortholder inden accept af ordre og tilmelding til Automatisk betaling. Læs mere om regler og krav til internethandel på: P. 3-31

4 2.2 Kundenummer Når kunden klikker på tilmeldingslinket forudsættes, at et kundenummer automatisk tilføres i linket. Her er flere løsningsscenarier: A. Virksomheden benytter på sin hjemmeside kunde login, hvor unikt kundenummer automatisk generes. B. Virksomheden genererer ikke automatisk kundernummer, men indgår aftale med Nets om at generere midlertidig kundenummer ved kundetilmelding. C. Hvis virksomhedenr hverken har a) eller b) på plads vil kald til pop up en uden kundenummer udløse en fejl. 3. Tekstforslag Inden kunden trykker på link til Automatisk betaling bør du, udover de påkrævede oplysninger angivet i din betalingskortaftale med indløser, også tilføre en tekst om automatiske betalinger. Forslag til tekst: Ved at tilmelde dig automatiske betalinger bliver dine fremtidige regninger betalt til tiden - hverken for tidligt eller for sent. Du slipper for besværet med at taste betalingsoplysningerne i din netbank. Og du slipper for kedelige rykkere og gebyrer. Ved på samme tid at tilmelde dig en saftale og en betalingsaftale, vil din første betaling automatisk ske via det tilmeldte kort og de efterfølgende opkrævninger på din Betalingsservice konto. Og du behøver ikke gøre mere. Dine betalingskortdata behandles i et sikkert miljø, der opfylder gældende PCI DSS krav, og betalingskortdata opbevares ikke. Såfremt du har straksopkrævning i forbindelse med kundens tilmelding, bør du tillige sikre information til dine kunde om, at der først gennemføres betaling, når varen afsendes fra lager. Hvis du kun ønsker, at dine kunder skal kunne betale med betalingskort og altså ikke giver dem muligheden for også at tilmelde sig Betalingsservice, kan overstående tekst omformuleres til: Ved at tilmelde dig automatiske betalinger bliver dine fremtidige regninger betalt til tiden - hverken for tidligt eller for sent. Du slipper for kedelige rykkere og gebyrer. Ved tilmelding til en P. 4-31

5 saftale vil dine betalinger automatisk ske via det tilmeldte kort. Og du behøver ikke gøre mere. Dine betalingskortdata behandles i et sikkert miljø, der opfylder gældende PCI DSS krav, og betalingskortdata opbevares ikke. 4. Pop up vindue for tilmelding, ændring og afmelding 4.1 Tilmeldingslink Tilmeldingslink - eller knap - efter eget valg, indsættes et passende sted på hjemmesiden i forhold til virksomhedens tilmeldingsflow. Vises tilmeldingsknappen/linket på et område, som er offentligt (dvs. uden forudgående login), anbefaler vi, at linket først bliver aktivt efter, at virksomheden har logget kunden ind og et kundenummer er genereret. Alternativt kan Nets generere et midlertidigt kundenummer ved oprettelse (dette aftales mellem virksomheden og Nets ved aftaleindgåelse). Tilmeldingslinket vil blive åbnet i et pop up vindue og et JavaScript benyttes til at initiere dette. Tilmeldingslinket åbnes via HTTP POST eller GET request, hvor Nets server certifikat benyttes ved kald. Nødvendige input til URL link Virksomheden skal dynamisk indsætte en række påkrævede oplysninger i den URL, der aktiverer tilmeldingslinket. Disse er anført nedenfor. De påkrævede oplysninger er: 1. Deb name = Kundens for- og efternavn 2. CPR no./cvr no. = Kundens CPR/CVR nummer (dette er valgfrit, hvis kreditor ikke indhenter dette selv, vil kunden blive bedt om at udfylde inde i tilmeldingslinket) 3. debnr = Kundenummer, kundens ID hos virksomheden (det er aftalt med Nets om virksomheden selv indsætter eller om Nets laver midlertidig kundenummer) 4. Deb.gr.no. = virksomhedens anvendte debitorgruppenummer 5. PBS no. = Kreditors PBS nr. hos Nets 6. Payment type = betalingstype angives: AUTH angives, hvis straksbetaling med reservation. Og anvendes, hvis du ikke sender/leverer varen/ydelsen til kunden straks ved betaling. SALE angives, hvis straksbetaling uden reservation. P. 5-31

6 Hvis feltet er blankt svarer det til, at der er tale om en tilmelding uden straksbetaling timePay* = beløb på straks betalingen (fx oprettelsesbeløb/udbetaling og er det første beløb som vil blive trukket på det tilmeldte kort) 8. RecurringAmount* = beløb på 1. abonnementsbetaling 9. ProductDesc* = produktbeskrivelse på produkt/ydelse som kunden køber (maks. 200 karakterer) 10. CreditorRef = virksomhedens reference vedrørende betalingen maks. 30 karakterer. Referencen er information til dig selv på transaktionsniveau, som returneres sammen med status på betalinger i Leverance Betalingsoplysninger. 11. Callbackurl 12. Return URL and redirect URL. Oplysninger, markeret med *, vil blive vist for kunden i tilmeldingslinket afhængig af om det er med eller uden straksopkrævning, mens resten er oplysninger, der vil blive registreret som del af aftalen hos Nets, og til brug for kommende betalinger. Se afsnit 6 for mere teknisk specifikation af opsætning af URL til tilmeldingslinket. 4.2 Tilmeldingsflow for kunden Når kunde klikker på tilmeldingslinket fremkommer et vindue, hvor indholdet i dette vil være baseret på den aftaletype, der er registreret i aftalen med Nets. Dvs enten: 1. Altid kort 2. Kort & Betalingsservice 3. Altid kort og Kort & Betalingsservice Se eksempler på de tre typer af pop up vinduer nedenfor P. 6-31

7 Ad 1) Altid kort (relevant hvis betalingsfrekvens forskellig fra betalingscyklus i Betalingsservice ) Når kunden klikker på det lille fremkommer hjælpetekster Ad 2) Kort & Betalingsservice (relevant til fx første betaling på kort og efterflg. abonnement via normale Betalingsservice opkrævninger) P. 7-31

8 Ad 3) Altid kort og Kort & Betalingsservice (her er det helt op til kunden selv at bestemme hvordan de ønsker at blive opkrævet) Når kunden har valgt aftaleform og accepteret vilkår, i et af ovenstående pop up vinduer, er næste skridt i flowet at indtaste kortoplysningerne. Se eksempel nedenfor. Når kunden har indtastet kortoplysninger vises bekræftelse. Hvis den pågældende kunde ikke har en aktiv e-boks, vil vedkommende blive bedt om at aktivere denne. Hvis kunden har en aktiv e-boks (dette valideres i automatisk i linket) vil tilmeldingen være afsluttet efter kortoplysningerne er indtastet, se eksempel nedenfor. P. 8-31

9 Kunden kan herefter lukke vinduet og vende retur til virksomhedens bagvedliggende side. Den side kunden vender retur til, vil være den returside, som er angivet, som del af input parametre i link url en (se nærmere specifikation for mulighederne for redirect og return url i afsnit 5. Kunden vil herudover også automatisk modtage bekræftelse om tilmeldingen i sin e-boks med specifikationer om aftalen, se eksempel nedenfor. 4.3 Redigering/afmelding af aftale Kunden skal kunne skifte kortnummer på sin aftale eller afmelde sin aftale om Automatisk på virksomhedens hjemmesiden. Det anbefales, at der benyttes bruger-login, således at kunden derigennem er identificeret og kan tilgå tilmeldingslinket (som også fungerer som afmelding og redigeringslink for eksisterende kunder). Hvis Automatisk betalings linket vises på et offentligt område (dvs. uden forudgående login) kræves, at linket først bliver aktivt efter, at kunden er P. 9-31

10 logget ind, eller hvis kunden får mulighed for at udfylde sit eget kundenummer på hjemmesiden. Systemet udleder herefter selv om kortholder har en saftale med virksomheden, og derefter viser de rette valgmuligheder. URL en behøver i denne sammenhæng kun at indeholde følgende dynamiske parametre: - PBS nummer: Kreditors ID ift. Nets - Debitor-gruppenummer: Hvilken debitorgruppe betalingerne skal tilknyttes - Kundenummer: kortholders ID i forhold til kreditor Ændrings-/afmeldingsflow for kunden Når kortholder har lavet de ønskede ændringer til sin betalingsaftale i vinduet, vil følgende bekræftelser blive vist. Hvis kunden har ændret sine kortoplysninger: P

11 Hvis kunden har afmeldt sin aftale: Efterfølgende afsnit vil være på engelsk og omhandler formatbeskrivelser, konfigurationseksempler og fejlkoder og fejltekster. P

12 5. Option call back/redirect The basic use case for client can be the following: Precondition: client has opened a page with Automatic card payment snippets embedded. Automatic card payment registration can be activated by button Register for automatic card payments. 1. Client clicks Register button. Automatic card payment registration page is opened in pop-up window. 2. Client enters necessary information and clicks proceed. 3. In terminal page client enters credit card information and funds reservation is made. 4. Receipt page is opened in pop-up window. 5. Client closes pop-up window manually. After step 4 card mandate is registered, however there s no feedback provided back to company s side about whether registration was successful. There are two additional features supported that can be used to provide some sort of feedback: - Callback to web-service. When Automatic card payment pop-up is being called from company s page an URL for callback might be passed along with other parameters. After successful card mandate registration this URL is programmatically called from Automatic card payment application via HTTP GET request and registration status is passed. - Redirect-on-success. This feature allows opening a Thank you page for client after successful card mandate registration. Redirect-on-success feature requires more thorough and complicated configuration. When redirect-on-success feature is used, use case for the client would be the following: Precondition is the same: client has opened a page with Automatic card payment snippets embedded. Automatic card payment registration can be activated by button Register for automatic card payments. 1. Client clicks Register button. Automatic card payment registration page is opened in pop-up window. 2. Client enters necessary information, accepts terms of use and clicks proceed. Terminal page is opened in pop-up window. 3. In terminal page client enters credit card information and funds reservation is made. a. Thank you page is opened in the browser window from which Automatic card payment pop-up is opened. b. Receipt page is opened in pop-up window. 4. Client closes pop-up window manually. P

13 Automatic card payment Vejledning Layout/opsætning/integration af tilmeldingslink til Automatisk The diagram below explains in high-level terms the integration between company s site and Automatic card payment pop-up. Automatic Card payment Enter data Automatic Card payment Terminal Automatic Card payment Receipt Based on which features the company would like to use in integration with card mandate registration pop-up there might be different kinds of setup works: 1. Basic setup, which enables basic use-case (also sufficient for having callback to web-service). 2. Setup for redirect-on-success functionality. As an optional thing, a proxy page may be added in between company s page and Automatic card payment registration form. The simplest variant of proxy page may be HTML document without any visual appearance, which intended to receive parameters via HTTP protocol and pass them further to Card payment pop-up. In order to do this some code need to be injected (PHP, Java/JSP or any other) into the page which can place input parameter values into HTML form and JavaScript snippet that automatically submits the form to Automatic card payment registration page. The proxy page can be used for example to default some values and/or to track, when debtor is started registration pop-up. P

14 6. Interface description This chapter describes expected URL formats, parameters that should be passed to or properly received from Automatic card payment. 1) Creditor s portal call to Automatic card payment pop-up The page URL to be called in order to open pop-up is: Either HTTP GET or POST request may be used. The URL should also be provided with parameters, containing information about creditor, product/service, debtor and first-time payment if applicable. All parameters that can be handled by the pop-up are listed in Table 1. Table 1. Pop-up parameters Parameter Data type Required Format Description Required GR RwFP Pbs Number 1 8 digits debgr Number 1 5 digits PBS number of creditor Yes Yes Debtor group number Yes Yes debnr Text 1 15 chars Debtor number (aka customer number) No* No* Cpr Number 8 or 10 digits CPR Number for debtor (if known) No No debname Text 1-35 chars Debtor name No* No* creditorreference Text 1-30 chars Reference for first-time payment --- Yes onetimeamount Number Integer Amount of first-time payment in cents --- Yes recurrentamount Number Integer Amount or recurrent payment in cents No No productdescription Text Free text up to 200 chars Description of product or service provided by creditor to debtor No Yes P

15 paymenttype Text AUTH or SALE Indicates whether payment amount should be withdrawn (SALE) or reserved (AUTH). --- Yes callbackurl Text (URL) not validated If specified called in case if registration is successful or failed. No No returnurl Text (URL) not validated If specified called from registration pop-up after the registration incl. card payment or reservation was successful. No No redirecturl Text (URL) not validated URL, where page in debtor s browser from which the pop-up has been opened should be navigated to. No No GR in table stands for General registration and RwFP Registration with first-time payment. As the pop-up can be called in two modes, Required column in the table above is split into two columns: GR (general registration) and RwFP (registration with first-time payment). --- in the Required column means that parameter is not applicable for this mode. Parameters that are marked as No* are not required if some condition is satisfied: - debnr is optional if creditor allows temporary customer number to be generated by Nets; - debname is optional if debnr is not being sent. Please note that callbackurl, returnurl and redirecturl are not validated in Automatic card payment pop up. It is expected to be valid and used as is. If invalid URL is passed it won t have negative impact on registration popup, though data in creditor s database can get corrupted because callback is not preformed successfully. Be aware that different text parameters have some limitations on kinds of characters to be used: P

16 Table 2. Allowed characters in text parameters Parameter Latin characters National characters Punctuation Space and digits debnr Yes No No No debname Yes Yes Yes Yes creditorreference Yes Yes Yes Yes productdescription Yes Yes Yes Yes 2) Callback Callback URL is called whether registration is successful or not. HTTP GET is always used to call the URL. Registration status is passed via query parameter result with two values possible: success or failure (parameter name and values are used without quotes). The result parameter is simply added to the URL, so the service which is called should be able to handle this parameter. Below are examples how callback URLs transformed before call: Example 1 Example 2 from creditor actually called from creditor actually called ) Return page (redirect-on-success) Return page in its simplest implementation is HTML document without any visual appearance which intended to receive registration status and other parameters via HTTP protocol, update opener browser window via JavaScript and automatically redirect back to BsExpress page. Return page should properly receive and handle following parameters: P

17 Parameter Data type Description receipturl Text (URL) If specified called from the registration pop-up after the registration incl. card payment or reservation was successful. result String Whether registration was successful or not ( success or failure ). Now only success is passed since return page is called in case of successful registration only. In order to handle unsuccessful registration please use callback URL, this is called in any case. redirecturl Text (URL) URL, where page in debtor s browser from which the pop-up has been opened should be navigated to. Please see detailed description of return page logic in Redirect-on-success feature setup chapter. Basic integration setup This type of setup is sufficient to use all the abilities of the pop-up except redirect in browser. The easiest way to integrate Automatic card payment call is to add piece of HTML and JavaScript into existing web-page: <form id="startbsexpform" method="get" name="startbsexpform" onsubmit="openinpopup(this, 800, 800);return false;" target="betalingservice" action=" <input type="hidden" name="callbackurl" value="" /> <input type="hidden" name="pbs" value="" /> <input type="hidden" name="debgr" value="" /> <input type="hidden" name="debnr" value="" /> <input type="hidden" name="cpr" value="" /> <input type="hidden" name="debname" value="" /> <input type="hidden" name="creditorreference" value="" /> <input type="hidden" name="onetimeamount" value="" /> <input type="hidden" name="recurrentamount" value="" /> <input type="hidden" name="productdescription" value="" /> <input type="hidden" name="paymenttype" value="" /> </form> <script language="javascript"> function openinpopup(formref, popw, poph) { P

18 } </script> window.name = 'DebtorPage'; newwin = window.open('', 'BetalingService', 'resizable = 1,width=' formref.submit(); newwin.focus(); And then a control element for debtor: + popw + ',height=' + poph); <input type="button" onclick="openinpopup(document.startbsexpform, 800, 800);">Automatisk </input> or <a href="#" onclick="openinpopup(document.startbsexpform, 800, 800);">Automatisk </a> Number and names of input elements inside form may vary since unused optional parameters may be omitted in the form. Please check Table 1 in Interface description section to find out which parameters are mandatory in your case. Basic setup is sufficient to use any parameters except returnurl and redirecturl. Redirect-on-success feature setup Redirect-on-success functionality provides ability to redirect the page in debtor s browser from which the pop-up has been opened to another URL. In order to enable this feature two things should be done: 1. Basic setup should be completed. 2. Special web page (a return page ) should be created and hosted on creditor s side. 3. Pop-up launch form should be extended with two more parameters: return URL and redirect URL. The need in special return page is dictated by cross-domain security, which does not allow updating one browser window from JavaScript in another if these windows contain HTML documents from different domain. Intention here is to temporary redirect pop-up window to a page hosted on creditor side, execute JavaScript snippet against redirecturl parameter value and navigate back to Automatic card payment registration page. With two more parameters launch form in creditor s page might look like this (part of sample is omitted since it is exactly the same as in basic setup): P

19 <form id="startbsexpform" method="get" name="startbsexpform" onsubmit="openinpopup(this, 800, 800);return false;" target="betalingservice" action=" <input type="hidden" name="callbackurl" value="" /> <input type="hidden" name="returnurl" value="" /> <input type="hidden" name="redirecturl" value="" /> <input type="hidden" name="pbs" value="" /> <input type="hidden" name="debgr" value="" /> <input type="hidden" name="debnr" value="" /> <input type="hidden" name="cpr" value="" /> <input type="hidden" name="debname" value="" /> <input type="hidden" name="creditorreference" value="" /> <input type="hidden" name="onetimeamount" value="" /> <input type="hidden" name="recurrentamount" value="" /> <input type="hidden" name="productdescription" value="" /> <input type="hidden" name="paymenttype" value="" /> </form> The return page is a simple web page that takes query parameters into form parameters and automatically does the following: 1. Takes all the input HTTP parameters into the HTML form. 2. Updates opener browser window with redirect URL. 3. Automatically submits form back to BsExpress. In order to have item 1. working, any programming language\framework that can be injected into HTML markup can be used (PHP, ASP, JSP etc.). Items 2. and 3. Require JavaScript enabled on debtor s computer. P

20 Below is an example of return page: <html xmlns=" <body onload="updateopenerandreturntobsexp();"> <form method="get" name="returntobsexpform" action="$request.receipturl"> </form> <input type="hidden" name="result" value="$request.result" /> <input type="hidden" name="redirecturl" value="$request.redirecturl" /> <script language="javascript"> function updateopenerandreturntobsexp(){ } var redirecturl = ""+document.getelementsbyname('redirecturl')[0].value; if(redirecturl.length > 0){ } window.opener.location.href = redirecturl; document.returntobsexpform.submit(); </script> </body> </html> The $REQUEST entity in code is a pseudo-entity and should be replaced in accordance to programming language supported by creditor s web-server. For example in PHP it should be <?php echo(htmlspecialchars($_request["redirecturl"]));?> instead of $REQUEST.redirecturl. Proxy-page setup It might be useful to setup proxy page in case there is some values among those passed to the pop-up that are always the same for all debtor s registrations or it is necessary to track, when debtor is starting registration. The proxy-page does not have any visual elements and is similar to the return page: 1. It receives values from debtor s page and places them into form that can be submitted to the pop-up. 2. Contains values of some parameters that are the same for all debtors so they can be defaulted. P

21 3. Some pre-registration code can be added to this page (for example tracking when debtor is started registration). 4. The page should be automatically submitted to the pop-up page. Same way as return page the proxy page requires a programming language\framework that can be injected into HTML markup can be used (PHP, ASP, JSP etc.) for implementation of items 1-3 and JavaScript enabled on debtor s computer in order to do item 4. In order to make debtor s page call the pop-up via proxy page, action parameter of form should be changed to refer proxy page: <form id="startbsexpform" method="get" name="startbsexpform" onsubmit="openinpopup(this, 800, 800);return false;" target="betalingservice" action="creditor_web_site/bsexppop-launch.html"> The proxy page example is below: <html xmlns=" <body onload="document.bsexpform.submit();"> <form method="post" name="bsexpform" action=" <input type="hidden" name="returnurl" value="creditor_web_site/bsexppop-return.html" /> <input type="hidden" name="redirecturl" value="$request.redirecturl" /> <input type="hidden" name="callbackurl" value="$request.callbackurl" /> <input type="hidden" name="pbs" value="$request.pbs" /> <input type="hidden" name="debgr" value="$request.debgr" /> <input type="hidden" name="debnr" value="$request.debnr" /> <input type="hidden" name="cpr" value="$request.cpr" /> <input type="hidden" name="debname" value="$request.debname" /> <input type="hidden" name="creditorreference" value="$request.creditorreference" /> <input type="hidden" name="onetimeamount" value="$request.onetimeamount" /> /> <input type="hidden" name="recurrentamount" value="$request.recurrentamount" <input type="hidden" name="productdescription" value="$request.productdescription" /> <input type="hidden" name="paymenttype" value="$request.paymenttype" /> </form> </body> </html> P

22 Setup Example 1: Only mandate registration Task: Creditor would like to enable debtors to register card mandates for automatic payments. Debtors are supposed to make card mandate registration without first-time payment. Callback and redirect functionality are not going to be used. Step 1. Prepare form for pop-up call and add it to debtor s page. Parameters that not used can be omitted from the form. In this example this piece of code needs to be added: <form id="startbsexpform" method="get" name="startbsexpform" onsubmit="openinpopup(this, 800, 800);return false;" target="betalingservice" action=" <input type="hidden" name="pbs" value="[pbs]" /> <input type="hidden" name="debgr" value="[debgr]" /> <input type="hidden" name="debnr" value="[debnr]" /> <input type="hidden" name="cpr" value="[cpr]" /> <input type="hidden" name="debname" value="[debname]" /> </form> <script language="javascript"> function openinpopup(formref, popw, poph) { } </script> window.name = 'DebtorPage'; newwin = window.open('', 'BetalingService', 'resizable = 1,width=' formref.submit(); newwin.focus(); + popw + ',height=' + poph); Step 2. Prepare control (let it be a button) that will launch the pop-up and add it to the same creditor s page. <input type="button" onclick="openinpopup(document.startbsexpform, 800, 800);">Automatisk </input> P

23 Setup Example 2: Mandate registration with first-time payment, callback and redirect Task: Creditor would like to enable debtors to register card mandates for automatic payments. Debtors are required to make a payment as part of registration. Creditor has set up a web-service at and would like to receive status of registration and payment to this webservice. After successful registration debtor should be redirected to Thank-you page ( It is assumed for this example that creditor uses JSP technology for debtor s portal. Creditor s pbs No and return URL will be the same for all debtors, so it is possible to use them via proxy page. Step 1. Prepare form for pop-up call and add it to debtor s page. Parameters that have defaults in proxy page (pbs and returnurl) can be omitted from the form. Since it was decided to use proxy page, the form s action changed to the proxy page. <form id="startbsexpform" method="get" name="startbsexpform" onsubmit="openinpopup(this, 800, 800);return false;" target="betalingservice" action=" <input type="hidden" name="callbackurl" value=" /> <input type="hidden" name="redirecturl" value=" /> <input type="hidden" name="debgr" value="[debgr]" /> <input type="hidden" name="debnr" value="[debnr]" /> <input type="hidden" name="cpr" value="[cpr]" /> <input type="hidden" name="debname" value="[debname]" /> <input type="hidden" name="creditorreference" value="[creditorreference]" /> <input type="hidden" name="onetimeamount" value="[onetimeamount]" /> <input type="hidden" name="recurrentamount" value="[recurrentamount]" /> P

24 /> <input type="hidden" name="productdescription" value="[productdescription]" <input type="hidden" name="paymenttype" value="[paymenttype]" /> </form> <script language="javascript"> function openinpopup(formref, popw, poph) { } </script> window.name = 'DebtorPage'; newwin = window.open('', 'BetalingService', 'resizable = 1,width=' formref.submit(); newwin.focus(); + popw + ',height=' + poph); Step 2. Prepare control (let it be a button) that will launch the pop-up and add it to the same creditor s page. <input type="button" onclick="openinpopup(document.startbsexpform, 800, 800);">Automatisk </input> Step 3. Prepare proxy page (JSP technology is used for this example) and host it at address In this example proxy page will receive all parameters except returnurl and pbs, that are defaulted. <?xml version="1.0" encoding="utf-8"?> <%@ page language="java" contenttype="text/html; charset=utf-8" pageencoding="utf-8"%> <%@ taglib prefix="c" uri=" %> <html xmlns=" <body onload="document.bsexpform.submit();"> <form method="post" name="bsexpform" action=" <input type="hidden" name="returnurl" value=" /> <input type="hidden" name="pbs" value=" " /> <input type="hidden" name="debgr" value="<c:out value="${param.debgr}"/>" /> <input type="hidden" name="debnr" value="<c:out value="${param.debnr}"/>" /> P