# ChargeOver integrations: customers and invoices

> Create a customer, create an invoice and create a subscription in ChargeOver, and start a workflow when ChargeOver sends “Customer created”.

**Canonical page:** https://tray.ai/connectors/chargeover-integrations/
**Categories:** Finance
**Connects through:** HTTP Connector

## Overview

ChargeOver is recurring billing and invoicing software that automates subscriptions, card and ACH payments, dunning and customer payment portals. Tray.ai connects to ChargeOver through the HTTP Connector, so your workflows can call the ChargeOver API alongside the rest of your stack.

## Use cases

### Customers

Create, update, and delete customers in ChargeOver from any Tray.ai workflow. The ChargeOver API covers calls such as create a customer and query customers.

- Create a customer
- Query customers
- Update a customer

### Invoices

Create and update invoices in ChargeOver from any Tray.ai workflow. The ChargeOver API covers calls such as create an invoice and query invoices.

- Create an invoice
- Query invoices
- Update an invoice

### Subscriptions

Create and delete subscriptions in ChargeOver from any Tray.ai workflow. The ChargeOver API covers calls such as create a subscription and query subscriptions.

- Create a subscription
- Query subscriptions
- Upgrade a subscription

### ChargeOver events

Start a Tray.ai workflow the moment something happens in ChargeOver. ChargeOver sends events such as customer created and customer updated to a Tray.ai webhook trigger.

- Customer created
- Customer updated
- Invoice created

## Challenges Tray.ai solves

### Keeping ChargeOver credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store ChargeOver credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the ChargeOver API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the ChargeOver API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to ChargeOver?

Yes. Tray.ai connects to ChargeOver through the HTTP Connector, which calls the ChargeOver API directly. Any call the ChargeOver API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with ChargeOver?

The ChargeOver API uses basic authentication. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated ChargeOver connector?

ChargeOver runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated ChargeOver connector from the ChargeOver API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/