Last update 20/04/2016

7. Payment method exceptions

For certain payment methods, the parameter values differ from the standard credit card values.

7.1 Direct Debits

7.1.1 Direct Debits AT

The following table contains the specific parameter values allowing the transmission of Direct Debit AT transactions via DirectLink.

Format: AN= Alphanumeric / N=Numeric, maximum allowed amount of characters
Field Description Format/Value
CARDNO

Bank account number

AN, 21

Format: XXXXXXXXXXXBLZYYYYY

XXXXXXXXXXX: account number, numeric, 11 digits.
YYYYY: Bank code (Bankleitzahl), 5 digits. 
CN Bank account holder’s name AN, 35
ED Expiry date
„99/99“ oder „9999“
OPERATION

Operation code (Action to be performed)

A, 3

Possible values:

  • RES: authorisation
  • SAL/SAS: debit money from the bank account
  • RFD/RFS: refund money (*)
OWNERADDRESS Address of the account holder AN, 50
OWNERTOWN City/town of the account holder AN, 40
OWNERZIP Postal code of the account holder AN, 10
PM Payment method AN, 25

“Direct Debits AT”

(*If the Refund option is available and active, and DTAUS Refunds is available)

7.1.2 Direct Debits DE (ELV)

The following table contains the specific parameter values allowing the transmission of ELV transactions via DirectLink. (not Wirecard/Billpay)

Format: AN= Alphanumeric / N=Numeric, maximum allowed amount of characters
Field Description Format/Value Mandatory
CARDNO Bank account number

IBAN: 22 alphanumeric characters

OR

Bank account number + BLZ. Format: XXXXXXXXXBLZYYYYYYYY
XXXXXXXXXX: account number, numeric, 1 to 10 digits.
YYYYYYYY: Bank code (Bankleitzahl), 8 digits.
Yes
CN Bank account holder’s name AN, 35 Yes
ED Expiry date „99/99“ oder „9999“ Yes
MANDATEID Unique mandate reference.
Telego:
If not provided, the platform will take the ORDERID or PAYID
Note: If not provided, easycash will generate a value.

Telego: AN, 35 / Charset: “A-Z a-z 0-9 space /-?:().,'+”)
If not provided, the platform will take the ORDERID or PAYID

Easycash: Format: AN, 27 / Charset: “A-Z a-z 0-9 space /-?:().,'+”)
Note: If not provided, easycash will generate a value.

No
OPERATION Operation code (Action to be performed)

A, 3

Possible values:

  • RES: authorisation
  • SAL/SAS: debit money from the bank account
  • RFD/RFS: refund money (*)
No
OWNERADDRESS Account holder's street name and number AN, 50 Yes
OWNERTOWN Account holder's city/town AN, 40 Yes
OWNERZIP Account holder's postal code AN, 10 Yes
PM Payment method

AN, 25

"Direct Debits DE” 

Yes

Note: These fields can be returned in the DirectLink XML-response and need to be included in the SHA-IN calculation (optionally also SHA-OUT)

(*If the Refund option is available and active, and DTAUS Refunds is available)

7.1.3 Direct Debits NL

The following table contains the specific parameter values allowing the transmission of Direct Debits NL transactions via DirectLink.

Format: AN= Alphanumeric / N=Numeric, maximum allowed amount of characters
Field Description Format/Value
CARDNO Bank account number Regular Dutch account number: max. 10 alphanumeric characters (if less, left pad with zeros).

OR

IBAN account number: max. 35 alphanumeric characters (SEPA)

CN Bank account holder’s name AN, 35
ED Expiry date „99/99“ oder „9999“
OPERATION

Operation code (Action to be performed)

A, 3

Possible values:

  • SAL or SAS: debit money from the bank account
  • RFD or RFS: credit money to the bank account (refund) 
OWNERTOWN City of the bank account holder AN, 40
PM Payment method

AN, 25

“Direct Debits NL” 

Only relevant for SEPA (*) transactions:  
BIC Bank Identifier Code AN, 11
MANDATEID

Unique mandate reference.

Note: If not provided, the ORDERID will be used.

AN, 35

No spaces; cannot start or end with a forward slash "/", or contain two consecutive slashes. 

SEQUENCETYPE

The Direct Debit transaction type

Note: If not provided, the transactions will be considered as a “one-off” and value "OOFF" will be used. 

Possible values to indicate the Direct Debit transaction type (AN, 4):
  • "FRST": First collection of a series of Direct Debit instructions
  • "RCUR": Direct Debit instructions where the debtor's authorisation is used for regular Direct Debit transactions initiated by the creditor
  • "FNAL": Final collection of a series of Direct Debit instructions (afterwards same MandateID can't be used anymore)
  • "OOFF": Direct Debit instruction where the debtor's authorisation is used to initiate one single Direct Debit transaction
SIGNDATE

Date mandate was signed by the buyer.

Note: If not provided, the transaction date will be used.

YYYYMMDD

(*SEPA: Single Euro Payments Area)

Note: These fields can be returned in the DirectLink XML-response and need to be included in the SHA-IN (and optionally SHA-OUT) calculation.

7.2 Payment methods with only maintenance via DirectLink

For certain payment methods (excluding credit cards), you cannot send new transactions via DirectLink, but you can send certain maintenance operations via DirectLink. This is the case for PostFinance Card, PostFinance E-finance, PayPal Express Checkout and TUNZ.

When sending maintenance operations, the PM, BRAND, CARDNO and ED fields are not required, so no specific values need to be sent for these payment methods.

This website uses cookies to be able to give you the best user experience. If you don't want to accept these cookies, we allow you to change the cookie settings. Click 'Accept' to allow all cookies from this website.

Cookie settings

Introduction

Functional

Functional cookies are required for the website to operate correctly. These cookies cannot be disabled.

Optimized

Optimization cookies allow us to analyze site usage so we can measure and improve our website.
This is the default level.

Personalized

Personalization cookies are used for social media and advanced personalization. They allow us to show you information related to your company.


Example functionality allowed

  • Store country preference
  • Store language preference

Example functionality not allowed

  • Saving personal data
  • Anonymous tracking via Google Analytics
  • Tracking for remarketing purposes

Example functionality allowed

  • Store country preference
  • Store language preference
  • Anonymous tracking via Google Analytics

Example functionality not allowed

  • Saving personal data
  • Tracking for remarketing purposes

Example functionality allowed

  • Store country preference
  • Store language preference
  • Anonymous tracking via Google Analytics
  • Serve content relevant to your interests
  • Serve ads relevant to your interests
  • Tracking for remarketing purposes

Example functionality not allowed

  • Saving personal data