Skip to main content
Direct model. These endpoints report on activity attributed to your customers via the customer object — see the Direct integration guide. For a member’s history on the Managed model, use Member Transactions.
Fetch a Transaction: Looks up a single transaction by the reference issued when it was created, or by its id, and reports whether the payment behind it succeeded. Unlike the two below, it serves both the Direct and Managed models — use it on the page a buyer lands on after paying. Get Customer Transactions: Retrieves a list of transactions associated with an API client’s customer, identified by the customer’s email. Get Total Transaction Volume: Retrieves the total volume of transactions conducted on an API client’s account.

​
Transaction types

Every transaction carries a type. These are the ones that describe what happened to your customer’s money or holdings: To filter a list by type, pass the filter value, not the response value — type=wht matches WITHOLDING_TAX. The filter is case-insensitive. The two list endpoints only return transactions tied to a token. A movement of money alone, such as a withdrawal of cash wallet balance, won’t appear in them; look it up with Fetch a Transaction instead.
You may occasionally see other types, such as Send, Receive or Fee. These record internal ledger movements that sit behind the types above — moving tokens between a customer’s wallets, for example — and don’t represent a separate action by your customer. Build against the types in the table and treat anything else as informational.