Billing Booth One icon

Billing Booth One

Interact with Billing Booth One API

Actions476

Overview

This node interacts with the Billing Booth One API to perform various operations related to billing and payments. Specifically, the 'Take Payment' operation under the 'Payments' resource allows users to process a payment for a customer by specifying details such as customer ID, payment amount, description, and payment provider settings. This node is useful for automating payment processing workflows, integrating payment collection into business processes, and managing billing operations programmatically.

Use Case Examples

  1. Automatically take a payment from a customer when an order is completed.
  2. Process payments linked to specific invoices by providing invoice IDs.
  3. Record payments with optional payment dates for accurate financial tracking.

Properties

Name Meaning
Customer Id Unique identifier of the customer for whom the payment is being taken.
Description Description of the payment as it appears on the payment provider's system.
Amount The amount of money to be taken as payment.
Payment Provider Settings Id Identifier for the payment provider settings to be used for processing the payment.
Additional Body Fields Optional additional fields such as invoice ID and payment date to provide more context for the payment.

Output

JSON

  • data - The response data from the Billing Booth One API after taking the payment, typically including payment confirmation details.

Dependencies

  • Requires an API key credential for Billing Booth One API authentication.

Troubleshooting

  • Common issues include missing or incorrect required parameters such as customer ID, amount, or payment provider settings ID, which will cause the API request to fail.
  • Errors related to authentication usually indicate invalid or missing API credentials; ensure the API key is correctly configured.
  • If the binary property name is specified but the binary data is missing, the node will throw an error indicating the binary property does not exist on the item.
  • Network or API endpoint errors can occur if the base URL is incorrect or the API service is unavailable; verify the base URL and network connectivity.

Links

Discussion