Links
➡️

Demo institution and test connectors

The Demo Institution and the Test connector have been developed to help you easily discover the capabilities of our products and the various scenarios of our Webview.

How to open them?

  1. 1.
    Create an account on the Console
  2. 2.
    Create a client application
  3. 3.
    Click on Webview
  4. 4.
    Click on "Test Bank" or "Test Wealth" or "Test Trust" depending on what you want to test
  5. 5.
    Open the Webview and accept the TOS
  6. 6.
    Use the searcher to find them
You can test the addition of a new connection on the “Demo Institution” using the https://docs.powens.com/demo-integration/ or by creating an account on the Console and open your own client application flow

Demo Institution

The “Demo Institution” (also called “Institution de démonstration”) is a new institution that is specifically designed for demos. Similarly to the “Test connector”, it returns fake data for the Bank, Wealth, Bill & Trust products, but does not trigger any errors (wrongpass, website unavailable, etc.). It is therefore not suited for API integration but provides an easy way to understand the workflow of our technical solutions.

How it works?

  • The “Usecase” field is used to select your usecase of interest: depending on your target audience, you may want to display only personal bank accounts, only professional bank accounts, wealth accounts, loans, or all these accounts at once.
  • The “Password” field is just there to look like an actual institution, but you can enter anything you want, it will not be verified and will never trigger any wrongpass.

Here is a list of the available use cases

Usecase
Data
bank
2 personal checking accounts + 2 personal deferred cards + transactions for all these accounts
bankpro
2 professional checking accounts + 2 professional deferred cards + transactions for all these accounts
loans
1 Loan + 1 Mortgage + 1 Consumer credit + 1 Revolving credit + transactions for all these accounts
wealth
1 Savings + 1 Deposit + 1 Life insurance + 1 Market account + 1 PEE + 1 PERCO + 1 Article 83 + 1 RSP + 1 PEA + 1 Capitalisation + 1 PERP + 1 Madelin + 1 PER + 1 Real Estate + 1 Crowdlending + transactions for all these accounts + investments for all these accounts + pockets for all the employee savings accounts + market orders for the market account and the PEA
bankloans
All data from the “bank” usecase + all data from the “loans” usecase
bankwealth
All data from the “bank” usecase + all data from the “wealth” usecase
all
All data from the “bank” usecase + all data from the “loans” usecase + all data from the “wealth” usecase
check
Only the first checking account from “bank” with complete Account Check information with an account holder and a co-holder.
empty
Only the first checking account from “bank” but without any transactions. Designed to push transactions manually and test the Advisory product.
bill
One subscription with 5 downloadable documents (Powens bills from January 2023 to May 2023).
trust
One subscription with 1 downloadable document (the most recent from the “bill” usecase) that can be used as proof of address.
statement
One subscription with 3 downloadable documents (Bank statements from April 2023 to June 2023).

Test connector

The test connector provides some use cases that will happen in production when trying to connect to real banks or providers.
It could be used to help customer developers integrate our API or just for testing.
To reproduce real behaviors that normally happen at discontinuous times, we implemented an additional parameter to force some situations. This parameter is called 'website' and will only be found on the test connector.

How it works?

  • Select a scenario you would like to test
  • Fill in
    • Login : Test
    • Password : 1234
In some cases, you won't have to fill in any Login or Password and will be automatically redirected to a fake bank interface. In that case, just continue the flow.

Here is a list of the available scenario

Scenario
Description
actionNeeded
Simulate a connection that will require an end user action. So the synchronisation process is stopped until the connection state changes. And on this test connector, the connection state is only changeable updating the 'website' paramater.
additionalInformationNeeded
Simulate a connection with SCA in which case an OTP will be asked.
AppValidationCancelled
Simulate a connection with SCA in which case a validation has been asked to the end user but was not approved a few seconds later.
AppValidationExpired
Simulate a connection with a SCA and in that case, a notification validation will be “asked” and the validation will not be exipred few seconds later.
bug
Simulate a connection as if a bug occurred in Powens information system.
doubleotp
Simulate a connection that will need two distincts OTP.
longDecoupled
Simulate a connection with SCA and in that case, a notification validation will be “asked” and the validation will be accepted few minutes later.
notSupported
Simulate the connection state 'notSupported' that sometimes happen for some banks or providers that use specific authentication feature.
otp_transfer
Simulate a connection that requires an OTP to perform a transfer (only for directaccess or fallback source).
passwordExpired
Simulate a connection with an expired password.
SCARequiredAndDecoupled
Simulate a connection with a required decoupled SCA which is triggered by a background synchronization.
SCARequiredAndOTP
Simulate a connection with a required OTP SCA which is triggered by a background synchronization.
shortDecoupled
Simulate a connection with SCA and in that case, a notification validation will be “asked” and the validation will be accepted a few seconds later.
webauthRequired
Simulate a connection on which a synchronization resulted in requiring authorization via the bank/provider interface.
websiteUnavailable
Simulate a connection with a website unavailable error on the bank.
wrongpass
Simulate a connection with an invalid password.