This is a discussion on Dibs Payment Integration within the PHP Programming forums, part of the Web Development category; Hi friends.. i am working on shopping cart project in which.. i would like to use DIBS as my payment ...
| |||||||
| Register | FAQ | Members List | Calendar | Mark Forums Read |
| |||
| Hi friends.. i am working on shopping cart project in which.. i would like to use DIBS as my payment gateway... i belive..that...some of you would have used it.., so can some give me tips for using it..?
__________________ J Suresh Kumar Google Hacks ![]() |
| Sponsored Links |
| |||
| Hi Suresh, When integrating DIBS, certain elements must be taken into consideration: 1. How do you wish to carry out the authorization? 2. How do you wish to carry out capture? 3. Do you wish to have reports automatically sent from the DIBS system to your own? If you have answers for these questions, i can get a clear idea of your requirement.
__________________ H2O Without us, no one can survive.. |
| |||
| hi H20 Thanks for your options... but as far as DIBS is concerned, i dont have any idea.. ! it would be help ful.. if you would suggest me the right option..
__________________ J Suresh Kumar Google Hacks ![]() |
| |||
| yes suresh, I will get you all the possible ways of integration and you can choose it yourself. First of all we go with "method of authorization" Method of authorization: Definition: Authorization is the point where card information is keyed in and a check is carried out to ensure that there are sufficient funds on the customer’s credit card for a given purchase, etc. Types: 1. DIBS 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. Advantages: 1. Integration is definitely easier than "server-to-server". 2. The Payment Window hosts a variety of sophisticated features which facilitate the process for the cardholder and make implementation easier 3. When implementing new types of payment, your shop does not need to do anything – this can be activated or deactivated at DIBS. 4. 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. Disadvantages: 1. You have less control of the layout/appearance of your payment pages. 2. Dialogue is relatively fixed without much room for customization. 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. Advantages: 1. Full control of layout/appearance of payment pages. 2. There are standard objects used for the control of "server-to-server" communication with DIBS. 3. Your own optimal control of the payment procedure. Disadvantages: 1. Acquisition of own SSL certificate is mandatory, hence a costlier solution. 2. Integration package required. 3. Customization is necessary 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. Choose the one which suits you and so we can move on from there. Wishes, H2O
__________________ H2O Without us, no one can survive.. |
| |||
| Thanks H2O but do DIBS provide us with the sample template.. as in the case of Paypal..? and also is there an option for testing with the sample "Test Account " if so let me know ...!
__________________ J Suresh Kumar Google Hacks ![]() |
| |||
| I think you didn't get idea about methods provided by "H2O". In DIBS Payment Window method, the webmaster will have to pass the essential payment processing information to DIBS server using DIBS form. i.e, the DIBS payment form should be integrated to our site. In other sense, on order placment, the control will transfer to DIBS payment form. In Server-to-server, the form should be developed on our own and integrated with DIBS API. Only the payment values be sent to the processing server for validation. So to conclude, DIBS Payment Window is basic method of processing which requires no development time and will not support extended features. Whereas Server-to-server includes extended features. |
| |||
| ok.. bluesky.. Thats fine..! i will prefer to use the server-to-server method...,So will the dibs API provide us the details of form field values....which we would be to sending to the dibs API..? also..can you give some information about storing order information thru dibs..?
__________________ J Suresh Kumar Google Hacks ![]() |
| |||
| fine suresh, Before entering into API implementation, you have to conclude what method of capture to be implmented on your end. I have furnished all the available capture methods. Manual capture: An administrative interface is included in all DIBS subscriptions, enabling the user to log in and execute payment operations, incl. capture. If you deal with relatively few orders (e.g. less than 100 per day), this interface would be the ideal choice. Automatic capture through API: When employing "Remote capture", capture is not managed via DIBS Administration, but instead via an HTTP-call to the DIBS API. This is relevant in several cases, e.g. where the shop’s website is already equipped with an administration interface, or if you wish to manage capture from other existing administrative systems. Instant capture: Instant Capture simply means that capture and authorization occur simultaneously. This is relevant in certain cases where the transfer of funds is simultaneous with the delivery of an item. Instant capture requires a command to initiate capture (via the capturenow parameter) and capture must also be activated at the DIBS Central Administration. Furthermore, it has to be approved the acquirer. Batch capture: Batch Capture is applied when a webshop continuously delivers files containing several transactions requiring capture – typically once every 24 hours (see API-description of information on file format). Upon successful processing of the file, a file is returned (also via FTP) which contains status information on each individual transaction. Furthermore, an e-mail may also be generated containing information on any problems relevant to the batch-run, e.g. if a transaction could not be renewed. Batch capture is especially relevant in cases where the underlying logistics do not make any current capture requests possible (or in cases where a company’s administrative system does not have any direct Internet access). You can also look at Batch capture as a type of tool, if you wish to automate the capture process. Better try to analyze your need and then come up with capture method. Regards, >>>>>>>: Blue Sky :<<<<<<< Last edited by bluesky : 08-03-2007 at 09:53 AM. |
| |||
| I am also working in dibs integration. Thank god, i got a help in this website. Can you tell me about capture "Batch Capture" works Thanks in advance.
__________________ G.A.P Last edited by garunprasad : 08-03-2007 at 10:02 AM. |
![]() |
| Thread Tools | |
| Display Modes | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| paypal integration | sathian | C# Programming | 1 | 02-27-2008 09:45 PM |
| SSL integration for ASP.NET web application | garunprasad | ASP and ASP.NET Programming | 13 | 08-23-2007 05:29 AM |
| Need help on payment gateway integration in a website using C# | garunprasad | C# Programming | 1 | 08-01-2007 04:44 AM |
| Credit cards or Payment Payment Processors | nhoj | eCommerce | 0 | 04-03-2007 12:29 PM |
| Integration Testing | sri_cci | Software Testing | 2 | 03-30-2007 02:52 AM |