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!

Split Mode

Description

The Split-Mode combines the benefits of the Payment Page with an authorization via a stable server-to-server interface. This leads to a significant increase in process control with credit card payments. In this way faulty debiting is almost completely eliminated.

When using the Split Mode, the final authorization call happens via a secure server to server request. As already seen with the Secure Fields integration, the uppTransactionId is used to 'finalise' a payment transaction with a call to the Split Authorization API Endpoint.

Merchant Setup

At first contact our team at Datatrans and ask to have your merchant-id setup for split processing

Payment Page Setup

Set up your payment pages as described here. Once your payment page is setup and your merchant-id is used to configure split processing the merchant will then be redirect to the success, error and cancel urls you defined. The return urls will receive all necessary return parameters to proceed with the split processing. The return parameters will look something like this:

merchantId = 1100002469
currency = CHF
expm = 12
amount = 1000
reqtype = CAA
uppTransactionId = 180704121453549743
language = en
refno = 969522
theme = DT2015
pmethod = VIS
sign = 130930125157625194
expy = 18
status = success

Finalize the Authorization

Send the uppTransactionId together will all other needed data to your server and call the Split Authorization API Endpoint.

Request

curl -v -X POST https://api.sandbox.datatrans.com/upp/jsp/XML_authorizeSplit.jsp \
-H 'Content-Type: application/xml' \
-H 'Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=' \
-d @- << EOF
<?xml version="1.0" encoding="UTF-8" ?>
<authorizationSplit version="4">
   <body merchantId="1100002469">
     <transaction refno="969522">
       <request>
         <uppTransactionId>180704121453549743</uppTransactionId>
         <amount>1000</amount>
         <currency>CHF</currency>
       </request>
     </transaction>
   </body>
</authorizationSplit>
EOF

Response

<authorizationSplit version="4">
 <body merchantId="1100002469" status="accepted">
  <transaction refno="757181" trxStatus="response">
   <request>
    <uppTransactionId>180704121453549743</uppTransactionId>
    <amount>1000</amount>
    <currency>CHF</currency>
   </request>
   <response>
    <responseCode>01</responseCode>
    <responseMessage>Authorized</responseMessage>
    <authorizationCode>918639404</authorizationCode>
    <acqAuthorizationCode>135918</acqAuthorizationCode>
    <maskedCC>424242xxxxxx4242</maskedCC>
    <sign2>N/A</sign2>
   </response>
 </transaction>
 </body>
</authorizationSplit>

Split Mode


Suggested Edits are limited on API Reference Pages

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