---- dataentry gateway ----
type                   : gateway # do not change this line
name                   : DIBS
countries              : DK, NO, SE, GB
support-added          : 1.1
support-removed        : 
auth-net-emulation     :  # enter "yes" or "no" (without quotes)
supports-3dsecure      : yes # enter "yes" or "no" (without quotes)
supports-multicurrency : yes # enter "yes" or "no" (without quotes)
gateway_url            : http://www.dibspayment.com/
----




====== DIBS ======
<WRAP center round important 90%>
Subscriptions are not supported with DIBS at this time. If you intend to sell subscriptions with your FoxyCart store, you will need to make use of another payment gateway.
</WRAP>
===== Setting Up DIBS for FoxyCart =====
  - In DIBS admin go to //MD5 keys// under the //Integration// menu item.
  - k1 and k2 are your secret 1 and secret 2.
  - Make sure //Perform MD5 control// is checked.
  - Be sure to check the //statuscode// (//Transaktionens status kode//) under //Returværdier// or //Return Values// under //Integration// and save.
  - Check the option //Accept payments using your DIBS account:// in FoxyCart admin.
  - Paste your ID and secret keys into the appropriate fields in FoxyCart admin.


===== Testing =====
==== Obtaining a Test Account ====
Contact DIBS for info. <wrap help>Know more? Feel free to edit this page with info.</wrap>
==== Test Card Numbers ====
General information - http://tech.dibs.dk/10_step_guide/your_own_test/

List of test credit cards - http://tech.dibspayment.com/D2/Toolbox/Test_information/Cards



===== Troubleshooting & Interpreting Response Codes =====
Contact DIBS for info. <wrap help>Know more? Feel free to edit this page with info.</wrap>



===== Important Notes and Caveats =====

==== Possible Action: Datafeed Handling ====

At the time of the customer completing the transaction - we don't necessarily know whether the transaction was completed yet or not. We instead rely on a notification from the gateway after the checkout has been completed to confirm whether the transaction was approved or not. To handle this, transactions are initially marked as pending, and when we get a confirmation from the gateway on the result of the transaction, we update it accordingly. Each time the status changes, a datafeed will be sent to your endpoint if configured with the transaction details and the ''status'' node will be present.

The ''status'' node can contain one of three different values: ''pending'', ''approved'' or ''rejected''. Depending on the types of actions you're needing to perform at your datafeed endpoint, you need to make sure the appropriate status value is present first.

===== User Notes and Experiences =====
<wrap tip>If you have tips, experience, or helpful notes related to this gateway that would benefit others, please add them below, including your name and the date.</wrap> We reserve the right to edit or remove comments that don't add value to this page.