---
updatedAt: 2026-03-09T18:45:03.000Z
agentTools:
  projectIndex: https://guides.tell.money/llms.txt
---

# Configuration

When you have registered and created a Gateway, you can start configuring it.

<Callout icon="📙" theme="default">
  ### ACCOUNT PROVIDER GUIDE

  ##### 🤔 [Is this the right developer guide for me?](https://guides.tell.money/docs/which-guide)
</Callout>

# Public Identifier

Each Gateway needs a unique Public Identifier which is used to form URLs for both the API and <Glossary>Developer Portal</Glossary>. For example, if you choose “alias” then the API is located at:

```
https://secure.tell.money/alias
```

and Developer Portal is at:

```
<https://developer.tell.money/alias
```

To configure a <Glossary>Gateway</Glossary>, access the Integration Environment, enable the required functionality, and complete your testing. Once you’re ready, you can apply the same changes in Production.

There’s no need to configure the Sandbox environment - this is set up automatically for you. However, if you’d like to make your <Glossary>Developer Portal</Glossary> available to <Glossary>Third Party Providers</Glossary> (TPPs) ahead of Production go-live, you can update your Sandbox functionality to reflect your intended setup. This allows <Glossary>TPP</Glossary>s to begin integration and testing while you finalize your Production readiness.

***

# Communication Paths

Each <Glossary>Gateway</Glossary> requires an **Authorisation URL** and **API URL** for each environment, both of which are configured in the <Glossary>Console</Glossary>.

## ❯ Authorisation URL

When a consent request is initiated by a <Glossary>Third Party Provider</Glossary>, the <Glossary>Account Holder</Glossary> is redirected to the Authorisation URL you have specified, with a ConsentId appended in the querystring. For example, if the Authorisation Service is located at:

```
https://your-bank.com/tell-gateway
```

then the Account Holder is redirected to:

```
https://your-bank.com/tell-gateway?ConsentId={ConsentId}&CallbackURL={CallbackURL}
```

**This is explained in more detail in Development->Authorisation.**

<Callout icon="📘" theme="info">
  We will always attempt to redirect to your Authorisation URL on the device that the account holder is currently using. For example, if they are using a laptop and you have provided a web URL then they will be redirected to that URL on the browser of their laptop.

  If you have provided the URL of a mobile app – e.g. beginning aliasbank:// rather than https:// – we will automatically detect that the redirect is not possible and instead present the account holder with a QR code on their laptop browser. They will be prompted to scan the QR code using a mobile device which has your app installed. Doing so will launch the app on that mobile device at the Authorisation URL (including ConsentId) location.
</Callout>

## ❯ API URL

This is the location we will send API requests to when we have a valid consent in place.

**This is explained in more in Development->Resources.**

***

# Security Credentials

## ❯ Calling Tell APIs

In order to call our API, you will need to use a set of credentials specific to a <Glossary>Gateway</Glossary> and its environment. These can be found under the "Calling tell. APIs" tab. Please note that different credentials are required per <Glossary>Gateway</Glossary>, but are mirrored for each version specification within a <Glossary>Gateway</Glossary>.

## ❯ Calling Your APIs

When we calls your API to retrieve account information or initiate a payment, we will do so using the credentials in the "Calling Your APIs" tab. Please note that different credentials are required per <Glossary>Gateway</Glossary>, but are mirrored for each version specification within a <Glossary>Gateway</Glossary>.

***

# API Functionality

We support all mandatory APIs and endpoints but not all will be relevant to your business or to a particular <Glossary>Gateway</Glossary>. For example, if your product does not support Direct Debits then there is no need to enable the Get Direct Debit endpoint. You can switch each API and endpoint on and off in real time as required, per specification available via your Gateway.

Select the relevant specification and environment to configure as per below.

## ❯ Account Information Services

Select Account Information Services and enable or disable each endpoint to match those that you wish to support. You will notice that some items cannot be disabled – these are mandatory endpoints required for compliance and technical purposes.
Once you have completed your integration and testing, you can mirror this functionality in production and continue to make your <Glossary>Developer Portal</Glossary> available.

If your <Glossary>Gateway</Glossary> is already live, you can make changes in the integration environment with no impact to your <Glossary>Developer Portal</Glossary>. When ready you can mirror these changes in production and they will be instantly available in the <Glossary>Developer Portal</Glossary>.

## ❯ Payment Initiation

If you are required to support Payment Initiation then there are a number of payment types you can choose from based on your specification type, and product set up. You can choose to enable all payment types that you support.

## ❯ Confirmation of Funds

If a Gateway is required to support Confirmation of Funds, enable this option. When enabled you do not need to make any further selections as this entire API is either “on” or “off”, with no other configuration necessary.

<Callout icon="📘" theme="info">
  If you are unsure about which APIs and Operations you need to support, or have any other questions then please reach out to our Support team who would be happy to help. Contact us via slack if you have an existing connection, or via [support@tell.money](mailto:support@tell.money)
</Callout>