Consents Service - SMBC NextGenPSD2
|
|
- Noah Buddy Pope
- 5 years ago
- Views:
Transcription
1 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 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 Consents This document, based on the NextGenPSD2 YAML, which itself is based on the NextGenPSD2 Implementation Guidelines, defines SMBC's Consents 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 Consents Concents Details POST /berlingroup/v1/consents Create consent This method creates a consent resource, defining access rights to dedicated accounts of a given PSU-ID. SMBC uses the NextGenPSD2 'Bank offered consent' model where the Account access is configured as a pre-step directly between the PSU and SMBC. The Access access for this request is then empty and will be populated by SMBC once SCA is completed. The TPP can then retrieve the Consent Resource to read the Account access. Side Effects If a valid Consent Resource already exists for the TPP for the PSU then it will be expired by this request. Remark: ValidUntil dates beyond 90 days will be amended by SMBC to 90 days. Remark: RecurringIndicator will be ignoredby SMBC and always treated as "true". Remark: CombinedServicesIndicator will be ignoredby SMBC and always treated as "true". Parameters Try it out Name Description X-Requestrequired ID * PSU-ID * required ID of the request, unique to the call, as determined by the initiating party. Client ID of the PSU in the ASPSP client interface. Might be mandated in the ASPSP's documentation. Is not contained if an OAuth2 based authentication was performed in a pre-step or an OAuth2 based SCA was performed in an preceeding AIS service in the same session.
4 Name Description TPP-Redirectrequired URI * PSU-IP- Address * PSU-IP-Port PSU-Accept PSU-Devicerequired ID * PSU-Accept- Charset PSU-Accept- Encoding required URI of the TPP, where the transaction flow shall be redirected to after a Redirect. The forwarded IP Address header field consists of the corresponding http request IP Address field between PSU and TPP. 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 an installation identification this ID need to be unaltered until removal from device. 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.
5 Name Description PSU-Accept- Language The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available. PSU-User-Agent The forwarded Agent header field of the HTTP request between PSU and TPP, if available. 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. Request body application/json Requestbody for a consents request Example Value Schema consents Content of the body of a consent request. access accountaccess Requested access services for a consent.
6 accounts [ Is asking for detailed account information. Should be left empty as the access was agreed as a pre-step between the PSU and SMBC directly. Once authorised SMBC will populate the access and it can be retrieved. 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
7 customer. currency currencycode pattern: [A-Z]3} example: EUR entity entity maxlength: 35 ISO 4217 Alpha 3 currency code 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 balances }] [ Is asking for balances of the addressed accounts. Should be left empty as the access was agreed as a pre-step between the PSU and SMBC directly. Once authorised SMBC will populate the access and it can be retrieved. 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
8 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 entity entity maxlength: 35 ISO 4217 Alpha 3 currency code 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 transactions }] [ Is asking for transactions of the addressed accounts. Should be left empty as the access was agreed as a pre-step between the PSU and SMBC directly. Once authorised SMBC
9 will populate the access and it can be retrieved. 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
10 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 paymentcreations }] [ Is asking for payment creation for the addressed accounts. Should be left empty as the access was agreed as a pre-step between the PSU and SMBC directly. Once authorised SMBC will populate the access and it can be retrieved. 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
11 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 entity entity maxlength: 35 ISO 4217 Alpha 3 currency code 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 paymentauthorisations }] [ Is asking for payment authorisation for the addressed accounts. Should be left empty as the access was agreed as a pre-step between the PSU and SMBC directly. Once authorised SMBC will populate the access and it can be retrieved. accountreference Reference to an account using:
12 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 entity entity maxlength: 35 ISO 4217 Alpha 3 currency code Title of the account holder, given by the bank in online banking.
13 bic bicfi pattern: [A-Z]6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]3,3})0,1} example: AAAADEBBXXX BICFI }] } recurringindicator recurringindicator boolean example: true "true", if the consent is for recurring access to the account data. "false", if the consent is for one access to the account data. validuntil* validuntil ($date) example: This parameter is requesting a valid until date for the requested consent. The content is the local ASPSP date in ISO-Date Format, e.g Future dates might get adjusted by ASPSP. If a maximal available date is requested, a date in far future is to be used: " ". In both cases the consent object to be retrieved by the GET Consent Request will contain the adjusted date. frequencyperday frequencyperday integer example: 4 combinedserviceindicator boolean example: false This field indicates the requested maximum frequency for an access without PSU involvement per day. For a one-off access, this attribute is set to "1". If "true" indicates that a payment initiation service will be addressed in the same "session". }
14 Responses 201 Created application/json Controls Accept header. Example Value Schema consentsresponse-201 Body of the JSON response for a successful conset request. consentstatus* consentstatus example: received This is the overall lifecycle status of the consent. Enum: [ received, rejected, valid, revokedbypsu, expired, terminatedbytpp ] consentid* consentid ID of the corresponding consent object as returned by an Account Information Consent Request. _* _Consents A list of hyper to be recognised by the TPP. documentation): 'scaredirect': In case of an SCA Redirect Approach, the ASPSP is transmitting the link to which to redirect the PSU browser. 'self': The link to the Establish Account Information Consent resource created by this request. This link can be used to retrieve the resource data. 'status': The link to retrieve the status of the account information consent. 'scastatus': The link to retrieve
15 Code Description the scastatus of the corresponding authorisation sub-resource. This link is only contained, if an authorisation sub-resource has been already created. Links scaredirect hreftype example: /v1/payments/sepa-credittransfers/1234-wertiq-983 Link to a resource self hreftype example: /v1/payments/sepa-credittransfers/1234-wertiq-983 Link to a resource status hreftype example: /v1/payments/sepa-credittransfers/1234-wertiq-983 Link to a resource scastatus hreftype example: /v1/payments/sepa-credittransfers/1234-wertiq-983 Link to a resource } } Location Location of the created resource. X-Request-ID ID of the request, unique to the call, as determined by the initiating party. ASPSP-SCA- Approach This data element must be contained, if the SCA Approach is already fixed. Example: EMBEDDED
16 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. }
17 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: [ PSU_CREDENTIALS_INVALID, TOKEN_UNKNOWN, TOKEN_INVALID, TOKEN_EXPIRED ] }
18 405 Method t 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 ] }
19 429 Too Many Requests 500 Internal Server Error 503 Service Unavailable GET /berlingroup/v1/consents/consentid} Get Consent Request Returns the content of an account information consent object. This is returning the data for the TPP especially in cases, where the consent was directly managed between ASPSP and PSU e.g. in a re-direct SCA Approach. Parameters Try it out
20 Name Description consentid * (path) PSU-IP-Address PSU-Device-ID PSU-IP-Port PSU-Accept X-Requestrequired ID * PSU-Accept- Charset required ID of the corresponding consent object as returned by an Account Information Consent Request. 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. 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.
21 Name Description PSU-Accept- Encoding 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 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
22 OK 200 application/json Controls Accept header. Example Value Schema consentinformationresponse-200_json Body of the JSON response for a successfull get consent request. access* accountaccess Requested access services for a consent. accounts [ Is asking for detailed account information. Should be left empty as the access was agreed as a pre-step between the PSU and SMBC directly. Once authorised SMBC will populate the access and it can be retrieved. 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
23 (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 balances }] [ Is asking for balances of the addressed accounts. Should be left empty as the access was
24 agreed as a pre-step between the PSU and Code Description SMBC directly. Once authorised SMBC will Links populate the access and it can be retrieved. 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.
25 Code Description pattern: [A-Z]3} example: EUR ISO 4217 Alpha 3 currency Links 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 transactions }] [ Is asking for transactions of the addressed accounts. Should be left empty as the access was agreed as a pre-step between the PSU and SMBC directly. Once authorised SMBC will populate the access and it can be retrieved. 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
26 Code Description pattern: [a-za-z0-9]1,30} example: BARC Basic Bank Account Number Links (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 paymentcreations }] [
27 Is asking for payment creation for the Code Description addressed accounts. Links Should be left empty as the access was agreed as a pre-step between the PSU and SMBC directly. Once authorised SMBC will populate the access and it can be retrieved. 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
28 Numbering Scheme(s), which Code Description uniquely identifies the Links 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 paymentauthorisations }] [ Is asking for payment authorisation for the addressed accounts. Should be left empty as the access was agreed as a pre-step between the PSU and SMBC directly. Once authorised SMBC will populate the access and it can be retrieved. 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}
29 example: Code Description FR Links 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
30 }] } recurringindicator* recurringindicator boolean example: true "true", if the consent is for recurring access to the account data. "false", if the consent is for one access to the account data. validuntil* validuntil ($date) example: This parameter is requesting a valid until date for the requested consent. The content is the local ASPSP date in ISO-Date Format, e.g Future dates might get adjusted by ASPSP. If a maximal available date is requested, a date in far future is to be used: " ". In both cases the consent object to be retrieved by the GET Consent Request will contain the adjusted date. frequencyperday* frequencyperday integer example: 4 This field indicates the requested maximum frequency for an access without PSU involvement per day. For a one-off access, this attribute is set to "1". lastactiondate* lastactiondate ($date) example: This date is containing the date of the last action on the consent object either through the XS2A interface or the PSU/ASPSP interface having an impact on the status. consentstatus* consentstatus example: received This is the overall lifecycle status of the consent. Enum: [ received, rejected, valid, revokedbypsu, expired, terminatedbytpp ] }
31 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. }
32 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: [ PSU_CREDENTIALS_INVALID, TOKEN_UNKNOWN, TOKEN_INVALID, TOKEN_EXPIRED ] }
33 403 Forbidden application/problem+json Example Value Schema Error403_AIS type* Standardised definition of reporting error information according to [RFC7807] in case of a HTTP error code 403 for AIS. ($uri) maxlength: 70 A NextGenPSD2 URI reference [RFC3986] that identifies the problem type. code* MessageCode403_AIS Message codes defined for AIS for HTTP Error code 403 (FORBIDDEN). Enum: [ CONSENT_UNKNOWN ] }
34 405 Method t 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 ] }
35 429 Too Many Requests 500 Internal Server Error 503 Service Unavailable DELETE /berlingroup/v1/consents/consentid} Delete Consent The TPP can delete an account information consent object if needed. Parameters Try it out
36 Name Description consentid * (path) PSU-IP-Address PSU-Device-ID PSU-IP-Port PSU-Accept X-Requestrequired ID * PSU-Accept- Charset required ID of the corresponding consent object as returned by an Account Information Consent Request. 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. 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.
37 Name Description PSU-Accept- Encoding 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 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
38 204 Content 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. }
39 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: [ PSU_CREDENTIALS_INVALID, TOKEN_UNKNOWN, TOKEN_INVALID, TOKEN_EXPIRED ] }
40 403 Forbidden application/problem+json Example Value Schema Error403_AIS type* Standardised definition of reporting error information according to [RFC7807] in case of a HTTP error code 403 for AIS. ($uri) maxlength: 70 A NextGenPSD2 URI reference [RFC3986] that identifies the problem type. code* MessageCode403_AIS Message codes defined for AIS for HTTP Error code 403 (FORBIDDEN). Enum: [ CONSENT_UNKNOWN ] }
41 405 Method t 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 ] }
42 429 Too Many Requests 500 Internal Server Error 503 Service Unavailable GET /berlingroup/v1/consents/consentid}/status Consent status request Read the status of an account information consent resource. Parameters Try it out
43 Name Description consentid * (path) PSU-IP-Address PSU-Device-ID PSU-IP-Port PSU-Accept X-Requestrequired ID * PSU-Accept- Charset required ID of the corresponding consent object as returned by an Account Information Consent Request. 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. 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.
44 Name Description PSU-Accept- Encoding 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 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
45 OK 200 application/json Controls Accept header. Example Value Schema consentstatusresponse-200 Body of the JSON response for a successful get status request for a consent. consentstatus* consentstatus example: received This is the overall lifecycle status of the consent. Enum: [ received, rejected, valid, revokedbypsu, expired, terminatedbytpp ] scastatus* scastatus example: started This data element is containing information about the status of the SCA method applied. The following codes are defined for this data type. Enum: 'received': An authorisation or cancellation-authorisation resource has been created successfully. 'started': The addressed SCA routine has been started. 'finalised': The SCA routine has been finalised successfully. 'failed': The SCA routine failed [ received, started, finalised, failed ] }
46 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. }
47 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: [ PSU_CREDENTIALS_INVALID, TOKEN_UNKNOWN, TOKEN_INVALID, TOKEN_EXPIRED ] }
48 403 Forbidden application/problem+json Example Value Schema Error403_AIS type* Standardised definition of reporting error information according to [RFC7807] in case of a HTTP error code 403 for AIS. ($uri) maxlength: 70 A NextGenPSD2 URI reference [RFC3986] that identifies the problem type. code* MessageCode403_AIS Message codes defined for AIS for HTTP Error code 403 (FORBIDDEN). Enum: [ CONSENT_UNKNOWN ] }
49 405 Method t 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 ] }
50 429 Too Many Requests 500 Internal Server Error 503 Service Unavailable
51 Schemas
Accounts Service - SMBC NextGenPSD2
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
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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 informationThe production version of your service API must be served over HTTPS.
This document specifies how to implement an API for your service according to the IFTTT Service Protocol. It is recommended that you treat this document as a reference and follow the workflow outlined
More informationOCF Core Specification Extension
OCF Core Specification Extension OCF Cloud VERSION 2.0 March 2018 CONTACT admin@openconnectivity.org Copyright Open Connectivity Foundation, Inc. 2018. All Rights Reserved. 2 3 4 5 6 7 8 9 10 11 12 13
More informationGuide Swish QR Code specification
Version 1.6 Guide Swish QR Code specification Integration Guide Datum: 2017/07/07 Table of content 1 Introduction... 3 2 Payment flows... 3 2.1 Swish C2B flow with QR code... 3 3 Create QR code via getswish.se...
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 informationWriting REST APIs with OpenAPI and Swagger Ada
Writing REST APIs with OpenAPI and Swagger Ada Stéphane Carrez FOSDEM 2018 OpenAPI and Swagger Ada Introduction to OpenAPI and Swagger Writing a REST Ada client Writing a REST Ada server Handling security
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 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 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 informationPSD2/EIDAS DEMONSTRATIONS
PSD2/EIDAS DEMONSTRATIONS Chris Kong, Azadian Kornél Réti, Microsec Luigi Rizzo, InfoCert All rights reserved Overview for this Presentation As previously reported and reviewed at ERPB, with ECB and EC,
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 informationLINK Mobility SMS REST API MT and Delivery Reports Version 1.3; Last updated September 21, 2017
LINK Mobility SMS REST API MT and Delivery Reports Version 1.3; Last updated September 21, 2017 For help, contact support@linkmobility.com The most up-to-date version of this document is available at http://www.linkmobility.com/developers/
More informationLUCITY REST API INTRODUCTION AND CORE CONCEPTS
LUCITY REST API INTRODUCTION AND CORE CONCEPTS REST API OFFERINGS Lucity Citizen Portal REST API Lucity REST API Both products are included in our REST API Historically we also offered a COM API and a.net
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 informationSIP Compliance APPENDIX
APPENDIX E This appendix describes Cisco SIP proxy server (Cisco SPS) compliance with the Internet Engineering Task Force (IETF) definition of Session Initiation Protocol (SIP) as described in the following
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 informationAuthentication (Strong Customer Authentication)
API Evaluation Group Authentication (Strong Customer Authentication) Key topic clarification for API standards initiatives N.B. Views expressed in the document do not necessarily reflect the views of the
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 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 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 informationAPI Integration Guide
API Integration Guide Introduction SULU Mobile Solutions API is a programmable SMS message service. It enables your in-house applications to have fully featured SMS capabilities using your favorite programming
More informationT2S GRAPHICAL USER INTERFACE BUSINESS FUNCTIONALITY
TS GRAPHICAL USER INTERFACE Reference: 0.0.0/0/000 Author: ECB TS Programme Office Date: 0-0-0 Version:. Status: Draft Classification: TABLE OF CONTENTS TS GRAPHICAL USER INTERFACE INTRODUCTION.... Structure
More informationT2S GRAPHICAL USER INTERFACE BUSINESS FUNCTIONALITY
TS GRAPHICAL USER INTERFACE BUSINESS FUNCTIONALITY Reference: 0.0.01/01/00 Author: ECB TS Programme Office Date: 01-0- Version: 1. Status: Draft Classification: Public TS Graphical User Interface TABLE
More informationX-Road Message Protocol for REST
X-Road Message Protocol for REST XRDDEV-121 - As an X-Road user I want that a draft version of X-Road Message Protocol for REST is created so that I know how REST clients and services will communicate
More informationRegistration & Payments User Guide
Registration & Payments User Guide Contingency Payment Access Contents Contingency Payment Access 4 Introduction 4 1. Self-Registration 4 1.1. Password 4 1.2 Client Identification Number and Client Details
More informationOMF Documentation. Release 1.1-alpha1. OSIsoft, LLC
OMF Documentation Release 1.1-alpha1 OSIsoft, LLC Oct 03, 2018 Contents 1 v1.1 1 2 Overview 3 3 Contents 5 3.1 What s New............................................... 5 3.2 Headers..................................................
More informationSalesforce IoT REST API Getting Started Guide
Salesforce IoT REST API Getting Started Guide Version 42.0, Spring 18 @salesforcedocs Last updated: March 9, 2018 Copyright 2000 2018 salesforce.com, inc. All rights reserved. Salesforce is a registered
More informationewallet API integration guide version 5.1 8/31/2015
ewallet API integration guide version 5.1 8/31/2015 International Payout Systems, Inc. (IPS) ewallet API Integration Guide contains information proprietary to IPS, and is intended only to be used in conjunction
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 informationAPI Specification Doc
API Specification Doc (SMS System Gateway) Version Date Description 1.0 01-Nov-2017 Initial draft 1.1 18-Feb-2018 Updated to include Delivery report call back options 1.2 10-Apr-2018 Appended API to include
More informationHPE StoreVirtual REST API Reference Guide
HPE StoreVirtual REST API Reference Guide Abstract This reference guide provides information about the HPE StoreVirtual Storage REST API which can be integrated with the management of applications hosted
More informationPSD2 AND OPEN BANKING SOLUTION GUIDE
PSD2 AND OPEN BANKING SOLUTION GUIDE IMPLEMENTING FINANCIAL-GRADE API SECURITY TABLE OF CONTENTS 03 03 04 08 11 20 21 INTRODUCTION SCOPE OF THE DOCUMENT WHAT IS FINANCIAL-GRADE API SECURITY? TECHNICAL
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 informationNordea e-identification Service description
Nordea e-identification Service description October 2018 1 Change log Version Description/ Changes 1.0 Initial version 1.1 Minor updates to examples & service hours October 2018 2 Contents Change log...
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 informationvrealize Operations Manager API Programming Guide vrealize Operations Manager 6.6
vrealize Operations Manager API Programming Guide vrealize Operations Manager 6.6 vrealize Operations Manager API Programming Guide You can find the most up-to-date technical documentation on the VMware
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 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 informationPartner Web Services. GetMyPrice Service Manual
Partner Web Services GetMyPrice Service Manual Contents 1 Introduction... 5 1.1 Overview... 5 1.2 Supporting Resources... 5 2 Service Overview... 5 2.1 Benefits of GetMyPrice Service... 6 3 Service Endpoints...
More informationReviewing the API Documentation
About the Cisco APIC-EM API Documentation, page 1 Testing the Cisco APIC-EM APIs, page 6 About the Cisco APIC-EM API Documentation Cisco APIC-EM controller provides interactive, northbound Representational
More informationIf the presented credentials are valid server will respond with a success response:
Telema EDI REST API Telema EDI REST API allows client to send and receive document to and from Telema server. In order to use EDI REST API client must have correct channel configured in Telema system.
More informationThe OAuth 2.0 Authorization Protocol
The OAuth 2.0 Authorization Protocol Abstract The OAuth 2.0 authorization protocol enables a third-party application to obtain limited access to an HTTP service, either on behalf of a resource owner by
More informationPayMorrow Integration Guide. Version As of: About PayMorrow: General information about PayMorrow
About PayMorrow: General information about PayMorrow PayMorrow Integration Guide Version 6.2.1 As of: 04.10.2016 Integration Guide Computop PayMorrow 1 About PayMorrow: General information about PayMorrow
More informationScalable applications with HTTP
Scalable applications with HTTP Patrice Neff, co-founder Memonic patrice@memonic.com twitter.com/pneff 20100407 memonic Memonic Founded in 2009 Your personal digital notebook Easy web research Try it out
More informationMediaAUTH Draft Proposal
MediaAUTH Draft Proposal August 21, 2012 Contents 1 Introduction 2 2 Service & User Perspective 2 2.1 Login...................................... 2 2.2 Soft Login.................................... 3
More informationGuideline for support SWIFTNet for Corporates
Guideline for support SWIFTNet for Corporates Table of contents 1 Purpose of this document... 1 2 SWIFTNet for Corporates Service Support... 1 2.1 General information on SWIFTNet for Corporates 1 2.2 One
More informationElectronic transmission manual for the BOP 1.1 report «Breakdown of selected items from the credit institutions profit and loss account»
In case of discrepancies between the French and the English text, the French text shall prevail Electronic transmission manual for the BOP 1.1 report «Breakdown of selected items from the credit institutions
More informationCitrix Analytics Data Governance Collection, storage, and retention of logs generated in connection with Citrix Analytics service.
Citrix Analytics Data Governance Collection, storage, and retention of logs generated in connection with Citrix Analytics service. Citrix.com Data Governance For up-to-date information visit: This section
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 informationC U B I T S. API DOCUMENTATION Version 1.8
C U B I T S API DOCUMENTATION Version 1.8 Table of Contents Table of Contents Introduction Request and Response Format Authentication Callbacks User language selection Test Invoices Channels Quote Channels
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 informationLogin with Amazon. Developer Guide for Websites
Login with Amazon Developer Guide for Websites Login with Amazon: Developer Guide for Websites Copyright 2017 Amazon Services, LLC or its affiliates. All rights reserved. Amazon and the Amazon logo are
More informationUnderstanding RESTful APIs and documenting them with Swagger. Presented by: Tanya Perelmuter Date: 06/18/2018
Understanding RESTful APIs and documenting them with Swagger Presented by: Tanya Perelmuter Date: 06/18/2018 1 Part 1 Understanding RESTful APIs API types and definitions REST architecture and RESTful
More informationCompliance with RFC 3261
APPENDIX A Compliance with RFC 3261 This appendix describes how the Cisco Unified IP Phone 7960G and 7940G complies with the IETF definition of SIP as described in RFC 3261. It contains compliance information
More informationBusiness ebanking User Guide
Business ebanking User Guide If you have any questions, please contact Business ebanking Support at 1-800-593-4345 Contents About Business Online Banking... 3 System Requirements/Considerations... 4 Password
More informationThe OAuth 2.0 Authorization Framework draft-ietf-oauth-v2-30
OAuth Working Group D. Hardt, Ed. Internet-Draft Microsoft Obsoletes: 5849 (if approved) D. Recordon Intended status: Standards Track Facebook Expires: January 16, 2013 July 15, 2012 The OAuth 2.0 Authorization
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 informationInformation About SIP Compliance with RFC 3261
APPENDIX A Information About SIP Compliance with RFC 3261 This appendix describes how the Cisco SIP IP phone complies with the IETF definition of SIP as described in RFC 3261. It has compliance information
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 informationAWS Elemental MediaPackage API Reference. API Reference
AWS Elemental MediaPackage API Reference API Reference API Reference: API Reference Copyright 2018 Amazon Web Services, Inc. and/or its affiliates. All rights reserved. Amazon's trademarks and trade dress
More informationCOMPUTER NETWORKS AND COMMUNICATION PROTOCOLS. Web Access: HTTP Mehmet KORKMAZ
COMPUTER NETWORKS AND COMMUNICATION PROTOCOLS Web Access: HTTP 16501018 Mehmet KORKMAZ World Wide Web What is WWW? WWW = World Wide Web = Web!= Internet Internet is a global system of interconnected computer
More informationConnect. explained. Vladimir Dzhuvinov. :
Connect explained Vladimir Dzhuvinov Email: vladimir@dzhuvinov.com : Twitter: @dzhivinov Married for 15 years to Java C Python JavaScript JavaScript on a bad day So what is OpenID Connect? OpenID Connect
More informationPayPal PLUS integration. Let our handbook be the fast track to achieve your business goals.
PayPal PLUS integration Let our handbook be the fast track to achieve your business goals. Content Introduction 3 Change History 3 Using the PayPal API 4 Architecture 4 PayPal Sandbox 4 API endpoints 4
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 informationCorporate Internet Banking Service Application Form
Bank of China (UK) Limited 90 Cannon Street London EC4N 6HA www.bocukltd.co.uk Corporate Internet Banking Service Application Form Corporate Internet Banking is available to current corporate customers
More informationDepartment of Computer Science. Burapha University 6 SIP (I)
Burapha University ก Department of Computer Science 6 SIP (I) Functionalities of SIP Network elements that might be used in the SIP network Structure of Request and Response SIP messages Other important
More informationUSERS GUIDE. Revision 02
USERS GUIDE Revision 0 06 I. TABLE OF CONTENTS... II. AVAILABLE SERVICES QUICK REFERENCE... 4 III. USEFUL SECURITY TIPS... 5. LOGIN AND NAVIGATION... 6.. The Login Screen... 6 Logging into Web Banking...
More informationMerchant e-solutions Payment Acceptance User Guide for Magento (M1)
Merchant e-solutions Payment Acceptance User Guide for Magento (M1) Step-by-step guidance for setup and use of the Payment Acceptance extension for Magento 1 Table of Contents Key Contacts... 3 Extension
More informationBlackBerry AtHoc Networked Crisis Communication. BlackBerry AtHoc API Quick Start Guide
BlackBerry AtHoc Networked Crisis Communication BlackBerry AtHoc API Quick Start Guide Release 7.6, September 2018 Copyright 2018 BlackBerry Limited. All Rights Reserved. This document may not be copied,
More informationCanonical Identity Provider Documentation
Canonical Identity Provider Documentation Release Canonical Ltd. December 14, 2018 Contents 1 API 3 1.1 General considerations.......................................... 3 1.2 Rate limiting...............................................
More informationTechnical Overview. Version March 2018 Author: Vittorio Bertola
Technical Overview Version 1.2.3 26 March 2018 Author: Vittorio Bertola vittorio.bertola@open-xchange.com This document is copyrighted by its authors and is released under a CC-BY-ND-3.0 license, which
More informationISO and JSON: An Implementation Best Practices Whitepaper. ISO and JSON: An Implementation Best Practices Whitepaper
ISO 20022 and JSON: An Implementation Best Practices Whitepaper January 2018 By members of the ISO 20022 Registration Management Group and the Technical Support Group Approved for publication by the ISO
More informationRealtime API. API Version: Document Revision: 16 Last change:26 October Kwebbl Swiss Software House GmbH
Realtime API API Version: 1.0.0 Document Revision: 16 Last change:26 October 2016 Kwebbl Swiss Software House GmbH Haldenstrasse 5 6340 Baar info@kwebbl.com Switzerland www.kwebbl.com Table of Contents
More informationSCR-Ident API Guide 1 - Start. Standard Connect & Result (SCR) API
SCR-Ident API Guide 1 - Start Standard Connect & Result (SCR) API Version 2.3 23.02.2018 SCR-Ident API Guide 1 Start Contents 1. Overview................................................................................
More informationOpen Cloud Computing Interface Service Level Agreements
1 2 3 4 Draft OCCI-WG Gregory Katsaros, Intel February 23, 2016 5 Open Cloud Computing Interface Service Level Agreements 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Status of this Document This document
More informationMerchant Portal User Guide
Merchant Portal User Guide TABLE OF CONTENTS Accessing the Click Merchant Portal... 3 Virtual Terminal... 4 Single Entry (Merchant Enters Card Details)... 5 Payment Using Collected Card Details... 5 Payment
More informationUser Manual SL-DD-Collect-1 v2.0.9 (with v2010)
User Manual SL-DD-Collect-1 v2.0.9 (with v2010) Objective A means to collect money from customer accounts via the Sales Ledger in Sage 200 using Direct Debit mechanisms provided by BACS systems, in a similar
More informationConnexion Documentation
Connexion Documentation Release 0.5 Zalando SE Nov 16, 2017 Contents 1 Quickstart 3 1.1 Prerequisites............................................... 3 1.2 Installing It................................................
More informationToken System Integration & Protocol Guideline (Server & Direct)
Token System Integration & Protocol Guideline (Server & Direct) Token System Protocol and Integration Guideline Content Welcome to the Sage Pay Token System integration... 2 General overview of how the
More information