OnlineCheckWriter

Complete payment processing suite - checks, ACH, wire transfers, virtual cards, and document mailing

Actions13

Check Actions
- Create
- Email
- Get
- List
- Mail
- Print
- Void
Payment Actions
Payee Actions
- Create
Document Actions
- Mail Document
- Save Payment Form

Overview

This node enables processing credit card payments through the "Payment" resource with the "Credit Card Payment" operation. It is designed to facilitate secure and flexible payment transactions by accepting detailed card information and optional customer/payment metadata.

Common scenarios where this node is beneficial include:

E-commerce platforms needing to process customer credit card payments.
Subscription services charging customers automatically.
Businesses wanting to save card details for future payments or send receipts automatically.
Situations requiring tax and tip amounts to be added to a payment.

Practical example: A small online store can use this node to charge customers' credit cards securely, optionally save their card for faster checkout next time, and email them a receipt immediately after payment.

Properties

Name	Meaning
Amount	Payment amount in USD. Must be at least $0.50. Supports two decimal places (e.g., 50.00).
Card Number	Credit card number without spaces or dashes. Input is masked for security.
CVV	Card security code (3 or 4 digits), input is masked.
Expiry Month	Card expiration month. Options range from "01 - January" to "12 - December".
Expiry Year	Card expiration year as 4 digits (e.g., 2025). Validated to ensure correct format.
Cardholder Name	Name exactly as it appears on the credit card.
Billing ZIP Code	ZIP code of the billing address used for Address Verification Service (AVS). Must be either 5 digits or ZIP+4 format (e.g., 94105 or 94105-6789).
Payment Options	Collection of optional settings: • Customer Email: Email address for sending receipts and notifications. • Customer ID: Existing customer identifier if saving or using saved card. • Description: Text shown on statement. • Save Card: Boolean to save card details for future use (requires customer email). • Send Receipt: Boolean to email payment receipt. • Statement Descriptor: Text (max 22 chars) appearing on customer's credit card statement. • Tax Amount: Tax included in payment. • Tip Amount: Additional tip amount to add.

Output

The node outputs JSON data representing the result of the credit card payment transaction. This typically includes confirmation details such as transaction ID, status, amount charged, and any relevant metadata returned by the payment processor.

If the payment is successful, the output JSON will contain fields confirming the processed payment. In case of failure, error information will be provided.

The node does not output binary data.

Dependencies

Requires an API key credential for authenticating with the OnlineCheckWriter payment processing service.
The node depends on the external OnlineCheckWriter API to process credit card payments.
Proper configuration of the API authentication credential within n8n is necessary.
Network connectivity to the OnlineCheckWriter service endpoint is required.

Troubleshooting

Invalid Card Details: Errors may occur if card number, CVV, expiry date, or billing ZIP code are invalid or incorrectly formatted. Ensure all inputs meet the specified validation rules.
Insufficient Funds or Declined Card: The payment processor may reject the transaction due to insufficient funds or card restrictions.
Missing Required Fields: All required properties must be provided; missing mandatory fields like amount or card number will cause errors.
API Authentication Failures: Incorrect or expired API credentials will prevent successful communication with the payment service.
Validation Errors: For example, entering a non-4-digit expiry year or improperly formatted ZIP code will trigger validation errors with descriptive messages.
Saving Card Without Email: Attempting to save card details without providing a customer email will likely fail since the email is required for saving cards.

To resolve issues:

Double-check all input values against the property descriptions and validation rules.
Verify API credentials and network access.
Review error messages returned in the node output for specific guidance.