StraddleInstall

Overview

This node retrieves detailed information about a specific user by their unique identifier. It is useful in scenarios where you need to fetch user profile data, compliance details, bank account information, or status and verification details from an external system that manages users.

Practical examples include:

• Fetching user details for display in a dashboard.
• Retrieving compliance and verification status for audit or KYC processes.
• Accessing bank account information linked to a user for payment processing or reconciliation.

Properties

Output

The output JSON contains comprehensive user information structured with multiple nested objects describing various aspects of the user:

• metadata: Custom key-value pairs defined by the user.
• device: Device-related info such as IP address and user agent.
• config: Configuration options related to the user.
• address: User's address details including line1, city, state, postal code, and country.
• compliance_profile: Compliance-related data like date of birth, SSN last 4 digits, EIN, legal business name, and website.
• capabilities: Supported payment types (ACH, card, wire) and customer types (individual, business).
• settings: Account settings including charge and payout configurations.
• industry: Industry classification details such as Merchant Category Code (MCC), sector, and category.
• support_channels: Support contact information including email, phone, and URL.
• bank_details: Bank account information including routing number, masked account number, account type, and bank name.
• status_details: Status messages, reasons, sources, and timestamps related to the user's current status.
• verification: Verification status, method used, number of attempts, and completion timestamp.
• bank_data: Additional bank account data similar to bank_details but possibly more specific.

No binary data output is indicated.

Dependencies

• Requires an API key credential for authentication to the external user management service.
• The base URL for API requests is dynamically constructed based on the environment specified in credentials.
• HTTP headers accept and send JSON content.
• Optional custom headers can be set via "Request Id" and "Correlation Id" properties for tracing/debugging.

Troubleshooting

• Missing or invalid User Id: Since User Id is required, omitting it or providing an incorrect value will likely cause errors or empty responses. Ensure the User Id is correct and exists in the system.
• Authentication errors: If the API key credential is missing or invalid, the node will fail to authenticate. Verify the API key configuration.
• Network or connectivity issues: Failures to reach the API endpoint may occur due to network problems or incorrect environment setup.
• Unexpected response structure: If the external API changes its schema, some fields might be missing or different. Review the API documentation and update the node accordingly.
• Header injection issues: Improper values in "Request Id" or "Correlation Id" could cause request failures or tracing mismatches.

Links and References

• No direct links are provided in the source code. For further details, consult the external API documentation corresponding to the user management service you are integrating with.