Application settings
Manage your client ID and secret and configure redirect URIs in Console.
To change app-wide settings, access the Settings page within your preferred app and navigate to Application settings near the top of the page. On this page, you can set variables such as client credentials and return URIs.
Note that the changes you make on this page only apply to the app you currently have open.
The headings on this page provide an overview of each section on the Application settings page.
Identifiers
The Identifiers section on the right of the Settings page contains two options:
client_id
: This contains yourclient_id
, which you need to authenticate your requests to any TrueLayer API.
You can click the blue button to copy yourclient_id
to your clipboard.client_secret
: The secret key which you need to authenticate your API requests. This is blurred out on the Settings screen, as you receive yourclient_secret
as a text file when you create a new app or reset your secret.
When you get yourclient_secret
, store it securely and do not share it.
Redirect URIs
This section contains all of the possible return URIs for your application. These are used when you redirect users during payment authorisation or data authentication .
To add a new redirect URI:
- Click the + button in the top-right corner of the Redirect URIs section.
- Enter your redirect URI.
This must be in a valid URI format, starting withhttps://
. - Click the tick icon to the right of your URI, or press Enter, to confirm your selection.
Redirect URIs can take up to 15 minutes to take effect.
To delete or edit an existing URI, click the pencil or bin icon next to it.
Payments settings
This section of the Application settings page lets you upload a public key to sign payments requests, and to specify your webhook URI to receive notifications over.
Payouts settings
This section only displays if you are still using our legacy Payouts API. Note that the Payments API v3 also supports payouts, so this section only displays in some rare cases.
Enable legacy API settings
If you integrated before the introduction of the Payments API v3, you may need access to some legacy features. This section contains toggles so you can turn such features on and off:
- Enable reports in legacy PayDirect API format: If you enable this, the transactions table within the merchant account dashboard only displays transactions for a single day. Additionally, the format of any exports from the transactions table and payments view change to match the legacy format.
- Enable legacy PayDirect API Webhook URI: Enables you to specify a webhook URI for the legacy PayDirect API.
- Enable Payments v2 UI customisation: Lets you customise the UI of a legacy Payments API v2 integration.
Updated 17 days ago