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 allows you to create a new charge via the Straddle API by sending detailed payment information. It is useful in scenarios where you need to programmatically initiate charges on customer accounts, such as billing customers for services or products, processing payments, or integrating payment workflows into your automation.
Practical examples include:
- Charging a customer’s saved payment method with a specified amount and currency.
- Recording payment details including consent type and device information for compliance.
- Adding metadata and configuration options to customize the charge request.
Properties
| Name | Meaning |
|---|---|
| Straddle Account Id | For platforms to specify an account ID to scope the request (sent as HTTP header). |
| Request Id | Optional client-generated identifier to trace and debug a single request (HTTP header). |
| Correlation Id | Optional client-generated identifier to trace and debug a series of related requests (HTTP header). |
| Paykey | The paykey identifying the payment source or method. |
| Description | A description of the charge. |
| Amount | The monetary amount to be charged. |
| Currency | The currency code for the amount (e.g., USD, EUR). |
| Payment Date | The date when the payment is made. |
| Consent Type | The type of consent given by the payer; options are: Internet or Signed. |
| Device | JSON object containing device information such as IP address and user agent. |
| External Id | An external identifier for the charge, useful for idempotency or tracking. |
| Config | JSON object with additional configuration options for the charge. |
| Metadata | JSON object with user-defined key-value pairs for custom metadata associated with the charge. |
Output
The node outputs the response from the Straddle API after creating the charge. This output is structured as JSON and typically contains details about the created charge, such as its status, identifiers, and any relevant messages.
If the API returns binary data (not indicated here), it would be included accordingly, but this operation primarily deals with JSON responses.
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).
- The node expects the environment variable or credential to provide the correct API endpoint domain.
Troubleshooting
- Invalid or missing required fields: Ensure all required properties (paykey, description, amount, currency, payment_date, consent_type, device, external_id, config) are provided and correctly formatted.
- Authentication errors: Verify that the API key credential is correctly set up and has the necessary permissions.
- Malformed JSON in device, config, or metadata: These fields expect valid JSON strings; invalid JSON will cause parsing errors.
- API rate limits or network issues: Check connectivity and API usage limits if requests fail unexpectedly.
- Consent type mismatch: Use only the allowed values "internet" or "signed" for consent_type.
Links and References
- Straddle API Documentation (hypothetical link)
- n8n Documentation - Creating Custom Nodes
- JSON Schema Reference for device, config, and metadata objects can be found in the Straddle API docs.