How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Tietoevry Open Banking XS2A APIs

PSD2-compliant Access to Account (XS2A) APIs implementing the Berlin Group NextGenPSD2 framework, plus Tietoevry premium extensions beyond the PSD2 mandate. Covers account information (AIS), payment initiation (PIS), confirmation of funds (PIIS), bulk payments, future-dated and periodic payments, payment recall, request-to-pay and subscriptions to request-to-pay, signing baskets, card and card-account information, extended account owner details, and Virtual Account Management (VAM). Every endpoint shares one hostname and is selected by a sandbox|live path segment; a free self-service sandbox with simulated SCA and fake PSUs requires no eIDAS certificate.

This API exposes 26 operations across 21 paths, organized into 5 resource areas, and defines 35 schemas. It is described by OpenAPI 2.0, at version 1.3.4.

Requests are made against the base URL https://openbanking.api.tietoevry.com.

26 operations 21 paths 35 schemas 2 DELETE17 GET7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 2.0
API Version
1.3.4
Base URL
https://openbanking.api.tietoevry.com
Resource Areas
5

Paths & Operations 26

Across 21 paths, the API surfaces 26 operations — 2 DELETE, 17 GET, 7 POST. They span 5 resource areas: Account information service, Account consent service, Confirmation of Funds Service, Confirmation of Funds Service consent, Payment Initiation Service. Each is listed below with its method, path, parameters, and response codes.

Account information service 5

Operations for managing account information.

GET
/sandbox/xs2a/v1.3/accounts
Read Account List
getAccounts 6 params → 200400401403429
GET
/sandbox/xs2a/v1.3/accounts/{account-id}
Read Account Details
getAccount 7 params → 200400401403404429
GET
/sandbox/xs2a/v1.3/accounts/{account-id}/balances
Read Balance
getAccountBalances 6 params → 200400401403404429
GET
/sandbox/xs2a/v1.3/accounts/{account-id}/transactions
Read Transaction List
getAccountTransactions 10 params → 200400401403404429
GET
/sandbox/xs2a/v1.3/accounts/{account-id}/transactions/{transactionId}
Read Transaction detail
getAccountTransaction 7 params → 200400401403404429
Account consent service 7

Operations for establish and managing account information consent.

POST
/sandbox/xs2a/v1.3/consents
Establish Consent Transaction
postConsent 7 params → 200201400
GET
/sandbox/xs2a/v1.3/consents/{consent-id}
Get Consent Request
getConsent 4 params → 200400404
DELETE
/sandbox/xs2a/v1.3/consents/{consent-id}
Delete an Account Information Consent Object
deleteConsent 3 params → 204400404
GET
/sandbox/xs2a/v1.3/consents/{consent-id}/authorisations
Get authorisation sub-resources request
consentsGetAuthorizations 3 params → 200
POST
/sandbox/xs2a/v1.3/consents/{consent-id}/authorisations
Start authorisation process
consentsStartAuthorization 5 params → 201
GET
/sandbox/xs2a/v1.3/consents/{consent-id}/authorisations/{authorisation-id}
Get SCA status request
consentsGetAuthorizationStatus 4 params → 200
GET
/sandbox/xs2a/v1.3/consents/{consent-id}/status
Get Status Request
getConsentStatus 4 params → 200400404
Confirmation of Funds Service 1

Operations for receiving funds confirmation.

POST
/sandbox/xs2a/v1.3/funds-confirmations
Confirmation of Funds Request
getFundsConfirmation 5 params → 200400
Confirmation of Funds Service consent 7

Operations for establish and managing confirmation of funds consent.

POST
/sandbox/xs2a/v1.3/funds-confirmation-consents
Establish Funds Confirmation Consent Transaction
postFundsConfirmationConsent 7 params → 200201400
GET
/sandbox/xs2a/v1.3/funds-confirmation-consents/{consent-id}
Get Funds Confirmation Consent Request
getFundsConfirmationConsent 4 params → 200400404
DELETE
/sandbox/xs2a/v1.3/funds-confirmation-consents/{consent-id}
Delete an Confirmation of Funds Service Object
deleteFundsConsent 3 params → 204400404
GET
/sandbox/xs2a/v1.3/funds-confirmation-consents/{consent-id}/authorisations
Get authorisation sub-resources request
fundsConfirmationConsentsGetAuthorizations 3 params → 200
POST
/sandbox/xs2a/v1.3/funds-confirmation-consents/{consent-id}/authorisations
Start authorisation process
fundsConfirmationConsentsStartAuthorization 5 params → 200201
GET
/sandbox/xs2a/v1.3/funds-confirmation-consents/{consent-id}/authorisations/{authorisation-id}
Get SCA status request
fundsConfirmationConsentsGetAuthorizationStatus 4 params → 200
GET
/sandbox/xs2a/v1.3/funds-confirmation-consents/{consent-id}/status
Get Status Request
getFundsConfirmationConsentStatus 4 params → 200400404
Payment Initiation Service 6

Operations for payments.

GET
/sandbox/xs2a/v1.3/payments/{payment-product}/{payment-id}
Get Payment Details
getJSONPayment 4 params → 200
GET
/sandbox/xs2a/v1.3/payments/{payment-product}/{payment-id}/authorisations
Payment: Get authorisation sub-resources request
paymentsGetAuthorizations 4 params → 200
POST
/sandbox/xs2a/v1.3/payments/{payment-product}/{payment-id}/authorisations
Payment: Start authorisation process
paymentsStartAuthorization 6 params → 201
GET
/sandbox/xs2a/v1.3/payments/{payment-product}/{payment-id}/authorisations/{authorisation-id}
Payment: Get SCA status request
paymentsGetAuthorizationStatus 5 params → 200
GET
/sandbox/xs2a/v1.3/payments/{payment-product}/{payment-id}/status
Payment: Get Status Request
getJSONPaymentStatus 5 params → 200400404
POST
/sandbox/xs2a/v1.3/payments/{payment-product}
Payment Initiation with JSON encoding of the Payment Instruction
initiateJSONPayment 9 params → 200201400404

Schemas 35

The contract defines 35 schemas that model the data the API accepts and returns. The most detailed are JsonLinks (16 properties), JsonAccountDetails (10 properties), JsonGetPaymentResponse (9 properties), JsonTransaction (9 properties). Each schema is shown below with its type and property counts.

JsonAccountAccess
object
3 properties
JsonAccountDetails
object
JsonAccountDetails must contain one of iban,bban,maskedPan,msisdn or pan field
10 properties 1 required
JsonAccountReference
object
Must contain one of iban,bban,maskedPan,msisdn or pan field
6 properties 1 required
JsonAccountReport
object
3 properties 1 required
JsonAddress
object
5 properties 1 required
JsonAmount
object
2 properties 2 required
JsonBalance
object
4 properties 2 required
JsonErrorResponse
object
3 properties 1 required
JsonFundsConfirmationRequest
object
4 properties 2 required
JsonFundsConfirmationResponse
object
1 property 1 required
JsonGetAccountBalancesResponse
object
2 properties 1 required
JsonGetAccountResponse
object
1 property 1 required
JsonGetAccountTransactionsResponse
object
3 properties
JsonGetAccountsResponse
object
1 property 1 required
JsonGetAuthorisationStatusResponse
object
1 property
JsonGetAuthorisationsResponse
object
1 property
JsonGetConsentResponse
object
7 properties 6 required
JsonGetConsentStatusResponse
object
1 property
JsonGetFundsConfirmationConsentResponse
object
8 properties 5 required
JsonGetPaymentResponse
object
9 properties 5 required
JsonGetBulkPaymentResponse
object
4 properties 2 required
JsonPostBulkPaymentRequest
object
2 properties 2 required
JsonGetPaymentStatusResponse
object
1 property 1 required
JsonHref
object
1 property
JsonLinks
object
16 properties
JsonMessage
object
4 properties 2 required
JsonPostAuthorisationsResponse
object
4 properties
JsonPostConsentsRequest
object
5 properties 5 required
JsonPostConsentsResponse
object
5 properties
JsonPostFundsConfirmationConsentsRequest
object
5 properties 3 required
JsonPostPaymentRequest
object
7 properties 5 required
JsonPostPaymentResponse
object
7 properties 2 required
JsonGetAccountTransactionDetailsResponse
object
1 property
JsonTransaction
object
9 properties
TransactionStatus
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tietoevry-openbanking-xs2a-swagger.json Raw ↑
Where this information came from

This is an independent, third-party profile of Tietoevry Open Banking XS2A APIs, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.