The developer.datatrans.com Developer Hub

Welcome to the developer.datatrans.com developer hub. You'll find comprehensive guides and documentation to help you start working with developer.datatrans.com as quickly as possible, as well as support if you get stuck. Let's jump right in!

paymentmethod=DEA

paymentmethod=DEA

Payment Process
Integration

Authorization

:heavy-check-mark+:

Payment Page

:heavy-check-mark+:

Deferred Settlement

:x+:

Split Mode

:x+:

Refund

:x+:

Mobile SDK

:x+:

Cancel

:x+:

Alias

:x+:

Description

So as to simplify payments for online products and services, the Dutch banks have developed the iDEAL method of payment. iDEAL allows online payments via online banking.

iDEAL is a standard method of payment for secure online payments directly between bank accounts. If you provide iDEAL in your webshop as a method of payment, a direct link to your bank is established. In other words, this connection to iDEAL enables every visitor to your website, who has access to the online banking at one of the participating banks, to handle his or her payment in this way. The basic requirement is a branch or the company’s headquarters in Holland.
Payment Method provider website :link+:

Test

iDeal does not support a test enviornment

Web payment flow

 1 
[Not supported by viewer]
Customer clicks Pay
Customer clicks Pay
Merchant Website
Merchant Website
Merchant Server
Merchant Server
Redirects to Bank
Redirects to Bank
Bank
Bank<br>
Customer enters Banking Information
[Not supported by viewer]
 2 
[Not supported by viewer]
 4 
[Not supported by viewer]
Authorization / Forwarding
Authorization / Forwarding
 5 
[Not supported by viewer]
Receives Result 
Receives Result 
5.1
[Not supported by viewer]
 6 
[Not supported by viewer]
Invokes merchant's
POST URL (Webhook)
Invokes merchant's<br>POST URL (Webhook)
Receives Result 
Receives Result 
 7 
[Not supported by viewer]
Redirects customer back to merchant
Redirects customer back to merchant
Customer gets redirected to merchant page
Customer gets redirected to merchant page
 3 
[Not supported by viewer]

Server to Server API calls

After a transactionId or alias was received by completing the payment flow on the web, the following server to server API calls can be used to do other actions.

Authorization

Is only possible through the web interface.

Settlement

Is not possible because it is a direct debit method

Cancel

Can not be canceled since it is a direct debit method

Credit

Credit option not available

Status

Request

curl -v -X POST https://api.sandbox.datatrans.com/upp/jsp/XML_status.jsp \
-H 'Content-Type: application/xml' \
-H 'Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=' \
-d @- << EOF
<?xml version="1.0" encoding="UTF-8" ?>
<statusService version="3">
  <body merchantId="1000011011">
    <transaction>
      <request>
        <uppTransactionId>180830161324498844</uppTransactionId>
        <reqtype>STX</reqtype>
      </request>
    </transaction>
  </body>
</statusService>
EOF

Response

<?xml version='1.0' encoding='UTF-8'?>
<statusService version='3'>
    <body merchantId='1000011011' status='accepted'>
        <transaction trxStatus='response'>
            <request>
                <uppTransactionId>180830161324498844</uppTransactionId>
                <reqtype>STX</reqtype>
            </request>
            <response itemNr='1'>
                <responseCode>11</responseCode>
                <responseMessage>Trx authentified</responseMessage>
                <refno>396617</refno>
                <refno2>Testing purchase</refno2>
                <amount>100</amount>
                <currency>EUR</currency>
                <authorizationCode>409188939</authorizationCode>
                <pmethod>GPA</pmethod>
                <uppTransactionId>180830161324498844</uppTransactionId>
                <maskedCC></maskedCC>
                <aliasCC></aliasCC>
                <expm></expm>
                <expy></expy>
                <trxDate>20180830</trxDate>
                <trxTime>161324</trxTime>
                <trtype>05</trtype>
            </response>
        </transaction>
    </body>
</statusService>

iDeal


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.