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 Paykey in an unmasked form. The operation get__v1_paykeys_id_unmasked fetches sensitive or full details of a Paykey identified by its unique ID.
Typical use cases include:
- Retrieving full Paykey details for reconciliation or auditing.
- Accessing unmasked payment key data for processing or compliance checks.
- Platforms managing multiple accounts can specify account scope via headers.
Example scenario: A financial platform wants to fetch the complete details of a Paykey to verify its status and associated bank data before initiating a payout.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the Paykey to retrieve (required). |
| Straddle Account Id | Optional header to specify an account ID, used by platforms to set the scope of the request. |
| 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 node outputs JSON data representing the full, unmasked details of the specified Paykey. This includes:
- Basic Paykey information such as ID and status.
- Bank account data including routing number, masked account number, and account type.
- Status details with messages, reasons, sources, and timestamps.
- Verification details like status, method, attempts, and completion time.
- Additional nested objects describing metadata, device info, compliance profiles, capabilities, settings, industry info, support channels, and more.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Straddle API.
- The base URL for API requests depends on the configured environment (e.g., sandbox or production).
- Proper network access to the Straddle API endpoint is necessary.
Troubleshooting
- Missing or invalid Id: The operation requires a valid Paykey ID; ensure it is provided and correctly formatted.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Scope issues: If using the Straddle Account Id header, confirm the account ID is valid and accessible.
- Rate limiting or API errors: Handle HTTP error responses gracefully; check API limits and retry policies.
- Debugging identifiers: Use Request Id and Correlation Id headers to trace requests in logs or support tickets.
Links and References
- Straddle API Documentation (general reference for API endpoints and data models)
- n8n documentation on HTTP Request Node for understanding how headers and authentication are handled in custom nodes.