Get stats for an org or paypoint
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Long-lived API token sent in the requestToken header. See API token authentication.
Path parameters
Frequency to group series. Allowed values:
m- monthlyw- weeklyd- dailyh- hourly
For example, w groups the results by week.
The entry level for the request:
- 0 for Organization
- 2 for Paypoint
Mode for the request. Allowed values:
custom- Allows you to set a custom date rangeytd- Year To Datemtd- Month To Datewtd- Week To Datetoday- All current daym12- Last 12 monthsd30- Last 30 daysh24- Last 24 hourslasty- Last Yearlastm- Last Monthlastw- Last Weekyesterday- Last Day
Query parameters
Used with custom mode. The end date for the range.
Valid formats:
- YYYY-mm-dd
- YYYY/mm/dd
- mm-dd-YYYY
- mm/dd/YYYY
Used with custom mode. The start date for the range.
Valid formats:
- YYYY-mm-dd
- YYYY/mm/dd
- mm-dd-YYYY
- mm/dd/YYYY
Response
The time bucket for this row, formatted according to the query’s freq (for example, 2025-11 for a monthly bucket). The response returns one object per bucket across the requested range.
Cumulative number of vendors, as a running total through the end of this bucket rather than a per-bucket count. On the payout (money out) side, “customers” are vendors.
Number of vendors created during this bucket, scoped to the paypoint (level 2) or organization (level 0).
Count of payout (money out) transactions. The payout method counts (outCardTransactions, outVCardTransactions, outACHTransactions, outCheckTransactions, outPendingMethodTransactions, outRTPTransactions, outWireTransactions) are mutually exclusive and together account for this total.
Count of payout transactions sent by virtual card (vCard).
Count of payout transactions sent by real-time payments (RTP).
Count of approved inbound (money in) transactions. This counts approved transactions only and leaves out declines. The payment method counts (inCardTransactions, inACHTransactions, inCheckTransactions, inCashTransactions, inWalletTransactions) are mutually exclusive and sum to this total.
Count of approved inbound transactions charged by a recurring schedule. This is a subset of inTransactions, not an amount to add on top of it.
Cumulative number of customers, as a running total through the end of this bucket rather than a per-bucket count.
Number of customers created during this bucket, scoped to the paypoint (level 2) or organization (level 0).
Count of approved inbound card transactions, including card, cloud device, and in-person device payments.
Count of card chargebacks recorded. Tracked separately from inACHReturns.