As well as configuring your Interface, you will need to intergrate with our services. For more information on this aspect, see our Integration Guide.
If you haven't done so already, register as a FinTech Account Provider by clicking here .
You only need to provide some basic information at this stage. Verify your email address, register your MFA device, then you're ready to go. You will be given access to the Management Console and will be issued with:
You should store these details securely - you'll need them to call our API.
A Dedicated Interface is your PSD2 gateway, providing an end to end solution including a Developer Portal, API Gateway, Consent Management and much more. You can create as many Interfaces as you need. You may wish to have different Interfaces if you operate multiple brands, otherwise one will be enough.
To add an Interface within the Management Console, go to Interfacesand select Create New Interface.
When you submit the form, your Interface will be created instantly. This will include:
* Your Developer Portal uses the subdomain you selected. For example, if you chose “alias-bank” as your subdomain, the Portal will be located athttps://alias-bank.tell.money. It can sometimes take a few minutes for the domain to fully propogate so if the site isn't available immediately, leave it briefly then try again.
When your Interface is created, you can configure it by selecting General Information where you can view and edit the name and description. You can also upload the logo and favicon that you wish to use in the Developer Portal.
An Account Information Service Provider (AISP) is a type of Third Party Provider (TPP) that is permitted to access account information and to perform certain account-based activities on behalf of a user. An AISP needs a user's explicit consent to do so.
The way in which your users provide Account Access consent is described in more detail in the Integration Guide.
By selecting Account Access within the Management Console, you can configure which Endpoints (types of services) you will be exposing to TPPs.
We automatically configure a set of default Endpoints for you:
A Payment Initiation Service Provider (PISP) is a type of Third Party Provider (TPP) that is permitted to initiate payments from an account on your system on behalf of a user. A PISP needs a user's explicit consent to do so.
The way in which your users provide Payment Initiation Consent is described in more detail in the Integration Guide.
By selecting Payment Initation within the Management Console, you can configure this service. If you are not intending to support outbound payment initiation, simply select "not supported" and this option will not be made available to PISPs (this is the default setting).
If you switch Payment Initiation on, you can then configure the type of payments that you accept and the message schema you expect to receive. The Management Console allows you to choose a number of different options including:
These options can be changed at any time.
The way in which you integrate with tell.connect is described in details in the Integration Guide. The Management Console allows you to control how and where the integration with your application takes place. Within your Interface, select Integration from the menu.
You can set the location of your Authorisation service for both Sandbox and Production. This is the location on your website or app where you present the user with the consent being requested and allow them to review and approve it.
In Sandbox you can select Simulator Mode. Doing so means that all authorisation requests will be auto-approved by our simulator without any communication with your application. You can switch this on and off as required.
Simulator Mode is the default setting when you create an Interface. This means that you can try out the API immediately without any development. You may choose to leave this setting on so that all Authorisation requests into the Sandbox continue to be served directly by tell.connect.
You can set the location of your Resource service for both Sandbox and Production. This is the location of an endpoint on your application where we will direct all resource requests (Account Access & Payment Initiation).
In Sandbox you can select Stub Data Mode. Doing so means that all resource requests will responded to by our Stub Data Server, providing responses directly from your dedicated stub data enviornment without any communication with your application. You can switch this on and off as required.
Stub Data Mode is the default setting when you create an Interface. This means that you can try out the API immediately without any development. You may choose to leave this setting on so that all Resource requests into the Sandbox continue to be served directly from the tell.connect Stub Data Environment.
As part of integrating with the Service as described in the Integration Guide, you will receive API requests from tell.connect for Account Access and Payment Initiation.
These requests will always contain an API Key and may also be signed using aCertificate Public Key (use of a Public Key for signing messages is optional - this is described in more detail in the Integration Guide).
You can manage these settings in the Management Console by navigating to your Interface and selectingSecurity.
You can view your API Key and select from a list of your pre-configured Certificates. To view or create a Certificate, go toOrganisation in the main menu and selectCertificates.
You may find it useful to try out the API before carrying out any integration. Doing so will allow you to experience how the system behaves from the perspective of a TPP (AISP or PISP).
When a TPP registers on your Dedicated Interface, they will be issued with a client_id and client_secret in order to securely access the API, and they will be required to sign their requests using a shared certificate.
You don't have to go through this process. You can access the API in Sandbox instantly by using the phrasesandbox in place of: