DIBS API integration (Method 2)

- API introduction

Please note, that SSL connections require a PCI certification, as directed by Visa International.

All pages displayed to the customer, are placed on your shop’s own webserver, if you have a form on your server, your own SSL certificate, and communication with DIBS takes place via “server to server” communication. As a consequence of the SSL connection, the browser will show a closed padlock in its statusbar to indicate a secure connection.

Breaking this down into a simple diagram, payments with a payment card takes place as follows:

• The customer is presented with a form where information relating to his payment card is entered.
• This information is sent from the customer’s browser to the shop’s webserver (which is the reason for the shop having to have its own SSL certificate).
• The shop’s webserver sends an authorization inquiry (auth.cgi) to DIBS who will either reject or approve the transaction.
• The shop’s server displays the response to the customer (approved/rejected) and a receipt of the purchase, in the case of an approved transaction.

TIP:  It’s very easy to engage in “server to server” communication with DIBS by using a standard module, e.g. DIBS DOT Net, DIBS JAVA Bean or DIBS PHP Functions. By studying the DIBS API, you can also compose a module yourself which can “speak” to DIBS. If you plan to do this, please make sure your new module can handle extra variables, since new variables can be added.