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 retrieve payment reports based on specified filters and parameters. It is useful for scenarios where users need to fetch detailed payment data such as status, provider, date ranges, and other criteria to analyze or process payment information programmatically. For example, a user can get a report of payments filtered by status 'paidOut' within a specific date range or limit the number of returned entries for pagination purposes.

Use Case Examples

  1. Retrieve a list of payments with status 'confirmed' from the Go Cardless provider.
  2. Fetch payment reports filtered by organisation ID and date range for financial reconciliation.
  3. Limit the number of payment entries returned to 10 for display in a dashboard.

Properties

Name Meaning
Limit Maximum number of payment report entries to return.
Offset Starting offset for the payment report entries, useful for pagination.
Organisation Id Filter payment reports by a specific organisation ID.
Provider Filter payment reports by payment provider (e.g., Go Cardless, Smarter Pay, Stripe).
Source Filter payment reports by source (User, Billingbooth, or Provider).
Status Filter payment reports by payment status.
Created From Filter payments created from this date (start date).
Created To Filter payments created up to this date (end date).
Charge From Filter payments charged from this date (start date).
Charge To Filter payments charged up to this date (end date).

Output

JSON

  • data - The payment report data returned from the Billing Booth One API, containing details of payments matching the specified filters.

Dependencies

  • Billing Booth One API
  • An API key credential for authentication

Troubleshooting

  • Ensure the API base URL and credentials are correctly configured to avoid authentication errors.
  • Verify that the filter parameters (e.g., dates, status, provider) are valid and correctly formatted to prevent request failures.
  • If the node returns an error about missing routing information, check that the resource and operation parameters are correctly set to 'Payments' and 'Get Payment Report'.
  • For large data sets, use the 'limit' and 'offset' parameters to paginate results and avoid timeouts or memory issues.

Links

Discussion