put/payment-requests/{paymentRequestResourceId}
Cancellation of a Payment/Transfer Request (PISP)
OAuth2 scope: pisp
Description
The PISP sent a Payment/Transfer Request through a POST command. The ASPSP registered the Payment/Transfer Request, updated if necessary the relevant identifiers in order to avoid duplicates and returned the location of the updated Request. The PISP got the Payment/Transfer Request that was updated with the resource identifiers, and eventually the status of the Payment/Transfer Request and the status of the subsequent credit transfer. The PISP requests for the payment cancellation (global cancellation) or for some payment instructions cancellation (partial cancellation) No other modification of the Payment/Transfer Request is allowed.
Prerequisites
- The TPP was registered by the Registration Authority for the PISP role
- The TPP was provided with an OAUTH2 "Client Credential" access token by the ASPSP (cf. paragraph 3.4.2).
- The TPP previously posted a Payment/Transfer Request which was saved by the ASPSP (cf. paragraph 4.5.3)
- The ASPSP answered with a location link to the saved Payment/Transfer Request (cf. paragraph 4.5.4)
- The PISP retrieved the saved Payment/Transfer Request (cf. paragraph 4.5.4)
- The TPP and the ASPSP successfully processed a mutual check and authentication
- The TPP presented its "OAUTH2 Client Credential" access token.
- The TPP presented the payment/transfer request.
- The PSU was successfully authenticated.
Business flow
Payment/Transfer request cancellation circumstances
The cancellation of a Payment/Transfer request might be triggered by the PISP upon request of the PSU. It can also be triggered by the PISP itself in case of error or fraud detection. Since the consequence of the cancellation will be a rejection of the Payment/Transfer request globally or limited to some of its instructions, the modification of the payment request will focus on setting the relevant status to the value "CANC". This "CANC" status must however be explained through a reason code that can be set with the following values:
| Reason | description |
|---|---|
| DS02 | The PSU himsef/herself ordered the cancellation. |
| DUPL | The PISP requested the cancellation for a duplication of a previous Payment/Transfer request |
| FRAD | The PISP requested the cancellation for fraudulent origin of the Payment/Transfer request |
| TECH | The PISP requested the cancellation for a technical issue on its side |
Payment/Transfer request cancellation level
- Case of a payment with multiple instructions or a standing order, the PISP asks to cancel the whole Payment/Transfer or Standing Order Request including all non-executed payment instructions by setting the [paymentInformationStatus] and the relevant [statusReasonInformation] at payment level.
- Case of a payment with multiple instructions, the PISP asks to cancel one or several payment instructions by setting the [transactionStatus] and the relevant [statusReasonInformation] at each relevant instruction level.
The cancellation request might need a PSU authentication before committing, especially when the request is PSU-driven. In other cases, the ASPSP may consider that a PSU authentication is irrelevant. In order to meet all possibilities, the cancellation request must nevertheless include:
-
The specification of the authentication approaches that are supported by the PISP (any combination of "REDIRECT" and "DECOUPLED" values).
-
In case of possible REDIRECT or DECOUPLED authentication approach, one or two call-back URLs to be used by the ASPSP at the finalisation of the authentication and consent process :
- The first call-back URL will be called by the ASPSP if the Transfer Request is processed without any error or rejection by the PSU
- The second call-back URL is to be used by the ASPSP in case of processing error or rejection by the PSU. Since this second URL is optional, the PISP might not provide it. In this case, the ASPSP will use the same URL for any processing result.
- Both call-back URLS must be used in a TLS-secured request.
-
In case of possible "DECOUPLED" approach, a PSU identifier that can be processed by the ASPSP for PSU recognition.
-
The ASPSP saves the updated Payment/Transfer Request and answers to the PISP. The answer embeds
- The specification of the chosen authentication approach taking into account both the PISP and the PSU capabilities.
- In case of chosen REDIRECT authentication approach, the URL to be used by the PISP for redirecting the PSU in order to perform an authentication.
Case of the PSU neither gives nor denies his/her consent, the Cancellation Request shall expire and is then rejected to the PISP. The expiration delay is specified by each ASPSP. If any modification of the payment request other than cancellation is applied by the PISP, the ASPSP must reject the request with HTTP403 without modifying the payment request resource.
There is no need for the PISP to post a confirmation of the cancellation request.
Parameters (19)
- Authorizationheaderstringrequired
Access token to be passed as a header
- paymentRequestResourceIdpathstringrequired
Identification of the Payment Request Resource
- paymentRequestbodyrequired
ISO20022 based payment Initiation Request
- PSU-IP-Addressheaderstring
IP address used by the PSU's terminal when connecting to the TPP
- PSU-IP-Portheaderstring
IP port used by the PSU's terminal when connecting to the TPP
- PSU-HTTP-Methodheaderstring
Http method for the most relevant PSU's terminal request to the TTP
- PSU-Dateheaderstring
Timestamp of the most relevant PSU's terminal request to the TTP
- PSU-GEO-Locationheaderstring
Geographical location of the PSU as provided by the PSU mobile terminal if any to the TPP
- PSU-User-Agentheaderstring
"User-Agent" header field sent by the PSU terminal when connecting to the TPP
- PSU-Refererheaderstring
"Referer" header field sent by the PSU terminal when connecting to the TPP. Notice that an initial typo in RFC 1945 specifies that "referer" (incorrect spelling) is to be used. The correct spelling "referrer" can be used but might not be understood.
- PSU-Acceptheaderstring
"Accept" header field sent by the PSU terminal when connecting to the TPP
- PSU-Accept-Charsetheaderstring
"Accept-Charset" header field sent by the PSU terminal when connecting to the TPP
- PSU-Accept-Encodingheaderstring
"Accept-Encoding" header field sent by the PSU terminal when connecting to the TPP
- PSU-Accept-Languageheaderstring
"Accept-Language" header field sent by the PSU terminal when connecting to the TPP
- PSU-Device-IDheaderstring
UUID (Universally Unique Identifier) for a device, which is used by the PSU, if available. UUID identifies either a device or a device dependant application installation. In case of installation identification this ID need to be unaltered until removal from device.
- Digestheaderstring
Digest of the body
- Signatureheaderstring
http-signature of the request The keyId must specify the way to get the relevant qualified certificate. It is requested that this identifier is an URL aiming to provide the relevant Qualified Certificate.
- X-Request-IDheaderstringrequired
Correlation header to be set in a request and retrieved in the relevant response
- X-JWS-Signatureheaderstring
Request body
PaymentRequestResource
ISO20022: The PaymentRequestResource message is sent by the Creditor sending party to the Debtor receiving party, directly or through agents. It is used by a Creditor to request movement of funds from the debtor account to a creditor. API: Information about the creditor (Id, account and agent) must be placed at instruction level. Thus multi-beneficiary payments can be handled. The requested execution date must be placed at payment level even when all instructions are requested to be executed at the same date. The latest case includes:
- multiple instructions having different requested execution dates
- standing orders settings
Fields (20)
- resourceIdResourceId
Schema: ResourceId
- paymentInformationIdPaymentInformationIdrequired
Schema: PaymentInformationId
- batchBookingBatchBookingIndicator
Schema: BatchBookingIndicator
- creationDateTimeCreationDateTimerequired
Schema: CreationDateTime
- numberOfTransactionsintegerrequired
ISO20022: Number of individual transactions contained in the message.
ISO20022: Number of individual transactions contained in the message. API: Each ASPSP will specify a maximum value for this field taking into accounts its specificities about payment request handling
- initiatingPartyPartyIdentificationrequired
Schema: PartyIdentification
- namestringrequired
ISO20022: Name by which a party is known and which is usually used to identify that party.
ISO20022: Name by which a party is known and which is usually used to identify that party. The [organisationId] property allows the specification of an unique and unambiguous way to identify an organisation. The [privateId] property allows the specification of an unique and unambiguous way to identify a person.
Constraints: maxLength: 140
- dateAndPlaceOfBirthDateAndPlaceOfBirth
Schema: DateAndPlaceOfBirth
- birthDatestring (date)required
Date on which a person is born.
- cityOfBirthstringrequired
City where a person was born.
Constraints: maxLength: 35
- countryOfBirthstringrequired
Country where a person was born.
Constraints: pattern: `^[A-Z]{2,2}$`
- postalAddressPostalAddress
Schema: PostalAddress
- addressTypestringenum · 6
ISO20022: Identifies the nature of the postal address.
ISO20022: Identifies the nature of the postal address. API: Cannot be used for SEPA payments. Proprietary codes can be specified and documented if needed.
Code Name Description BIZZ Business Address is the business address DLVY Delivery Address is the address to which delivery is to take place MLTO Mail To Address is the address to which mail is sent PBOX PO Box Address is is a postal office (PO) box ADDR Postal Address is the complete postal address HOME Home Address is the home address Code Name Description BIZZ— — DLVY— — MLTO— — PBOX— — ADDR— — HOME— — - departmentstring
ISO20022: Identification of a division of a large organisation or building.
ISO20022: Identification of a division of a large organisation or building. API: Cannot be used for SEPA payments.
Constraints: maxLength: 70
- subDepartmentstring
ISO20022: Identification of a sub-division of a large organisation or building.
ISO20022: Identification of a sub-division of a large organisation or building. API: Cannot be used for SEPA payments.
Constraints: maxLength: 70
- streetNamestring
ISO20022: Name of a street or thoroughfare.
ISO20022: Name of a street or thoroughfare. API: Cannot be used for SEPA payments.
Constraints: maxLength: 70
- buildingNumberstring
ISO20022: Number that identifies the position of a building on a street.
ISO20022: Number that identifies the position of a building on a street. API: Cannot be used for SEPA payments.
Constraints: maxLength: 16
- buildingNamestring
ISO20022: Name of the building or house.
ISO20022: Name of the building or house. API: Cannot be used for SEPA payments.
Constraints: maxLength: 16
- postCodestring
ISO20022: Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail.
ISO20022: Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail. API: Cannot be used for SEPA payments.
Constraints: maxLength: 16
- townNamestring
ISO20022: Name of a built-up area, with defined boundaries, and a local government.
ISO20022: Name of a built-up area, with defined boundaries, and a local government. API: Cannot be used for SEPA payments.
Constraints: maxLength: 35
- countrySubDivisionstring
ISO20022: Identifies a subdivision of a country such as state, region, county.
ISO20022: Identifies a subdivision of a country such as state, region, county. API: Cannot be used for SEPA payments.
Constraints: maxLength: 35
- countrystringrequired
ISO20022: Country in which a person resides (the place of a person's home). In the case of a company, it is the country from which the affairs of that company are directed.
ISO20022: Country in which a person resides (the place of a person's home). In the case of a company, it is the country from which the affairs of that company are directed.
Constraints: pattern: `^([A-Z]{2,2})$`
- addressLinearray<string>
Unstructured address. The lines must embed zip code and town name.
Unstructured address. The lines must embed zip code and town name. For SEPA payments, only two address lines are allowed.
- contactDetailsContactDetails
Schema: ContactDetails
- phoneNumberPhoneNumber
Schema: PhoneNumber
- faxNumberPhoneNumber
Schema: PhoneNumber
- emailAddressstring
email address of the contact
Constraints: maxLength: 2048 · pattern: `^.+@.+$`
- organisationIdGenericIdentification
Schema: GenericIdentification
- identificationstringrequired
API: Identifier
API: Identifier
Constraints: maxLength: 70
- schemeNamestringrequired
Name of the identification scheme.
Name of the identification scheme. Possible values for the scheme name, partially based on ISO20022 external code list, are the following:
Code Name Description BANK BankPartyIdentification Unique and unambiguous assignment made by a specific bank or similar financial institution to identify a relationship as defined between the bank and its client. BBAN BBANIdentifier Basic Bank Account Number (BBAN) - identifier used nationally by financial institutions, ie, in individual countries, generally as part of a National Account Numbering Scheme(s), to uniquely identify the account of a customer. COID CountryIdentificationCode) : Country authority given organisation identification (e.g., corporate registration number) SREN SIREN The SIREN number is a 9 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation in France. SRET SIRET The SIRET number is a 14 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation unit in France. It consists of the SIREN number, followed by a five digit classification number, to identify the local geographical unit of that entity. NIDN NationalIdentityNumber Number assigned by an authority to identify the national identity number of a person. Other values are also permitted, for instance: Code Name Description ---- ---- ----------- OAUT OAUTH2 OAUTH2 access token that is owned by the PISP being also an AISP and that can be used in order to identify the PSU CPAN CardPan Card PAN MPAN MaskedPan Card PAN where some digits were replaced for security reason TPAN TokenizedPan Token which was provided by a Token Service Provider (TSP) in order to obfuscate a real card PAN. The TSP must be identified in the issuer field TBAN TokenizedIBAN Token which was provided by a Token Service Provider (TSP) in order to obfuscate an IBAN. The TSP must be identified in the issuer field Each implementation of the STET PSD2 API must specify in its own documentation which schemes can actually been used Constraints: maxLength: 70
- issuerstring
ISO20022: Entity that assigns the identification. this could a country code or any organisation name or identifier that can be recognized by both parties
ISO20022: Entity that assigns the identification. this could a country code or any organisation name or identifier that can be recognized by both parties
Constraints: maxLength: 35
- privateIdGenericIdentification
Schema: GenericIdentification
- identificationstringrequired
API: Identifier
API: Identifier
Constraints: maxLength: 70
- schemeNamestringrequired
Name of the identification scheme.
Name of the identification scheme. Possible values for the scheme name, partially based on ISO20022 external code list, are the following:
Code Name Description BANK BankPartyIdentification Unique and unambiguous assignment made by a specific bank or similar financial institution to identify a relationship as defined between the bank and its client. BBAN BBANIdentifier Basic Bank Account Number (BBAN) - identifier used nationally by financial institutions, ie, in individual countries, generally as part of a National Account Numbering Scheme(s), to uniquely identify the account of a customer. COID CountryIdentificationCode) : Country authority given organisation identification (e.g., corporate registration number) SREN SIREN The SIREN number is a 9 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation in France. SRET SIRET The SIRET number is a 14 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation unit in France. It consists of the SIREN number, followed by a five digit classification number, to identify the local geographical unit of that entity. NIDN NationalIdentityNumber Number assigned by an authority to identify the national identity number of a person. Other values are also permitted, for instance: Code Name Description ---- ---- ----------- OAUT OAUTH2 OAUTH2 access token that is owned by the PISP being also an AISP and that can be used in order to identify the PSU CPAN CardPan Card PAN MPAN MaskedPan Card PAN where some digits were replaced for security reason TPAN TokenizedPan Token which was provided by a Token Service Provider (TSP) in order to obfuscate a real card PAN. The TSP must be identified in the issuer field TBAN TokenizedIBAN Token which was provided by a Token Service Provider (TSP) in order to obfuscate an IBAN. The TSP must be identified in the issuer field Each implementation of the STET PSD2 API must specify in its own documentation which schemes can actually been used Constraints: maxLength: 70
- issuerstring
ISO20022: Entity that assigns the identification. this could a country code or any organisation name or identifier that can be recognized by both parties
ISO20022: Entity that assigns the identification. this could a country code or any organisation name or identifier that can be recognized by both parties
Constraints: maxLength: 35
- leiLeiIdentification
Schema: LeiIdentification
- acceptDebtorAccountChangeboolean
indicator that the debtor account can be changed in the payment request by the ASPSP if needed
indicator that the debtor account can be changed in the payment request by the ASPSP if needed
- true: debtor account can be changed (default value)
- false: debtor account cannot be changed
- acceptChargeHandlingChangeboolean
indicator that the charge handling can be changed in the payment request by the ASPSP if needed
indicator that the charge handling can be changed in the payment request by the ASPSP if needed
- true: charge handling can be changed (default value)
- false: charge handling cannot be changed
- acceptInstantPaymentDowngradeboolean
Indicator that the requested instant SEPA Credit Transfer method can be downgraded by the ASPSP into a plain-vanilla SEPA Credit Transfer, when Instant SCT cannot apply or is refused by the PSU.
Indicator that the requested instant SEPA Credit Transfer method can be downgraded by the ASPSP into a plain-vanilla SEPA Credit Transfer, when Instant SCT cannot apply or is refused by the PSU. Eventually, it is up to the ASPSP to downgrade or reject the payment. In case of a downgrade, the ASPSP will have to update de relevant field [LocalInstrument] and remove the "INST" value in order to keep the PISP informed.
- true: payment method can be downgraded
- false: payment method cannot be downgraded (default value)
- paymentTypeInformationPaymentTypeInformationrequired
Schema: PaymentTypeInformation
- instructionPriorityPriorityCode
Schema: PriorityCode
- serviceLevelServiceLevelCode
Schema: ServiceLevelCode
- localInstrumentLocalInstrumentCode
Schema: LocalInstrumentCode
- categoryPurposeCategoryPurposeCode
Schema: CategoryPurposeCode
Code Name Description CASHCashManagementTransfer Transaction is a general cash management instruction. CORTTradeSettlementPayment Transaction is related to settlement of a trade, e.g. a foreign exchange deal or a securities transaction. DVPMDeliverAgainstPayment Code used to pre-advise the account servicer of a forthcoming deliver against payment instruction. INTCIntraCompanyPayment Transaction is an intra-company payment, i.e. a payment between two companies belonging to the same group. SALASalaryPayment Transaction is the payment of salaries. TREATreasuryPayment Transaction is related to treasury operations. E.g. financial contract settlement.
- debtorPartyIdentification
Schema: PartyIdentification
- namestringrequired
ISO20022: Name by which a party is known and which is usually used to identify that party.
ISO20022: Name by which a party is known and which is usually used to identify that party. The [organisationId] property allows the specification of an unique and unambiguous way to identify an organisation. The [privateId] property allows the specification of an unique and unambiguous way to identify a person.
Constraints: maxLength: 140
- dateAndPlaceOfBirthDateAndPlaceOfBirth
Schema: DateAndPlaceOfBirth
- birthDatestring (date)required
Date on which a person is born.
- cityOfBirthstringrequired
City where a person was born.
Constraints: maxLength: 35
- countryOfBirthstringrequired
Country where a person was born.
Constraints: pattern: `^[A-Z]{2,2}$`
- postalAddressPostalAddress
Schema: PostalAddress
- addressTypestringenum · 6
ISO20022: Identifies the nature of the postal address.
ISO20022: Identifies the nature of the postal address. API: Cannot be used for SEPA payments. Proprietary codes can be specified and documented if needed.
Code Name Description BIZZ Business Address is the business address DLVY Delivery Address is the address to which delivery is to take place MLTO Mail To Address is the address to which mail is sent PBOX PO Box Address is is a postal office (PO) box ADDR Postal Address is the complete postal address HOME Home Address is the home address Code Name Description BIZZ— — DLVY— — MLTO— — PBOX— — ADDR— — HOME— — - departmentstring
ISO20022: Identification of a division of a large organisation or building.
ISO20022: Identification of a division of a large organisation or building. API: Cannot be used for SEPA payments.
Constraints: maxLength: 70
- subDepartmentstring
ISO20022: Identification of a sub-division of a large organisation or building.
ISO20022: Identification of a sub-division of a large organisation or building. API: Cannot be used for SEPA payments.
Constraints: maxLength: 70
- streetNamestring
ISO20022: Name of a street or thoroughfare.
ISO20022: Name of a street or thoroughfare. API: Cannot be used for SEPA payments.
Constraints: maxLength: 70
- buildingNumberstring
ISO20022: Number that identifies the position of a building on a street.
ISO20022: Number that identifies the position of a building on a street. API: Cannot be used for SEPA payments.
Constraints: maxLength: 16
- buildingNamestring
ISO20022: Name of the building or house.
ISO20022: Name of the building or house. API: Cannot be used for SEPA payments.
Constraints: maxLength: 16
- postCodestring
ISO20022: Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail.
ISO20022: Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail. API: Cannot be used for SEPA payments.
Constraints: maxLength: 16
- townNamestring
ISO20022: Name of a built-up area, with defined boundaries, and a local government.
ISO20022: Name of a built-up area, with defined boundaries, and a local government. API: Cannot be used for SEPA payments.
Constraints: maxLength: 35
- countrySubDivisionstring
ISO20022: Identifies a subdivision of a country such as state, region, county.
ISO20022: Identifies a subdivision of a country such as state, region, county. API: Cannot be used for SEPA payments.
Constraints: maxLength: 35
- countrystringrequired
ISO20022: Country in which a person resides (the place of a person's home). In the case of a company, it is the country from which the affairs of that company are directed.
ISO20022: Country in which a person resides (the place of a person's home). In the case of a company, it is the country from which the affairs of that company are directed.
Constraints: pattern: `^([A-Z]{2,2})$`
- addressLinearray<string>
Unstructured address. The lines must embed zip code and town name.
Unstructured address. The lines must embed zip code and town name. For SEPA payments, only two address lines are allowed.
- contactDetailsContactDetails
Schema: ContactDetails
- phoneNumberPhoneNumber
Schema: PhoneNumber
- faxNumberPhoneNumber
Schema: PhoneNumber
- emailAddressstring
email address of the contact
Constraints: maxLength: 2048 · pattern: `^.+@.+$`
- organisationIdGenericIdentification
Schema: GenericIdentification
- identificationstringrequired
API: Identifier
API: Identifier
Constraints: maxLength: 70
- schemeNamestringrequired
Name of the identification scheme.
Name of the identification scheme. Possible values for the scheme name, partially based on ISO20022 external code list, are the following:
Code Name Description BANK BankPartyIdentification Unique and unambiguous assignment made by a specific bank or similar financial institution to identify a relationship as defined between the bank and its client. BBAN BBANIdentifier Basic Bank Account Number (BBAN) - identifier used nationally by financial institutions, ie, in individual countries, generally as part of a National Account Numbering Scheme(s), to uniquely identify the account of a customer. COID CountryIdentificationCode) : Country authority given organisation identification (e.g., corporate registration number) SREN SIREN The SIREN number is a 9 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation in France. SRET SIRET The SIRET number is a 14 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation unit in France. It consists of the SIREN number, followed by a five digit classification number, to identify the local geographical unit of that entity. NIDN NationalIdentityNumber Number assigned by an authority to identify the national identity number of a person. Other values are also permitted, for instance: Code Name Description ---- ---- ----------- OAUT OAUTH2 OAUTH2 access token that is owned by the PISP being also an AISP and that can be used in order to identify the PSU CPAN CardPan Card PAN MPAN MaskedPan Card PAN where some digits were replaced for security reason TPAN TokenizedPan Token which was provided by a Token Service Provider (TSP) in order to obfuscate a real card PAN. The TSP must be identified in the issuer field TBAN TokenizedIBAN Token which was provided by a Token Service Provider (TSP) in order to obfuscate an IBAN. The TSP must be identified in the issuer field Each implementation of the STET PSD2 API must specify in its own documentation which schemes can actually been used Constraints: maxLength: 70
- issuerstring
ISO20022: Entity that assigns the identification. this could a country code or any organisation name or identifier that can be recognized by both parties
ISO20022: Entity that assigns the identification. this could a country code or any organisation name or identifier that can be recognized by both parties
Constraints: maxLength: 35
- privateIdGenericIdentification
Schema: GenericIdentification
- identificationstringrequired
API: Identifier
API: Identifier
Constraints: maxLength: 70
- schemeNamestringrequired
Name of the identification scheme.
Name of the identification scheme. Possible values for the scheme name, partially based on ISO20022 external code list, are the following:
Code Name Description BANK BankPartyIdentification Unique and unambiguous assignment made by a specific bank or similar financial institution to identify a relationship as defined between the bank and its client. BBAN BBANIdentifier Basic Bank Account Number (BBAN) - identifier used nationally by financial institutions, ie, in individual countries, generally as part of a National Account Numbering Scheme(s), to uniquely identify the account of a customer. COID CountryIdentificationCode) : Country authority given organisation identification (e.g., corporate registration number) SREN SIREN The SIREN number is a 9 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation in France. SRET SIRET The SIRET number is a 14 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation unit in France. It consists of the SIREN number, followed by a five digit classification number, to identify the local geographical unit of that entity. NIDN NationalIdentityNumber Number assigned by an authority to identify the national identity number of a person. Other values are also permitted, for instance: Code Name Description ---- ---- ----------- OAUT OAUTH2 OAUTH2 access token that is owned by the PISP being also an AISP and that can be used in order to identify the PSU CPAN CardPan Card PAN MPAN MaskedPan Card PAN where some digits were replaced for security reason TPAN TokenizedPan Token which was provided by a Token Service Provider (TSP) in order to obfuscate a real card PAN. The TSP must be identified in the issuer field TBAN TokenizedIBAN Token which was provided by a Token Service Provider (TSP) in order to obfuscate an IBAN. The TSP must be identified in the issuer field Each implementation of the STET PSD2 API must specify in its own documentation which schemes can actually been used Constraints: maxLength: 70
- issuerstring
ISO20022: Entity that assigns the identification. this could a country code or any organisation name or identifier that can be recognized by both parties
ISO20022: Entity that assigns the identification. this could a country code or any organisation name or identifier that can be recognized by both parties
Constraints: maxLength: 35
- leiLeiIdentification
Schema: LeiIdentification
- debtorAccountAccountIdentification
Schema: AccountIdentification
- workspacestring
Workspace to which the account is linked.
Workspace to which the account is linked. This workspace might be specified by the AISP when forwarding the consent on accounts. If not provided, the default workspace is computed from the authentication that was used for getting the OAuth2 Access Token.
Constraints: maxLength: 32
- ibanstring
ISO20022: International Bank Account Number (IBAN) - identification used internationally by financial institutions to uniquely identify the account of a customer.
ISO20022: International Bank Account Number (IBAN) - identification used internationally by financial institutions to uniquely identify the account of a customer.
Further specifications of the format and content of the IBAN can be found in the standard ISO 13616 "Banking and related financial services - International Bank Account Number (IBAN)" version 1997-10-01, or later revisions.
Constraints: pattern: `^[A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}$`
- otherGenericIdentification
Schema: GenericIdentification
- identificationstringrequired
API: Identifier
API: Identifier
Constraints: maxLength: 70
- schemeNamestringrequired
Name of the identification scheme.
Name of the identification scheme. Possible values for the scheme name, partially based on ISO20022 external code list, are the following:
Code Name Description BANK BankPartyIdentification Unique and unambiguous assignment made by a specific bank or similar financial institution to identify a relationship as defined between the bank and its client. BBAN BBANIdentifier Basic Bank Account Number (BBAN) - identifier used nationally by financial institutions, ie, in individual countries, generally as part of a National Account Numbering Scheme(s), to uniquely identify the account of a customer. COID CountryIdentificationCode) : Country authority given organisation identification (e.g., corporate registration number) SREN SIREN The SIREN number is a 9 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation in France. SRET SIRET The SIRET number is a 14 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation unit in France. It consists of the SIREN number, followed by a five digit classification number, to identify the local geographical unit of that entity. NIDN NationalIdentityNumber Number assigned by an authority to identify the national identity number of a person. Other values are also permitted, for instance: Code Name Description ---- ---- ----------- OAUT OAUTH2 OAUTH2 access token that is owned by the PISP being also an AISP and that can be used in order to identify the PSU CPAN CardPan Card PAN MPAN MaskedPan Card PAN where some digits were replaced for security reason TPAN TokenizedPan Token which was provided by a Token Service Provider (TSP) in order to obfuscate a real card PAN. The TSP must be identified in the issuer field TBAN TokenizedIBAN Token which was provided by a Token Service Provider (TSP) in order to obfuscate an IBAN. The TSP must be identified in the issuer field Each implementation of the STET PSD2 API must specify in its own documentation which schemes can actually been used Constraints: maxLength: 70
- issuerstring
ISO20022: Entity that assigns the identification. this could a country code or any organisation name or identifier that can be recognized by both parties
ISO20022: Entity that assigns the identification. this could a country code or any organisation name or identifier that can be recognized by both parties
Constraints: maxLength: 35
- currencyCurrencyCode
Schema: CurrencyCode
- debtorAgentFinancialInstitutionIdentification
Schema: FinancialInstitutionIdentification
- bicFistringrequired
ISO20022: Code allocated to a financial institution by the ISO 9362 Registration Authority as described in ISO 9362 "Banking - Banking telecommunication messages - Business identification code (BIC)".
ISO20022: Code allocated to a financial institution by the ISO 9362 Registration Authority as described in ISO 9362 "Banking - Banking telecommunication messages - Business identification code (BIC)".
Constraints: pattern: `^[A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}$`
- clearingSystemMemberIdClearingSystemMemberIdentification
Schema: ClearingSystemMemberIdentification
- clearingSystemIdstringrequired
ISO20022: Specification of a pre-agreed offering between clearing agents or the channel through which the payment instruction is processed.
ISO20022: Specification of a pre-agreed offering between clearing agents or the channel through which the payment instruction is processed.
Constraints: maxLength: 35
- memberIdstringrequired
ISO20022: Identification of a member of a clearing system.
ISO20022: Identification of a member of a clearing system.
Constraints: maxLength: 35
- leiLeiIdentification
Schema: LeiIdentification
- namestring
Name of the financial institution
Constraints: maxLength: 140
- postalAddressPostalAddress
Schema: PostalAddress
- addressTypestringenum · 6
ISO20022: Identifies the nature of the postal address.
ISO20022: Identifies the nature of the postal address. API: Cannot be used for SEPA payments. Proprietary codes can be specified and documented if needed.
Code Name Description BIZZ Business Address is the business address DLVY Delivery Address is the address to which delivery is to take place MLTO Mail To Address is the address to which mail is sent PBOX PO Box Address is is a postal office (PO) box ADDR Postal Address is the complete postal address HOME Home Address is the home address Code Name Description BIZZ— — DLVY— — MLTO— — PBOX— — ADDR— — HOME— — - departmentstring
ISO20022: Identification of a division of a large organisation or building.
ISO20022: Identification of a division of a large organisation or building. API: Cannot be used for SEPA payments.
Constraints: maxLength: 70
- subDepartmentstring
ISO20022: Identification of a sub-division of a large organisation or building.
ISO20022: Identification of a sub-division of a large organisation or building. API: Cannot be used for SEPA payments.
Constraints: maxLength: 70
- streetNamestring
ISO20022: Name of a street or thoroughfare.
ISO20022: Name of a street or thoroughfare. API: Cannot be used for SEPA payments.
Constraints: maxLength: 70
- buildingNumberstring
ISO20022: Number that identifies the position of a building on a street.
ISO20022: Number that identifies the position of a building on a street. API: Cannot be used for SEPA payments.
Constraints: maxLength: 16
- buildingNamestring
ISO20022: Name of the building or house.
ISO20022: Name of the building or house. API: Cannot be used for SEPA payments.
Constraints: maxLength: 16
- postCodestring
ISO20022: Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail.
ISO20022: Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail. API: Cannot be used for SEPA payments.
Constraints: maxLength: 16
- townNamestring
ISO20022: Name of a built-up area, with defined boundaries, and a local government.
ISO20022: Name of a built-up area, with defined boundaries, and a local government. API: Cannot be used for SEPA payments.
Constraints: maxLength: 35
- countrySubDivisionstring
ISO20022: Identifies a subdivision of a country such as state, region, county.
ISO20022: Identifies a subdivision of a country such as state, region, county. API: Cannot be used for SEPA payments.
Constraints: maxLength: 35
- countrystringrequired
ISO20022: Country in which a person resides (the place of a person's home). In the case of a company, it is the country from which the affairs of that company are directed.
ISO20022: Country in which a person resides (the place of a person's home). In the case of a company, it is the country from which the affairs of that company are directed.
Constraints: pattern: `^([A-Z]{2,2})$`
- addressLinearray<string>
Unstructured address. The lines must embed zip code and town name.
Unstructured address. The lines must embed zip code and town name. For SEPA payments, only two address lines are allowed.
- chargeBearerChargeBearerCode
Schema: ChargeBearerCode
Code Name Description DEBTBorneByDebtor All transaction charges are to be borne by the debtor. CREDBorneByCreditor All transaction charges are to be borne by the creditor. SHARShared In a credit transfer context, means that transaction charges on the sender side are to be borne by the debtor, transaction charges on the receiver side are to be borne by the creditor. In a direct debit context, means that transaction charges on the sender side are to be borne by the creditor, transaction charges on the receiver side are to be borne by the debtor. SLEVFollowingServiceLevel Charges are to be applied following the rules agreed in the service level and/or scheme. - paymentInformationStatusPaymentInformationStatusCode
Schema: PaymentInformationStatusCode
Code Name Description ACCOAcceptedCustomerCOnfirmed The customer, during his/her authentication, has confirmed the payment request. ACCPAcceptedCustomerProfile Preceding check of technical validation was successful. Customer profile check was also successful. ACSCAcceptedSettlementCompleted Settlement on the debtor's account was completed. In the case of SCTInst, this status must not been set by the debtor's Bank before the reception of the positive confirmation. ACSPAcceptedSettlementInProcess All preceding checks such as technical validation and customer profile were successful. Dynamic risk assessment is now also successful and therefore the Payment Request was accepted for execution. ACTCAcceptedTechnicalValidation Authentication and syntactical and semantical validation are successful. ACWCAcceptedWithChange Instruction is accepted but a change will be made, such as date or remittance not sent. ACWPAcceptedWithoutPosting Payment instruction included in the credit transfer is accepted without being posted to the creditor customer's account. CANCCancelled Payment initiation was successfully cancelled after having received a request for cancellation. PARTPartiallyAccepted A number of transactions were accepted, whereas another number of transactions have not yet achieved 'accepted' status. PATCPartiallyAcceptedTechnicalCorrect Payment initiation needs multiple authentications, where some but not yet all were performed. Syntactical and semantical validations are successful. RCVDReceived Payment initiation was received by the receiving agent. PDNGPending Payment request or individual transaction included in the Payment Request is pending. Further checks and status update will be performed. RJCTRejected Payment request was rejected. - statusReasonInformationStatusReasonInformation
Schema: StatusReasonInformation
Code Name Description AC01IncorectAccountNumber the account number is either invalid or does not exist AC04ClosedAccountNumber the account is closed and cannot be used AC06BlockedAccount the account is blocked and cannot be used AG01TransactionForbidden Transaction forbidden on this type of account AG03TransactionNotSupported Transaction type not supported/authorized on this account AM02NotAllowedAccount SPecific transaction/message amount is greater than allowed maximum AM04InsufficientFunds Amount of funds available to cover specified message amount is insufficient AM18InvalidNumberOfTransactions the number of transactions exceeds the ASPSP acceptance limit CH03RequestedExecutionDateOrRequestedCollectionDateTooFarInFuture The requested execution date is too far in the future CH04RequestedExecutionDateOrRequestedCollectionDateTooFarInPast Value in Requested Execution Date or Requested Collection Date is too far in the past CNORCreditorBankIsNotRegistered Creditor bank is not registered under this BIC in the CSM CUSTRequestedByCustomer The reject is due to the debtor: refusal or lack of liquidity DS02OrderCancelled An authorized user has cancelled the order DUPLDuplicatePayment Payment is a duplicate of another payment. Can only be set by a PISP for a payment request cancellation. FF01InvalidFileFormat The reject is due to the original Payment Request which is invalid (syntax, structure or values) FRADFraudulentOriginated the Payment Request is considered as fraudulent MS03NotSpecifiedReasonAgentGenerated No reason specified by the ASPSP NOASNoAnswerFromCustomer The PSU has neither accepted nor rejected the Payment Request and a time-out has occurred RR01MissingDebtorAccountOrIdentification The Debtor account and/or Identification are missing or inconsistent RR03MissingCreditorNameOrAddress Specification of the creditor's name and/or address needed for regulatory requirements is insufficient or missing. RR04RegulatoryReason Reject from regulatory reason RR12InvalidPartyID Invalid or missing identification required within a particular country or payment type. TECHTechnicalProblem Technical problems resulting in an erroneous transaction. Can only be set by a PISP for a payment request cancellation. - fundsAvailabilityFundsAvailabilityInformation
Schema: FundsAvailabilityInformation
- bookingBookingInformation
Schema: BookingInformation
- creditTransferTransactionarray<CreditTransferTransactionResource>required
ISO20022: Payment processes required to transfer cash from the debtor to the creditor.
ISO20022: Payment processes required to transfer cash from the debtor to the creditor. API: Each ASPSP will specify a maxItems value for this field taking into accounts its specificities about payment request handling
Item: CreditTransferTransactionResource
- paymentIdPaymentIdentificationrequired
Schema: PaymentIdentification
- instructionIdstringrequired
ISO20022: Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction.
ISO20022: Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction.
API: Unique identification shared between the PISP and the ASPSP
Constraints: pattern: `^([a-zA-Z0-9 /\-?:\()\.,']{1,36})$`
- endToEndIdEndToEndId
Schema: EndToEndId
- uetrstring
ISO20022: Universally unique identifier to provide an end-to-end reference of a payment transaction.
ISO20022: Universally unique identifier to provide an end-to-end reference of a payment transaction.
Constraints: pattern: `^[a-f0-9]{8}-[a-f0-9]{4}-4[a-f0-9]{3}-[89ab][a-f0-9]{3}-[a-f0-9]{12}$`
- resourceIdResourceId
Schema: ResourceId
- requestedExecutionDateRequestedExecutionDate
Schema: RequestedExecutionDate
- cancellableTillstring (date-time)
This field may allow the PISP to get information on the limit timestamp for requesting cancelation of the transaction.
This field may allow the PISP to get information on the limit timestamp for requesting cancelation of the transaction. When this field is not provided by the ASPSP, the PISP must rely on the status of the transaction [transactionStatus] in order to estimate if the transaction is actually cancellable.
- acceptanceDateTimestring (date-time)
ISO20022: Date and time at which all processing conditions for execution of the payment are met and adequate financial cover is available at the account servicing agent.
ISO20022: Date and time at which all processing conditions for execution of the payment are met and adequate financial cover is available at the account servicing agent.
- debtorDecisionDatestring (date-time)
ISO20022: Date and time on when the debtor has accepted or rejected the request.
ISO20022: Date and time on when the debtor has accepted or rejected the request.
- appliedExecutionDatestring (date-time)
ISO20022: Date and time on when the payment was executed.
ISO20022: Date and time on when the payment was executed.
- standingOrderCharacteristicsStandingOrderCharacteristics
Schema: StandingOrderCharacteristics
- startDateStartDaterequired
Schema: StartDate
- endDateEndDate
Schema: EndDate
- executionRuleExecutionRulerequired
Schema: ExecutionRule
Code Name Description FWNGfollowing — PRECpreceding — - frequencyFrequencyCoderequired
Schema: FrequencyCode
Code Name Description DAILDaily — WEEKWeekly — TOWKEveryTwoWeeks — MNTHMonthly — TOMNEveryTwoMonths — QUTRQuarterly — SEMISemiAnnual — YEARAnnual —
- instructedAmountAmountType
Schema: AmountType
- amountnumber (float)required
ISO20022: Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party.
ISO20022: Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party.
Constraints: pattern: `^\-{0,1}[0-9]{1,13}(\.[0-9]{0,5}){0,1}$`
- currencyCurrencyCoderequired
Schema: CurrencyCode
- equivalentAmountEquivalentAmountType
Schema: EquivalentAmountType
- amountnumber (float)required
ISO20022: Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party.
ISO20022: Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party.
Constraints: pattern: `^\-{0,1}[0-9]{1,13}(\.[0-9]{0,5}){0,1}$`
- currencyCurrencyCoderequired
Schema: CurrencyCode
- currencyOfTransferCurrencyCoderequired
Schema: CurrencyCode
- exchangeRateInformationExchangeRate
Schema: ExchangeRate
- unitCurrencyCurrencyCode
Schema: CurrencyCode
- exchangeRatenumber (float)
The factor used for conversion of an amount from one currency to another. This reflects the price at which one currency was bought with another currency.
The factor used for conversion of an amount from one currency to another. This reflects the price at which one currency was bought with another currency.
- rateTypestringrequiredenum · 3
Specifies the type used to complete the currency exchange.
Specifies the type used to complete the currency exchange.
Code Name Description SPOT Spot Exchange rate applied is the spot rate. SALE Sale Exchange rate applied is the market rate at the time of the sale. AGRD Agreed Exchange rate applied is the rate agreed between the parties. Code Name Description SPOT— — SALE— — AGRD— — - contractIdentificationstring
Unique and unambiguous reference to the foreign exchange contract agreed between the initiating party/creditor and the debtor agent.
Constraints: maxLength: 35
- estimatedPayerAmountAmountType
Schema: AmountType
- amountnumber (float)required
ISO20022: Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party.
ISO20022: Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party.
Constraints: pattern: `^\-{0,1}[0-9]{1,13}(\.[0-9]{0,5}){0,1}$`
- currencyCurrencyCoderequired
Schema: CurrencyCode
- estimatedPayeeAmountAmountType
Schema: AmountType
- amountnumber (float)required
ISO20022: Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party.
ISO20022: Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party.
Constraints: pattern: `^\-{0,1}[0-9]{1,13}(\.[0-9]{0,5}){0,1}$`
- currencyCurrencyCoderequired
Schema: CurrencyCode
- ultimateDebtorPartyIdentification
Schema: PartyIdentification
- namestringrequired
ISO20022: Name by which a party is known and which is usually used to identify that party.
ISO20022: Name by which a party is known and which is usually used to identify that party. The [organisationId] property allows the specification of an unique and unambiguous way to identify an organisation. The [privateId] property allows the specification of an unique and unambiguous way to identify a person.
Constraints: maxLength: 140
- dateAndPlaceOfBirthDateAndPlaceOfBirth
Schema: DateAndPlaceOfBirth
- birthDatestring (date)required
Date on which a person is born.
- cityOfBirthstringrequired
City where a person was born.
Constraints: maxLength: 35
- countryOfBirthstringrequired
Country where a person was born.
Constraints: pattern: `^[A-Z]{2,2}$`
- postalAddressPostalAddress
Schema: PostalAddress
- addressTypestringenum · 6
ISO20022: Identifies the nature of the postal address.
ISO20022: Identifies the nature of the postal address. API: Cannot be used for SEPA payments. Proprietary codes can be specified and documented if needed.
Code Name Description BIZZ Business Address is the business address DLVY Delivery Address is the address to which delivery is to take place MLTO Mail To Address is the address to which mail is sent PBOX PO Box Address is is a postal office (PO) box ADDR Postal Address is the complete postal address HOME Home Address is the home address Code Name Description BIZZ— — DLVY— — MLTO— — PBOX— — ADDR— — HOME— — - departmentstring
ISO20022: Identification of a division of a large organisation or building.
ISO20022: Identification of a division of a large organisation or building. API: Cannot be used for SEPA payments.
Constraints: maxLength: 70
- subDepartmentstring
ISO20022: Identification of a sub-division of a large organisation or building.
ISO20022: Identification of a sub-division of a large organisation or building. API: Cannot be used for SEPA payments.
Constraints: maxLength: 70
- streetNamestring
ISO20022: Name of a street or thoroughfare.
ISO20022: Name of a street or thoroughfare. API: Cannot be used for SEPA payments.
Constraints: maxLength: 70
- buildingNumberstring
ISO20022: Number that identifies the position of a building on a street.
ISO20022: Number that identifies the position of a building on a street. API: Cannot be used for SEPA payments.
Constraints: maxLength: 16
- buildingNamestring
ISO20022: Name of the building or house.
ISO20022: Name of the building or house. API: Cannot be used for SEPA payments.
Constraints: maxLength: 16
- postCodestring
ISO20022: Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail.
ISO20022: Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail. API: Cannot be used for SEPA payments.
Constraints: maxLength: 16
- townNamestring
ISO20022: Name of a built-up area, with defined boundaries, and a local government.
ISO20022: Name of a built-up area, with defined boundaries, and a local government. API: Cannot be used for SEPA payments.
Constraints: maxLength: 35
- countrySubDivisionstring
ISO20022: Identifies a subdivision of a country such as state, region, county.
ISO20022: Identifies a subdivision of a country such as state, region, county. API: Cannot be used for SEPA payments.
Constraints: maxLength: 35
- countrystringrequired
ISO20022: Country in which a person resides (the place of a person's home). In the case of a company, it is the country from which the affairs of that company are directed.
ISO20022: Country in which a person resides (the place of a person's home). In the case of a company, it is the country from which the affairs of that company are directed.
Constraints: pattern: `^([A-Z]{2,2})$`
- addressLinearray<string>
Unstructured address. The lines must embed zip code and town name.
Unstructured address. The lines must embed zip code and town name. For SEPA payments, only two address lines are allowed.
- contactDetailsContactDetails
Schema: ContactDetails
- phoneNumberPhoneNumber
Schema: PhoneNumber
- faxNumberPhoneNumber
Schema: PhoneNumber
- emailAddressstring
email address of the contact
Constraints: maxLength: 2048 · pattern: `^.+@.+$`
- organisationIdGenericIdentification
Schema: GenericIdentification
- identificationstringrequired
API: Identifier
API: Identifier
Constraints: maxLength: 70
- schemeNamestringrequired
Name of the identification scheme.
Name of the identification scheme. Possible values for the scheme name, partially based on ISO20022 external code list, are the following:
Code Name Description BANK BankPartyIdentification Unique and unambiguous assignment made by a specific bank or similar financial institution to identify a relationship as defined between the bank and its client. BBAN BBANIdentifier Basic Bank Account Number (BBAN) - identifier used nationally by financial institutions, ie, in individual countries, generally as part of a National Account Numbering Scheme(s), to uniquely identify the account of a customer. COID CountryIdentificationCode) : Country authority given organisation identification (e.g., corporate registration number) SREN SIREN The SIREN number is a 9 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation in France. SRET SIRET The SIRET number is a 14 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation unit in France. It consists of the SIREN number, followed by a five digit classification number, to identify the local geographical unit of that entity. NIDN NationalIdentityNumber Number assigned by an authority to identify the national identity number of a person. Other values are also permitted, for instance: Code Name Description ---- ---- ----------- OAUT OAUTH2 OAUTH2 access token that is owned by the PISP being also an AISP and that can be used in order to identify the PSU CPAN CardPan Card PAN MPAN MaskedPan Card PAN where some digits were replaced for security reason TPAN TokenizedPan Token which was provided by a Token Service Provider (TSP) in order to obfuscate a real card PAN. The TSP must be identified in the issuer field TBAN TokenizedIBAN Token which was provided by a Token Service Provider (TSP) in order to obfuscate an IBAN. The TSP must be identified in the issuer field Each implementation of the STET PSD2 API must specify in its own documentation which schemes can actually been used Constraints: maxLength: 70
- issuerstring
ISO20022: Entity that assigns the identification. this could a country code or any organisation name or identifier that can be recognized by both parties
ISO20022: Entity that assigns the identification. this could a country code or any organisation name or identifier that can be recognized by both parties
Constraints: maxLength: 35
- privateIdGenericIdentification
Schema: GenericIdentification
- identificationstringrequired
API: Identifier
API: Identifier
Constraints: maxLength: 70
- schemeNamestringrequired
Name of the identification scheme.
Name of the identification scheme. Possible values for the scheme name, partially based on ISO20022 external code list, are the following:
Code Name Description BANK BankPartyIdentification Unique and unambiguous assignment made by a specific bank or similar financial institution to identify a relationship as defined between the bank and its client. BBAN BBANIdentifier Basic Bank Account Number (BBAN) - identifier used nationally by financial institutions, ie, in individual countries, generally as part of a National Account Numbering Scheme(s), to uniquely identify the account of a customer. COID CountryIdentificationCode) : Country authority given organisation identification (e.g., corporate registration number) SREN SIREN The SIREN number is a 9 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation in France. SRET SIRET The SIRET number is a 14 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation unit in France. It consists of the SIREN number, followed by a five digit classification number, to identify the local geographical unit of that entity. NIDN NationalIdentityNumber Number assigned by an authority to identify the national identity number of a person. Other values are also permitted, for instance: Code Name Description ---- ---- ----------- OAUT OAUTH2 OAUTH2 access token that is owned by the PISP being also an AISP and that can be used in order to identify the PSU CPAN CardPan Card PAN MPAN MaskedPan Card PAN where some digits were replaced for security reason TPAN TokenizedPan Token which was provided by a Token Service Provider (TSP) in order to obfuscate a real card PAN. The TSP must be identified in the issuer field TBAN TokenizedIBAN Token which was provided by a Token Service Provider (TSP) in order to obfuscate an IBAN. The TSP must be identified in the issuer field Each implementation of the STET PSD2 API must specify in its own documentation which schemes can actually been used Constraints: maxLength: 70
- issuerstring
ISO20022: Entity that assigns the identification. this could a country code or any organisation name or identifier that can be recognized by both parties
ISO20022: Entity that assigns the identification. this could a country code or any organisation name or identifier that can be recognized by both parties
Constraints: maxLength: 35
- leiLeiIdentification
Schema: LeiIdentification
- intermediaryAgentIntermediaryAgent
Schema: IntermediaryAgent
- agentPartyIdentification
Schema: PartyIdentification
- namestringrequired
ISO20022: Name by which a party is known and which is usually used to identify that party.
ISO20022: Name by which a party is known and which is usually used to identify that party. The [organisationId] property allows the specification of an unique and unambiguous way to identify an organisation. The [privateId] property allows the specification of an unique and unambiguous way to identify a person.
Constraints: maxLength: 140
- dateAndPlaceOfBirthDateAndPlaceOfBirth
Schema: DateAndPlaceOfBirth
- postalAddressPostalAddress
Schema: PostalAddress
- contactDetailsContactDetails
Schema: ContactDetails
- organisationIdGenericIdentification
Schema: GenericIdentification
- privateIdGenericIdentification
Schema: GenericIdentification
- leiLeiIdentification
Schema: LeiIdentification
- agentAccountAccountIdentification
Schema: AccountIdentification
- workspacestring
Workspace to which the account is linked.
Workspace to which the account is linked. This workspace might be specified by the AISP when forwarding the consent on accounts. If not provided, the default workspace is computed from the authentication that was used for getting the OAuth2 Access Token.
Constraints: maxLength: 32
- ibanstring
ISO20022: International Bank Account Number (IBAN) - identification used internationally by financial institutions to uniquely identify the account of a customer.
ISO20022: International Bank Account Number (IBAN) - identification used internationally by financial institutions to uniquely identify the account of a customer.
Further specifications of the format and content of the IBAN can be found in the standard ISO 13616 "Banking and related financial services - International Bank Account Number (IBAN)" version 1997-10-01, or later revisions.
Constraints: pattern: `^[A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}$`
- otherGenericIdentification
Schema: GenericIdentification
- currencyCurrencyCode
Schema: CurrencyCode
- beneficiaryBeneficiaryrequired
Schema: Beneficiary
- workspaceWorkspace
Schema: Workspace
- identificationstringrequired
identification of the workspace to be used as an optional query parameter for some AISP queries
Constraints: maxLength: 32
- labelstringrequired
textual description of the workspace as specified by the ASPSP in relationship wth the PSU
Constraints: maxLength: 128
- idstring
Id of the beneficiary
Constraints: pattern: `^([a-zA-Z0-9 /\-?:\()\.,']{1,36})$`
- isTrustedboolean
The ASPSP having not implemented the trusted beneficiaries list must not set this flag.
The ASPSP having not implemented the trusted beneficiaries list must not set this flag. Otherwise, the ASPSP indicates whether or not the beneficiary was registered by the PSU within the trusted beneficiaries list.
- true: the beneficiary is actually a trusted beneficiary
- false: the beneficiary is not a trusted beneficiary
- creditorAgentFinancialInstitutionIdentification
Schema: FinancialInstitutionIdentification
- bicFistringrequired
ISO20022: Code allocated to a financial institution by the ISO 9362 Registration Authority as described in ISO 9362 "Banking - Banking telecommunication messages - Business identification code (BIC)".
ISO20022: Code allocated to a financial institution by the ISO 9362 Registration Authority as described in ISO 9362 "Banking - Banking telecommunication messages - Business identification code (BIC)".
Constraints: pattern: `^[A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}$`
- clearingSystemMemberIdClearingSystemMemberIdentification
- leiLeiIdentification
Schema: LeiIdentification
- namestring
Name of the financial institution
Constraints: maxLength: 140
- postalAddressPostalAddress
Schema: PostalAddress
- creditorPartyIdentificationrequired
Schema: PartyIdentification
- namestringrequired
ISO20022: Name by which a party is known and which is usually used to identify that party.
ISO20022: Name by which a party is known and which is usually used to identify that party. The [organisationId] property allows the specification of an unique and unambiguous way to identify an organisation. The [privateId] property allows the specification of an unique and unambiguous way to identify a person.
Constraints: maxLength: 140
- dateAndPlaceOfBirthDateAndPlaceOfBirth
Schema: DateAndPlaceOfBirth
- postalAddressPostalAddress
Schema: PostalAddress
- contactDetailsContactDetails
Schema: ContactDetails
- organisationIdGenericIdentification
Schema: GenericIdentification
- privateIdGenericIdentification
Schema: GenericIdentification
- leiLeiIdentification
Schema: LeiIdentification
- creditorAccountAccountIdentification
Schema: AccountIdentification
- workspacestring
Workspace to which the account is linked.
Workspace to which the account is linked. This workspace might be specified by the AISP when forwarding the consent on accounts. If not provided, the default workspace is computed from the authentication that was used for getting the OAuth2 Access Token.
Constraints: maxLength: 32
- ibanstring
ISO20022: International Bank Account Number (IBAN) - identification used internationally by financial institutions to uniquely identify the account of a customer.
ISO20022: International Bank Account Number (IBAN) - identification used internationally by financial institutions to uniquely identify the account of a customer.
Further specifications of the format and content of the IBAN can be found in the standard ISO 13616 "Banking and related financial services - International Bank Account Number (IBAN)" version 1997-10-01, or later revisions.
Constraints: pattern: `^[A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}$`
- otherGenericIdentification
Schema: GenericIdentification
- currencyCurrencyCode
Schema: CurrencyCode
- ultimateCreditorPartyIdentification
Schema: PartyIdentification
- namestringrequired
ISO20022: Name by which a party is known and which is usually used to identify that party.
ISO20022: Name by which a party is known and which is usually used to identify that party. The [organisationId] property allows the specification of an unique and unambiguous way to identify an organisation. The [privateId] property allows the specification of an unique and unambiguous way to identify a person.
Constraints: maxLength: 140
- dateAndPlaceOfBirthDateAndPlaceOfBirth
Schema: DateAndPlaceOfBirth
- birthDatestring (date)required
Date on which a person is born.
- cityOfBirthstringrequired
City where a person was born.
Constraints: maxLength: 35
- countryOfBirthstringrequired
Country where a person was born.
Constraints: pattern: `^[A-Z]{2,2}$`
- postalAddressPostalAddress
Schema: PostalAddress
- addressTypestringenum · 6
ISO20022: Identifies the nature of the postal address.
ISO20022: Identifies the nature of the postal address. API: Cannot be used for SEPA payments. Proprietary codes can be specified and documented if needed.
Code Name Description BIZZ Business Address is the business address DLVY Delivery Address is the address to which delivery is to take place MLTO Mail To Address is the address to which mail is sent PBOX PO Box Address is is a postal office (PO) box ADDR Postal Address is the complete postal address HOME Home Address is the home address Code Name Description BIZZ— — DLVY— — MLTO— — PBOX— — ADDR— — HOME— — - departmentstring
ISO20022: Identification of a division of a large organisation or building.
ISO20022: Identification of a division of a large organisation or building. API: Cannot be used for SEPA payments.
Constraints: maxLength: 70
- subDepartmentstring
ISO20022: Identification of a sub-division of a large organisation or building.
ISO20022: Identification of a sub-division of a large organisation or building. API: Cannot be used for SEPA payments.
Constraints: maxLength: 70
- streetNamestring
ISO20022: Name of a street or thoroughfare.
ISO20022: Name of a street or thoroughfare. API: Cannot be used for SEPA payments.
Constraints: maxLength: 70
- buildingNumberstring
ISO20022: Number that identifies the position of a building on a street.
ISO20022: Number that identifies the position of a building on a street. API: Cannot be used for SEPA payments.
Constraints: maxLength: 16
- buildingNamestring
ISO20022: Name of the building or house.
ISO20022: Name of the building or house. API: Cannot be used for SEPA payments.
Constraints: maxLength: 16
- postCodestring
ISO20022: Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail.
ISO20022: Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail. API: Cannot be used for SEPA payments.
Constraints: maxLength: 16
- townNamestring
ISO20022: Name of a built-up area, with defined boundaries, and a local government.
ISO20022: Name of a built-up area, with defined boundaries, and a local government. API: Cannot be used for SEPA payments.
Constraints: maxLength: 35
- countrySubDivisionstring
ISO20022: Identifies a subdivision of a country such as state, region, county.
ISO20022: Identifies a subdivision of a country such as state, region, county. API: Cannot be used for SEPA payments.
Constraints: maxLength: 35
- countrystringrequired
ISO20022: Country in which a person resides (the place of a person's home). In the case of a company, it is the country from which the affairs of that company are directed.
ISO20022: Country in which a person resides (the place of a person's home). In the case of a company, it is the country from which the affairs of that company are directed.
Constraints: pattern: `^([A-Z]{2,2})$`
- addressLinearray<string>
Unstructured address. The lines must embed zip code and town name.
Unstructured address. The lines must embed zip code and town name. For SEPA payments, only two address lines are allowed.
- contactDetailsContactDetails
Schema: ContactDetails
- phoneNumberPhoneNumber
Schema: PhoneNumber
- faxNumberPhoneNumber
Schema: PhoneNumber
- emailAddressstring
email address of the contact
Constraints: maxLength: 2048 · pattern: `^.+@.+$`
- organisationIdGenericIdentification
Schema: GenericIdentification
- identificationstringrequired
API: Identifier
API: Identifier
Constraints: maxLength: 70
- schemeNamestringrequired
Name of the identification scheme.
Name of the identification scheme. Possible values for the scheme name, partially based on ISO20022 external code list, are the following:
Code Name Description BANK BankPartyIdentification Unique and unambiguous assignment made by a specific bank or similar financial institution to identify a relationship as defined between the bank and its client. BBAN BBANIdentifier Basic Bank Account Number (BBAN) - identifier used nationally by financial institutions, ie, in individual countries, generally as part of a National Account Numbering Scheme(s), to uniquely identify the account of a customer. COID CountryIdentificationCode) : Country authority given organisation identification (e.g., corporate registration number) SREN SIREN The SIREN number is a 9 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation in France. SRET SIRET The SIRET number is a 14 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation unit in France. It consists of the SIREN number, followed by a five digit classification number, to identify the local geographical unit of that entity. NIDN NationalIdentityNumber Number assigned by an authority to identify the national identity number of a person. Other values are also permitted, for instance: Code Name Description ---- ---- ----------- OAUT OAUTH2 OAUTH2 access token that is owned by the PISP being also an AISP and that can be used in order to identify the PSU CPAN CardPan Card PAN MPAN MaskedPan Card PAN where some digits were replaced for security reason TPAN TokenizedPan Token which was provided by a Token Service Provider (TSP) in order to obfuscate a real card PAN. The TSP must be identified in the issuer field TBAN TokenizedIBAN Token which was provided by a Token Service Provider (TSP) in order to obfuscate an IBAN. The TSP must be identified in the issuer field Each implementation of the STET PSD2 API must specify in its own documentation which schemes can actually been used Constraints: maxLength: 70
- issuerstring
ISO20022: Entity that assigns the identification. this could a country code or any organisation name or identifier that can be recognized by both parties
ISO20022: Entity that assigns the identification. this could a country code or any organisation name or identifier that can be recognized by both parties
Constraints: maxLength: 35
- privateIdGenericIdentification
Schema: GenericIdentification
- identificationstringrequired
API: Identifier
API: Identifier
Constraints: maxLength: 70
- schemeNamestringrequired
Name of the identification scheme.
Name of the identification scheme. Possible values for the scheme name, partially based on ISO20022 external code list, are the following:
Code Name Description BANK BankPartyIdentification Unique and unambiguous assignment made by a specific bank or similar financial institution to identify a relationship as defined between the bank and its client. BBAN BBANIdentifier Basic Bank Account Number (BBAN) - identifier used nationally by financial institutions, ie, in individual countries, generally as part of a National Account Numbering Scheme(s), to uniquely identify the account of a customer. COID CountryIdentificationCode) : Country authority given organisation identification (e.g., corporate registration number) SREN SIREN The SIREN number is a 9 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation in France. SRET SIRET The SIRET number is a 14 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation unit in France. It consists of the SIREN number, followed by a five digit classification number, to identify the local geographical unit of that entity. NIDN NationalIdentityNumber Number assigned by an authority to identify the national identity number of a person. Other values are also permitted, for instance: Code Name Description ---- ---- ----------- OAUT OAUTH2 OAUTH2 access token that is owned by the PISP being also an AISP and that can be used in order to identify the PSU CPAN CardPan Card PAN MPAN MaskedPan Card PAN where some digits were replaced for security reason TPAN TokenizedPan Token which was provided by a Token Service Provider (TSP) in order to obfuscate a real card PAN. The TSP must be identified in the issuer field TBAN TokenizedIBAN Token which was provided by a Token Service Provider (TSP) in order to obfuscate an IBAN. The TSP must be identified in the issuer field Each implementation of the STET PSD2 API must specify in its own documentation which schemes can actually been used Constraints: maxLength: 70
- issuerstring
ISO20022: Entity that assigns the identification. this could a country code or any organisation name or identifier that can be recognized by both parties
ISO20022: Entity that assigns the identification. this could a country code or any organisation name or identifier that can be recognized by both parties
Constraints: maxLength: 35
- leiLeiIdentification
Schema: LeiIdentification
- instructionForCreditorAgentarray<InstructionForCreditorAgent>
Further information related to the processing of the payment instruction, provided by the initiating party, and intended for the creditor agent.
Item: InstructionForCreditorAgent
- codestringenum · 4
Coded information related to the processing of the payment instruction, provided by the initiating party, and intended for the creditor's agent.
Coded information related to the processing of the payment instruction, provided by the initiating party, and intended for the creditor's agent.
Code Name Description CHQB PayCreditorByCheque (Ultimate) creditor must be paid by cheque. HOLD HoldCashForCreditor Amount of money must be held for the (ultimate) creditor, who will call. Pay on identification. PHOB PhoneBeneficiary Please advise/contact (ultimate) creditor/claimant by phone. TELB Telecom Please advise/contact (ultimate) creditor/claimant by the most efficient means of telecommunication. Code Name Description CHQB— — HOLD— — PHOB— — TELB— — - instructionInformationstring
Further information complementing the coded instruction or instruction to the creditor's agent that is bilaterally agreed or specific to a user community.
Constraints: maxLength: 140
- purposePurposeCode
Schema: PurposeCode
Code Name Description ACCTAccountManagement Funds moved between 2 accounts of same account holder at the same bank) CASHCashManagementTransfer (general cash management instruction) may be used for Transfer Initiation COMCCommercialPayment Transaction is related to a payment of commercial credit or debit. CPKCCarparkCharges General Carpark Charges Transaction is related to carpark charges. SALASalaryPayment Transaction is the payment of salaries. TRPTRoadPricing Transport RoadPricing Transaction is for the payment to top-up pre-paid card and electronic road pricing for the purpose of transportation. - regulatoryReportingCodesRegulatoryReportingCodes
Schema: RegulatoryReportingCodes
- remittanceInformationRemittanceInformation
Schema: RemittanceInformation
- unstructuredarray<string>
Unstructured remittance information.
Unstructured remittance information. Each implementation may add a pattern in order to specify its own character set constraints.
- structuredarray<StructuredRemittanceInformation>
Structured remittance information
Item: StructuredRemittanceInformation
- referredDocumentInformationReferredDocumentInformations
Schema: ReferredDocumentInformations
- referredDocumentAmountRemittanceAmount
Schema: RemittanceAmount
- creditorReferenceInformationCreditorReferenceInformation
Schema: CreditorReferenceInformation
- invoicerPartyIdentification
Schema: PartyIdentification
- invoiceePartyIdentification
Schema: PartyIdentification
- taxRemittanceTaxInformation
Schema: TaxInformation
- transactionStatusTransactionIndividualStatusCode
Schema: TransactionIndividualStatusCode
Code Name Description ACSCAcceptedSettlementCompleted Settlement on the debtor's account was completed. In the case of SCTInst, this status must not been set by the debtor's Bank before the reception of the positive confirmation. The transaction cannot be cancelled. ACSPAcceptedSettlementInProcess All preceding checks such as technical validation and customer profile were successful and therefore the Payment Request was accepted for execution. The transaction cannot be cancelled. ACTCAcceptedTechnicalValidation Authentication and syntactical and semantical validation are successful. The transaction might be cancelled. CANCCancelled Payment initiation was successfully cancelled after having received a request for cancellation. PDNGPending Payment request or individual transaction included in the Payment Request is pending. Further checks and status update will be performed. The transaction might be cancelled. RJCTRejected Payment request or individual transaction included in the Payment Request was rejected. - statusReasonInformationStatusReasonInformation
Schema: StatusReasonInformation
Code Name Description AC01IncorectAccountNumber the account number is either invalid or does not exist AC04ClosedAccountNumber the account is closed and cannot be used AC06BlockedAccount the account is blocked and cannot be used AG01TransactionForbidden Transaction forbidden on this type of account AG03TransactionNotSupported Transaction type not supported/authorized on this account AM02NotAllowedAccount SPecific transaction/message amount is greater than allowed maximum AM04InsufficientFunds Amount of funds available to cover specified message amount is insufficient AM18InvalidNumberOfTransactions the number of transactions exceeds the ASPSP acceptance limit CH03RequestedExecutionDateOrRequestedCollectionDateTooFarInFuture The requested execution date is too far in the future CH04RequestedExecutionDateOrRequestedCollectionDateTooFarInPast Value in Requested Execution Date or Requested Collection Date is too far in the past CNORCreditorBankIsNotRegistered Creditor bank is not registered under this BIC in the CSM CUSTRequestedByCustomer The reject is due to the debtor: refusal or lack of liquidity DS02OrderCancelled An authorized user has cancelled the order DUPLDuplicatePayment Payment is a duplicate of another payment. Can only be set by a PISP for a payment request cancellation. FF01InvalidFileFormat The reject is due to the original Payment Request which is invalid (syntax, structure or values) FRADFraudulentOriginated the Payment Request is considered as fraudulent MS03NotSpecifiedReasonAgentGenerated No reason specified by the ASPSP NOASNoAnswerFromCustomer The PSU has neither accepted nor rejected the Payment Request and a time-out has occurred RR01MissingDebtorAccountOrIdentification The Debtor account and/or Identification are missing or inconsistent RR03MissingCreditorNameOrAddress Specification of the creditor's name and/or address needed for regulatory requirements is insufficient or missing. RR04RegulatoryReason Reject from regulatory reason RR12InvalidPartyID Invalid or missing identification required within a particular country or payment type. TECHTechnicalProblem Technical problems resulting in an erroneous transaction. Can only be set by a PISP for a payment request cancellation. - supplementaryDataSupplementaryData
Schema: SupplementaryData
- acceptedAuthenticationApproachAuthenticationApproaches
Schema: AuthenticationApproaches
- appliedAuthenticationApproachAuthenticationApproach
Schema: AuthenticationApproach
- appliedAuthenticationstringenum · 3
Can only be set by the ASPSP.
Can only be set by the ASPSP. This field allows the ASPSP to inform the PISP about the way authentication was processed during the payment request confirmation.
Code Name Description noAuthentication— — oneFactorAuthentication— — strongAuthentication— — - scaHintstringenum · 2
can only be set by the PISP
can only be set by the PISP Hint given by the merchant and/or the PISP about an SCA exemption context
Code Name Description noScaExemption— — scaExemption— — - successfulReportUrlstring
URL to be used by the ASPSP in order to notify the PISP of the finalisation of the authentication and consent process in REDIRECT and DECOUPLED approach
URL to be used by the ASPSP in order to notify the PISP of the finalisation of the authentication and consent process in REDIRECT and DECOUPLED approach
- unsuccessfulReportUrlstring
URL to be used by the ASPSP in order to notify the PISP of the failure of the authentication and consent process in REDIRECT and DECOUPLED approach
URL to be used by the ASPSP in order to notify the PISP of the failure of the authentication and consent process in REDIRECT and DECOUPLED approach If this URL is not provided by the PISP, the ASPSP will use the "successfulReportUrl" even in case of failure of the Payment Request processing
- nextStatusRequestHintstring (date-time)
Date and time at which the PISP is suggested to ask again for the status of the payment request.
Date and time at which the PISP is suggested to ask again for the status of the payment request.
- loginHintTokenstring
The LOGIN_HINT_TOKEN is a piece of data that may be provided to the API client by the API server, once a PSU has been identified and authenticated.
The LOGIN_HINT_TOKEN is a piece of data that may be provided to the API client by the API server, once a PSU has been identified and authenticated.
- through a response to a token introspection request (RFC7662)
- through a status response to a Payment Request This LOGIN_HINT_TOKEN can then be sent back by the API client to the API server through the posting of a new Payment request. This will help the API server to identify the relevant PSU and ease the authentication process.
- investigationStatusboolean
Boolean indicator aiming to clarify that the relevant transaction is under dispute investigation.
Boolean indicator aiming to clarify that the relevant transaction is under dispute investigation.
- supplementaryDataSupplementaryDatarequired
Schema: SupplementaryData
- acceptedAuthenticationApproachAuthenticationApproaches
Schema: AuthenticationApproaches
- appliedAuthenticationApproachAuthenticationApproach
Schema: AuthenticationApproach
- appliedAuthenticationstringenum · 3
Can only be set by the ASPSP.
Can only be set by the ASPSP. This field allows the ASPSP to inform the PISP about the way authentication was processed during the payment request confirmation.
Code Name Description noAuthentication— — oneFactorAuthentication— — strongAuthentication— — - scaHintstringenum · 2
can only be set by the PISP
can only be set by the PISP Hint given by the merchant and/or the PISP about an SCA exemption context
Code Name Description noScaExemption— — scaExemption— — - successfulReportUrlstring
URL to be used by the ASPSP in order to notify the PISP of the finalisation of the authentication and consent process in REDIRECT and DECOUPLED approach
URL to be used by the ASPSP in order to notify the PISP of the finalisation of the authentication and consent process in REDIRECT and DECOUPLED approach
- unsuccessfulReportUrlstring
URL to be used by the ASPSP in order to notify the PISP of the failure of the authentication and consent process in REDIRECT and DECOUPLED approach
URL to be used by the ASPSP in order to notify the PISP of the failure of the authentication and consent process in REDIRECT and DECOUPLED approach If this URL is not provided by the PISP, the ASPSP will use the "successfulReportUrl" even in case of failure of the Payment Request processing
- nextStatusRequestHintstring (date-time)
Date and time at which the PISP is suggested to ask again for the status of the payment request.
Date and time at which the PISP is suggested to ask again for the status of the payment request.
- loginHintTokenstring
The LOGIN_HINT_TOKEN is a piece of data that may be provided to the API client by the API server, once a PSU has been identified and authenticated.
The LOGIN_HINT_TOKEN is a piece of data that may be provided to the API client by the API server, once a PSU has been identified and authenticated.
- through a response to a token introspection request (RFC7662)
- through a status response to a Payment Request This LOGIN_HINT_TOKEN can then be sent back by the API client to the API server through the posting of a new Payment request. This will help the API server to identify the relevant PSU and ease the authentication process.
Responses
200
The cancellation request was saved. The ASPSP may have to authenticate the PSU before committing the update.
HalAuthenticationRequest
Data forwarded by the ASPSP top the PISP after creation of the Payment Request resource creation The ASPSP, based on the authentication approaches proposed by the PISP, choose the one that it can processed, in respect with the preferences and constraints of the PSU and indicates in this field which approach was chosen. It may happen that the ASPSP considers that, in case of payment cancellation request, there is no need for authentication and will then return "NONE".
Fields (3)
- appliedAuthenticationApproachAuthenticationApproach
Schema: AuthenticationApproach
- nonceNonce
Schema: Nonce
- _linksPaymentRequestResourceCreationLinks
Schema: PaymentRequestResourceCreationLinks
- consentApprovalGenericLink
Schema: GenericLink
- hrefstringrequired
URI to be used. HREF stands for Hypertext REFerence.
Constraints: maxLength: 2000
- templatedboolean
This field must be set with "true" when [href] is an URI template, i.e. with parameters that will be set by the client afterwards. Parameter fields must be included by the API server according to RFC6570.
This field must be set with "true" when [href] is an URI template, i.e. with parameters that will be set by the client afterwards. Parameter fields must be included by the API server according to RFC6570. Otherwise, this property must be absent or set to false default value: false
400
Invalid status value
ErrorModel
Generic error report structure
Fields (6)
- timestampstring (date-time)
current timestamp
- statusinteger (int32)required
HTTP error code
- errorstring
HTTP error text
Constraints: maxLength: 140
- messagestringrequired
HTTP textual reason phrase
Constraints: maxLength: 140
- pathstring
Relevant path that was used
Constraints: maxLength: 140
- detailsarray<ErrorDetail>
list of detailed errors that were encountered
Item: ErrorDetail
- locationstringenum · 2
Location of the erroneous parameter when not in request body
Code Name Description header— — query— — - namestring
Name of the erroneous parameter when not in request body
- pathstring
JsonPath of the erroneous request body property
- erroneousValuestring
Erroneous parameter value
- messagestring
Relevant message for the erroneous parameter
- expectedPatternstring
Expected pattern, if any, that the erroneous parameter does not match with
- expectedValueRangeobject
Expected value range, if any, that the erroneous parameter does not match with
- expectedValueCountobject
Expected value count, in the case of an array item, that the erroneous parameter does not match with
- expectedEnumerationarray<string>
Expected enumeration, if any, that the erroneous parameter do not match with
401
Unauthorized, authentication failure.
ErrorModel
Generic error report structure
Fields (6)
- timestampstring (date-time)
current timestamp
- statusinteger (int32)required
HTTP error code
- errorstring
HTTP error text
Constraints: maxLength: 140
- messagestringrequired
HTTP textual reason phrase
Constraints: maxLength: 140
- pathstring
Relevant path that was used
Constraints: maxLength: 140
- detailsarray<ErrorDetail>
list of detailed errors that were encountered
Item: ErrorDetail
- locationstringenum · 2
Location of the erroneous parameter when not in request body
Code Name Description header— — query— — - namestring
Name of the erroneous parameter when not in request body
- pathstring
JsonPath of the erroneous request body property
- erroneousValuestring
Erroneous parameter value
- messagestring
Relevant message for the erroneous parameter
- expectedPatternstring
Expected pattern, if any, that the erroneous parameter does not match with
- expectedValueRangeobject
Expected value range, if any, that the erroneous parameter does not match with
- expectedValueCountobject
Expected value count, in the case of an array item, that the erroneous parameter does not match with
- expectedEnumerationarray<string>
Expected enumeration, if any, that the erroneous parameter do not match with
403
Forbidden, authentication successful but access to resource is not allowed.
ErrorModel
Generic error report structure
Fields (6)
- timestampstring (date-time)
current timestamp
- statusinteger (int32)required
HTTP error code
- errorstring
HTTP error text
Constraints: maxLength: 140
- messagestringrequired
HTTP textual reason phrase
Constraints: maxLength: 140
- pathstring
Relevant path that was used
Constraints: maxLength: 140
- detailsarray<ErrorDetail>
list of detailed errors that were encountered
Item: ErrorDetail
- locationstringenum · 2
Location of the erroneous parameter when not in request body
Code Name Description header— — query— — - namestring
Name of the erroneous parameter when not in request body
- pathstring
JsonPath of the erroneous request body property
- erroneousValuestring
Erroneous parameter value
- messagestring
Relevant message for the erroneous parameter
- expectedPatternstring
Expected pattern, if any, that the erroneous parameter does not match with
- expectedValueRangeobject
Expected value range, if any, that the erroneous parameter does not match with
- expectedValueCountobject
Expected value count, in the case of an array item, that the erroneous parameter does not match with
- expectedEnumerationarray<string>
Expected enumeration, if any, that the erroneous parameter do not match with
404
Not found, no request available.
ErrorModel
Generic error report structure
Fields (6)
- timestampstring (date-time)
current timestamp
- statusinteger (int32)required
HTTP error code
- errorstring
HTTP error text
Constraints: maxLength: 140
- messagestringrequired
HTTP textual reason phrase
Constraints: maxLength: 140
- pathstring
Relevant path that was used
Constraints: maxLength: 140
- detailsarray<ErrorDetail>
list of detailed errors that were encountered
Item: ErrorDetail
- locationstringenum · 2
Location of the erroneous parameter when not in request body
Code Name Description header— — query— — - namestring
Name of the erroneous parameter when not in request body
- pathstring
JsonPath of the erroneous request body property
- erroneousValuestring
Erroneous parameter value
- messagestring
Relevant message for the erroneous parameter
- expectedPatternstring
Expected pattern, if any, that the erroneous parameter does not match with
- expectedValueRangeobject
Expected value range, if any, that the erroneous parameter does not match with
- expectedValueCountobject
Expected value count, in the case of an array item, that the erroneous parameter does not match with
- expectedEnumerationarray<string>
Expected enumeration, if any, that the erroneous parameter do not match with
405
Method Not Allowed.
ErrorModel
Generic error report structure
Fields (6)
- timestampstring (date-time)
current timestamp
- statusinteger (int32)required
HTTP error code
- errorstring
HTTP error text
Constraints: maxLength: 140
- messagestringrequired
HTTP textual reason phrase
Constraints: maxLength: 140
- pathstring
Relevant path that was used
Constraints: maxLength: 140
- detailsarray<ErrorDetail>
list of detailed errors that were encountered
Item: ErrorDetail
- locationstringenum · 2
Location of the erroneous parameter when not in request body
Code Name Description header— — query— — - namestring
Name of the erroneous parameter when not in request body
- pathstring
JsonPath of the erroneous request body property
- erroneousValuestring
Erroneous parameter value
- messagestring
Relevant message for the erroneous parameter
- expectedPatternstring
Expected pattern, if any, that the erroneous parameter does not match with
- expectedValueRangeobject
Expected value range, if any, that the erroneous parameter does not match with
- expectedValueCountobject
Expected value count, in the case of an array item, that the erroneous parameter does not match with
- expectedEnumerationarray<string>
Expected enumeration, if any, that the erroneous parameter do not match with
406
Not Acceptable.
ErrorModel
Generic error report structure
Fields (6)
- timestampstring (date-time)
current timestamp
- statusinteger (int32)required
HTTP error code
- errorstring
HTTP error text
Constraints: maxLength: 140
- messagestringrequired
HTTP textual reason phrase
Constraints: maxLength: 140
- pathstring
Relevant path that was used
Constraints: maxLength: 140
- detailsarray<ErrorDetail>
list of detailed errors that were encountered
Item: ErrorDetail
- locationstringenum · 2
Location of the erroneous parameter when not in request body
Code Name Description header— — query— — - namestring
Name of the erroneous parameter when not in request body
- pathstring
JsonPath of the erroneous request body property
- erroneousValuestring
Erroneous parameter value
- messagestring
Relevant message for the erroneous parameter
- expectedPatternstring
Expected pattern, if any, that the erroneous parameter does not match with
- expectedValueRangeobject
Expected value range, if any, that the erroneous parameter does not match with
- expectedValueCountobject
Expected value count, in the case of an array item, that the erroneous parameter does not match with
- expectedEnumerationarray<string>
Expected enumeration, if any, that the erroneous parameter do not match with
408
Request Timeout.
ErrorModel
Generic error report structure
Fields (6)
- timestampstring (date-time)
current timestamp
- statusinteger (int32)required
HTTP error code
- errorstring
HTTP error text
Constraints: maxLength: 140
- messagestringrequired
HTTP textual reason phrase
Constraints: maxLength: 140
- pathstring
Relevant path that was used
Constraints: maxLength: 140
- detailsarray<ErrorDetail>
list of detailed errors that were encountered
Item: ErrorDetail
- locationstringenum · 2
Location of the erroneous parameter when not in request body
Code Name Description header— — query— — - namestring
Name of the erroneous parameter when not in request body
- pathstring
JsonPath of the erroneous request body property
- erroneousValuestring
Erroneous parameter value
- messagestring
Relevant message for the erroneous parameter
- expectedPatternstring
Expected pattern, if any, that the erroneous parameter does not match with
- expectedValueRangeobject
Expected value range, if any, that the erroneous parameter does not match with
- expectedValueCountobject
Expected value count, in the case of an array item, that the erroneous parameter does not match with
- expectedEnumerationarray<string>
Expected enumeration, if any, that the erroneous parameter do not match with
409
Conflict. The request could not be completed due to a conflict with the current state of the target resource.
ErrorModel
Generic error report structure
Fields (6)
- timestampstring (date-time)
current timestamp
- statusinteger (int32)required
HTTP error code
- errorstring
HTTP error text
Constraints: maxLength: 140
- messagestringrequired
HTTP textual reason phrase
Constraints: maxLength: 140
- pathstring
Relevant path that was used
Constraints: maxLength: 140
- detailsarray<ErrorDetail>
list of detailed errors that were encountered
Item: ErrorDetail
- locationstringenum · 2
Location of the erroneous parameter when not in request body
Code Name Description header— — query— — - namestring
Name of the erroneous parameter when not in request body
- pathstring
JsonPath of the erroneous request body property
- erroneousValuestring
Erroneous parameter value
- messagestring
Relevant message for the erroneous parameter
- expectedPatternstring
Expected pattern, if any, that the erroneous parameter does not match with
- expectedValueRangeobject
Expected value range, if any, that the erroneous parameter does not match with
- expectedValueCountobject
Expected value count, in the case of an array item, that the erroneous parameter does not match with
- expectedEnumerationarray<string>
Expected enumeration, if any, that the erroneous parameter do not match with
429
Too many requests.
ErrorModel
Generic error report structure
Fields (6)
- timestampstring (date-time)
current timestamp
- statusinteger (int32)required
HTTP error code
- errorstring
HTTP error text
Constraints: maxLength: 140
- messagestringrequired
HTTP textual reason phrase
Constraints: maxLength: 140
- pathstring
Relevant path that was used
Constraints: maxLength: 140
- detailsarray<ErrorDetail>
list of detailed errors that were encountered
Item: ErrorDetail
- locationstringenum · 2
Location of the erroneous parameter when not in request body
Code Name Description header— — query— — - namestring
Name of the erroneous parameter when not in request body
- pathstring
JsonPath of the erroneous request body property
- erroneousValuestring
Erroneous parameter value
- messagestring
Relevant message for the erroneous parameter
- expectedPatternstring
Expected pattern, if any, that the erroneous parameter does not match with
- expectedValueRangeobject
Expected value range, if any, that the erroneous parameter does not match with
- expectedValueCountobject
Expected value count, in the case of an array item, that the erroneous parameter does not match with
- expectedEnumerationarray<string>
Expected enumeration, if any, that the erroneous parameter do not match with
500
Internal server error.
ErrorModel
Generic error report structure
Fields (6)
- timestampstring (date-time)
current timestamp
- statusinteger (int32)required
HTTP error code
- errorstring
HTTP error text
Constraints: maxLength: 140
- messagestringrequired
HTTP textual reason phrase
Constraints: maxLength: 140
- pathstring
Relevant path that was used
Constraints: maxLength: 140
- detailsarray<ErrorDetail>
list of detailed errors that were encountered
Item: ErrorDetail
- locationstringenum · 2
Location of the erroneous parameter when not in request body
Code Name Description header— — query— — - namestring
Name of the erroneous parameter when not in request body
- pathstring
JsonPath of the erroneous request body property
- erroneousValuestring
Erroneous parameter value
- messagestring
Relevant message for the erroneous parameter
- expectedPatternstring
Expected pattern, if any, that the erroneous parameter does not match with
- expectedValueRangeobject
Expected value range, if any, that the erroneous parameter does not match with
- expectedValueCountobject
Expected value count, in the case of an array item, that the erroneous parameter does not match with
- expectedEnumerationarray<string>
Expected enumeration, if any, that the erroneous parameter do not match with
503
Service unavailable.
ErrorModel
Generic error report structure
Fields (6)
- timestampstring (date-time)
current timestamp
- statusinteger (int32)required
HTTP error code
- errorstring
HTTP error text
Constraints: maxLength: 140
- messagestringrequired
HTTP textual reason phrase
Constraints: maxLength: 140
- pathstring
Relevant path that was used
Constraints: maxLength: 140
- detailsarray<ErrorDetail>
list of detailed errors that were encountered
Item: ErrorDetail
- locationstringenum · 2
Location of the erroneous parameter when not in request body
Code Name Description header— — query— — - namestring
Name of the erroneous parameter when not in request body
- pathstring
JsonPath of the erroneous request body property
- erroneousValuestring
Erroneous parameter value
- messagestring
Relevant message for the erroneous parameter
- expectedPatternstring
Expected pattern, if any, that the erroneous parameter does not match with
- expectedValueRangeobject
Expected value range, if any, that the erroneous parameter does not match with
- expectedValueCountobject
Expected value count, in the case of an array item, that the erroneous parameter does not match with
- expectedEnumerationarray<string>
Expected enumeration, if any, that the erroneous parameter do not match with
Schemas used by this endpoint
Every structure referenced by this operation, listed once. Cross-references resolve to anchors on this page.
AccountIdentification
Unique and unambiguous identification for the account between the account owner and the account servicer. Card accounts must provide the identification of the card through the "other" substructure by giving, for instance, the masked PAN (MPAN). The currency used for the account, when needed, can be specified through the [currency] field.
Fields (4)
- workspacestring
Workspace to which the account is linked.
Workspace to which the account is linked. This workspace might be specified by the AISP when forwarding the consent on accounts. If not provided, the default workspace is computed from the authentication that was used for getting the OAuth2 Access Token.
Constraints: maxLength: 32
- ibanstring
ISO20022: International Bank Account Number (IBAN) - identification used internationally by financial institutions to uniquely identify the account of a customer.
ISO20022: International Bank Account Number (IBAN) - identification used internationally by financial institutions to uniquely identify the account of a customer.
Further specifications of the format and content of the IBAN can be found in the standard ISO 13616 "Banking and related financial services - International Bank Account Number (IBAN)" version 1997-10-01, or later revisions.
Constraints: pattern: `^[A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}$`
- otherGenericIdentification
Schema: GenericIdentification
- currencyCurrencyCode
Schema: CurrencyCode
AmountType
Structure aiming to embed the amount and the currency to be used.
Fields (2)
- amountnumber (float)required
ISO20022: Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party.
ISO20022: Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party.
Constraints: pattern: `^\-{0,1}[0-9]{1,13}(\.[0-9]{0,5}){0,1}$`
- currencyCurrencyCoderequired
Schema: CurrencyCode
AuthenticationApproach
Authentication approaches that can be applied. REDIRECT: the PSU is redirected by the TPP to the ASPSP which processes identification and authentication DECOUPLED: the TPP identifies the PSU and forwards the identification to the ASPSP which processes the authentication through a decoupled device NONE: there is no need for the PSU to authenticate
AuthenticationApproaches
List of authentication approaches
Items: AuthenticationApproach
BatchBookingIndicator
Identifies whether a single entry per individual transaction or a batch entry for the sum of the amounts of all transactions within the group of a message is requested. Meaning When True: Identifies that a batch entry for the sum of the amounts of all transactions in the batch or message is requested. Meaning When False: Identifies that a single entry for each of the transactions in the batch or message is requested. Default value: each ASPSP must be able to specify its own default value.
Beneficiary
Specification of a beneficiary
Fields (6)
- workspaceWorkspace
Schema: Workspace
- idstring
Id of the beneficiary
Constraints: pattern: `^([a-zA-Z0-9 /\-?:\()\.,']{1,36})$`
- isTrustedboolean
The ASPSP having not implemented the trusted beneficiaries list must not set this flag.
The ASPSP having not implemented the trusted beneficiaries list must not set this flag. Otherwise, the ASPSP indicates whether or not the beneficiary was registered by the PSU within the trusted beneficiaries list.
- true: the beneficiary is actually a trusted beneficiary
- false: the beneficiary is not a trusted beneficiary
- creditorAgentFinancialInstitutionIdentification
- creditorPartyIdentificationrequired
Schema: PartyIdentification
- creditorAccountAccountIdentification
Schema: AccountIdentification
BookingInformation
Indicator that the payment can be immediately booked or not
- true: payment is booked
- false: payment is not booked Booking a transaction means that the funds required by this transaction are immediatly reserved and that a subsequent transaction will not interfere with the proper execution of the payment. However, usual fraud detection mechanisms might still be triggered and result as a rejection of the payment. This indicator must be provided when the relevant Credit Transfer will be executed as soon as possible but not as an instant payment. This indicator is irrelevant and will not be provided for delayed payments. This indicator is only relevant for the first occurrence of a standing order when this occurrence is not delayed and will be executed as soon as possible.
Case the Information System cannot handle this immediate booking, the ASPSP will have to provide the funds availability information.
CategoryPurposeCode
ISO20022: Specifies the high level purpose of the instruction based on a set of pre-defined categories. This is used by the initiating party to provide information concerning the processing of the payment. It is likely to trigger special processing by any of the agents involved in the payment chain. API: The following values are allowed:
| Code | Name | Description |
|---|---|---|
CASH | CashManagementTransfer | Transaction is a general cash management instruction. |
CORT | TradeSettlementPayment | Transaction is related to settlement of a trade, e.g. a foreign exchange deal or a securities transaction. |
DVPM | DeliverAgainstPayment | Code used to pre-advise the account servicer of a forthcoming deliver against payment instruction. |
INTC | IntraCompanyPayment | Transaction is an intra-company payment, i.e. a payment between two companies belonging to the same group. |
SALA | SalaryPayment | Transaction is the payment of salaries. |
TREA | TreasuryPayment | Transaction is related to treasury operations. E.g. financial contract settlement. |
ChargeBearerCode
ISO20022: Specifies which party/parties will bear the charges associated with the processing of the payment transaction. The following values are allowed:
| Code | Name | Description |
|---|---|---|
DEBT | BorneByDebtor | All transaction charges are to be borne by the debtor. |
CRED | BorneByCreditor | All transaction charges are to be borne by the creditor. |
SHAR | Shared | In a credit transfer context, means that transaction charges on the sender side are to be borne by the debtor, transaction charges on the receiver side are to be borne by the creditor. In a direct debit context, means that transaction charges on the sender side are to be borne by the creditor, transaction charges on the receiver side are to be borne by the debtor. |
SLEV | FollowingServiceLevel | Charges are to be applied following the rules agreed in the service level and/or scheme. |
ClearingSystemMemberIdentification
ISO20022: Information used to identify a member within a clearing system. API: to be used for some specific international credit transfers in order to identify the beneficiary bank
Fields (2)
- clearingSystemIdstringrequired
ISO20022: Specification of a pre-agreed offering between clearing agents or the channel through which the payment instruction is processed.
ISO20022: Specification of a pre-agreed offering between clearing agents or the channel through which the payment instruction is processed.
Constraints: maxLength: 35
- memberIdstringrequired
ISO20022: Identification of a member of a clearing system.
ISO20022: Identification of a member of a clearing system.
Constraints: maxLength: 35
CodeAndIssuer
Specifies a code and the issuer of this code.
Fields (2)
- codestringrequired
Provides the code.
Constraints: maxLength: 4
- issuerstring
Identification of the issuer of the code.
Constraints: maxLength: 35
ContactDetails
Indicates how to contact the party.
Fields (3)
- phoneNumberPhoneNumber
Schema: PhoneNumber
- faxNumberPhoneNumber
Schema: PhoneNumber
- emailAddressstring
email address of the contact
Constraints: maxLength: 2048 · pattern: `^.+@.+$`
CreationDateTime
ISO20022: Date and time at which a (group of) payment instruction(s) was created by the instructing party.
CreditDebitIndicator
Accounting flow of the amount
| Code | Name | Description |
|---|---|---|
CRDT | Credit type amount | — |
DBIT | Debit type amount | — |
CreditorReferenceInformation
Reference information provided by the creditor to allow the identification of the underlying documents.
Fields (2)
- typeCodeAndIssuer
Schema: CodeAndIssuer
- referencestring
Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction.
Constraints: maxLength: 35
CreditTransferTransactionResource
ISO20022: Payment processes required to transfer cash from the debtor to the creditor. The [instructedAmount] property indicates Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. Usage: This amount has to be transported unchanged through the transaction chain. API: Amounts must always be set as positive values.
Fields (23)
- paymentIdPaymentIdentificationrequired
Schema: PaymentIdentification
- resourceIdResourceId
Schema: ResourceId
- requestedExecutionDateRequestedExecutionDate
Schema: RequestedExecutionDate
- cancellableTillstring (date-time)
This field may allow the PISP to get information on the limit timestamp for requesting cancelation of the transaction.
This field may allow the PISP to get information on the limit timestamp for requesting cancelation of the transaction. When this field is not provided by the ASPSP, the PISP must rely on the status of the transaction [transactionStatus] in order to estimate if the transaction is actually cancellable.
- acceptanceDateTimestring (date-time)
ISO20022: Date and time at which all processing conditions for execution of the payment are met and adequate financial cover is available at the account servicing agent.
ISO20022: Date and time at which all processing conditions for execution of the payment are met and adequate financial cover is available at the account servicing agent.
- debtorDecisionDatestring (date-time)
ISO20022: Date and time on when the debtor has accepted or rejected the request.
ISO20022: Date and time on when the debtor has accepted or rejected the request.
- appliedExecutionDatestring (date-time)
ISO20022: Date and time on when the payment was executed.
ISO20022: Date and time on when the payment was executed.
- standingOrderCharacteristicsStandingOrderCharacteristics
Schema: StandingOrderCharacteristics
- instructedAmountAmountType
Schema: AmountType
- equivalentAmountEquivalentAmountType
Schema: EquivalentAmountType
- exchangeRateInformationExchangeRate
Schema: ExchangeRate
- ultimateDebtorPartyIdentification
Schema: PartyIdentification
- intermediaryAgentIntermediaryAgent
Schema: IntermediaryAgent
- beneficiaryBeneficiaryrequired
Schema: Beneficiary
- ultimateCreditorPartyIdentification
Schema: PartyIdentification
- instructionForCreditorAgentarray<InstructionForCreditorAgent>
Further information related to the processing of the payment instruction, provided by the initiating party, and intended for the creditor agent.
Item schema: InstructionForCreditorAgent
- purposePurposeCode
Schema: PurposeCode
- regulatoryReportingCodesRegulatoryReportingCodes
Schema: RegulatoryReportingCodes
- remittanceInformationRemittanceInformation
Schema: RemittanceInformation
- transactionStatusTransactionIndividualStatusCode
Schema: TransactionIndividualStatusCode
- statusReasonInformationStatusReasonInformation
Schema: StatusReasonInformation
- supplementaryDataSupplementaryData
Schema: SupplementaryData
- investigationStatusboolean
Boolean indicator aiming to clarify that the relevant transaction is under dispute investigation.
Boolean indicator aiming to clarify that the relevant transaction is under dispute investigation.
CurrencyCode
Specifies the currency of the amount or of the account. A code allocated to a currency by a Maintenance Agency under an international identification scheme, as described in the latest edition of the international standard ISO 4217 "Codes for the representation of currencies and funds".
DateAndPlaceOfBirth
Date and place of birth of a person. This information must be requested for detection of Fraud, Money-Laundering and Terrorism Financing in case of international payment.
Fields (3)
- birthDatestring (date)required
Date on which a person is born.
- cityOfBirthstringrequired
City where a person was born.
Constraints: maxLength: 35
- countryOfBirthstringrequired
Country where a person was born.
Constraints: pattern: `^[A-Z]{2,2}$`
DocumentAdjustment
ISO20022: Specifies detailed information on the amount and reason of the adjustment. API: Amounts must always be set as positive values.
Fields (4)
- amountAmountTyperequired
Schema: AmountType
- creditDebitIndicatorCreditDebitIndicator
Schema: CreditDebitIndicator
- reasonstring
Specifies the reason for the adjustment.
Constraints: maxLength: 4
- additionalInformationstring
Provides further details on the document adjustment.
Constraints: maxLength: 140
DocumentLineIdentification
Provides identification of the document line. the [type] property must be used for specifying the type of referred document type.
Fields (3)
- typeCodeAndIssuer
Schema: CodeAndIssuer
- numberstring
Unique and unambiguous identification of the referred document line.
Constraints: maxLength: 35
EndDate
The last applicable day of execution for a given period. If not given, the period is considered as endless.
EndToEndId
ISO20022: Unique identification assigned by the initiating party to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain.
EquivalentAmountType
Amount of money to be moved between debtor and creditor, before deduction of charges, expressed in the currency of the debtor's account, and to be moved in a different currency. Usage: The first agent will convert the equivalent amount into the amount to be moved.
Fields (3)
- amountnumber (float)required
ISO20022: Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party.
ISO20022: Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party.
Constraints: pattern: `^\-{0,1}[0-9]{1,13}(\.[0-9]{0,5}){0,1}$`
- currencyCurrencyCoderequired
Schema: CurrencyCode
- currencyOfTransferCurrencyCoderequired
Schema: CurrencyCode
ErrorDetail
detailed error description
Fields (9)
- locationstringenum · 2
Location of the erroneous parameter when not in request body
Code Name Description header— — query— — - namestring
Name of the erroneous parameter when not in request body
- pathstring
JsonPath of the erroneous request body property
- erroneousValuestring
Erroneous parameter value
- messagestring
Relevant message for the erroneous parameter
- expectedPatternstring
Expected pattern, if any, that the erroneous parameter does not match with
- expectedValueRangeobject
Expected value range, if any, that the erroneous parameter does not match with
- expectedValueCountobject
Expected value count, in the case of an array item, that the erroneous parameter does not match with
- expectedEnumerationarray<string>
Expected enumeration, if any, that the erroneous parameter do not match with
ErrorModel
Generic error report structure
Fields (6)
- timestampstring (date-time)
current timestamp
- statusinteger (int32)required
HTTP error code
- errorstring
HTTP error text
Constraints: maxLength: 140
- messagestringrequired
HTTP textual reason phrase
Constraints: maxLength: 140
- pathstring
Relevant path that was used
Constraints: maxLength: 140
- detailsarray<ErrorDetail>
list of detailed errors that were encountered
Item schema: ErrorDetail
ExchangeRate
ISO20022: Provides details on the currency exchange rate and contract. The [unitCurrency] property specifies the currency in which the rate of exchange is expressed in a currency exchange. In the example 1GBP = xxxCUR, the unit currency is GBP. The [estimatedPayerAmount] gives an estimation of the amount that will be debited on the payer's account, including transaction and change fees. The [estimatedPayeeAmunt] gives an estimation of the amount that will be credited on the payee's account. API: Amounts must always be set as positive values.
Fields (6)
- unitCurrencyCurrencyCode
Schema: CurrencyCode
- exchangeRatenumber (float)
The factor used for conversion of an amount from one currency to another. This reflects the price at which one currency was bought with another currency.
The factor used for conversion of an amount from one currency to another. This reflects the price at which one currency was bought with another currency.
- rateTypestringrequiredenum · 3
Specifies the type used to complete the currency exchange.
Specifies the type used to complete the currency exchange.
Code Name Description SPOT Spot Exchange rate applied is the spot rate. SALE Sale Exchange rate applied is the market rate at the time of the sale. AGRD Agreed Exchange rate applied is the rate agreed between the parties. Code Name Description SPOT— — SALE— — AGRD— — - contractIdentificationstring
Unique and unambiguous reference to the foreign exchange contract agreed between the initiating party/creditor and the debtor agent.
Constraints: maxLength: 35
- estimatedPayerAmountAmountType
Schema: AmountType
- estimatedPayeeAmountAmountType
Schema: AmountType
ExecutionRule
Execution date shifting rule for standing orders This data attribute defines the behaviour when recurring payment dates falls on a weekend or bank holiday. The payment is then executed either the "preceding" or "following" working day. ASPSP might reject the request due to the communicated value, if rules in Online-Banking are not supporting this execution rule.
| Code | Name | Description |
|---|---|---|
FWNG | following | — |
PREC | preceding | — |
FinancialInstitutionIdentification
ISO20022: Unique and unambiguous identification of a financial institution, as assigned under an internationally recognised or proprietary identification scheme.
Fields (5)
- bicFistringrequired
ISO20022: Code allocated to a financial institution by the ISO 9362 Registration Authority as described in ISO 9362 "Banking - Banking telecommunication messages - Business identification code (BIC)".
ISO20022: Code allocated to a financial institution by the ISO 9362 Registration Authority as described in ISO 9362 "Banking - Banking telecommunication messages - Business identification code (BIC)".
Constraints: pattern: `^[A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}$`
- clearingSystemMemberIdClearingSystemMemberIdentification
- leiLeiIdentification
Schema: LeiIdentification
- namestring
Name of the financial institution
Constraints: maxLength: 140
- postalAddressPostalAddress
Schema: PostalAddress
FrequencyCode
Frequency rule for standing orders. The following codes from the "EventFrequency7Code" of ISO 20022 are supported. However, each ASPSP might restrict these values into a subset if needed.
| Code | Name | Description |
|---|---|---|
DAIL | Daily | — |
WEEK | Weekly | — |
TOWK | EveryTwoWeeks | — |
MNTH | Monthly | — |
TOMN | EveryTwoMonths | — |
QUTR | Quarterly | — |
SEMI | SemiAnnual | — |
YEAR | Annual | — |
FundsAvailabilityInformation
Indicator that the payment can be covered or not by the funds available on the relevant account
- true: payment is covered
- false: payment is not covered This indicator must be provided by the ASPSP when the Booking Information is present and set to "False". This indicator will not be provided if the Booking Information is absent or set to "True".
GenericIdentification
ISO20022: Unique identification of an account, a person or an organisation, as assigned by an issuer. API: The ASPSP will document which account reference type it will support.
Fields (3)
- identificationstringrequired
API: Identifier
API: Identifier
Constraints: maxLength: 70
- schemeNamestringrequired
Name of the identification scheme.
Name of the identification scheme. Possible values for the scheme name, partially based on ISO20022 external code list, are the following:
Code Name Description BANK BankPartyIdentification Unique and unambiguous assignment made by a specific bank or similar financial institution to identify a relationship as defined between the bank and its client. BBAN BBANIdentifier Basic Bank Account Number (BBAN) - identifier used nationally by financial institutions, ie, in individual countries, generally as part of a National Account Numbering Scheme(s), to uniquely identify the account of a customer. COID CountryIdentificationCode) : Country authority given organisation identification (e.g., corporate registration number) SREN SIREN The SIREN number is a 9 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation in France. SRET SIRET The SIRET number is a 14 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation unit in France. It consists of the SIREN number, followed by a five digit classification number, to identify the local geographical unit of that entity. NIDN NationalIdentityNumber Number assigned by an authority to identify the national identity number of a person. Other values are also permitted, for instance: Code Name Description ---- ---- ----------- OAUT OAUTH2 OAUTH2 access token that is owned by the PISP being also an AISP and that can be used in order to identify the PSU CPAN CardPan Card PAN MPAN MaskedPan Card PAN where some digits were replaced for security reason TPAN TokenizedPan Token which was provided by a Token Service Provider (TSP) in order to obfuscate a real card PAN. The TSP must be identified in the issuer field TBAN TokenizedIBAN Token which was provided by a Token Service Provider (TSP) in order to obfuscate an IBAN. The TSP must be identified in the issuer field Each implementation of the STET PSD2 API must specify in its own documentation which schemes can actually been used Constraints: maxLength: 70
- issuerstring
ISO20022: Entity that assigns the identification. this could a country code or any organisation name or identifier that can be recognized by both parties
ISO20022: Entity that assigns the identification. this could a country code or any organisation name or identifier that can be recognized by both parties
Constraints: maxLength: 35
GenericLink
hypertext reference
Fields (2)
- hrefstringrequired
URI to be used. HREF stands for Hypertext REFerence.
Constraints: maxLength: 2000
- templatedboolean
This field must be set with "true" when [href] is an URI template, i.e. with parameters that will be set by the client afterwards. Parameter fields must be included by the API server according to RFC6570.
This field must be set with "true" when [href] is an URI template, i.e. with parameters that will be set by the client afterwards. Parameter fields must be included by the API server according to RFC6570. Otherwise, this property must be absent or set to false default value: false
HalAuthenticationRequest
Data forwarded by the ASPSP top the PISP after creation of the Payment Request resource creation The ASPSP, based on the authentication approaches proposed by the PISP, choose the one that it can processed, in respect with the preferences and constraints of the PSU and indicates in this field which approach was chosen. It may happen that the ASPSP considers that, in case of payment cancellation request, there is no need for authentication and will then return "NONE".
Fields (3)
- appliedAuthenticationApproachAuthenticationApproach
Schema: AuthenticationApproach
- nonceNonce
Schema: Nonce
- _linksPaymentRequestResourceCreationLinks
InstructionForCreditorAgent
Further information related to the processing of the payment instruction that may need to be acted upon by the creditor's agent. The instruction may relate to a level of service, or may be an instruction that has to be executed by the creditor's agent, or may be information required by the creditor's agent.
Fields (2)
- codestringenum · 4
Coded information related to the processing of the payment instruction, provided by the initiating party, and intended for the creditor's agent.
Coded information related to the processing of the payment instruction, provided by the initiating party, and intended for the creditor's agent.
Code Name Description CHQB PayCreditorByCheque (Ultimate) creditor must be paid by cheque. HOLD HoldCashForCreditor Amount of money must be held for the (ultimate) creditor, who will call. Pay on identification. PHOB PhoneBeneficiary Please advise/contact (ultimate) creditor/claimant by phone. TELB Telecom Please advise/contact (ultimate) creditor/claimant by the most efficient means of telecommunication. Code Name Description CHQB— — HOLD— — PHOB— — TELB— — - instructionInformationstring
Further information complementing the coded instruction or instruction to the creditor's agent that is bilaterally agreed or specific to a user community.
Constraints: maxLength: 140
IntermediaryAgent
Agent and agent account between the debtor's agent and the creditor's agent.
Fields (2)
- agentPartyIdentification
Schema: PartyIdentification
- agentAccountAccountIdentification
Schema: AccountIdentification
LeiIdentification
Legal Entity Identifier is a code allocated to a party as described in ISO 17442 "Financial Services - Legal Entity Identifier (LEI)".
LineDetail
Set of elements used to provide the content of the referred document line.
Fields (3)
- identificationDocumentLineIdentification
Schema: DocumentLineIdentification
- descriptionstring
Description associated with the document line.
Constraints: maxLength: 2048
- amountRemittanceAmount
Schema: RemittanceAmount
LocalInstrumentCode
ISO20022: User community specific instrument. Usage: This element is used to specify a local instrument, local clearing option and/or further qualify the service or service level. API: "INST" value is to be used in order to ask for an SEPA instant Payment (SCTInst). For International payments, this field may be valued with one of the ISO20022 external code to specify which payment instrument should be used by the creditor's bank.
Nonce
Challenge to be sent in order to avoid replay of the authentication process.
PartyIdentification
API : Description of a Party which can be either a person or an organization.
Fields (7)
- namestringrequired
ISO20022: Name by which a party is known and which is usually used to identify that party.
ISO20022: Name by which a party is known and which is usually used to identify that party. The [organisationId] property allows the specification of an unique and unambiguous way to identify an organisation. The [privateId] property allows the specification of an unique and unambiguous way to identify a person.
Constraints: maxLength: 140
- dateAndPlaceOfBirthDateAndPlaceOfBirth
Schema: DateAndPlaceOfBirth
- postalAddressPostalAddress
Schema: PostalAddress
- contactDetailsContactDetails
Schema: ContactDetails
- organisationIdGenericIdentification
Schema: GenericIdentification
- privateIdGenericIdentification
Schema: GenericIdentification
- leiLeiIdentification
Schema: LeiIdentification
PaymentIdentification
ISO20022: Set of elements used to reference a payment instruction.
Fields (3)
- instructionIdstringrequired
ISO20022: Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction.
ISO20022: Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction.
API: Unique identification shared between the PISP and the ASPSP
Constraints: pattern: `^([a-zA-Z0-9 /\-?:\()\.,']{1,36})$`
- endToEndIdEndToEndId
Schema: EndToEndId
- uetrstring
ISO20022: Universally unique identifier to provide an end-to-end reference of a payment transaction.
ISO20022: Universally unique identifier to provide an end-to-end reference of a payment transaction.
Constraints: pattern: `^[a-f0-9]{8}-[a-f0-9]{4}-4[a-f0-9]{3}-[89ab][a-f0-9]{3}-[a-f0-9]{12}$`
PaymentInformationId
ISO20022: Reference assigned by a sending party to unambiguously identify the payment information block within the message. API: This field is a clue for idempotency check by the ASPSP in order to avoid duplicate SCA or payment execution. However the ASPSP may use other mechanisms.
PaymentInformationStatusCode
ISO20022: Specifies the status of the payment information.
API: Mandatory. The following values are allowed to provide the status of the Payment Request

| Code | Name | Description |
|---|---|---|
ACCO | AcceptedCustomerCOnfirmed | The customer, during his/her authentication, has confirmed the payment request. |
ACCP | AcceptedCustomerProfile | Preceding check of technical validation was successful. Customer profile check was also successful. |
ACSC | AcceptedSettlementCompleted | Settlement on the debtor's account was completed. In the case of SCTInst, this status must not been set by the debtor's Bank before the reception of the positive confirmation. |
ACSP | AcceptedSettlementInProcess | All preceding checks such as technical validation and customer profile were successful. Dynamic risk assessment is now also successful and therefore the Payment Request was accepted for execution. |
ACTC | AcceptedTechnicalValidation | Authentication and syntactical and semantical validation are successful. |
ACWC | AcceptedWithChange | Instruction is accepted but a change will be made, such as date or remittance not sent. |
ACWP | AcceptedWithoutPosting | Payment instruction included in the credit transfer is accepted without being posted to the creditor customer's account. |
CANC | Cancelled | Payment initiation was successfully cancelled after having received a request for cancellation. |
PART | PartiallyAccepted | A number of transactions were accepted, whereas another number of transactions have not yet achieved 'accepted' status. |
PATC | PartiallyAcceptedTechnicalCorrect | Payment initiation needs multiple authentications, where some but not yet all were performed. Syntactical and semantical validations are successful. |
RCVD | Received | Payment initiation was received by the receiving agent. |
PDNG | Pending | Payment request or individual transaction included in the Payment Request is pending. Further checks and status update will be performed. |
RJCT | Rejected | Payment request was rejected. |
PaymentRequestResource
ISO20022: The PaymentRequestResource message is sent by the Creditor sending party to the Debtor receiving party, directly or through agents. It is used by a Creditor to request movement of funds from the debtor account to a creditor. API: Information about the creditor (Id, account and agent) must be placed at instruction level. Thus multi-beneficiary payments can be handled. The requested execution date must be placed at payment level even when all instructions are requested to be executed at the same date. The latest case includes:
- multiple instructions having different requested execution dates
- standing orders settings
Fields (20)
- resourceIdResourceId
Schema: ResourceId
- paymentInformationIdPaymentInformationIdrequired
Schema: PaymentInformationId
- batchBookingBatchBookingIndicator
Schema: BatchBookingIndicator
- creationDateTimeCreationDateTimerequired
Schema: CreationDateTime
- numberOfTransactionsintegerrequired
ISO20022: Number of individual transactions contained in the message.
ISO20022: Number of individual transactions contained in the message. API: Each ASPSP will specify a maximum value for this field taking into accounts its specificities about payment request handling
- initiatingPartyPartyIdentificationrequired
Schema: PartyIdentification
- acceptDebtorAccountChangeboolean
indicator that the debtor account can be changed in the payment request by the ASPSP if needed
indicator that the debtor account can be changed in the payment request by the ASPSP if needed
- true: debtor account can be changed (default value)
- false: debtor account cannot be changed
- acceptChargeHandlingChangeboolean
indicator that the charge handling can be changed in the payment request by the ASPSP if needed
indicator that the charge handling can be changed in the payment request by the ASPSP if needed
- true: charge handling can be changed (default value)
- false: charge handling cannot be changed
- acceptInstantPaymentDowngradeboolean
Indicator that the requested instant SEPA Credit Transfer method can be downgraded by the ASPSP into a plain-vanilla SEPA Credit Transfer, when Instant SCT cannot apply or is refused by the PSU.
Indicator that the requested instant SEPA Credit Transfer method can be downgraded by the ASPSP into a plain-vanilla SEPA Credit Transfer, when Instant SCT cannot apply or is refused by the PSU. Eventually, it is up to the ASPSP to downgrade or reject the payment. In case of a downgrade, the ASPSP will have to update de relevant field [LocalInstrument] and remove the "INST" value in order to keep the PISP informed.
- true: payment method can be downgraded
- false: payment method cannot be downgraded (default value)
- paymentTypeInformationPaymentTypeInformationrequired
Schema: PaymentTypeInformation
- debtorPartyIdentification
Schema: PartyIdentification
- debtorAccountAccountIdentification
Schema: AccountIdentification
- debtorAgentFinancialInstitutionIdentification
- chargeBearerChargeBearerCode
Schema: ChargeBearerCode
- paymentInformationStatusPaymentInformationStatusCode
Schema: PaymentInformationStatusCode
- statusReasonInformationStatusReasonInformation
Schema: StatusReasonInformation
- fundsAvailabilityFundsAvailabilityInformation
Schema: FundsAvailabilityInformation
- bookingBookingInformation
Schema: BookingInformation
- creditTransferTransactionarray<CreditTransferTransactionResource>required
ISO20022: Payment processes required to transfer cash from the debtor to the creditor.
ISO20022: Payment processes required to transfer cash from the debtor to the creditor. API: Each ASPSP will specify a maxItems value for this field taking into accounts its specificities about payment request handling
Item schema: CreditTransferTransactionResource
- supplementaryDataSupplementaryDatarequired
Schema: SupplementaryData
PaymentRequestResourceCreationLinks
links that can be used for further navigation, especially in REDIRECT approach
| Link | Description |
|---|---|
| consentApproval | URL to be used by the PISP in order to start the ASPSP authentication and consent management process |
Fields (1)
- consentApprovalGenericLink
Schema: GenericLink
PaymentTypeInformation
ISO20022: Set of elements used to further specify the type of transaction.
Fields (4)
- instructionPriorityPriorityCode
Schema: PriorityCode
- serviceLevelServiceLevelCode
Schema: ServiceLevelCode
- localInstrumentLocalInstrumentCode
Schema: LocalInstrumentCode
- categoryPurposeCategoryPurposeCode
Schema: CategoryPurposeCode
PercentageRate
Rate expressed as a percentage, ie, in hundredths, eg, 0.7 is 7/10 of a percent, and 7.0 is 7%.
PhoneNumber
The collection of information which identifies a specific phone or FAX number as defined by telecom services. It consists of a "+" followed by the country code (from 1 to 3 characters) then a "-" and finally, any combination of numbers, "(", ")", "+" and "-" (up to 30 characters).
PostalAddress
ISO20022: Information that locates and identifies a specific address, as defined by postal services.
Fields (11)
- addressTypestringenum · 6
ISO20022: Identifies the nature of the postal address.
ISO20022: Identifies the nature of the postal address. API: Cannot be used for SEPA payments. Proprietary codes can be specified and documented if needed.
Code Name Description BIZZ Business Address is the business address DLVY Delivery Address is the address to which delivery is to take place MLTO Mail To Address is the address to which mail is sent PBOX PO Box Address is is a postal office (PO) box ADDR Postal Address is the complete postal address HOME Home Address is the home address Code Name Description BIZZ— — DLVY— — MLTO— — PBOX— — ADDR— — HOME— — - departmentstring
ISO20022: Identification of a division of a large organisation or building.
ISO20022: Identification of a division of a large organisation or building. API: Cannot be used for SEPA payments.
Constraints: maxLength: 70
- subDepartmentstring
ISO20022: Identification of a sub-division of a large organisation or building.
ISO20022: Identification of a sub-division of a large organisation or building. API: Cannot be used for SEPA payments.
Constraints: maxLength: 70
- streetNamestring
ISO20022: Name of a street or thoroughfare.
ISO20022: Name of a street or thoroughfare. API: Cannot be used for SEPA payments.
Constraints: maxLength: 70
- buildingNumberstring
ISO20022: Number that identifies the position of a building on a street.
ISO20022: Number that identifies the position of a building on a street. API: Cannot be used for SEPA payments.
Constraints: maxLength: 16
- buildingNamestring
ISO20022: Name of the building or house.
ISO20022: Name of the building or house. API: Cannot be used for SEPA payments.
Constraints: maxLength: 16
- postCodestring
ISO20022: Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail.
ISO20022: Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail. API: Cannot be used for SEPA payments.
Constraints: maxLength: 16
- townNamestring
ISO20022: Name of a built-up area, with defined boundaries, and a local government.
ISO20022: Name of a built-up area, with defined boundaries, and a local government. API: Cannot be used for SEPA payments.
Constraints: maxLength: 35
- countrySubDivisionstring
ISO20022: Identifies a subdivision of a country such as state, region, county.
ISO20022: Identifies a subdivision of a country such as state, region, county. API: Cannot be used for SEPA payments.
Constraints: maxLength: 35
- countrystringrequired
ISO20022: Country in which a person resides (the place of a person's home). In the case of a company, it is the country from which the affairs of that company are directed.
ISO20022: Country in which a person resides (the place of a person's home). In the case of a company, it is the country from which the affairs of that company are directed.
Constraints: pattern: `^([A-Z]{2,2})$`
- addressLinearray<string>
Unstructured address. The lines must embed zip code and town name.
Unstructured address. The lines must embed zip code and town name. For SEPA payments, only two address lines are allowed.
PriorityCode
ISO20022: Indicator of the urgency or order of importance that the instructing party would like the instructed party to apply to the processing of the instruction. API: This field is useless for SCTInst and thus should be ignored.
PurposeCode
ISO20022: Underlying reason for the payment transaction, as published in an external purpose code list. API: The following values are allowed for Payment Request
| Code | Name | Description |
|---|---|---|
ACCT | AccountManagement | Funds moved between 2 accounts of same account holder at the same bank) |
CASH | CashManagementTransfer | (general cash management instruction) may be used for Transfer Initiation |
COMC | CommercialPayment | Transaction is related to a payment of commercial credit or debit. |
CPKC | CarparkCharges | General Carpark Charges Transaction is related to carpark charges. |
SALA | SalaryPayment | Transaction is the payment of salaries. |
TRPT | RoadPricing | Transport RoadPricing Transaction is for the payment to top-up pre-paid card and electronic road pricing for the purpose of transportation. |
ReferredDocumentInformation
Provides the identification and the content of the referred document.
Fields (4)
- typeCodeAndIssuer
Schema: CodeAndIssuer
- numberstring
Unique and unambiguous identification of the referred document.
Constraints: maxLength: 35
- lineDetailsarray<LineDetail>
Sets of elements used to provide the content of the referred document line.
Item schema: LineDetail
ReferredDocumentInformations
Provides the identification and the content of the referred documents.
Items: ReferredDocumentInformation
RegulatoryReportingCode
Information needed due to regulatory and statutory requirements. Economical codes to be used are provided by the National Competent Authority
RegulatoryReportingCodes
List of needed regulatory reporting codes for international payments
Items: RegulatoryReportingCode
RemittanceAmount
ISO20022: Provides details on the amounts of the document line. API: Amounts must always be set as positive values.
| Property | Description |
|---|---|
| duePayableAmount | Amount specified is the exact amount due and payable to the creditor. |
| discountAppliedAmount | Amount of discount to be applied to the amount due and payable to the creditor. |
| creditNoteAmount | Amount of a credit note. |
| taxAmount | Amount of the tax. |
| adjustmentAmountAndReason | Specifies detailed information on the amount and reason of the adjustment. |
| remittedAmount | Amount of money remitted. |
Fields (6)
- duePayableAmountAmountType
Schema: AmountType
- discountAppliedAmountTypedAmount
Schema: TypedAmount
- creditNoteAmountAmountType
Schema: AmountType
- taxAmountTypedAmount
Schema: TypedAmount
- adjustmentAmountAndReasonDocumentAdjustment
Schema: DocumentAdjustment
- remittedAmountAmountType
Schema: AmountType
RemittanceInformation
ISO20022: Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts' receivable system. API:
- Only one occurrence of the unstructured information is allowed.
- Only one occurrence of the structured information is allowed.
- Structured and unstructured information can coexist.
Fields (2)
- unstructuredarray<string>
Unstructured remittance information.
Unstructured remittance information. Each implementation may add a pattern in order to specify its own character set constraints.
- structuredarray<StructuredRemittanceInformation>
Structured remittance information
Item schema: StructuredRemittanceInformation
RequestedExecutionDate
ISO20022: Date at which the initiating party requests the clearing agent to process the payment. API: When set by the PISP, this field indicates the future date at which the payment instruction should be executed and the debtor account should be debited. if this field is not set by the PISP, the ASPSP is requested to execute the payment instruction as soon as possible. In most of the cases, especially for international payments, the date of the credit on the credit account cannot be set. Only SCTInst can guarantee having the same date for this credit. When the payment cannot be processed at the requested date, the ASPSP is allowed to shift the applied execution date to the next possible execution date for non-standing orders. For standing orders, this field is useless since the [startDate] parameter already provides the needed information for the first payment instruction to be executed.
ResourceId
API: Identifier assigned by the ASPSP for further use of the created resource through API calls. The API client cannot set or modify the value of this field. Since this value can be exchanged between the server and the client as an URL element or for support information, it must not contain sensitive value such as personal or business data. However it is the duty of each ASPSP to perform its own risk analysis on this topic.
ServiceLevelCode
ISO20022: Agreement under which or rules under which the transaction should be processed. Specifies a pre-agreed service or level of service between the parties, as published in an external service level code list. API: Only "SEPA" (SEPA Credit Transfer) value is allowed
StandingOrderCharacteristics
Specifies the characteristics of a standing order.
Fields (4)
- startDateStartDaterequired
Schema: StartDate
- endDateEndDate
Schema: EndDate
- executionRuleExecutionRulerequired
Schema: ExecutionRule
- frequencyFrequencyCoderequired
Schema: FrequencyCode
StartDate
The first applicable day of execution for a given period.
StatusReasonInformation
ISO20022: Provides detailed information on the status reason.
API: Can only be used in case the status is equal to "RJCT" or "CANC". Only the following values are allowed:
| Code | Name | Description |
|---|---|---|
AC01 | IncorectAccountNumber | the account number is either invalid or does not exist |
AC04 | ClosedAccountNumber | the account is closed and cannot be used |
AC06 | BlockedAccount | the account is blocked and cannot be used |
AG01 | TransactionForbidden | Transaction forbidden on this type of account |
AG03 | TransactionNotSupported | Transaction type not supported/authorized on this account |
AM02 | NotAllowedAccount | SPecific transaction/message amount is greater than allowed maximum |
AM04 | InsufficientFunds | Amount of funds available to cover specified message amount is insufficient |
AM18 | InvalidNumberOfTransactions | the number of transactions exceeds the ASPSP acceptance limit |
CH03 | RequestedExecutionDateOrRequestedCollectionDateTooFarInFuture | The requested execution date is too far in the future |
CH04 | RequestedExecutionDateOrRequestedCollectionDateTooFarInPast | Value in Requested Execution Date or Requested Collection Date is too far in the past |
CNOR | CreditorBankIsNotRegistered | Creditor bank is not registered under this BIC in the CSM |
CUST | RequestedByCustomer | The reject is due to the debtor: refusal or lack of liquidity |
DS02 | OrderCancelled | An authorized user has cancelled the order |
DUPL | DuplicatePayment | Payment is a duplicate of another payment. Can only be set by a PISP for a payment request cancellation. |
FF01 | InvalidFileFormat | The reject is due to the original Payment Request which is invalid (syntax, structure or values) |
FRAD | FraudulentOriginated | the Payment Request is considered as fraudulent |
MS03 | NotSpecifiedReasonAgentGenerated | No reason specified by the ASPSP |
NOAS | NoAnswerFromCustomer | The PSU has neither accepted nor rejected the Payment Request and a time-out has occurred |
RR01 | MissingDebtorAccountOrIdentification | The Debtor account and/or Identification are missing or inconsistent |
RR03 | MissingCreditorNameOrAddress | Specification of the creditor's name and/or address needed for regulatory requirements is insufficient or missing. |
RR04 | RegulatoryReason | Reject from regulatory reason |
RR12 | InvalidPartyID | Invalid or missing identification required within a particular country or payment type. |
TECH | TechnicalProblem | Technical problems resulting in an erroneous transaction. Can only be set by a PISP for a payment request cancellation. |
StructuredRemittanceInformation
Information supplied to enable the matching/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts' receivable system, in a structured form.
Fields (6)
- referredDocumentInformationReferredDocumentInformations
Schema: ReferredDocumentInformations
- referredDocumentAmountRemittanceAmount
Schema: RemittanceAmount
- creditorReferenceInformationCreditorReferenceInformation
Schema: CreditorReferenceInformation
- invoicerPartyIdentification
Schema: PartyIdentification
- invoiceePartyIdentification
Schema: PartyIdentification
- taxRemittanceTaxInformation
Schema: TaxInformation
SupplementaryData
ISO20022: Additional information that cannot be captured in the structured elements and/or any other specific block. API: This structure is used to embed the relevant URLs for returning the status report to the PISP and to specify which authentication approaches are accepted by the PISP and which was chosen by the ASPSP The [acceptedAuthenticationApproach] property can only be set by the PISP.
- Authentication approaches that are supported by the PISP. The PISP can provide several choices separated by commas.
- Case of none of the accepted approaches is supported by the ASPSP, the latest will respond with HTTP400 (Bad request) and specify wich approaches are actually supported. The [appliedAuthentication] will be set by the ASPSP.
- The ASPSP, based on the authentication approaches proposed by the PISP, choose the one that it can processed, in respect with the preferences and constraints of the PSU and indicates in this field which approach was chosen.
- It may happen that the ASPSP considers that, in case of payment cancellation request, there is no need for authentication and will then return "NONE".
Fields (8)
- acceptedAuthenticationApproachAuthenticationApproaches
Schema: AuthenticationApproaches
- appliedAuthenticationApproachAuthenticationApproach
Schema: AuthenticationApproach
- appliedAuthenticationstringenum · 3
Can only be set by the ASPSP.
Can only be set by the ASPSP. This field allows the ASPSP to inform the PISP about the way authentication was processed during the payment request confirmation.
Code Name Description noAuthentication— — oneFactorAuthentication— — strongAuthentication— — - scaHintstringenum · 2
can only be set by the PISP
can only be set by the PISP Hint given by the merchant and/or the PISP about an SCA exemption context
Code Name Description noScaExemption— — scaExemption— — - successfulReportUrlstring
URL to be used by the ASPSP in order to notify the PISP of the finalisation of the authentication and consent process in REDIRECT and DECOUPLED approach
URL to be used by the ASPSP in order to notify the PISP of the finalisation of the authentication and consent process in REDIRECT and DECOUPLED approach
- unsuccessfulReportUrlstring
URL to be used by the ASPSP in order to notify the PISP of the failure of the authentication and consent process in REDIRECT and DECOUPLED approach
URL to be used by the ASPSP in order to notify the PISP of the failure of the authentication and consent process in REDIRECT and DECOUPLED approach If this URL is not provided by the PISP, the ASPSP will use the "successfulReportUrl" even in case of failure of the Payment Request processing
- nextStatusRequestHintstring (date-time)
Date and time at which the PISP is suggested to ask again for the status of the payment request.
Date and time at which the PISP is suggested to ask again for the status of the payment request.
- loginHintTokenstring
The LOGIN_HINT_TOKEN is a piece of data that may be provided to the API client by the API server, once a PSU has been identified and authenticated.
The LOGIN_HINT_TOKEN is a piece of data that may be provided to the API client by the API server, once a PSU has been identified and authenticated.
- through a response to a token introspection request (RFC7662)
- through a status response to a Payment Request This LOGIN_HINT_TOKEN can then be sent back by the API client to the API server through the posting of a new Payment request. This will help the API server to identify the relevant PSU and ease the authentication process.
TaxAmount
ISO20022: Set of elements used to provide information on the amount of the tax record. API: Amounts must always be set as positive values.
| Property | Description |
|---|---|
| rate | Rate used to calculate the tax. |
| taxableBaseAmount | Amount of money on which the tax is based. |
| totalAmount | Total amount that is the result of the calculation of the tax for the record. |
| details | Set of elements used to provide details on the tax period and amount. |
Fields (4)
- ratePercentageRate
Schema: PercentageRate
- taxableBaseAmountAmountType
Schema: AmountType
- totalAmountAmountType
Schema: AmountType
- detailsarray<TaxRecordDetails>
Set of elements used to provide details on the tax period and amount.
Item schema: TaxRecordDetails
TaxInformation
ISO20022: Details about tax paid, or to be paid, to the government in accordance with the law, including pre-defined parameters such as thresholds and type of account. API: Amounts must always be set as positive values. The [totalTaxableBaseAmount] property indicates the total amount of money on which the tax is based. The [totalTaxAmount] property indicates the total amount of money as result of the calculation of the tax.
Fields (11)
- creditorTaxParty
Schema: TaxParty
- debtorTaxParty
Schema: TaxParty
- ultimateDebtorTaxParty
Schema: TaxParty
- administrationZonestring
Territorial part of a country to which the tax payment is related.
Constraints: maxLength: 35
- referenceNumberstring
Tax reference information that is specific to a taxing agency.
Constraints: maxLength: 140
- methodstring
Method used to indicate the underlying business or how the tax is paid.
Constraints: maxLength: 35
- totalTaxableBaseAmountAmountType
Schema: AmountType
- totalTaxAmountAmountType
Schema: AmountType
- datestring (date)
Date by which tax is due.
- sequenceNumberinteger (int32)
Sequential number of the tax report.
- recordarray<TaxRecord>
Records of tax details
Item schema: TaxRecord
TaxParty
Set of elements used to identify a party of the transaction to which the tax applies. The [authorization] property aims to provide the details of the authorised tax paying party.
Fields (4)
- taxIdentificationstring
Tax identification number of the party.
Constraints: maxLength: 35
- registrationIdentificationstring
Unique identification, as assigned by an organisation, to unambiguously identify a party.
Constraints: maxLength: 35
- taxTypestring
Type of tax payer.
Constraints: maxLength: 35
TaxPeriod
Set of elements used to provide details on the period of time related to the tax payment. The [type] property aims to identify the period related to the tax payment.
Fields (4)
- yearstring
Year related to the tax payment.
Constraints: pattern: `^[0-9]{4,4}$`
- typeTaxRecordPeriodCode
Schema: TaxRecordPeriodCode
- fromDatestring (date)
Start date of the range.
- toDatestring (date)
End date of the range.
TaxRecord
Record of tax details the [period] property embbeds the set of elements used to provide details on the period of time related to the tax payment. the [amount] property embbeds the set of elements used to provide information on the amount of the tax record.
Fields (9)
- typestring
High level code to identify the type of tax details.
Constraints: maxLength: 35
- categorystring
Specifies the tax code as published by the tax authority.
Constraints: maxLength: 35
- categoryDetailsstring
Provides further details of the category tax code.
Constraints: maxLength: 35
- debtorStatusstring
Code provided by local authority to identify the status of the party that has drawn up the settlement document.
Constraints: maxLength: 35
- certificateIdentificationstring
Identification number of the tax report as assigned by the taxing authority.
Constraints: maxLength: 35
- formsCodestring
Identifies, in a coded form, on which template the tax report is to be provided.
Constraints: maxLength: 35
- periodTaxPeriod
Schema: TaxPeriod
- taxAmountTaxAmount
Schema: TaxAmount
- additionalInformationstring
Further details of the tax record.
Constraints: maxLength: 140
TaxRecordDetails
ISO20022: Elements used to provide details on the tax period and amount. API: Amounts must always be set as positive values.
| Property | Description |
|---|---|
| period | Set of elements used to provide details on the period of time related to the tax payment. |
| amount | Underlying tax amount related to the specified period. |
Fields (2)
- periodTaxPeriod
Schema: TaxPeriod
- amountAmountTyperequired
Schema: AmountType
TaxRecordPeriodCode
Identification of the period related to the tax payment.
| Code | Name | Description |
|---|---|---|
MM01 | FirstMonth Tax is related to the second month of the period. | — |
MM02 | SecondMonth Tax is related to the first month of the period. | — |
MM03 | ThirdMonth Tax is related to the third month of the period. | — |
MM04 | FourthMonth Tax is related to the fourth month of the period. | — |
MM05 | FifthMonth Tax is related to the fifth month of the period. | — |
MM06 | SixthMonth Tax is related to the sixth month of the period. | — |
MM07 | SeventhMonth Tax is related to the seventh month of the period. | — |
MM08 | EighthMonth Tax is related to the eighth month of the period. | — |
MM09 | NinthMonth Tax is related to the ninth month of the period. | — |
MM10 | TenthMonth Tax is related to the tenth month of the period. | — |
MM11 | EleventhMonth Tax is related to the eleventh month of the period. | — |
MM12 | TwelfthMonth Tax is related to the twelfth month of the period. | — |
QTR1 | FirstQuarter Tax is related to the first quarter of the period. | — |
QTR2 | SecondQuarter Tax is related to the second quarter of the period. | — |
QTR3 | ThirdQuarter Tax is related to the third quarter of the period. | — |
QTR4 | FourthQuarter Tax is related to the fourth quarter of the period. | — |
HLF1 | FirstHalf Tax is related to the first half of the period. | — |
HLF2 | SecondHalf Tax is related to the second half of the period. | — |
TitleAndName
Title and Name of the party or the party's authorised reprensentative.
Fields (2)
- titlestring
Title or position of the party or the party's authorised reprensentative.
Constraints: maxLength: 35
- namestring
Name of the party or the party's authorised reprensentative.
Constraints: maxLength: 140
TransactionIndividualStatusCode
ISO20022: Specifies the status of the payment information group.
API: Only the following values are allowed to provide the status of the subsequent CREDIT TRANSFER to the Payment Request

| Code | Name | Description |
|---|---|---|
ACSC | AcceptedSettlementCompleted | Settlement on the debtor's account was completed. In the case of SCTInst, this status must not been set by the debtor's Bank before the reception of the positive confirmation. The transaction cannot be cancelled. |
ACSP | AcceptedSettlementInProcess | All preceding checks such as technical validation and customer profile were successful and therefore the Payment Request was accepted for execution. The transaction cannot be cancelled. |
ACTC | AcceptedTechnicalValidation | Authentication and syntactical and semantical validation are successful. The transaction might be cancelled. |
CANC | Cancelled | Payment initiation was successfully cancelled after having received a request for cancellation. |
PDNG | Pending | Payment request or individual transaction included in the Payment Request is pending. Further checks and status update will be performed. The transaction might be cancelled. |
RJCT | Rejected | Payment request or individual transaction included in the Payment Request was rejected. |
TypedAmount
ISO20022: Typed Amount API: Amounts must always be set as positive values.
Fields (2)
- typestring
Type of the amount
Constraints: maxLength: 35
- amountAmountTyperequired
Schema: AmountType
Workspace
Some ASPSP may provide different user workspaces that can be accessed by the same authenticated PSU. In this case, the AISP is able to retrieve the different pieces of account information by specifying the relevant workspace as a QUERY parameter. Identification of the workspace to be used when processing the request. If not present, the default workspace to be used is the one that is linked to the authentication processed during the OAuth2 access token request.
Fields (2)
- identificationstringrequired
identification of the workspace to be used as an optional query parameter for some AISP queries
Constraints: maxLength: 32
- labelstringrequired
textual description of the workspace as specified by the ASPSP in relationship wth the PSU
Constraints: maxLength: 128