Sync Online Banking Accounts
Generate a GathrLink iFrame in order to allow a Customer to login to their internet banking profile and retrieve transactional data and PDF bank statements.
Sync Online Banking Accounts
GET
{{baseUrl}}/bank-accounts/:bank_account_id/sync?redirect_url={{redirectUrl}}
GET
{{baseUrl}}/bank-accounts/:bank_account_id/sync?redirect_url={{redirectUrl}}
Path Parameters
bank_account_id*
String
Query Parameters
result_url
String
Add a value for this parameter to send the outcome of the online login session.
i.e. the URL to which you would like to receive the results of the online login session (successful, failed, in progress).
You can save the value in the environment variable {{resultUrl}}.
category_engine
string
To enable refined transaction categorisation you will need to set the category_engine
to
repeat_application
Boolean
allow_redirect
Boolean
Set allow_redirect to "true" if you would like to redirect the end-user/customer after they have completed the online process.
By default, it is null and therefore the redirect_url
will not work unless allow_redirect
= true
.
redirect_url
String
Add a value for this parameter to dictate where the end-user/customer is redirected to after they have successfully completed the online process.
i.e. the URL of the page to which you want the end-user/customer to return/progress to once their transaction data and bank statements have been collected.
You can save the value in the environment variable {{redirectUrl}}.
Status Codes
Webhook Requirements | result_url
result_url
The following is the payload that gets sent to the url that is provided in the result_url
parameter in the POST Sync Online Banking Accounts request.
The webhook gets triggered once transaction and statement(s) has successfully been collected. Once you receive the relevant successful payloads, you can query the relevant/transactions
, /statements
, /accounts
and /transaction-reports
endpoints to retrieve the affordability data you require.
As this is a specific post query, we need to make sure we are sending customer/clients to a safe destination, as such, there is validation done on the Redirect and Result URL.
The Filed under validation must have a valid A or AAAA record when querying the dns_get_record PHP function.
A a simple guideline:
Must be RFC compliant
Must include the hostname
Be careful with special characters that might mess with the structure of the post request
Webhook Success Notifications
Once you receive the transaction successful payload, you can query /transactions
and /transaction-reports
endpoints to retrieve the transactional data you require.
Webhook Failure Notifications
Transaction Failure Codes
LOGIN_FAILED = "login-failed"
OTP_FAILED = "otp-failed"
LOGIN_UNATHORISED = "login-unauthorised"
USER_ACCOUNT_FAILED = "user-accounts-failed"
ACCOUNT_SELECTION_FAILED = "accounts-failed"
STATEMENT_FAILED = "statement-failed"
TRANSACTION_FAILED = "transactions-failed"
IFrame Events
Clients can subscribe to specific events triggered within the iframe, enabling real-time monitoring and integration with their systems.
"LOGIN_BUTTON_CLICKED"
"ACCOUNT_SELECTION_CHECKBOX_CHECKED"
"ACCOUNT_SELECTION_BUTTON_CLICKED"
"OTP_BUTTON_CLICKED"
"EXIT_BUTTON_CLICKED"
"ACCOUNT_SELECTION_CHECKBOX_UNCHECKED"
"RETRY_BUTTON_CLICKED"
"CONNECTION_LOST_ERROR"
"CONNECTION_LOST_RETRY_WARNING"
Last updated
Was this helpful?