2. Choose your method of authorization
There are two main authorization methods:
Method 1: DIBS FlexWin or Payment Window.
Once the customer has decided which items he wishes to purchase and has informed the online shop where these are to be delivered, the DIBS system assumes full control of the customer’s browser window via pop-up or inline. Upon successful completion of payment or in the event the customer wishes to cancel the payment, the customer will be returned to the webshop.
Method 2: Server-to-server.
Once the customer is ready to start the payment process, the webshop displays a form in which the necessary card information must be entered. This card information is transferred from the customer’s browser to the webshop itself which then carries out authorization with the help of a web-service call to DIBS.
To assist you in selecting between methods 1 and 2, take a look at the summary below of the main advantages and disadvantages.
Method 1 pros and cons
- Seen from a technical viewpoint, integration is definitely easier.
- The payment window hosts a variety of sophisticated features which facilitate the process for the cardholder and make implementation easier (e.g. client-side algorithm control of card numbers and the automatic application and calculation of extra charges).
- This method supports more types of payments since several payment types require control of user interface level.
- When implementing new types of payment, your shop does not need to do anything — this can be activated or deactivated at DIBS.
- Language control — so you don’t have to worry about setting up your own pages in several languages.
- The most inexpensive solution — included in all products.
- With the DIBS payment window there is no need for the customer to purchase and install an SSL-certificate, a task which could prove both complex and costly.
- And last but not least: The DIBS payment window is set up so card data never comes into direct contact with the systems of the individual web shop. This relieves the shop of any relationship with PCI, hence the setup will not require any form of external certification or control.
- You have less control of the layout/appearance of your payment pages.
- Dialogue is relatively fixed without much room for customization.
Method 2 pros and cons
- Full control of layout/appearance of payment pages.
- There are standard objects used for the control of "server-to-server" communication with DIBS (DIBS .NET Object, DIBS PHP Functions and DIBS JAVA Bean).
- Your own optimal control of the payment procedure.
- Acquisition of own SSL certificate is mandatory, hence a costlier solution.
- Integration package required.
- You have to make a number of corrections if you wish to connect additional forms of payments at a later date, as a number of payment forms are not available with this method.
- Having contact with credit card data, the webshop will be subject to the current PCI requirements — which in certain instances may prove to be an expensive venture. Please visit www.pcisecuritystandards.org for further information.