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, including sensitive data that is normally masked. It is useful in scenarios where you need to unmask and access full bank account details for verification, reconciliation, or compliance purposes. For example, a financial application might use this operation to securely fetch the full bank account number and routing number of a user's linked bank account after proper authorization.
Properties
| Name | Meaning |
|---|---|
| Linked Bank Account Id | The unique identifier of the linked bank account to retrieve and unmask. (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: Status message, reason, source, and timestamp of last status change.
- verification: Verification status, method used, number of attempts, and completion timestamp.
- Other metadata fields such as compliance profile, industry info, support channels, capabilities, and settings may also be included depending on the API response.
The node does not explicitly output binary data.
Dependencies
- Requires an API key credential for authentication with the Straddle API.
- Needs configuration of the environment subdomain (e.g., sandbox or production) to construct the base URL.
- The node sends HTTP requests with appropriate headers including optional tracing headers (
request-idandcorrelation-id).
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 valid and has necessary permissions.
- Network or connectivity issues: Check network access to the configured Straddle API environment.
- Unmasking restrictions: Some accounts may have restrictions preventing unmasking; check API error messages for details.
- Invalid header values: If using
request-idorcorrelation-id, ensure they are properly formatted strings.
Links and References
- Straddle API Documentation (general reference for API endpoints and authentication)
- n8n documentation on HTTP Request Node for understanding how headers and credentials work in n8n nodes