Actions81
- Users Actions
- Organizations Actions
- Representatives Actions
- Bridge Actions
- Platforms Actions
- Tools Actions
- User Invites Actions
- Customers Actions
- Paykeys Actions
- Reports Actions
- Charge Actions
- Funding Events Actions
- Payments Actions
- Payout Actions
- Accounts Actions
- Get Account By Id
- put__v1_accounts_account_id
- Create Account
- get__v1_accounts
- post__v1_accounts_account_id_onboard
- post__v1_accounts_account_id_simulate
- patch__v1_internal_accounts_account_id
- get__v1_internal_accounts_account_id
- patch__v1_internal_accounts_account_id_status
- get__v1_internal_accounts_account_id_settings
- Capability Requests Actions
- Linked Bank Accounts Actions
Overview
This node operation retrieves detailed information about a specific linked bank account by its unique identifier. It is useful in scenarios where you need to fetch the current status, verification details, and bank account metadata for a particular linked bank account within a financial or payment platform.
Practical examples include:
- Verifying the status and details of a user's linked bank account before processing payments.
- Auditing linked bank accounts for compliance or troubleshooting purposes.
- Displaying bank account information in user dashboards or administrative panels.
Properties
| Name | Meaning |
|---|---|
| Linked Bank Account Id | The unique identifier of the linked bank account to retrieve. This is required. |
| Request Id | Optional client-generated identifier to trace and debug this specific request. |
| Correlation Id | Optional client-generated identifier to trace and debug a series of related requests. |
Output
The output JSON contains detailed information about the linked bank account, including but not limited to:
- bank_details: Object containing bank routing number, masked account number, account type (e.g., checking, savings), and bank name.
- status_details: Object describing the current status message, reason for the status, source of status change, and timestamp of last status change.
- verification: Object with verification status, method used, number of attempts, and completion timestamp.
- Additional metadata fields may include compliance profiles, support channels, capabilities, settings, and industry information depending on the API response.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authentication with the Straddle API.
- The base URL for API requests depends on the configured environment (e.g., sandbox or production).
- Proper network connectivity to the Straddle API endpoint is necessary.
Troubleshooting
- Missing or invalid Linked Bank Account Id: Ensure the provided ID is correct and exists in the system.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Request tracing issues: Use the optional
Request IdandCorrelation Idheaders to help trace and debug requests through logs. - API endpoint unreachable: Check network connectivity and environment configuration for the base URL.
- Unexpected response structure: Confirm that the API version matches the expected schema and that no breaking changes have occurred.
Links and References
- Straddle API Documentation (general reference for API endpoints and schemas)
- n8n documentation on creating custom nodes