Accounts Service - SMBC NextGenPSD2
|
|
- Miles Walters
- 5 years ago
- Views:
Transcription
1 Accounts Service - SMBC NextGenPSD2 1.3.SMBC February 2019 Framework (Berlin Group V1.3) Summary OAS3 SMBC offers third party access to accounts (XS2A) in a safe and efficient way using Application Programming Interfaces (APIs) in line with the Berlin Group's NextGenPSD2 Framework Version 1.3. SMBC supports the following NextGenPSD2 services: Consents Accounts Payments Signing-baskets Funds-confirmations SMBC uses an OAuth authentication approach for which the following service is supported: Tokens The NextGenPSD2 framework supports a number of SCA approaches for granting TPPs safe and secure access to accounts as well as SCA approaches for submitting payments. SMBC supports the following approach: Redirect SCA Approach Under our implementation, TPPs will first use our Token service to obtain a TPP Access Token via a Client Credentials Grant Flow which will then be used to create a Consent Resource using our Consents service. The creation of the Consent Resource starts an OAuth Grant Flow resulting in the PSU performing SCA via redirect and the TPP obtaining a PSU Access Token and Refresh Token. PSU Access Tokens are short lived while Refresh Tokens will remain valid for the duration of the requested access (maximum of 90 days). Using a valid PSU Access Token and accompanying Consent-Id, the TPP may make unlimited AISP requests using our Accounts service and may create Payments and read Payment data using our Payments and Signing-baskets services. In addition to holding a valid PSU Access Token, every Payment requires two PSUs to undergo an additional SCA using the Redirect SCA Approach for authorisation. PSUs may provide their authorisation to multiple Payments at once using a Signing-basket.
2 Accounts This document, based on the NextGenPSD2 YAML, which itself is based on the NextGenPSD2 Implementation Guidelines, defines SMBC's Accounts service. In this document we describe which endpoints are supported and the request and response specifications for each. According to the OpenAPI-Specification [ "If in is "header" and the name field is "Accept", "Content-Type" or "Authorization", the parameter definition SHALL be ignored." The element "Accept" will not be defined in this file at any place. The elements "Content-Type" and "Authorization" are implicitly defined by the OpenApi tags "content" and "security". We omit the definition of all standard HTTP header elements (mandatory/optional/conditional) except they are mention in the Implementation Guidelines. Therefore the implementer might add the in his own realisation of a PSD2 comlient API in addition to the elements define in this file. General Remarks on Data Types The Berlin Group definition of UTF-8 s in context of the PSD2 API have to support at least the following characters a b c d e f g h i j k l m n o p q r s t u v w x y z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z / -? : ( )., ' + Space The Berlin Group - A European Standards Initiative - Website Send to The Berlin Group - A European Standards Initiative Creative Commons Attribution 4.0 International Public License Full Documentation of NextGenPSD2 Access to Account Interoperability Framework (General Introduction Paper, Operational Rules, Implementation Guidelines) Servers
3 - SMBC Sandbox PSD2 Project Authorize Accounts Details of accounts GET /berlingroup/v1/accounts Read Account List Read the identifiers of the available payment accounts together with booking balance information, depending on the consent granted. Consent of the PSU to this access must have already been given and stored on the ASPSP system via the Consents serivce. The addressed list of accounts depends then on the PSU ID and the stored consent addressed by consentid, respectively the OAuth2 access token. Returns all identifiers of the accounts, to which an account access has been granted to through the /consents endpoint by the PSU. In addition, relevant information about the accounts and hyperlinks to corresponding account information resources are provided if a related consent has been already granted. Remark: Note that the Query Paramater withbalance is ignored and interimavailable balance is always returned with each account if the consent includes access to balances. Parameters Try it out Name Description X-Requestrequired ID * Consent- ID * required ID of the request, unique to the call, as determined by the initiating party. This then contains the consentid of the related AIS consent, which was performed prior to this payment initiation.
4 Name Description PSU-IP- Address PSU- Device-ID The forwarded IP Address header field consists of the corresponding HTTP request IP Address field between PSU and TPP. It must be contained if and only if this request was actively initiated by the PSU. 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. It must be contained if and only if this request was actively initiated by the PSU. PSU-IP-Port PSU-Accept The forwarded IP Port header field consists of the corresponding HTTP request IP Port field between PSU and TPP, if available. The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available. PSU- Accept- Charset PSU- Accept- Encoding The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available. The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available.
5 Name Description PSU- Accept- Language PSU-User- Agent PSU-Http- Method The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available. The forwarded Agent header field of the HTTP request between PSU and TPP, if available. HTTP method used at the PSU? TPP interface, if available. Valid values are: GET POST PUT PATCH DELETE Available values : GET, POST, PUT, PATCH, DELETE PSU-Geo- Location The forwarded Geo Location of the corresponding http request between PSU and TPP if available. Responses Code Description Links 200 OK No links
6 Code Description Links application/json Controls Accept header. Example Value Schema accountlist List of accounts with details. accounts* accountdetails [ SMBC will give the following for account reference identifiers: iban bban bic entity currency Customers will multiple accounts may use the same IBAN for all their accounts. Therefore when referencing an account using the iban identifier, it must be accompanied with its currency code. resourceid The account may be addressed by the resourceid on the /accounts/account-id endpoint. iban iban pattern: [A-Z]2,2[0-9]2,2[a-zA-Z0-9]1,30 example: FR IBAN of an account bban bban pattern: [a-za-z0-9]1,30 example: BARC Basic Bank Account Number (BBAN) Identifier This data element can be used in the body of the Consent Request Message for retrieving Account access Consent from this Account. This data elements is used for payment Accounts which have no IBAN. ISO20022: Basic Bank
7 Account Number (BBAN). Code Description Links Identifier used nationally by financial institutions, i.e., in individual countries, generally as part of a National Account Numbering Scheme(s), which uniquely identifies the account of a customer. amount* amountvalue currency* currencycode pattern: [A-Z]3 example: EUR ISO 4217 Alpha 3 currency code name maxlength: 35 Name of the account given by the bank or the PSU in online-banking. bic bicfi pattern: [A-Z]6,6[A-Z2-9][A-NP-Z0-9]([A-Z0-9]3,3)0,1 example: AAAADEBBXXX BICFI entity entity maxlength: 35 Title of the account holder, given by the bank in online banking. balances balancelist [ A list of balances regarding this account, e.g. the current balance, the last booked balance. The list might be restricted to the current balance. balance A single balance element balanceamount* amount currency* currencycode pattern: [A-Z] 3 example: EUR ISO 4217 Alpha 3 currency code
8 Code Description pattern: -?[0-9]1,14(\.[0-9]1,3)? example: The amount given with fractional digits, where fractions must be compliant to the currency definition. Up to 14 significant figures. Negative amounts are signed by minus. The decimal separator is a dot. Links Example: Valid representations for EUR with up to two decimals are: balancetype* balancetype The following balance types are defined: "closingbooked": Balance of the account at the end of the pre-agreed account reporting
9 Code Description of the opening booked balance at the beginning of the period and all entries booked to the account during the pre-agreed account reporting period. "openingbooked": Book balance of the account at the beginning of the account reporting period. It always equals the closing book balance from the previous report. "interimavailable": Available balance calculated in the course of the account servicer's business day, at the time specified, and subject to further changes during the business day. The interim balance is calculated on the basis of booked credit and debit items during the calculation time/period specified. "interimbooked": Booked balance calculated at the time specified, and subject to further changes during the business day. The interim balance is calculated on the basis of booked credit and debit Links
10 items during the Code Description calculation Links time/period specified. Enum: referencedate [ interimavailable, closingbooked, openingbooked, interimbooked ] ($date) Reference date of the balance _links ] _linksaccountdetails Links to the account, which can be directly used for retrieving account information from this dedicated account. Links to "balances" and/or "transactions" These links are only supported, when the corresponding consent has been already granted. balances hreftype example: /v1/payments/sepacredittransfers/1234- wertiq-983 Link to a resource transactions hreftype example: /v1/payments/sepa-
11 credit Code Description transfers/1234- wertiq-983 Links Link to a resource ] X-Request-ID ID of the request, unique to the call, as determined by the initiating party. Date Current time in UTC datetime
12 Code Description Links 400 Bad Request No links application/json Example Value Schema Error400_AIS_SMBC Error definition for additional SMBC validation. error* MessageCode400_AIS_SMBC Error attribute defining the type of error encountered. Enum: error_description* [ invalid_request, invalid_client ] ($uri) maxlength: 70 A description of the cause of the error, e.g. a mandatory request header is missing. X-Request-ID ID of the request, unique to the call, as determined by the initiating party.
13 Code Description Links 401 Unauthorized No links application/problem+json Example Value Schema Error401_AIS type* Standardised definition of reporting error information according to [RFC7807] in case of a HTTP error code 401 for AIS. ($uri) maxlength: 70 A NextGenPSD2 URI reference [RFC3986] that identifies the problem type. code* MessageCode401_AIS Message codes defined for AIS for HTTP Error code 401 (UNAUTHORIZED). Enum: [ TOKEN_UNKNOWN, TOKEN_INVALID, TOKEN_EXPIRED ] X-Request-ID ID of the request, unique to the call, as determined by the initiating party.
14 Code Description Links 405 Method Not Allowed No links application/problem+json Example Value Schema Error405_AIS type* Standardised definition of reporting error information according to [RFC7807] in case of a HTTP error code 405 for AIS. ($uri) maxlength: 70 A NextGenPSD2 URI reference [RFC3986] that identifies the problem type. code* MessageCode405_AIS Message codes defined for AIS for HTTP Error code 405 (METHOD NOT ALLOWED). Enum: [ SERVICE_INVALID ] X-Request-ID ID of the request, unique to the call, as determined by the initiating party.
15 Code Description Links 429 Too Many Requests No links X-Request-ID ID of the request, unique to the call, as determined by the initiating party. 500 Internal Server Error No links X-Request-ID ID of the request, unique to the call, as determined by the initiating party. 503 Service Unavailable No links X-Request-ID ID of the request, unique to the call, as determined by the initiating party. GET /berlingroup/v1/accounts/account-id Read Account Details Reads details about an account.consent of the PSU to this access must have already been given and stored on the ASPSP system via the Consents serivce. The addressed details of this account depends then on the stored consent addressed by consentid, respectively the OAuth2 access token. Remark: Note that the Query Paramater withbalance is ignored and interimavailable balance is always returned with the account if the consent includes access to balances.
16 Parameters Try it out Name Description accountid * (path) X-Requestrequired ID * PSU-IP- Address PSU- Device-ID Consent- ID * required required This identification is denoting the addressed account. The account-id is retrieved by using a "Read Account List" call. The account-id is the "id" attribute of the account structure. Its value is constant at least throughout the lifecycle of a given consent. ID of the request, unique to the call, as determined by the initiating party. The forwarded IP Address header field consists of the corresponding HTTP request IP Address field between PSU and TPP. It must be contained if and only if this request was actively initiated by the PSU. 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. It must be contained if and only if this request was actively initiated by the PSU. This then contains the consentid of the related AIS consent, which was performed prior to this payment initiation. PSU-IP-Port The forwarded IP Port header field consists of the corresponding HTTP request IP Port field between PSU and TPP, if available.
17 Name Description PSU-Accept The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available. PSU- Accept- Charset PSU- Accept- Encoding PSU- Accept- Language PSU-User- Agent The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available. The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available. The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available. The forwarded Agent header field of the HTTP request between PSU and TPP, if available.
18 Name Description PSU-Http- Method HTTP method used at the PSU? TPP interface, if available. Valid values are: GET POST PUT PATCH DELETE Available values : GET, POST, PUT, PATCH, DELETE PSU-Geo- Location The forwarded Geo Location of the corresponding http request between PSU and TPP if available. Responses Code Description Links 200 OK No links application/json Controls Accept header. Example Value Schema accountdetails SMBC will give the following for account reference identifiers: iban bban bic entity currency
19 Code Description Customers will multiple accounts may use the same IBAN for all their Links accounts. Therefore when referencing an account using the iban identifier, it must be accompanied with its currency code. resourceid The account may be addressed by the resourceid on the /accounts/account-id endpoint. iban iban pattern: [A-Z]2,2[0-9]2,2[a-zA-Z0-9]1,30 example: FR IBAN of an account bban bban pattern: [a-za-z0-9]1,30 example: BARC Basic Bank Account Number (BBAN) Identifier This data element can be used in the body of the Consent Request Message for retrieving Account access Consent from this Account. This data elements is used for payment Accounts which have no IBAN. ISO20022: Basic Bank Account Number (BBAN). Identifier used nationally by financial institutions, i.e., in individual countries, generally as part of a National Account Numbering Scheme(s), which uniquely identifies the account of a customer. currency* currencycode pattern: [A-Z]3 example: EUR ISO 4217 Alpha 3 currency code name maxlength: 35 Name of the account given by the bank or the PSU in online-banking. bic bicfi pattern: [A-Z]6,6[A-Z2-9][A-NP-Z0-9]([A-Z0-9]3,3)0,1 example: AAAADEBBXXX BICFI entity entity maxlength: 35 Title of the account holder, given by the bank in online banking. balances balancelist [ A list of balances regarding this account, e.g. the current balance,
20 the last booked balance. The list might be restricted to the current Code Description balance. Links balance A single balance element balanceamount* amount currency* amount* currencycode pattern: [A-Z] 3 example: EUR ISO 4217 Alpha 3 currency code amountvalue pattern: -?[0-9] 1,14(\.[0-9] 1,3)? example: The amount given with fractional digits, where fractions must be compliant to the currency definition. Up to 14 significant figures. Negative amounts are signed by minus. The decimal separator is a dot. Example: Valid representations for EUR with up to two decimals are:
21 Code Description Links balancetype* balancetype The following balance types are defined: Enum: "closingbooked": Balance of the account at the end of the pre-agreed account reporting period. It is the sum of the opening booked balance at the beginning of the period and all entries booked to the account during the pre-agreed account reporting period. "openingbooked": Book balance of the account at the beginning of the account reporting period. It always equals the closing book balance from the previous report. "interimavailable": Available balance calculated in the course of the account servicer's business day, at the time specified, and subject to further changes during the business day. The interim balance is calculated on the basis of booked credit and debit items during the calculation time/period specified. "interimbooked": Booked balance calculated at the time specified, and subject to further changes during the business day. The interim balance is calculated on the basis of booked credit and debit items during the calculation time/period specified. referencedate [ interimavailable, closingbooked, openingbooked, interimbooked ] ($date) Reference date of the balance _links ] _linksaccountdetails
22 Code Description Links to the account, which can be directly used for retrieving account Links information from this dedicated account. Links to "balances" and/or "transactions" These links are only supported, when the corresponding consent has been already granted. balances hreftype example: /v1/payments/sepa-credittransfers/1234-wertiq-983 Link to a resource transactions hreftype example: /v1/payments/sepa-credittransfers/1234-wertiq-983 Link to a resource X-Request-ID ID of the request, unique to the call, as determined by the initiating party. Date Current time in UTC datetime
23 Code Description Links 400 Bad Request No links application/json Example Value Schema Error400_AIS_SMBC Error definition for additional SMBC validation. error* MessageCode400_AIS_SMBC Error attribute defining the type of error encountered. Enum: error_description* [ invalid_request, invalid_client ] ($uri) maxlength: 70 A description of the cause of the error, e.g. a mandatory request header is missing. X-Request-ID ID of the request, unique to the call, as determined by the initiating party.
24 Code Description Links 401 Unauthorized No links application/problem+json Example Value Schema Error401_AIS type* Standardised definition of reporting error information according to [RFC7807] in case of a HTTP error code 401 for AIS. ($uri) maxlength: 70 A NextGenPSD2 URI reference [RFC3986] that identifies the problem type. code* MessageCode401_AIS Message codes defined for AIS for HTTP Error code 401 (UNAUTHORIZED). Enum: [ TOKEN_UNKNOWN, TOKEN_INVALID, TOKEN_EXPIRED ] X-Request-ID ID of the request, unique to the call, as determined by the initiating party.
25 Code Description Links 404 Not found No links application/problem+json Example Value Schema Error404_AIS type* Standardised definition of reporting error information according to [RFC7807] in case of a HTTP error code 404 for AIS. ($uri) maxlength: 70 A NextGenPSD2 URI reference [RFC3986] that identifies the problem type. code* MessageCode404_AIS Message codes defined for AIS for HTTP Error code 404 (NOT FOUND). Enum: [ RESOURCE_UNKNOWN ] X-Request-ID ID of the request, unique to the call, as determined by the initiating party.
26 Code Description Links 405 Method Not Allowed No links application/problem+json Example Value Schema Error405_AIS type* Standardised definition of reporting error information according to [RFC7807] in case of a HTTP error code 405 for AIS. ($uri) maxlength: 70 A NextGenPSD2 URI reference [RFC3986] that identifies the problem type. code* MessageCode405_AIS Message codes defined for AIS for HTTP Error code 405 (METHOD NOT ALLOWED). Enum: [ SERVICE_INVALID ] X-Request-ID ID of the request, unique to the call, as determined by the initiating party.
27 Code Description Links 429 Too Many Requests No links X-Request-ID ID of the request, unique to the call, as determined by the initiating party. 500 Internal Server Error No links X-Request-ID ID of the request, unique to the call, as determined by the initiating party. 503 Service Unavailable No links X-Request-ID ID of the request, unique to the call, as determined by the initiating party. GET /berlingroup/v1/accounts/account-id/balances Read Balance Reads account data from a given account addressed by "account-id". Remark: This account-id can be a tokenised identification due to data protection reason since the path information might be logged on intermediary servers within the ASPSP sphere. This account-id then can be retrieved by the "GET Account List" call. The account-id is constant at least throughout the lifecycle of a given consent.
28 Parameters Try it out Name Description accountid * (path) X-Requestrequired ID * Consent- ID * PSU-IP- Address PSU- Device-ID required required This identification is denoting the addressed account. The account-id is retrieved by using a "Read Account List" call. The account-id is the "id" attribute of the account structure. Its value is constant at least throughout the lifecycle of a given consent. ID of the request, unique to the call, as determined by the initiating party. This then contains the consentid of the related AIS consent, which was performed prior to this payment initiation. The forwarded IP Address header field consists of the corresponding HTTP request IP Address field between PSU and TPP. It must be contained if and only if this request was actively initiated by the PSU. 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. It must be contained if and only if this request was actively initiated by the PSU. PSU-IP-Port The forwarded IP Port header field consists of the corresponding HTTP request IP Port field between PSU and TPP, if available.
29 Name Description PSU-Accept The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available. PSU- Accept- Charset PSU- Accept- Encoding PSU- Accept- Language PSU-User- Agent The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available. The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available. The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available. The forwarded Agent header field of the HTTP request between PSU and TPP, if available.
30 Name Description PSU-Http- Method HTTP method used at the PSU? TPP interface, if available. Valid values are: GET POST PUT PATCH DELETE Available values : GET, POST, PUT, PATCH, DELETE PSU-Geo- Location The forwarded Geo Location of the corresponding http request between PSU and TPP if available. Responses Code Description Links 200 OK No links application/json Controls Accept header. Example Value Schema readaccountbalanceresponse-200 Body of the response for a successful read balance for an account request. account accountreference Reference to an account using:
31 iban Code Description bban bic Links entity currency iban iban pattern: [A-Z]2,2[0-9]2,2[a-zA-Z0-9] 1,30 example: FR IBAN of an account bban bban pattern: [a-za-z0-9]1,30 example: BARC Basic Bank Account Number (BBAN) Identifier This data element can be used in the body of the Consent Request Message for retrieving Account access Consent from this Account. This data elements is used for payment Accounts which have no IBAN. ISO20022: Basic Bank Account Number (BBAN). Identifier used nationally by financial institutions, i.e., in individual countries, generally as part of a National Account Numbering Scheme(s), which uniquely identifies the account of a customer. currency currencycode pattern: [A-Z]3 example: EUR ISO 4217 Alpha 3 currency code entity entity maxlength: 35 Title of the account holder, given by the bank in online banking. bic bicfi pattern: [A-Z]6,6[A-Z2-9][A-NP-Z0-9]([A- Z0-9]3,3)0,1 example: AAAADEBBXXX BICFI
32 Example: Valid representations for EUR with up to two decimals are: Code Description Links balances* balancelist [ A list of balances regarding this account, e.g. the current balance, the last booked balance. The list might be restricted to the current balance. balance balanceamount* A single balance element amount currency* amount* currencycode pattern: [A-Z] 3 example: EUR ISO 4217 Alpha 3 currency code amountvalue pattern: -?[0-9] 1,14(\.[0-9] 1,3)? example: The amount given with fractional digits, where fractions must be compliant to the currency definition. Up to 14 significant figures. Negative amounts are signed by minus. The decimal separator is a dot.
33 Code Description Links balancetype* balancetype The following balance types are defined: Enum: "closingbooked": Balance of the account at the end of the pre-agreed account reporting period. It is the sum of the opening booked balance at the beginning of the period and all entries booked to the account during the pre-agreed account reporting period. "openingbooked": Book balance of the account at the beginning of the account reporting period. It always equals the closing book balance from the previous report. "interimavailable": Available balance calculated in the course of the account servicer's business day, at the time specified, and subject to further changes during the business day. The interim balance is calculated on the basis of booked credit and debit items during the calculation time/period specified. "interimbooked": Booked balance calculated at the time specified, and subject to further changes during the business day. The interim balance is calculated on the basis of booked credit and debit items during the calculation time/period specified. referencedate [ interimavailable, closingbooked, openingbooked, interimbooked ] ($date) Reference date of the balance
34 Code Description Links ] X-Request-ID ID of the request, unique to the call, as determined by the initiating party. Date Current time in UTC datetime
35 Code Description Links 400 Bad Request No links application/json Example Value Schema Error400_AIS_SMBC Error definition for additional SMBC validation. error* MessageCode400_AIS_SMBC Error attribute defining the type of error encountered. Enum: error_description* [ invalid_request, invalid_client ] ($uri) maxlength: 70 A description of the cause of the error, e.g. a mandatory request header is missing. X-Request-ID ID of the request, unique to the call, as determined by the initiating party.
36 Code Description Links 401 Unauthorized No links application/problem+json Example Value Schema Error401_AIS type* Standardised definition of reporting error information according to [RFC7807] in case of a HTTP error code 401 for AIS. ($uri) maxlength: 70 A NextGenPSD2 URI reference [RFC3986] that identifies the problem type. code* MessageCode401_AIS Message codes defined for AIS for HTTP Error code 401 (UNAUTHORIZED). Enum: [ TOKEN_UNKNOWN, TOKEN_INVALID, TOKEN_EXPIRED ] X-Request-ID ID of the request, unique to the call, as determined by the initiating party.
37 Code Description Links 404 Not found No links application/problem+json Example Value Schema Error404_AIS type* Standardised definition of reporting error information according to [RFC7807] in case of a HTTP error code 404 for AIS. ($uri) maxlength: 70 A NextGenPSD2 URI reference [RFC3986] that identifies the problem type. code* MessageCode404_AIS Message codes defined for AIS for HTTP Error code 404 (NOT FOUND). Enum: [ RESOURCE_UNKNOWN ] X-Request-ID ID of the request, unique to the call, as determined by the initiating party.
38 Code Description Links 405 Method Not Allowed No links application/problem+json Example Value Schema Error405_AIS type* Standardised definition of reporting error information according to [RFC7807] in case of a HTTP error code 405 for AIS. ($uri) maxlength: 70 A NextGenPSD2 URI reference [RFC3986] that identifies the problem type. code* MessageCode405_AIS Message codes defined for AIS for HTTP Error code 405 (METHOD NOT ALLOWED). Enum: [ SERVICE_INVALID ] X-Request-ID ID of the request, unique to the call, as determined by the initiating party.
39 Code Description Links 429 Too Many Requests No links X-Request-ID ID of the request, unique to the call, as determined by the initiating party. 500 Internal Server Error No links X-Request-ID ID of the request, unique to the call, as determined by the initiating party. 503 Service Unavailable No links X-Request-ID ID of the request, unique to the call, as determined by the initiating party. GET /berlingroup/v1/accounts/account-id/transactions Read transaction list of an account Read transaction reports or transaction lists of booked transactions for a given account addressed by "account-id". A maximum of 50 records will be returned accompanied with a "next" link to retrieve further records, sorted in descending order by booking datetime. Optional query parameters "datefrom" and "dateto" may be given to request a period of up to 90 days between today and 730 days ago.
40 Optional query parameter "entryreferencefrom" may be given to request transactions starting with the transaction addressed by "entryreferencefrom" and up to 50 previous transactions. Remark: openingbooked balance will always be returned if the consent includes access to balances. Remark: If dateto is today and the consent includes access to balances, interimavailable and interimbooked balances will be returned otherwise closingbooked balance will be returned. Remark: if datefrom and dateto are not given, only transaction booked today will be returned. Parameters Try it out Name Description account-id * (path) datefrom (query) dateto (query) entryreferencefrom (query) required This identification is denoting the addressed account. The account-id is retrieved by using a "Read Account List" call. The account-id is the "id" attribute of the account structure. Its value is constant at least throughout the lifecycle of a given consent. Conditional: Starting date (inclusive the date datefrom) of the transaction list, mandated if no delta access is required. For booked transactions, the relevant date is the booking date. For pending transactions, the relevant date is the entry date, which may not be transparent neither in this API nor other channels of the ASPSP. End date (inclusive the data dateto) of the transaction list, default is "now" if not given. This data attribute is indicating that the AISP is in favour to get all transactions after the transaction with identification entryreferencefrom alternatively to the above defined period. bookingstatus * required Only "booked" is permitted. Available values : booked (query)
41 Name Description X-Request-ID * Consent-ID * PSU-IP-Address PSU-Device-ID PSU-IP-Port PSU-Accept PSU-Accept-Charset PSU-Accept-Encoding required required ID of the request, unique to the call, as determined by the initiating party. This then contains the consentid of the related AIS consent, which was performed prior to this payment initiation. The forwarded IP Address header field consists of the corresponding HTTP request IP Address field between PSU and TPP. It must be contained if and only if this request was actively initiated by the PSU. 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. It must be contained if and only if this request was actively initiated by the PSU. The forwarded IP Port header field consists of the corresponding HTTP request IP Port field between PSU and TPP, if available. The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available. The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available. The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available.
42 Name Description PSU-Accept-Language PSU-User-Agent PSU-Http-Method The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available. The forwarded Agent header field of the HTTP request between PSU and TPP, if available. HTTP method used at the PSU? TPP interface, if available. Valid values are: GET POST PUT PATCH DELETE Available values : GET, POST, PUT, PATCH, DELETE PSU-Geo-Location The forwarded Geo Location of the corresponding http request between PSU and TPP if available. Responses Code Description 200 OK application/json Controls Accept header. Example Value Schema
43 Code Description transactionsresponse-200_json Body of the JSON response for a successful read transaction list request. This account report contains transactions resulting from the query parameters. account accountreference Reference to an account using: iban bban bic entity currency iban iban pattern: [A-Z]2,2[0-9]2,2[a-zA-Z0-9]1,30 example: FR IBAN of an account bban bban pattern: [a-za-z0-9]1,30 example: BARC Basic Bank Account Number (BBAN) Identifier This data element can be used in the body of the Consent Request Message for retrieving Account access Consent from this Account. This data elements is used for payment Accounts which have no IBAN. ISO20022: Basic Bank Account Number (BBAN). Identifier used nationally by financial institutions, i.e., in individual countries, generally as part of a National Account Numbering Scheme(s), which uniquely identifies the account of a customer. currency currencycode pattern: [A-Z]3 example: EUR ISO 4217 Alpha 3 currency code entity entity maxlength: 35 Title of the account holder, given by the bank in online banking. bic bicfi pattern: [A-Z]6,6[A-Z2-9][A-NP-Z0-9]([A-Z0-9]3,3)0,1 example: AAAADEBBXXX BICFI
44 Code Description transactions accountreport JSON based account report. This account report contains transactions resulting from the query parameters. 'booked' shall be contained if bookingstatus parameter is set to "booked" or "both". booked transactionlist Array of transaction details [ transactiondetails entryreference endtoendid mandateid checkid creditorid Transaction details maxlength: 35 Is the identification of the transaction as used e.g. for reference for the entryreferencefrom query parameter. The same identification as for example used within camt.053 message. maxlength: 35 Unique end to end identity. maxlength: 35 Identification of Mandates, e.g. a SEPA Mandate ID. maxlength: 35 Identification of a Cheque. maxlength: 35 Identification of Creditors, e.g. a SEPA Creditor ID. bookingdate bookingdate ($date) The Date when an entry is posted to an account on the ASPSPs books. valuedate ($date) The Date at which assets become available to the account owner in case of a credit.
45 Code Description transactionamount* amount currency* currencycode pattern: [A-Z] 3 example: EUR ISO 4217 Alpha 3 currency code amount* amountvalue pattern: -?[0-9] 1,14(\.[0-9] 1,3)? example: The amount given with fractional digits, where fractions must be compliant to the currency definition. Up to 14 significant figures. Negative amounts are signed by minus. The decimal separator is a dot. Example: Valid representations for EUR with up to two decimals are: exchangerate exchangeratelist Array of exchange rates [
46 bban bban pattern: [a-za-z0-9]1,30 Code Description exchangerate Exchange Rate sourcecurrency* currencycode pattern: [A-Z] 3 example: EUR ISO 4217 Alpha 3 currency code rate* unitcurrency* targetcurrency* currencycode pattern: [A-Z] 3 example: EUR ISO 4217 Alpha 3 currency code ] creditorname creditorname maxlength: 70 example: Creditor Name Creditor Name creditoraccount accountreference Reference to an account using: iban bban bic entity currency iban iban pattern: [A-Z]2,2[0-9] 2,2[a-zA-Z0-9]1,30 example: FR IBAN of an account
47 Code Description example: BARC Basic Bank Account Number (BBAN) Identifier This data element can be used in the body of the Consent Request Message for retrieving Account access Consent from this Account. This data elements is used for payment Accounts which have no IBAN. ISO20022: Basic Bank Account Number (BBAN). Identifier used nationally by financial institutions, i.e., in individual countries, generally as part of a National Account Numbering Scheme(s), which uniquely identifies the account of a customer. currency currencycode pattern: [A-Z]3 example: EUR ISO 4217 Alpha 3 currency code entity entity maxlength: 35 Title of the account holder, given by the bank in online banking. bic bicfi pattern: [A-Z]6,6[A-Z2-9] [A-NP-Z0-9]([A-Z0-9]3,3) 0,1 example: AAAADEBBXXX BICFI ultimatecreditor ultimatecreditor maxlength: 70 example: Ultimate Creditor
48 Code Description Ultimate Creditor debtorname debtorname maxlength: 70 example: Debtor Name Debtor Name debtoraccount accountreference Reference to an account using: iban bban bic entity currency iban iban pattern: [A-Z]2,2[0-9] 2,2[a-zA-Z0-9]1,30 example: FR IBAN of an account bban bban pattern: [a-za-z0-9]1,30 example: BARC Basic Bank Account Number (BBAN) Identifier This data element can be used in the body of the Consent Request Message for retrieving Account access Consent from this Account. This data elements is used for payment Accounts which have no IBAN. ISO20022: Basic Bank Account Number (BBAN). Identifier used nationally by financial institutions, i.e., in individual countries, generally as part of a National Account Numbering Scheme(s), which uniquely identifies the
49 Code Description account of a customer. currency currencycode pattern: [A-Z]3 example: EUR ISO 4217 Alpha 3 currency code entity entity maxlength: 35 Title of the account holder, given by the bank in online banking. bic bicfi pattern: [A-Z]6,6[A-Z2-9] [A-NP-Z0-9]([A-Z0-9]3,3) 0,1 example: AAAADEBBXXX BICFI ultimatedebtor ultimatedebtor maxlength: 70 example: Ultimate Debtor Ultimate Debtor remittanceinformationunstructured maxlength: 140 remittanceinformationstructured maxlength: 140 Reference as contained in the structured remittance reference structure (without the surrounding XML structure). Different from other places the content is containt in plain form not in form of a structered field. purposecode purposecode ExternalPurpose1Code from ISO Values from ISO External Code List ExternalCodeSets_1Q2018 June Enum: Array [ 286 ] banktransactioncode banktransactioncode
50 amount* amountvalue pattern: -?[0-9]1,14(\.[0-9]1,3)? example: Code Description example: PMNT-RCDT-ESCT Bank transaction code as used by the ASPSP and using the sub elements of this structured code defined by ISO This code type is concatenating the three ISO20022 Codes Domain Code, Family Code, and SubFamiliy Code by hyphens, resulting in DomainCode - FamilyCode - SubFamilyCode. _links* ] _linksaccountreport account* hreftype example: /v1/payments/sepa-credit-transfers/1234- wertiq-983 Link to a resource next hreftype example: /v1/payments/sepa-credit-transfers/1234- wertiq-983 Link to a resource balances balancelist [ A list of balances regarding this account, e.g. the current balance, the last booked balance. The list might be restricted to the current balance. balance balanceamount* A single balance element amount currency* currencycode pattern: [A-Z]3 example: EUR ISO 4217 Alpha 3 currency code
51 Code Description The amount given with fractional digits, where fractions must be compliant to the currency definition. Up to 14 significant figures. Negative amounts are signed by minus. The decimal separator is a dot. Example: Valid representations for EUR with up to two decimals are: balancetype* balancetype The following balance types are defined: "closingbooked": Balance of the account at the end of the preagreed account reporting period. It is the sum of the opening booked balance at the beginning of the period and all entries booked to the account during the pre-agreed account reporting period. "openingbooked": Book balance of the account at the beginning of the account reporting period. It always equals the closing book balance from the previous report. "interimavailable": Available balance calculated in the course of the account servicer's business day, at the time specified, and subject to further changes during the business day. The interim balance is calculated on the basis of booked credit and debit items during the calculation time/period specified. "interimbooked": Booked balance calculated at the time specified, and subject to further changes during the business day. The interim balance is calculated on the basis of booked credit and debit items during the calculation time/period specified. Enum: referencedate [ interimavailable, closingbooked, openingbooked, interimbooked ] ($date) Reference date of the balance ]
52 Code Description X-Request-ID ID of the request, unique to the call, as determined by the initiating party. Date Current time in UTC datetime 400 Bad Request application/json Example Value Schema Error400_AIS_SMBC Error definition for additional SMBC validation. error* MessageCode400_AIS_SMBC Error attribute defining the type of error encountered. Enum: error_description* [ invalid_request, invalid_client ] ($uri) maxlength: 70 A description of the cause of the error, e.g. a mandatory request header is missing. X-Request-ID ID of the request, unique to the call, as determined by the initiating party.
53 Code Description 401 Unauthorized application/problem+json Example Value Schema Error401_AIS type* Standardised definition of reporting error information according to [RFC7807] in case of a HTTP error code 401 for AIS. ($uri) maxlength: 70 A NextGenPSD2 URI reference [RFC3986] that identifies the problem type. code* MessageCode401_AIS Message codes defined for AIS for HTTP Error code 401 (UNAUTHORIZED). Enum: [ TOKEN_UNKNOWN, TOKEN_INVALID, TOKEN_EXPIRED ] X-Request-ID ID of the request, unique to the call, as determined by the initiating party.
54 Code Description 404 Not found application/problem+json Example Value Schema Error404_AIS type* Standardised definition of reporting error information according to [RFC7807] in case of a HTTP error code 404 for AIS. ($uri) maxlength: 70 A NextGenPSD2 URI reference [RFC3986] that identifies the problem type. code* MessageCode404_AIS Message codes defined for AIS for HTTP Error code 404 (NOT FOUND). Enum: [ RESOURCE_UNKNOWN ] X-Request-ID ID of the request, unique to the call, as determined by the initiating party.
55 Code Description 405 Method Not Allowed application/problem+json Example Value Schema Error405_AIS type* Standardised definition of reporting error information according to [RFC7807] in case of a HTTP error code 405 for AIS. ($uri) maxlength: 70 A NextGenPSD2 URI reference [RFC3986] that identifies the problem type. code* MessageCode405_AIS Message codes defined for AIS for HTTP Error code 405 (METHOD NOT ALLOWED). Enum: [ SERVICE_INVALID ] X-Request-ID ID of the request, unique to the call, as determined by the initiating party. 429 Too Many Requests X-Request-ID ID of the request, unique to the call, as determined by the initiating party.
56 Code Description 500 Internal Server Error X-Request-ID ID of the request, unique to the call, as determined by the initiating party. 503 Service Unavailable X-Request-ID ID of the request, unique to the call, as determined by the initiating party. Schemas
Consents Service - SMBC NextGenPSD2
Consents Service - SMBC NextGenPSD2 1.3.SMBC February 2019 Framework (Berlin Group V1.3) Summary OAS3 SMBC offers third party access to accounts (XS2A) in a safe and efficient way using Application Programming
More informationIntroduction. Notations. Test with Curl. Value Examples
Introduction The European Union has published a new directive on payment services in the internal market with PSD2. Among others, PSD2 contains regulations of new services to be operated by Third Party
More informationJoint Initiative on a PSD2 Compliant XS2A Interface. NextGenPSD2 XS2A Framework Errata for Version 1.3
Joint Initiative on a PSD2 Compliant XS2A Interface NextGenPSD2 XS2A Framework Errata for Version 1.3 14 February 2019 License Notice This Specification has been prepared by the Participants of the Joint
More informationJoint Initiative on a PSD2 Compliant XS2A Interface XS2A Interface Interoperability Framework Implementation Guidelines
Joint Initiative on a PSD2 Compliant XS2A Interface XS2A Interface Interoperability Framework Implementation Guidelines 02.10.2017 Notice This Specification has been prepared by the Participants of the
More informationNextGenPSD2 Conference 2017
THE Berlin GROUP A EUROPEAN STANDARDS INITIATIVE NextGenPSD2 Conference 2017 General Approach of the Berlin Group PSD2 API Detlef Hillen, SRC Content 1 Services supported by the XS2A interface Core services
More informationJoint Initiative on a PSD2 Compliant XS2A Interface NextGenPSD2 XS2A Framework Operational Rules
Joint Initiative on a PSD2 Compliant XS2A Interface NextGenPSD2 XS2A Framework Operational Rules 02.10.2017 Notice This Specification has been prepared by the Participants of the Joint Initiative pan-european
More informationSlovak Banking API Standard. Rastislav Hudec, Marcel Laznia
Slovak Banking API Standard. Rastislav Hudec, Marcel Laznia 01. Slovak Banking API Standard: Introduction 1.1 Why did SBA decide to prepare API standard? We knew that from January 13, 2018, banks in Slovakia
More informationFormat Description CAMT and CAMT
Format CAMT.052.001.02 and CAMT.053.001.02 InsideBusiness Connect SwiftNet FileAct EBICS The Netherlands Document version history Version Date Changes 1.0 First version 2.0 14-02-2014 Updated - List of
More informationStrong Customer Authentication and common and secure communication under PSD2. PSD2 in a nutshell
Strong Customer Authentication and common and secure communication under PSD2 PSD2 in a nutshell Summary On August 12, the EBA has issued the long-awaited draft of the Regulatory Technical Standards (RTS)
More informationPSD2 API INTERFACE SPECIFICATION
PSD2 API INTERFACE SPECIFICATION CONTENTS Contents... 2 List of figures... 3 List of tables... 3 Document information... 4 List of acronyms... 5 References... 6 1 Introduction... 7 1.1 Main focus... 7
More informationConsent Model Guidelines
Consent Model Guidelines Part 1: Implementation Open Banking Read/Write API Date: October 2017 Version: v1.0 Classification: PUBLIC OBIE PUBLIC CONSENT MODEL GUIDELINES Page 1 of 25 Contents 1 Introduction
More informationOpen Banking Consent Model Guidelines. Part 1: Implementation
Open Banking Consent Model Guidelines Part 1: Implementation Open Banking Read/Write API October 2017 Contents 1 Introduction 3 2 Open Banking Consent Model - Consent, Authentication and Authorisation
More informationSEPA Credit Transfer Customer-to-Bank Implementation Guidelines for the Netherlands
SEPA Credit Transfer Customer-to-Bank Implementation Guidelines for the Netherlands Disclaimer These guidelines may be subject to changes. Utmost care has been taken to ensure the information in this publication
More informationISO TRANSACTION REPORTING GUIDE. v 1.3
ISO 20022 TRANSACTION REPORTING GUIDE v 1.3 4.10.2012 1 ISO 20022 Transaction Reporting Guide Table of contents 1 Introduction... 2 2 General... 2 3 Notification message structure... 3 3.1 Group Header
More informationING Format Description MT940 & MT942 Structured NL (V.4)
ING Format MT940 & MT942 Structured NL (V.4) InsideBusiness Connect SwiftNet FIN SwiftNet FileAct EBICS The Netherlands Document version history Version Date Changes 1.0 20-11-2013 First version 2.0 14-02-2014
More informationING Format Description
ING Format Structured MT940 & MT942 (Version 4) Strategic InsideBusiness Connect InsideBusiness Payments CEE SwiftNet FIN SwiftNet FileAct Telelink@Isabel EBICS Document version history Version Date Changes
More informationSEPA CREDIT TRANSFER SCHEME IMPLEMENTATION GUIDELINES
Doc: EPC115_06 13 December 2006 (Version 2.2) OITS SG SEPA CREDIT TRANSFER SCHEME IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the SEPA rules for implementing the
More informationSEPA Direct Debit Initiation Danske Bank's interpretation of ISO pain (Direct Debit Initiation)
SEPA Direct Debit Initiation Danske Bank's interpretation of ISO 20022 pain.008.001.02 (Direct Debit Initiation) Table of Contents Introduction File layout Description Group Header Payment Information
More informationcamt Account Statement BankToCustomerStatementV02
Corporate Access Account eporting Message Implementation Guidelines BankToCustomerStatementV02 MIG version: 1.00 : Corporate Access Account eporting version 1.0 2 of 10 Table of contents 1. Introduction...
More informationcamt BankToCustomerStatementV02
Corporate egateway Message Implementation Guideline camt.053.001.02 BankToCustomerStatementV02 MIG version: 1.4 : 2018.11.26 2 of 10 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Document references...
More informationcamt BankToCustomerStatementV02
Corporate egateway Message Implementation Guideline camt.053.001.02 BankToCustomerStatementV02 MIG version: 1.2 : 16-12-2013 2 of 7 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Document references...
More informationISO CustomerPaymentStatusReport Confirmation of Receipt
ISO 20022 CustomerPaymentStatusReport Confirmation of Receipt pain.002 version 3 Version 1.0.1 Publishing date 21 December 2012 Table of contents 1 INTRODUCTION... 3 1.1 Related documents... 3 1.2 History...
More informationAddendum on the XML message for SEPA Credit Transfer Initiation (PAIN)
Addendum on the XML message for SEPA Credit Transfer Initiation (PAIN) 201 Version 1.0 - August 201 2 Table of content 1. Introduction 3 1.1 Related documents 1.2 Character Set 1.3 Change history 1.4 Summary
More informationINTRODUCTION TO THE ISO AFT USAGE GUIDELINES
INTRODUCTION TO THE ISO 20022 AFT USAGE GUIDELINES INTRODUCTION 1.0 Scope This document outlines the specifications related to the formatting of CPA ISO 20022 Automated Funds Transfer (AFT) payment messages
More informationSEPA Credit Transfer Unpaid Report File Format
SEPA Credit Transfer Unpaid Report File Format PAIN.002.001.03 XML File Structure V 1.2 This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland.
More informationPartner Web Services. GetOrderStatus Version 1 Service Manual
Partner Web Services GetOrderStatus Version 1 Service Manual Contents 1 Introduction... 4 1.1 Overview... 4 1.2 Supporting Resources... 4 2 Service Overview... 4 3 Service Endpoints... 5 4 Request/Response
More informationSTET PSD2 API. Documentation. Author: Robache Hervé. Date: Version: (English)
STET PSD2 API Documentation Author: Robache Hervé Date: 2017-11-15 Version: 1.2.3 (English) Table of content 1. INTRODUCTION... 7 1.1. Context... 7 1.2. Mission... 7 1.3. Licence... 8 2. BUSINESS MODEL...
More informationRequests that are forwarded via redirects by a customer's web browser are authenticated via browser API authentication.
Poplatek Server API Version: 2016-06-22.2 Quick links Browser API Pay REST API Get Transaction Status Cancel Refund Settlement report Changes 2016-06-22: Document sandbox URL endpoints. Small miscellaneous
More informationING Format Description Transaction Details Camt InsideBusiness Connect InsideBusiness Payments SwiftNet FileAct EBICS
ING Format Transaction Details Camt.054.001.02 InsideBusiness Connect InsideBusiness Payments SwiftNet FileAct EBICS Document version history Version Date Changes 1.0 01-11-2016 First version 1.1 15-12-2016
More informationSWIFT FIN MT103. Format Description
SWIFT FIN MT103 Format Description June 2018 Contents 1. SWIFT FIN MT103: SINGLE CUSTOMER CREDIT TRANSFER 3 1.1 Introduction 3 1.2 General information 3 1.3 Format Specification 3 2. TECHNICAL DESCRIPTION
More informationOracle FLEXCUBE Direct Banking
Oracle FLEXCUBE Direct Banking Corporate Transfer and Payment User Manual Release 12.0.3.0.0 Part No. E52543-01 April 2014 Corporate Transfer and Payment User Manual April 2014 Oracle Financial Services
More informationRecord Descriptions - lang
Record s - lang Online Banking 01-02-2018 1 Indholdsfortegnelse Introduction... 4 Bankdata format... 4 of fixed-length records... 6 Data name Field name.... 6 of variable-length records... 7 Payment start...
More information{ Slovak Banking API Standard }
{ Slovak Banking API Standard } Version: 1.0 Bratislava, 20.11. 2017 1. License Slovak banking association grants to users of Slovak banking API standard a non-exclusive, royalty free, worldwide copyright
More informationUlster Bank SEPA Direct Debit Origination Collection Processing Report CPR XML Guide
Ulster Bank SEPA Direct Debit Origination Collection Processing Report CPR XML Guide Version 1.2 May 2016 These documents are strictly for illustrative purposes. Customers should not rely solely on the
More informationXML account report CAMT Service description April 2013
XML account report CAMT.052.001.02 Service description April 2013 Content 1 Purpose of the document... 2 2 Account report as an XML file... 2 2.1 Downloading of files... 2 3 Technical information... 2
More informationAPI Documentation. Release Version 1 Beta
API Documentation Release Version 1 Beta Document Version Control Version Date Updated Comment 0.1 April 1, 2016 Initialize document 1 Release version PROMOTEXTER V3 BETA - API Documentation 1 Table of
More informationSEPA DIRECT DEBIT SCHEME IMPLEMENTATION GUIDELINES
Doc: EPC114-06 13 December 2006 (Version 2.2) OITS SG SEPA DIRECT DEBIT SCHEME IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the SEPA rules for implementing the direct
More informationFormat Description MT940 Structured version 1.0. Rabo Direct Connect, SWIFT FileAct and Rabo Internetbanking (Professional)
Format Description MT940 Structured version 1.0 Rabo Direct Connect, SWIFT FileAct and Rabo Internetbanking (Professional) January 2018 Contents 1. MT940 CUSTOMER STATEMENT MESSAGE 3 1.1 General information
More informationSberbank Online User Guide
Sberbank Online User Guide Contents 1. Introduction... 2 1.1 Available services... 2 1.2 Security... 2 2. First use... 3 2.1 Login... 3 2.2 Password change... 3 2.3 PIN change... 5 2.3 User profile...
More informationEPC e-mandates e-operating Model. Detailed Specification
Doc: EPC208-08 9 April 2013 Version 1.2 Approved EPC EPC e-mandates e-operating Model Detailed Specification Abstract Document Reference Issue This is the Detailed Specification for the development of
More informationBankline Internet Banking Export File Layout User Guide
Bankline Internet Banking Export File Layout User Guide Bankline Internet Banking Export File Layout User Guide 2 Contents 1. Introduction to Bankline export... 3 1.1 What is Bankline export?... 3 1.2
More informationFIDO & PSD2. Providing for a satisfactory customer journey. April, Copyright 2018 FIDO Alliance All Rights Reserved.
FIDO & PSD2 Providing for a satisfactory customer journey April, 2018 Copyright 2018 FIDO Alliance All Rights Reserved. 1 Introduction When PSD2 is deployed in Europe, users will be able to take advantage
More informationFormat Description MT942 Structured version Rabo Direct Connect, SWIFT FileAct & Rabo Internetbankieren (Professional)
Format Description MT942 Structured version 1.0.1 Rabo Direct Connect, SWIFT FileAct & Rabo Internetbankieren (Professional) Contents 1. MT942 STRUCTURED INTERIM TRANSACTION REPORT 3 1.1 General information
More informationRequest for exemption from the obligation to set up a contingency mechanism (SUP 15C Annex 1D)
Request for exemption from the obligation to set up a contingency mechanism (SUP 15C Annex 1D) Interface name / ID (ASPSPs submitting a return should provide the name or ID used within the PSP to identify
More informationThe potential of SEPA Credit Transfer implementation in Croatia
The potential of SEPA Credit Transfer implementation in Croatia M. Ptiček *, B. Vrdoljak *, L. Humski *, Z. Skočir *, G. Bolanča ** and Ž. Gašparić ** * University of Zagreb, Faculty of Electrical Engineering
More informationETSI GS MEC 016 V1.1.1 ( )
GS MEC 016 V1.1.1 (2017-09) GROUP SPECIFICATION Mobile Edge Computing (MEC); UE application interface Disclaimer The present document has been produced and approved by the Mobile Edge Computing (MEC) Industry
More informationCredit Transfer. PAIN XML File Structure V 1.2
Credit Transfer PAIN.001.001.03 XML File Structure V 1.2 This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland. This document may not be reproduced
More informationFormat description CSV (csv-extension) Rabo Internetbanking (Professional)
Format description CSV (csv-extension) Rabo Internetbanking (Professional) Contents 1 CSV Exportformat 3 1.1 General description 3 1.2 Characteristics 3 1.3 Cancellation format Tekst file Comma Separated
More informationBANKING CIRCLE WEB BULK UPLOAD
18109 Training Manual - BULK UPLOAD_Layout 1 11/05/2016 10:06 Page 1 Freedom to BANKING CIRCLE WEB BULK UPLOAD SAXO PAYMENTS INTERNET BANKING WHAT IS A BULK PAYMENT? A bulk payment is defined as a payment
More information[MS-ADFSOAL]: Active Directory Federation Services OAuth Authorization Code Lookup Protocol
[MS-ADFSOAL]: Active Directory Federation Services OAuth Authorization Code Lookup Protocol Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft
More informationE POSTBUSINESS API Login-API Reference. Version 1.1
E POSTBUSINESS API Login-API Reference Imprint Software and documentation are protected by copyright and may not be copied, reproduced, stored, translated, or otherwise reproduced without the written approval
More informationSEPA Direct Debit Initiation Danske Bank's interpretation of ISO pain (Direct Debit Initiation)
SEPA Direct Debit Initiation Danske Bank's interpretation of ISO 20022 pain.008.001.02 (Direct Debit Initiation) Table of Contents Introduction File layout Description Group Header Payment Information
More informationSEPA Credit Transfer Conversion Service:
SEPA Credit Transfer Conversion Service: Standard 18 File Specification Winbits This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland. This document
More informationManual IBANC Software - Version 3.0.0
Manual IBANC Software - Version 3.0.0 XEU.com B.V. IBANC software is a software product that allows you to create credit transfer and direct debit batches easily and exibly that conform to the new SEPA
More informationUBS Implementation Guidelines
UBS Implementation Guidelines DFÜ Agreement of Deutsche Kreditwirtschaft for Cash Management Reports camt.052.001.02 - DK Version 3.0 UBS Version 1.0 March 2017 Table of Contents 1. Cash Management Reports
More informationTECHNICAL SPECIFICATIONS FOR THE PROCESSING OF SEPA CREDIT TRANSFER ORDERS AND SEPA PAYMENT RETURN ORDERS
Appendix 1.1 TECHNICAL SPECIFICATIONS FOR THE PROCESSING OF SEPA CREDIT TRANSFER ORDERS AND SEPA PAYMENT RETURN ORDERS 1 GENERAL PROVISIONS 1.1 Each participant shall pass a series of tests to prove its
More informationConfirminet Comprehensive Payment Management
Confirminet Comprehensive Payment Management Madrid February 2016 CONFIRMINET FILE FORMAT The entry format for the Comprehensive Payment Management Product is assimilable to the Transfer standards format,
More informationFormat description MT940 Structured version Rabo Direct Connect, SWIFT FileAct & Rabo Internetbankieren (Professional)
Format description MT940 Structured version 1.0.2 Rabo Direct Connect, SWIFT FileAct & Rabo Internetbankieren (Professional) Contents 1. MT940 CUSTOMER STATEMENT MESSAGE 3 1.1 General information 3 1.2
More informationFINSTA. Financial statement of an account message. Edition 2008
EANCOM 2002 S3 Financial statement of an account message Edition 2008 1. Introduction... 2 2. Message Structure Chart... 4 3. Branching Diagram... 5 4. Segments... 8... 10 6. Example(s)... 32 EANCOM 2002
More informationPAYMENTADMIN API 1.1 SveaWebPay
PAYMENTADMIN API 1.1 SveaWebPay 2 (22) PaymentAdmin API 1.1 Content Revisions... 4 Overview... 5 Testing... 5 Production... 5 Authentication... 6 Get order... 7 Get task... 8 Deliver order... 9 Cancel
More informationUOB Offline Data Input Software (ODIS)
UOB Offline Data Input Software (ODIS) Version 2 Collection User Guide Date: April 2015 TABLE OF CONTENT Page 1 COLLECTION FAST/GIRO... 3 1.1 Summary Listing... 3 1.1.1 Quick Search... 3 1.1.2 Main Menu...
More informationISO Payments. Swiss Implementation Guidelines for Customer-to-Bank Messages for the Swiss Direct Debit Procedure
ISO 20022 Payments Swiss Implementation Guidelines for Customer-to-Bank Messages for the Swiss Direct Debit Procedure Customer Direct Debit Initiation (pain.008) and Customer Payment Status Report (pain.002)
More informationTELIA OPERATOR SERVICE PLATFORM
TELIA OPERATOR SERVICE PLATFORM OMA Authorization REST API Guide Copyright 2017 Aepona Limited, and copyright 2017 Telia All rights reserved by respective owners. Revision: 6.0 Legal Information Legal
More informationvrealize Log Insight Developer Resources
vrealize Log Insight Developer Resources vrealize Log Insight 4.3 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new
More informationvrealize Log Insight Developer Resources Update 1 Modified on 03 SEP 2017 vrealize Log Insight 4.0
vrealize Log Insight Developer Resources Update 1 Modified on 03 SEP 2017 vrealize Log Insight 4.0 You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/
More informationOracle FLEXCUBE Direct Banking
Oracle FLEXCUBE Direct Banking Retail Transfer and User Manual Release 12.0.2.0.0 Part No. E50108-01 September 2013 Retail Tranfer and User Manual September 2013 Oracle Financial Services Software Limited
More informationSantander Online Corporate Banking. September BAI2 Record Field Ref
Santander Online Corporate Banking September 2013 BAI2 Record Field Ref Field Name Field Tag Field value File Header Record 1-2 Record Code X(02) 2n (01) 3 Filler X(01) comma (,) 4-10 Sender Id X(07) 7n
More informationIsabel 6 Guide #3. How to encode SEPA and Non-SEPA transactions from an ING account from region 3 & all other banks?
Isabel 6 Guide #3 How to encode SEPA and Non-SEPA transactions from an ING account from region 3 & all other banks? Version 2.1 06-11-2013 Purpose This document describes how to use the Isabel 6 Payment
More informationCASH WITHDRAWAL. User manual
CASH WITHDRAWAL User manual CONTENT Content... 2 1 Introduction... 3 1.1 Overview... 3 1.2 About Cash Withdrawal... 3 1.3 Using this manual... 3 2 How to Access the application... 4 2.1 Credentials and
More informationUsage of "OAuth2" policy action in CentraSite and Mediator
Usage of "OAuth2" policy action in CentraSite and Mediator Introduction Prerequisite Configurations Mediator Configurations watt.server.auth.skipformediator The pg.oauth2 Parameters Asset Creation and
More informationInland Revenue. Build Pack. Identity and Access Services. Date: 04/09/2017 Version: 1.5 IN CONFIDENCE
Inland Revenue Build Pack Identity and Access Services Date: 04/09/2017 Version: 1.5 IN CONFIDENCE About this Document This document is intended to provide Service Providers with the technical detail required
More informationDIGITAL SERVICES. API Documentation Retrieve Transactions
DIGITAL SERVICES API Documentation Retrieve Transactions Document Version Reason for change Author Signed-off by Status 0.12 Creation Gary Inkpen Final Draft 2016 Avios Group (AGL) Limited. All rights
More informationING Format Description
ING Format CAMT.052.001.02 and CAMT.053.001.02 InsideBusiness Connect InsideBusiness Payments SwiftNet FileAct EBICS Document version history Version Date Changes 1.0 First version 2.0 14-02-2014 Updated
More informationStop Cheque Request API Specification Document
Stop Request API Specification Document Table of Contents 1. INTRODUCTION 2. LIST OF API 3. API NAME 4. DESCRIPTION 5. TRANSPORT PROTOCOL (SOAP / REST) 6. API REQUEST URLS 7. ACCESS REQUIREMENT 8. REQUEST
More informationSWIFT gpi How payment market infrastructures can support gpi payments
How payment market infrastructures can support gpi payments SWIFT gpi an introduction 3 The role of payment market infrastructures in gpi payments 4 Sending a payment over a local payment market infrastructure
More informationHAL E-BANK MANUAL ADDITIONAL TOOLS AND SETTINGS. Hal E-Bank version: 20.X.X.01
HAL E-BANK MANUAL ADDITIONAL TOOLS AND SETTINGS Hal E-Bank version: 20.X.X.01 Content of Manual The manual consists of several content sections. The current section is highlighted on the list. The manual's
More informationRCB Remote Banking Services. User Guide
RCB Remote Banking Services User Guide Contents 1. Introduction 2. First login and customer registration to RCB Remote Banking Services 2.1. Registration to RCB Online Banking 3. User login to RCB Online
More informationVersion Event Protect Platform RESTfull API call
Event Protect Platform RESTfull API call Introduction Via available online service and through specified API, developers can connect to Event Protect platform and submit individual sales transaction. Service
More informationUsing OAuth 2.0 to Access ionbiz APIs
Using OAuth 2.0 to Access ionbiz APIs ionbiz APIs use the OAuth 2.0 protocol for authentication and authorization. ionbiz supports common OAuth 2.0 scenarios such as those for web server, installed, and
More informationK&H web Electra and web Electra+ user manual
K&H web Electra and web Electra+ user manual 27.11.2017. 1 TABLE OF CONTENTS Introduction... 6 1. Computer environment, security information... 7 1.1 General information... 7 1.2 Managing the Electra access
More informationBankline export file layout guide Bankline (CSV) format
Bankline export file layout guide Bankline (CSV) format Contents 1. Introduction to Bankline export...2 1.1 What is Bankline export?...2 1.2 How are Bankline export files structured?...2 2. Export files...3
More informationFormat Description MT940 Structured version 1.1. Rabo Direct Connect, SWIFT FileAct and Rabo Internetbanking (Professional)
Format Description MT940 Structured version 1.1 Rabo Direct Connect, SWIFT FileAct and Rabo Internetbanking (Professional) May 2018 Contents 1. MT940 CUSTOMER STATEMENT MESSAGE 3 1.1 General information
More information[MS-ADFSOAL]: Active Directory Federation Services OAuth Authorization Code Lookup Protocol
[MS-ADFSOAL]: Active Directory Federation Services OAuth Authorization Code Lookup Protocol Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft
More informationANZ TRANSACTIVE GLOBAL REPORTING USER GUIDE
ANZ TRANSACTIVE GLOBAL REPORTING USER GUIDE November 2016 CONTENTS Introduction 3 Reporting 4 Net Position... 6 Operating Accounts... 8 Transaction Search... 17 Nostro Accounts... 21 Nostro Accounts Search...
More informationIsi Net User Manual for Bank customers
1 Table of Contents 1 Introduction and overview... 4 1.1 Isi Net User Types... 4 1.2 Accessing the Isi Net service... 5 1.2.1 User Login... 5 1.2.2 User Logout... 7 1.3 User Interface... 7 1.3.1 Menus...
More informationISO Payments. Swiss Implementation Guidelines for Customer-Bank Messages Credit Transfer (Payment Transactions)
ISO 20022 Payments for Customer-Bank Messages Credit Transfer (Payment Transactions) Version 1.7 29.05.2017 General note Any suggestions or questions relating to this document should be addressed to the
More informationFawri+ Fawri& Transfer. Mar 2018
Fawri+ Fawri& Transfer Mar 2018 Table of Contents NBB Business Online Banking Initiate Funds Transfer... 3 Initiate Fawri+, Fawri & Remittance... 9 Initiate Bulk Transfer (Batch)... 18 Initiate Bulk Transfer
More informationUser s manual. Payments Module Deferred or multiple signatures
User s manual Payments Module Deferred or multiple signatures Deferred or multiple signatures Selection Deferred or multiple signatures Before commencing transfer creation, you must choose from the list
More informationSwedbank AB (publ) Swedbank Sweden's MIG Credit and Debit Notification (CAMT.054)
Swedbank AB (publ) 2016-02-11 Swedbank Sweden's MIG Credit and Debit Notification (CAMT.054) Introduction This document describes the usage on a set of ISO20022 messages. The main target systems on the
More informationDeutsche Postbank AG. Format Descriptions for Eurogiro Euro Settlement Service ESSP. ESSP Format Descriptions. Page 1.
Deutsche Postbank AG Format Descriptions for Eurogiro Euro Settlement Service ESSP Version, Feb 2009 Deckblatt Format Description Page 1 Contents page Abbreviations... 3 MT202 Settlement Instruction...
More informationNDEV Mobile HTTP Services for NDEV Mobile Clients
NDEV Mobile HTTP Services for NDEV Mobile Clients Notice NDEV Mobile HTTP Services for NDEV Mobile Clients Copyright 2011-2012 Nuance Communications, Inc. All rights reserved. Published by Nuance Communications,
More informationVersion Event Protect Platform RESTfull API call
Event Protect Platform RESTfull API call Introduction Via available online service and through specified API, developers can connect to Event Protect platform and submit individual sales transaction. Service
More informationService Description XML Account Reporting
Service Description XML Account Reporting 6.10.2016 Table of Contents 1 XML account reporting... 3 1.1 General... 3 1.2 XML account reporting services... 3 1.2.1 XML balance query (camt.052)... 3 1.2.2
More informationPayments and Collections Oracle FLEXCUBE Universal Banking Release CN Cluster Oracle Part Number E [January] [2016]
Payments and Collections Oracle FLEXCUBE Universal Banking Release 11.80.02.0.0 CN Cluster Oracle Part Number E64368-01 [January] [2016] Table of Contents Payments and Collections 1. ABOUT THIS MANUAL...
More informationSiebel REST API Guide. Siebel Innovation Pack 2017, Rev. A November 2017
Siebel REST API Guide Siebel Innovation Pack 2017, Rev. A November 2017 Copyright 2005, 2017 Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under
More informationAccess Online. Payment Upload
Access Online Payment Upload ABN AMRO Bank N.V. 2017 All rights reserved. Apart from those exceptions stipulated in or by virtue of the 1912 Copyright Law, no part of this publication may be reproduced
More informationAutorec File Specification
www.aib.ie/sepa Autorec File Specification This document is the property of AIB Group. No official or other user of this document, may, without the prior written permission of the Bank, disseminate the
More informationideal Integration Guide Version 6.2.3
ideal Integration Guide Version 6.2.3 As of: 13.06.2017 Table of Contents About ideal... 4 General information about ideal... 4 Process flow chart... 4 Paygate interface... 5 Definitions... 5 Calling the
More informationANNEX ANNEX. to the COMMISSION IMPLEMENTING REGULATION (EU)
Ref. Ares(2018)1944240-11/04/2018 EUROPEAN COMMISSION Brussels, XXX [ ](2018) XXX draft ANNEX ANNEX to the COMMISSION IMPLEMENTING REGULATION (EU) laying down minimum requirements implementing the provisions
More informationTARGET Instant Payment Settlement
s V0.1.0 Author 4CB Version 0.1.0 Date 27/09/2017 All rights reserved. INTRODUCTION... 6 READER S GUIDE... 7 1. GENERAL FEATURES OF TIPS... 9 1.1. INTRODUCTION TO THE TIPS SERVICE... 9 1.2. ACCESS TO TIPS...
More information