Table of Contents |
---|
General Information
The finAPI Test Bank for embedded/decoupled has the name “finAPI Test Bank” and the BLZ is DEMO0001.
Info |
---|
Request and response examples are provided here: https://finapi.jira.com/wiki/spaces/ACCDOC/pages/626491433/Approaches+explanation#Decoupled-approach Please use bankId, interface, login credentials and two-step procedures as provided below. |
Bank Id
Please use 280001
as bankId for this test bank.
Note: you can always find the bankId when searching for a bank via Get and search all banks service.
Interfaces and capabilities
The bank supports two interfaces:
XS2A
FINTS_SERVER
Both interfaces have the DECOUPLED_APPROACH
property set. The behaviour of both interfaces is completely identical and both return the same accounts and transactions.
It is possible to import a bank connection and initiate a SEPA Money Transfer with this test bank (no money will be moved).
Accounts and Transactions
2 Checking Accounts and 1 Savings Account are available for this test bank.
New transactions will be generated for the test accounts on a daily basis.
Credentials
The following credentials are required for accessing the test bank and are identical for both interfaces:
Onlinebanking-ID:
demo
PIN:
demo
To trigger no SCA scenario, please use:
Onlinebanking-ID:
demo_no_msa
PIN:
demo_no_msa
Two-step-procedures
The test bank supports different two-step-procedures to allow testing of different MSA approaches:
embedded approach: smsTan, pushTan, chipTan optical, chipTan QR
The challengeResponse value to use is always “123456”decoupled approach: Demo Decoupled Auth
Simulate errors
The following error cases can be simulated with the test bank:
Wrong credentials
If other credentials as demo/demo are given in step 1, the server will respond with HTTP 422 and the following error:
Code Block |
---|
HTTP/1.1 422
Date: Wed, 27 Nov 2019 12:15:12 GMT
{
"errors": [
{
"message": "Zugangsdaten sind falsch",
"code": "BANK_SERVER_REJECTION",
"type": "BUSINESS",
"multiStepAuthentication": null
}
],
"date": "2019-11-29 11:03:20.686",
"requestId": "selfgen-8074f0c7-e10e-429e-8624-5ca505c22ac2",
"endpoint": "POST /api/v1/bankConnections/import",
"authContext": "1/18",
"bank": "DEMO0001 - finAPI Test Bank"
} |
Wrong twoStepProcedureId
If the twoStepProcedureId value given in spec 2 is wrong, the server will respond with HTTP 422 and the following error
Code Block |
---|
HTTP/1.1 422
Date: Fri, 13 Nov 2019 09:37:06 GMT
{
"errors": [
{
"message": "Authentifizierung fehlgeschlagen - falsche Zwei-Faktor-Authentifizierungsmethode.",
"code": "BANK_SERVER_REJECTION",
"type": "BUSINESS",
"multiStepAuthentication": null
}
],
"date": "2020-11-13 10:37:06.930",
"requestId": "selfgen-b496fd58-72fd-4926-a875-6dddc5b8a5dc",
"endpoint": "POST /api/v1/bankConnections/import",
"authContext": "26/92",
"bank": "DEMO0001 - finAPI Test Bank"
} |
Wrong challengeResponse
If the challengeResponse value given in step 3 is wrong, the server will respond with HTTP 422 and the following error:
Code Block |
---|
Note |
This page is now deprecated. We urge you to check out our new Access Public Documentation that we recently published instead, which covers all state-of-the-art information of our products. Note: due to overall restructuring for our new Access Public Documentation, there might not be a corresponding page with the exact same content like this deprecated page in our new documentation. However, we make sure to already cover all information you need, including this content, in our new documentation. |