Actions13
- Check Actions
- Payment Actions
- Payee Actions
- Document Actions
Overview
This node integrates with an online payment and document mailing service, providing a comprehensive payment processing suite. Specifically, the Document - Save Payment Form operation allows users to save customized payment form submissions, capturing payer details and payment information.
Common scenarios for this node include:
- Recording payments made through custom payment forms embedded on websites.
- Automating bookkeeping by saving payment data directly into workflows.
- Collecting payer information alongside payment amounts and methods for further processing or reporting.
Practical example: A business uses a custom payment form on their site to accept payments via credit card, ACH transfer, or check. This node saves each submitted payment form with payer name, email, amount, and payment method, optionally including reference numbers or descriptions.
Properties
| Name | Meaning |
|---|---|
| Form ID | ID of your customized payment form |
| Payer Name | Name of the person making the payment |
| Payer Email | Email address of the payer |
| Amount | Payment amount in USD (minimum 0.01, precision up to 2 decimal places) |
| Payment Method | Method of payment used; options: Credit Card, ACH Transfer, Check |
| Additional Fields | Optional extra fields including: |
| - Reference Number | Invoice or reference number |
| - Description | Payment description or notes |
| - Custom Fields (JSON) | Additional custom form fields provided as JSON object |
Output
The node outputs a JSON object representing the saved payment form data. This typically includes all input fields along with any metadata returned by the external service confirming the save operation.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for the connected online payment/document service.
- The node depends on the external service's API to save payment form data.
- Proper configuration of the API authentication within n8n credentials is necessary.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing invalid email formats or negative payment amounts will likely trigger validation errors.
- Incorrect or missing required fields such as Form ID, Payer Name, or Amount will prevent successful submission.
Error messages:
- Errors related to "Unknown resource" indicate misconfiguration of the Resource parameter.
- Validation errors from the API may mention missing required fields or invalid data formats.
- Network or API errors should be checked by verifying connectivity and API key validity.
To resolve these, ensure all required fields are correctly filled, the API key is valid and active, and that the node parameters match the expected values.
Links and References
- Refer to the official OnlineCheckWriter API documentation for detailed field definitions and examples.
- n8n documentation on creating and using API credentials.
- General best practices for handling payment data securely in automation workflows.