# Poof integrations: checkout, invoices and wallets

> Create a checkout, create an invoice and create a wallet in Poof. Connect Poof to the rest of your finance stack with Tray.ai.

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

## Overview

Poof is a payments platform for developers that handles crypto wallets, checkouts, invoices, and ACH bank transfers through a single API. Tray.ai connects to Poof through the HTTP Connector, so your workflows can call the Poof API alongside the rest of your stack.

## Use cases

### Checkout

Create checkout in Poof from any Tray.ai workflow. The Poof API covers calls such as create a checkout and create a payment link.

- Create a checkout
- Create a payment link

### Invoices

Create invoices in Poof from any Tray.ai workflow. The Poof API covers calls such as create an invoice and create a charge.

- Create an invoice
- Create a charge

### Wallets

Read and create wallets in Poof from any Tray.ai workflow. The Poof API covers calls such as create a wallet and create a deposit address.

- Create a wallet
- Create a deposit address
- Check a balance

### Transactions

Read and create transactions in Poof from any Tray.ai workflow. The Poof API covers calls such as fetch a transaction and fetch all transactions.

- Fetch a transaction
- Fetch all transactions
- Send a transaction

### ACH transfers

Read and create ach transfers in Poof from any Tray.ai workflow. The Poof API covers calls such as create an ACH debit and check transfer status.

- Create an ACH debit
- Check transfer status

## Challenges Tray.ai solves

### Keeping Poof 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 Poof 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 Poof 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 Poof 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 Poof?

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

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

The Poof API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Poof connector?

Poof runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Poof connector from the Poof 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/