Skip to main content
Tesouro’s API uses graphQL. Once you are integrated, use the Reporting API to retrieve your reports programmatically.

​
Generate a report

  1. Prepare the pertinent report query.
  2. Create an $input variable to store your filters, sort order and pagination, and pass it into the query.
  3. List the fields you want returned within the query’s items field.

​
ACH notification of change

An itemized list of NOCs for a given activity date for ACH transactions.
Steps
  1. Query achNotificationsOfChange(input:$input)
  2. Create an $input variable to store your AchNotificationOfChangeInput filters, sort order and pagination, and pass it into the query.
  3. List the ach notification of change fields you want returned within the items field.

Example
Query
Inputs
Response

​
ACH return

An itemized list of ACH returns for a given activity date for ACH transactions.
Steps
  1. Query achReturns(input:$input)
  2. Create an $input variable to store your AchReturnsInput filters, sort order and pagination, and pass it into the query.
  3. List the ach return fields you want returned within the items field.

Example
Query
Inputs
Response

​
Allocation details

A comprehensive and detailed list of each money movement event for the partner and its acceptors for a given funds release date or activity date, including: settlements, disputes, processing fees, and partner-collected fees. Use this report to: reconcile partner and acceptor payments, get a detailed breakdown of a given funds release, and calculate acceptor profitability.
Steps
  1. Query allocations(input:$input)
  2. Create an $input variable to store your AllocationsInput filters, sort order and pagination, and pass it into the query.

    To return money movements for just the acceptors or partner, filter by perspective.
  3. List the allocation fields you want returned within the items field.
Query
Inputs
Response with both perspectives for same money movement

​
Authorization summary

A summary of authorization counts and amounts for the given transaction date. Can grouped by acceptor, transaction currency, response code, payment brand, and more.

Use this report to analyze your authorization rates and look for trends in declined transactions.
Steps
  1. Query authorizationSummaries(input:$input)
  2. Create an $input variable to store your AuthorizationSummaryInput filters, sort order and pagination, and pass it into the query.
  3. List the authorization summary fields you want returned within the items field.
Example query
Query
Inputs
Response

​
Fee

An itemized list of fees for a given transaction date or funds release date.
Steps
  1. Query fees(input:$input)
  2. Create an $input variable to store your StandardFeeInput filters and pagination, and pass it into your query.
  3. List the fee fields you want returned within the items field. NOTE: Transaction-level fields will present a null, “not applicable”, or empty value if the fee is not tied to a specific transaction.
Example
Query
Inputs
Response

​
Fee summary

A summary of fee counts and amounts, grouped by acceptor and fee type, for the given transaction date or funds release date. Use this report to understand the costs of your Merchant Services account.
Steps
  1. Query feeSummaries(input:$input)
  2. Create an $input variable to store your FeeSummaryInput filters, sort order and pagination, and pass it to your query.

    Note: A date filter, either feeActivityDate or fundsReleaseDate, is required.
  3. List the fee summary values and attributes you want returned under items.
-> Example
Query
Inputs
Response

​
Funding dispute events

An itemized list of financially impacting disputes events (e.g., 1st chargebacks, representments) for the given funds release date.
Steps
  1. Query fundingDisputeEvents(input:$input)
  2. Create an $input variable to store your FundingDisputeEventInput filters, sort order and pagination, and pass it to your query.
  3. List the funding dispute event fields you want returned within the items field.
Example
Query
Inputs
Response

​
Funding summary

A summary of funding activity (counts and amounts) by transaction date or funds release date. Use this report to understand the financial impact of daily sales, refunds, disputes, and associated fees, and to reconcile funds transfers to bank deposits.
Steps
  1. Query fundingSummaries(input:$input)
  2. Create an $input variable to store your FundingSummaryInput filters, sort order and pagination, and pass it to your query. Note: You must include a date range filter, either fundsReleaseDate - the date the trasnaction was funded, or transactionActivityDate - the date the transaction was submitted.
  3. List the funding summary fields you want returned within the items field.
Example
Query
Inputs
Response

​
Funding transaction

An itemized list of transactions that are in the process of being funded or were released for funding, filtered by transaction date or the date funds were released. Use this report to reconcile your payments back to your orders in order to move them to Account Receivable.
Steps
  1. Query fundingTransactions(input: $input)
  2. Create an $input variable to store your FundingTransactionInput filters, sort order and pagination, and pass it to your query.

    Note: You must include a date range filter, either fundsReleaseDate - the date the trasnaction was funded, or transactionActivityDate - the date the transaction was submitted. Results are automatically sorted by the specified date filter, descending.
  3. List the funding transaction fields you want returned in the items field.
Example
Query
Inputs
Response

​
Transaction

A list of transaction requests (including those that will be conveyed to another processor for funding) submitted on the pertinent transaction activity dates. Use this report as an operational tool to reconcile against your internal record of submitted transactions.
Steps
  1. Query paymentTransactions(input:$input)
  2. Create an $input variable to store your PaymentTransactionsInput filters and pagination, and pass it to your query.

    Note that transactionActivityDate is a required filter.
  3. List the pertinent payment transaction fields you want returned within the items field. To avoid nullable values, and to keep the data relevant, each transaction type returns its own pertinent set of fields depending on the approved or declined response.
Example
Query
Inputs
Response

​
Transaction summary

A summary of transaction counts and amounts. Use this report to reconcile transactions against your internal record of submitted transactions.
Steps
  1. Query paymentTransactionSummaries(input:$input)
  2. Create an $input variable to store your PaymentTransactionSummaryInput filters, sort order and pagination, and pass it to your query.
  3. List the transaction summary fields you want returned within the items field.
Example
Query
Inputs
Response