Configuring Your Open Banking App
When you subscribe to any Open Banking product for the first time, the portal will ask you to configure your OB App.
These settings define how your brand appears on bank consent pages and how Neotek returns data to your backend.
These settings apply to all Open Banking products (E-Statement, Income Verification, Single API, Credit Profiling, Average Balance, etc.).
Required fields
Shown in the popup when you first subscribe.
| Field | Type | Example | Why it matters |
|---|---|---|---|
Legal Name (legal_name) | Text | Xyz Finance | Displayed to users on bank consent screens. Use your legal entity name (English letters/spaces, ≤40 chars). |
Trading Name (trading_name) | Text | Xyz | Shown to users; can be your brand name (English letters/spaces, ≤40 chars). |
App Identifier (app_identifier) | Text | xyz-app | Short, URL-safe identifier with letters, digits, hyphens (no spaces). |
Redirection URL (redirection_url) | URL | https://xyz.com/consent/success | Where users are sent after bank consent completes. Must be reachable over HTTPS. |
Logo URL (logo) | URL (image) | https://xyz.com/logo.png | The logo representing your entity that users will see on the bank consent page. |
Legal/Trading names and Logo are what your customers will see on bank consent pages; choose values that clearly identify your brand.
Optional callback fields
Wait 3–5 seconds after the callback before you call
The callback fires as soon as the result is available — but call straight away and you can still get an empty response from an integration that is otherwise perfectly correct.
Build a 3–5 second delay into your callback handler. Nothing in the payload tells you to wait, which is exactly why this one gets missed.
If you would like Neotek to push results back to your backend automatically, fill all of the following. If you leave one blank, leave all blank. The callback URL must be a valid URL; none of the text values may contain spaces.
| Field | Type | Example | Purpose |
|---|---|---|---|
Callback URL (callback_url) | URL | https://api.xyz.com/ob/callback/status | HTTPS endpoint we call when data is ready. |
Callback Client ID (callback_client_id) | Text | neotek-cb-id | Credential we include so you can authenticate the call. |
Callback Client Secret (callback_client_secret) | Text | •••••••• | Shared secret to validate Neotek's request. Store securely. |
Client ID Header Label (callback_client_id_header) | Text | X-IBM-Client-Id | Header name used to pass the client ID. |
Client Secret Header Label (callback_client_secret_header) | Text | X-IBM-Client-Secret | Header name used to pass the client secret. |
Callback example
What you will receive:
{ "AccountLinkId": "8603", "PSUId": "7033461539"}Security tip: Reject any callback that (1) does not use HTTPS, (2) omits your agreed header labels, or (3) has mismatched client ID/secret. Log the x-request-id (if present) for traceability.