Mastercard Payment Services operate Betalingsservice, a widely used and common agreement targetting consumers and businesses in Denmark.

​
Setup a new agreement

First step is to register for a Betalingsservice agreement here. Debitdirect can also sign you up as a paid service.

When you sign up for the agreement, be sure to use the following identification in the step of using your designated data processer (data leverandør). Be sure to indicate that you want to use an external data processor.

Data processor: 38571583

Expect 4-5 business days before your get confirmation on your company e-boks. You can continue with the next steps, however your agreement will not be active until you get confirmation from Mastercard Payment Services.

​
Migrate an existing agreement

First step is to change the designated data processor for your existing Betalingsservice agreement. Sign in with your company MitID here to change the data processer.

When you change the agreement, be sure to use the following identification in the step of using your designated data processer (data leverandør). Be sure to indicate that you want to use an external data processor.

Data processor: 38571583

​
Request mandates from Betalingsservice

On the last page, type the following into the note field of the agreement configuration.

We are changing our data processer, and request that Betalingsservice provide a 605 delivery file with all mandates to the newly designated data processer Debitdirect - 38571583. We would like the change to happen on dd-mm-yyyy.

Expect 4-5 business days before your get confirmation on your company e-boks. You can continue with the next steps, however your agreement will not be active until you get confirmation from Mastercard Payment Services.

When all mandates are transferred to Debitdirect, no customer details is shared. If you are operating a Betalingservice Total agreement, you will have to ensure the customer details are connect.

​
Betalingservice total

Mastercard Payment Services offer a special agreement type for Betalingservice named Betalingservice Total. This agreement type offers customers to distribute payment-slips prior to any invoice or bill of payment.

Debitdirect does not support Betalingservice distributing payment-slips. However you can use Betalingservice Total to provide after-the-fact payment.

When adding a Betalingservice Total agreement, be sure to set the agreementType parameter to total, and please note that all customer information must be updated correctly. For Betalingservice Total, Debitdirect will provide the customer details as part of the payment.

​
Creating an agreement via API

To setup a Betalingservice agreement, the following parameters are supported. The parameters can be obtained from your agreement letter with Betalingservice.

ParameterTypeValue
cvrNumber *String. Required.8-digit cvr number.
pbsNumber *String. Required.8-digit BS merchant number.
creditorNumber *String. Required.8-digit BS merchant number.
agreementTypeString. Optional.Either value: standard, total

​
API Request

Use a scheme of nets-bs to indicate that you are creating a Betalingsservice agreement. More detail on the API endpoint can be found here.

Use the following snippet:

curl -X POST https://api.debitdirect.io/merchants/agreements \
    -H 'Content-Type: application/json' \
    -H 'Authorization: Basic XXXXXXXXXXXX' \
    -d '{
        "Scheme" : "nets-bs"
        , "Test" : false
        , "SchemeData" : 
        {
            "CvrNumber" : "12345678",
            "CreditorNumber" : "87654321",
            "PbsNumber" : "87654321",
            "AgreementType" : "standard"
        } }'

You will get a response as follows:

OverviewMandates