menu

Payment API

What's on this page

API Reference / Transaction Export

Transaction export MT940

MT940 format

We support export of successfully completed transactions in ING’s MT940-format. The operating Mode of the Api Key used decides if the export will contain TEST or LIVE transactions.

From Mijn ING Zakelijk:

An MT940 Customer Statement Message is a message standard for electronic account statements from the Society for Worldwide Interbank Financial Telecommunication (SWIFT). ING MT940 format is based on the standard of SWIFT FIN: Category 9 Cash Management and Customer Status. Many software process the data structured according to this international standard. With this guide, you can deploy the MT940 format itself into your systems.

Mapping of Tag 61 subfields with our transaction details.

Subfield Length Content Mapping Example
Valuta date 6!n YYMMDD Create date 150930
Booking date 4!n MMDD If paid out the paid out date, else create date 0930
Credit/Debit 1!x C or D type Sale:C or Refund:D
Amount 15n Transaction amount Amount 10.99
Transaction type 4!x The SWIFT transaction code is used and starts with “N” followed by a transaction type. SWIFT Transaction types are available in the attachments Fixed value: Transfer NTRF
Payment reference 16x The payment reference is derived from the transaction during processing. If no payment reference is available, “NONREF” is used If available your merchant order reference, else NONREF Order 1234
Transaction reference 16!x Starts with “//” followed by a unique ING reference (14 characters) If available the paid out reference, else 00000000000000 //00000000000000
Additional details 34x /TRCD// (See attachments for ING transaction codes) Fixed value: SEPA Credit Transfer /TRCD/00100

Example

:61:1509280928C316,35NTRF1091fbae-c4f7-45//00000000000000
/TRCD/00100/

Mapping of Tag 86 code words with our transaction details.

Code word Description Length Mapping Example
/EREF/ End to End reference 35x Transaction reference EREF/I15092816080395614.1/
/CNTP/ Counterpart ID 131x If available customer name & customer city CNTP///John Doe/Brussel/
/REMI/ Remittance info max 255x Contains custom tags /MOP/ and /TXDATE/. If available the unstructured reference used to collect the sale or pay the refund is prefixed REMI/USTD//0ad76e30 AFREK. CPSPi BCMC DAT. 20150923/5266 AANT. 1 MREF. CCV Demo/

In addition to these tags which are part of the MT940 spec, the remittance info contains custom tags to facilitate parsing useful information about the transaction.

Code word Description Length Mapping Example
/MOP/ Method of Payment 3x - 12x Will contain the payment method or in case of method card the brand. Always uppercase /MOP/IDEAL
/TXDATE/ Transaction date 15x Contains he creation date of the transaction in format ‘YYYYMMDD HHMMSS’ /TXDATE/20190514 071433

Example

:86:/EREF/I15092816080395614.1/

Export transactions as MT940 request

  • Resource: /api/v1/transaction/export/mt940
  • Method: GET
  • Authentication: basic auth
  • Parameters
Name Required Description
from Conditional Returns payments created after this timestamp, including payments with this create timestamp. Must be used with until.
until Conditional Returns payments created before this timestamp, excluding payments with this create timestamp. Must be used with from.
paidoutAfter Conditional Returns payments paidout after this timestamp, including payments with this paidout timestamp. Must be used with paidoutBefore.
paidoutBefore Conditional Returns payments paidout before this timestamp, excluding payments with this paidout timestamp. Must be used with paidoutAfter.
currency No Returns payments with the same currency. Possible values: Currencies. Defaults to EUR
customIban No This value will override your user’s merchant IBAN in the resulting file (if present and not empty)

Example

{1:F01INGBNL2ABXXX0000000000}{2:I940INGBNL2ABXXXN}{4:
:20:0001461842521445
:25:GE62510007547061EUR
:28C:00000
:60F:C160428EUR0
:62F:C160428EUR0
:64:C160428EUR0
:65:C160428EUR0
:86:/SUM/0/0/0/0/