Hosted form

Introduction

The hosted form mode is the easiest and safest way to integrate Dalenys.

It also prevents you from being impacted by PCI-DSS constraints, since none of the sensitive data (card code, cryptogram) passes through your servers.

Basic workflow

Here is a simple diagram illustrating the hosted form workflow.

Workflow

  1. You display a form to the user with all Dalenys parameters as hidden fields.
  2. The user submits the form through his browser. The submit process will result in redirecting the user to the Dalenys platform with all Dalenys parameters in a POST request.
  3. Dalenys displays a payment form to the user, in which he can fill in his card data.
  4. The user submits the payment form, then the card data transit from the user’s browser to the Dalenys platform.
  5. The Dalenys platform sends a request to the bank network and waits for the result.
  6. Dalenys redirects the user to the merchant’s website on the REDIRECT_URL along with the transaction parameters (of which EXECCODE and TRANSACTIONID).
  7. In parallel, the transaction result is confirmed by a notification request sent to the merchant’s ‘NOTIFICATION_URL containing the transaction’s parameters (of which EXECCODE and TRANSACTIONID).
info

The REDIRECT_URL and the NOTIFICATION_URL can be configured through the Dalenys extranet, in the technical account configuration.

Authentication

In order to be authenticated, your transaction request must be signed with the dalenys_signature function as described in the authentication section.

Basic hosted form example

Here is a simple code sample to display a Dalenys hosted payment form:

<form method="post" action="https://secure-test.be2bill.com/front/form/process">
    <input type="hidden" name="IDENTIFIER" value="YOUR_IDENTIFIER" />
    <input type="hidden" name="OPERATIONTYPE" value="payment" />
    <!-- 1000 => EUR 10 -->
    <input type="hidden" name="AMOUNT" value="1000" />
    <input type="hidden" name="CLIENTEMAIL" value="john.snow@example.com" />
    <input type="hidden" name="CLIENTIDENT" value="john.snow" />
    <input type="hidden" name="DESCRIPTION" value="Knows nothing" />
    <input type="hidden" name="ORDERID" value="1234" />
    <input type="hidden" name="VERSION" value="3.0" />
    <!-- Generated hash -->
    <input type="hidden" name="HASH" value="15477dcb8687adf90fa51e418f3c1a2d025f40b177a978c2734514734633b3c4" />
</form>

Validating the transaction status

In the hosted form mode (contrary to the server-to-server mode), the request is not directly initiated from the merchant’s platform to Dalenys, thus you need to process the transaction result through both the nofication and the redirection, separately.

warning

Keep in mind that the notification request is sent asynchronously (by default). It means that you can receive the notification before or after the user redirection to your platform.

Hosted form options

The hosted form is easily customised with several options described below.

Expiration date

If you don’t want a displayed payment form to live forever, you can configure it to expire after a certain date.

info

The TIMEZONE must be specified.

  • TRANSACTIONEXPIRATIONDATE datetime(yyyy-MM-dd HH:mm:ss)

    Form expiration date. By default, the date is UTC, the timezone can be specified by using the TIMEZONE parameter.

  • TIMEZONE string(1-128)

    Timezone / default value : UTC. Please see the Data sheet dedicated list of available timezones.

Fields pre-filling and/or hiding

It is possible to display the form with pre-filled fields, if you already have the relevant user data in your database.

Indeed, if you supply CLIENTEMAIL and/or CARDFULLNAME fields, they will appear already filled in the payment form.

If you supply these fields you can even choose to hide them by using optional fields HIDECLIENTEMAIL and HIDECARDFULLNAME valued to “yes”.

Enabling the user to choose to create an ALIAS for next transactions

Please refer to the Operations / Recurring payment section to setup recurring payment with aliases.

Even though you can create an alias on all your transactions, you can also leave it up to the user to do so, by using the optional parameter DISPLAYCREATEALIAS valued to yes.

This option will display a checkbox to the user, enabling him to choose whether he wants to be enrolled in your recurring payment strategy or not.

Alternative templates

You can use one of the following 3 alternative responsive templates provided by Dalenys.

To set up a template on a Dalenys account, simply copy / paste the URL in the TEMPLATE_URL field in Dalenys Extranet, in the technical account configuration.

warning

Please ensure to use an adapted template to your payment account type.

Template 1

  • https://form-template.dalenys.com/template1
  • https://form-template.dalenys.com/template1_amex
  • https://form-template.dalenys.com/template1_bcmc
  • https://form-template.dalenys.com/template1_giropay
  • https://form-template.dalenys.com/template1_ideal

Template 2

  • https://form-template.dalenys.com/template2
  • https://form-template.dalenys.com/template2_amex
  • https://form-template.dalenys.com/template2_bcmc
  • https://form-template.dalenys.com/template2_giropay
  • https://form-template.dalenys.com/template2_ideal

Template 3

  • https://form-template.dalenys.com/template3
  • https://form-template.dalenys.com/template3_amex
  • https://form-template.dalenys.com/template3_bcmc
  • https://form-template.dalenys.com/template3_giropay
  • https://form-template.dalenys.com/template3_ideal

Form customization

It is possible to customize your payment form at your will by providing an url pointing to your own platform in the TEMPLATE_URL field in Dalenys Extranet, in the technical account configuration.

You can configure up to 2 templates URLs, one dedicated to desktop display, the other one to mobile device display.

For each form transaction, the Dalenys platform will try to fetch the appropriate template registered as TEMPLATE_URL, but you can manually specify which template to use by using the USETEMPLATE parameter:

  • USETEMPLATE web, mobile

    Which custom payment form to use.

The template should be a classic and valid HTML page containing a %PLACEHOLDER% string which will be replaced by the Dalenys payment method specific form HTML code.

tips

If you provide resources such as stylesheets, images (…) in your template, you must use absolute links, since relative linking will not work. All your links must be HTTPS links with a valid certificate, otherwise the user’s browser will display security alerts.

info

If the TEMPLATE_URL page is too slow or not reachable, the Dalenys default page will be used instead.

Fallback mode

Mobile devices

We highly recommend to force numeric keyboard display on mobile devices for the card code and card CVV fields, by adding Javascript :

<script type="text/javascript">
function displayNumericKeyboard(elemId)
{
    document.getElementById(elemId).type = "tel";
}
</script>

<body onload="displayNumericKeyboard('b2b-ccnum-input'); displayNumericKeyboard('b2b-cvv-input');">

Iframe integration

It is even possible to use this customization mode through an iframe to ensure a better payment integration.

iframe integration is a good solution to easily include your payment page in your website.

info

With iframe mode, the payment page will be displayed in the browser with your own TLS certificate through your own domain name.

Iframe integration

Remember that after the payment form validation, the REDIRECT_URL will be displayed only in the iframe.

If you want to redirect in the whole parent page, you must use some JavaScript as in this example :

<script type="text/javascript">
    window.top.location.href = "http://myshop.com/payment/confirmation";
</script>