Definition of processes for payment.

Document types

These document types are defined as part of ISO 20022 payment exchange:

Name Document type

Pain.001

urn:iso:std:iso:20022:tech:xsd:pain.001.001.03

Pain.002

urn:iso:std:iso:20022:tech:xsd:pain.002.001.03

Pain.008

urn:iso:std:iso:20022:tech:xsd:pain.008.001.02

Pain.009

urn:iso:std:iso:20022:tech:xsd:pain.009.001.02

Pain.010

urn:iso:std:iso:20022:tech:xsd:pain.010.001.02

Pain.011

urn:iso:std:iso:20022:tech:xsd:pain.011.001.02

Pain.012

urn:iso:std:iso:20022:tech:xsd:pain.012.001.02

Camt.029

urn:iso:std:iso:20022:tech:xsd:camt.029.001.03

Camt.052

urn:iso:std:iso:20022:tech:xsd:camt.052.001.02

Camt.053

urn:iso:std:iso:20022:tech:xsd:camt.053.001.02

Camt.054

urn:iso:std:iso:20022:tech:xsd:camt.054.001.02

Camt.055

urn:iso:std:iso:20022:tech:xsd:camt.055.001.01

All document types uses the same customization: urn:fdc:bits.no:2017:iso20022:1.5

Processes

This is an overview of processes based upon "ISO 20022 messages in the Customer Bank interface - The profiles" by Bits.

Profile 01: General Credit transfer Initiion

Bank receives payment messages from customers, and returns status reports and notifications.

Identifier: urn:fdc:bits.no:2017:profile:01:1.0

Document type Sender

Pain.001 Credit transfer initiation

Customer

Pain.002 Payment status report (1..n)

Bank

Camt.054 B2C debit notification

Bank

Profile 02: Cancelation of General Credit transfer Initiation

Customer may request that previous payment initiations not yet processed, can be canceled.

Identifier: urn:fdc:bits.no:2017:profile:02:1.0

Document type Sender

Camt.055 CustomerPaymentCancellationRequest

Customer

Pain.002 Payment status report (1..n)

Bank

Camt.029 ResolutionOfInvestigation

Bank

Profile 03: Salary payments

Bank receives payment messages from customers, and returns status reports and notifications.

Identifier: urn:fdc:bits.no:2017:profile:03:1.0

Document type Sender

Pain.001 Credit transfer initiation

Customer

Pain.002 Payment status report (1..n)

Bank

Camt.054 B2C debit notification

Bank

Profile 04: Salary payments with request for cancelation

Bank receives payment messages from customers, and returns status reports and notifications. Customer may request that previous payment initiations not yet processed, can be canceled.

Identifier: urn:fdc:bits.no:2017:profile:04:1.0

Document type Sender

Camt.055 CustomerPaymentCancellationRequest

Customer

Pain.002 Payment status report (1..n)

Bank

Camt.029 ResolutionOfInvestigation

Bank

Profile 05: Billing

Customer prosesses invoices (paperbased or eInvoice, and forwards to customer. Bank returns notification file for automated reconciliation of account receivable.

Identifier: urn:fdc:bits.no:2017:profile:05:1.0

Document type Sender

Camt.054 B2C credit notification

Bank

Profile 06: Billing system with Direct Debit

Customer prosesses invoices (paperbased ,eInvoice, and forwards to customer, or a Direct Debit initiation, and forwards that to the bank. Bank returns notification file for automated reconciliation of account receivable.

Identifier: urn:fdc:bits.no:2017:profile:06:1.0

Document type Sender

Pain.008 CustomerDirectDebitInitiation

Customer

Pain.002 Payment status report

Bank

Camt.054 B2C credit notification

Bank

Profile 07: Canselation of DirectDebit Initiation

Customer may request that previous Direct Debit initiations not yet processed, can be canceled.

Identifier: urn:fdc:bits.no:2017:profile:07:1.0

Document type Sender

Camt.055 CustomerPaymentCancellationRequest

Customer

Pain.002 Payment status report (1..n)

Bank

Camt.029 ResolutionOfInvestigation

Bank

Profile 09: Accounting/General Ledger/cash management

Customer receive messages from the bank for updating account payable and account receivable and decision-/ liquidity -systems.

Identifier: urn:fdc:bits.no:2017:profile:09:1.0

Document type Sender

Camt.054 B2C debit/credit notification

Bank

Profile 10

Customer receive messages from the bank for updating general ledger and decision-/ liquidity -systems.

Identifier: urn:fdc:bits.no:2017:profile:10:1.0

Document type Sender

Camt.053 B2C account statement

Bank

Profile 11

Customer receive messages from the bank for updating decision-/ liquidity -systems.

Identifier: urn:fdc:bits.no:2017:profile:11:1.0

Document type Sender

Camt.052 B2C account report

Bank

Payment handling

Payment handling is a set of document types used in addition to business documents flowing in the network.

These messages uses the payment handling customization: urn:fdc:difi.no:2017:payment:handling:1.0

There are currently no rules attached to payment handling except those defining document types part of payment handling.

Recepion acknowledgement message

The document type ReceptionAcknowledgement from Payment Extras is used for reception acknowledge. This message copies the process identifier for which it responds to, and the document type identifier is created using identifiers from source document.

How to construct the document type identifier:
  • Namespace of Payment Extras (urn:fdc:difi.no:2017:payment:extras-1)

  • Separator (::)

  • Document type (ReceptionAcknowledgement)

  • Separator (##)

  • Identifier for payment handling (urn:fdc:difi.no:2017:payment:handling:1.0)

  • Separator (:for:)

  • Namespace of received document (urn:iso:std:iso:20022:tech:xsd:pain.001.001.03)

  • Separator (:restricted:)

  • Customization of received document (urn:fdc:bits.no:2017:iso20022:1.5)

  • Separator (::)

  • Version of ReceptionAcknowledgement (1.0)

Example of document type identifier: urn:fdc:difi.no:2017:payment:extras-1::ReceptionAcknowledgement##urn:fdc:difi.no:2017:payment:handling:1.0:for:urn:iso:std:iso:20022:tech:xsd:pain.001.001.03:restricted:urn:fdc:bits.no:2017:iso20022:1.5::1.0

Reception acknowledgement is registered to the sender of ISO 20022 document types.

Handling exception message

The document type HandlingException from Payment Extras is used to notify sender of problems during handling of received content. This message copies the process identifier for which it responds to, and the document type identifier is created using identifiers from source document.

How to construct the document type identifier:
  • Namespace of Payment Extras (urn:fdc:difi.no:2017:payment:extras-1)

  • Separator (::)

  • Document type (HandlingException)

  • Separator (##)

  • Identifier for payment handling (urn:fdc:difi.no:2017:payment:handling:1.0)

  • Separator (:for:)

  • Namespace of received document (urn:iso:std:iso:20022:tech:xsd:pain.001.001.03)

  • Separator (:restricted:)

  • Customization of received document (urn:fdc:bits.no:2017:iso20022:1.5)

  • Separator (::)

  • Version of ReceptionAcknowledgement (1.0)

Example of document type identifier: urn:fdc:difi.no:2017:payment:extras-1::HandlingException##urn:fdc:difi.no:2017:payment:handling:1.0:for:urn:iso:std:iso:20022:tech:xsd:pain.001.001.03:restricted:urn:fdc:bits.no:2017:iso20022:1.5::1.0

Handling exception is registered to the sender of ISO 20022 document types.