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 interacts with the Straddle API to retrieve detailed information about a specific Pay Key by its unique identifier. It is useful in scenarios where you need to fetch the current status, bank details, verification info, and other metadata related to a particular Pay Key within your payment or financial workflows.
Practical examples include:
- Verifying the status of a payment authorization before proceeding with further processing.
- Retrieving bank account data associated with a Pay Key for reconciliation or reporting.
- Debugging or auditing payment keys by fetching their detailed information using client-generated trace identifiers.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the Pay Key to retrieve. |
| Straddle Account Id | (Optional) For platforms to specify an account ID to scope the request. Sent as a request header. |
| Request Id | (Optional) Client-generated identifier to trace and debug this specific request. Sent as a request header. |
| Correlation Id | (Optional) Client-generated identifier to trace and debug a series of related requests. Sent as a request header. |
Output
The node outputs JSON data representing the full details of the requested Pay Key. This includes fields such as:
- Bank account data (routing number, masked account number, account type).
- Status details (status message, reason, source, last changed timestamp).
- Verification details (status, method, attempts, completion time).
- Metadata and configuration options.
- Compliance and industry information.
- Support contact channels.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Straddle API.
- The base URL for API requests is dynamically set based on the configured environment credential.
- Proper network access to the Straddle API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing Pay Key Id will result in errors or empty responses.
- Incorrect or missing API authentication credentials will cause authorization failures.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authorization errors typically indicate invalid or expired API keys; verify and update credentials.
- "Not Found" errors suggest the provided Pay Key Id does not exist or is inaccessible under the specified account scope.
- Rate limiting or quota exceeded errors require checking API usage limits and possibly adjusting request frequency.
Links and References
- Straddle API Documentation (general reference for API endpoints and data models)
- n8n Documentation (for general node usage and credential setup)