TPP registration
- record your contact data
- create an application
The existence of certificate referred to in the previous section, and listing in the EBA register are prerequisite for the registration.
To use K&H’s APIs, first record your contact data, after it create an application with the following API (APIs section’s POST /tpp/app API).
For testing purposes and the proper usage of our sandbox the valid tokens can be generated on your side via the dedicated sandox token generator endpoint after the finalization of your registration.
recording your contact data
Use the dedicated API to record your following contact data:
- contact person’s name;
- contact person’s phone number;
- contact person’s email address.
(The data will only be used for communication about K&H’s API.)
It is a required step before creating an application. Only one contact information can belong to a TPP. Access to the api will be granted after the approval of your initial contact registration which might entail further screening of your TPP.
create an application
When creating an application, the following data must be entered:
- Application name:
- This is the name to be displayed to customers upon events that require their approval.
- The TPP’s roles to be used by the application (e.g. AISP or PISP):
- This list cannot be longer than the list of the TPP’s roles, but it can be shorter (but it must contain at least one).
- An application will only be authorised to call the APIs corresponding to its role specified upon application registration (even if the TPP is authorised for more based on its own role)
- Redirect URL:
- The host of the TPP application to be used by K&H redirection screen for customer authentication, to which the PSU should be redirected back. During the redirect process only a redirect URL starting with this host is allowed.
The response to the application registration API call contains an application authentication token which must be used in all K&H API call launched from the application. The response also contains a unique application ID (tppAppId) which will be used to renew the application token later.
A TPP can have several applications.