ING Wholesale Banking

SWIFT MyStandards Readiness Portal

How to test payment files

Version 1.0 | January 2017

1

How to test payment files

Go to the website: https://mystandards.swift.com/ and Login

Click on Portals in the homepage

And select the portal in which you want to test

Step 1

Step 2

2

How to test payment files

Select the payment you want to test, for instance the SEPA Credit Transfer or SEPA Direct Debit

Step 3

3

How to test payment files

Drag & drop or upload the payment file you want to test

Select the payment type in the right screen

Click Test at the bottom of theright screen

Step 4

4

How to test payment files

By clicking on the error message you are directed to the exact spot of the error. On the right-hand screen the error and solution are explained.

You can repair the error at the bottom of the screen directly.

Step 5

5

How to test payment files

Adjust the file at the bottom of the screen and click revalidate at the top right of the screen

Step 6

6

How to test payment files

If the message is valid against the Usage Guideline no errors are found and you can import the payment in your ING banking application.

Step 7

7

Additional features

It is possible to export the repaired payment and download it to your local drive.

You can also check the history of your past tests and look at the tested payments

Export and test history

8

Additional features

After opening the history you can see past test files and their results by clicking on the error

History

9

Other Considerations

• Only “”Messages to ING” can be tested.

• Do not use real information in the payment files but replace amounts, names, account numbers etc. by dummy data.

• It is not intended to be used for volume testing. The Readiness Portal is used to ensure messages created by our customers comply with

ING’s Usage Guidelines.

10

Important TAGS in a payment

• <PmtInfId>batch title</PmtInfId> - Batch reference, must be unique for every file in Mijn ING Zakelijk

• <NbOfTxs>50</NbOfTxs> - Number of transactions in the file and batch

• <ReqdExctnDt>2017-02-30</ReqdExctnDt> - Requested execution date must be between 5 days in the past and 360 days in the

future

• End to End ID, visible through the complete payment and reporting chain

<CdtTrfTxInf>

<PmtId>

<EndToEndId>E2E-ID-001</EndToEndId>

11

Important TAGS in a Direct Debit

• Additionally to a the important tags in a payment some TAGS are important for a Direct Debit

• Use the correct scheme corresponding with your contract: <Cd>CORE</Cd> for business to consumer collections, or

<Cd>B2B</Cd> for non-refundable business to business collections

• <ReqdColltnDt>2017-02-02</ReqdColltnDt> - Requested Collection date must be between 5 days in the past and 360 days in the

future• Creditor IBAN Account number

<CdtrAcct><Id>

<IBAN>NL03INGB0000000000</IBAN></Id>

</CdtrAcct>• Creditor BIC / SWIFT Address must be INGBNL2A

<CdtrAgt><FinInstnId>

<BIC>INGBNL2A</BIC></FinInstnId>

</CdtrAgt>

12

Important TAGS in a Direct Debit

• Debtor IBAN Account number<DbtrAcct>

<Id><IBAN>NL03INGB0000000000</IBAN>

</Id></DbtrAcct>

• Debtor BIC / SWIFT Address<DbtrAgt>

<FinInstnId><BIC>INGBNL2A</BIC>

</FinInstnId></DbtrAgt>

• <MndtId>5-001</MndtId> - Mandate ID (Machtigingskenmerk)• <DtOfSgntr>2016-11-01</DtOfSgntr> - date of signature of the mandate, must always be in the past• Creditor Id / Direct Debit Contract ID given to you by the bank

<CdtrSchmeId><Id>

<PrvtId><Othr>

<Id>NL12ZZZ000000000000</Id>