> ## Documentation Index > Fetch the complete documentation index at: https://docs.tesouro.com/llms.txt > Use this file to discover all available pages before exploring further. # API Query > Retrieve reporting data programmatically using GraphQL queries with filtering, sorting, and pagination for all report types. Tesouro's API uses [graphQL](/acquiring/guides/getting-started/api). Once you are [integrated](/acquiring/guides/integration/overview), use the Reporting API to retrieve your reports programmatically. | Report | Query | | --------------------------------------------------------------- | ------------------------------- | | [ACH notification of change (NOC)](#ach-notification-of-change) | `achNotificationsOfChange()` | | [ACH return](#ach-return) | `achReturns()` | | [Allocation details](#allocation-details) | `allocations()` | | [Authorization summary](#authorization-summary) | `authorizationSummaries()` | | [Fee](#fee) | `fees()` | | [Fee summary](#fee-summary) | `feeSummaries()` | | [Funding dispute events](#funding-dispute-events) | `fundingDisputeEvents()` | | [Funding summary](#funding-summary) | `fundingSummaries()` | | [Funding transaction](#funding-transaction) | `fundingTransactions()` | | [Transaction](#transaction) | `paymentTransactions()` | | [Transaction summary](#transaction-summary) | `paymentTransactionSummaries()` | ### 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. | Input | Description | | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `where` | Used to filter the data and specify the groupings on summary reports. All reports require a date filter (unless noted), and offer a number of optional filters. | | `orderBy` | Used to specify the order of the results. Available only on summary reports. | | `paging` | Used to specify how many records to return using:

`skip` tells the query to "skip" over a specified number of records. If you are requesting all records to be contained within a single page, set this field to `skip:0`, or if you plan to request the results across multiple pages, set this field to the number of records you want returned on the given page, e.g., `skip:50`.

`take` is used to limit the number of records returned after the skip. e.g., If `skip:0, take:100`, then the response will return the first 100 records, i.e., rows 1-100. If `skip:100, take:100`, then the response will return the second set of 100 records, i.e., rows 101-200.

For reports in which you expect a large number of records, e.g., tens or hundreds of thousands (which is typical for itemized transaction reports like [Transaction](#transaction), [Funding transaction](#funding-transaction), or [Fee](#fee)), consider returning the records in sets of `500` or `1000` or more. For summmary reports, where there are not as many rows, a lower skip and take usually fine, e.g., `skip:0, take:100`.

Experiment to see what works best for you and your reports. | 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](/acquiring/reference/graphql/types/achnotificationofchangeinput) filters, sort order and pagination, and pass it into the query. | Filter | Description | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `activityDate` | The date the notification of change was received by Tesouro. | | `paymentId` | A unique 36 character identifier created by Tesouro and assigned to a group of transactions in the same payment request cohort. e.g., An ACH bank transfer, refund, notification of change, or [ACH return](/acquiring/reporting/api#ach-return) | 3. List the [ach notification of change](/acquiring/reference/graphql/types/achnotificationofchange) fields you want returned within the `items` field.
**Example** ```graphql Query lines expandable theme={null} query ExampleNotificationsOfChange(input: $input) { achNotificationsOfChange(input: $input) { items { accountNumber accountNumberUpdated accountType accountTypeUpdated activityDate changeReason changeReasonCode id routingNumber routingNumberUpdated transactionActivityDate transactionAmount transactionCurrency transactionDateTime transactionId transactionReference transactionType acceptor { businessName reference id } } pageInfo { hasNextPage hasPreviousPage } } } ``` ```json Inputs lines theme={null} { "input": { "where": { "activityDate": { "gte": "2025-03-24", "lte": "2025-03-24" } }, "paging": { "skip": 0, "take": 100 } } } ``` ```json Response lines expandable theme={null} { "data": { "achNotificationsOfChange": { "items": [ { "organization": { "id": "ab3d6f2d-9f4f-4731-ab2f-b63b7844ca3f" }, "acceptor": { "businessName": "Operational Heartbeat Acceptor", "reference": "Tesouro Universe Simulation, Inc", "id": "f5f5dc3d-bc68-4f43-bcc5-dd8fe88fda76" }, "id": "16ccdcb1-4507-4cbf-be49-6742be0919d8", "accountNumber": "12334567890", "accountNumberUpdated": "987765543", "accountType": "CHECKING", "accountTypeUpdated": null, "activityDate": "2025-03-25", "changeReason": "Incorrect DFI Account Number", "changeReasonCode": "C01", "routingNumber": "111111111", "routingNumberUpdated": null, "transactionActivityDate": "2025-03-21", "transactionAmount": 1.01, "transactionCurrency": "USD", "transactionDateTime": "2025-03-21T09:00:00.000Z", "transactionId": "1a3615b1-0b10-4d5a-8b1e-ece5ac91e028", "transactionReference": "ac321561-e910-4f26-8180-86ba1e56bb53", "transactionType": "SALE" }, { "organization": { "id": "ab3d6f2d-9f4f-4731-ab2f-b63b7844ca3f" }, "acceptor": { "businessName": "Operational Heartbeat Acceptor", "reference": "Tesouro Universe Simulation, Inc", "id": "f5f5dc3d-bc68-4f43-bcc5-dd8fe88fda76" }, "id": "715f9197-0a51-4365-9d99-19ce10036d21", "accountNumber": "12334567890", "accountNumberUpdated": null, "accountType": "CHECKING", "accountTypeUpdated": null, "activityDate": "2025-03-25", "changeReason": "Incorrect Routing Number", "changeReasonCode": "C02", "routingNumber": "222222222", "routingNumberUpdated": "777777777", "transactionActivityDate": "2025-03-21", "transactionAmount": 1.02, "transactionCurrency": "USD", "transactionDateTime": "2025-03-21T10:00:00.000Z", "transactionId": "2dae9a9b-f743-41bb-8c49-769328b567ea", "transactionReference": "9f907462-6bea-49a0-a4ba-5ed6b4949dac", "transactionType": "SALE" }, {...}, {...} ] } } } ``` ***
## ACH return An itemized list of [ACH return](/acquiring/reporting/api#ach-return)s for a given activity date for ACH transactions.
Steps 1. Query `achReturns(input:$input)` 2. Create an `$input` variable to store your [AchReturnsInput](/acquiring/reference/graphql/types/achreturnsinput) filters, sort order and pagination, and pass it into the query. | Filter | Description | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `id` | The unique id of the ach return that was generated by Tesouro. | | `acceptorId` | The unique, 36 character identifier assigned to the entity providing the goods or services to the customer. Other processors may refer to this as the Merchant ID (MID), Outlet ID, or Customer number. | | `activityDate` | The date the notification of change was received by Tesouro. | | `reasonCode` | Nacha Return Codes and associated ISO Status Reason Codes for returns and reversals from the External Code List. | | `transactionActivityDate` | The date Tesouro recognized the original ach payment request based upon the acceptor cutoff. | | `transactionId` | A unique identifier assigned by Tesouro to the original ach transaction. | | `transactionReference` | A unique identifier from original ach transaction created by the entity holding the direct relationship with the Acceptor. Tesouro uses this identifier to manage idempotency. | | `transactionType` | The type of original ach transaction, e.g., Sale or Refund. | 3. List the [ach return](/acquiring/reference/graphql/types/achreturn) fields you want returned within the `items` field.
**Example** ```graphql Query lines expandable theme={null} query AchReturns($input: AchReturnsInput!) { achReturns(input: $input) { items { id acceptor { businessName reference id } accountNumberEndingIn accountOwnerName accountOwnerType accountType activityDate amount currency organization { id } reasonCode reason routingNumber traceNumber transactionActivityDate transactionAmount transactionDateTime transactionId transactionReference transactionTraceNumber transactionType } } } ``` ```json Inputs lines theme={null} { "input": { "where": { "activityDate": { "gte": "2025-03-24", "lte": "2025-03-24" } }, "paging": { "skip": 0, "take": 100 } } } ``` ```json Response lines expandable theme={null} { "data": { "achReturns": { "items": [ { "id": "66401e9b-e86a-42a8-945b-b2d771d1ab6b", "organization": { "id": "ab3d6f2d-9f4f-4731-ab2f-b63b7844ca3f" }, "acceptor": { "businessName": "Operational Heartbeat Acceptor", "reference": "Tesouro Universe Simulation, Inc", "id": "f5f5dc3d-bc68-4f43-bcc5-dd8fe88fda76" }, "accountNumberEndingIn": "9258", "accountOwnerName": "R9GNPr39N", "accountOwnerType": "CONSUMER", "accountType": "SAVINGS", "activityDate": "2025-03-24", "amount": 100.05, "currency": "USD", "reason": "Returned due to ODFI's request", "reasonCode": "R06", "routingNumber": "555555555", "traceNumber": "1111111116", "transactionActivityDate": "2025-03-21", "transactionAmount": 100.05, "transactionDateTime": "2025-03-13T00:00:38.607Z", "transactionId": "506c586b-7085-4067-a415-1d9700fc9fc2", "transactionReference": "f03609e8-0bbf-4b91-9435-d777283aae15", "transactionTraceNumber": "1111111116", "transactionType": "SALE" }, { "id": "f85e012d-2bc1-40de-a352-25482a935b63", "organization": { "id": "ab3d6f2d-9f4f-4731-ab2f-b63b7844ca3f" }, "acceptor": { "businessName": "Operational Heartbeat Acceptor", "reference": "Tesouro Universe Simulation, Inc", "id": "f5f5dc3d-bc68-4f43-bcc5-dd8fe88fda76" }, "accountNumberEndingIn": "9258", "accountOwnerName": "R9GNPr39N", "accountOwnerType": "CONSUMER", "accountType": "SAVINGS", "activityDate": "2025-03-25", "amount": 100.06, "currency": "USD", "reason": "Authorization revoked by customer", "reasonCode": "R07", "routingNumber": "666666666", "traceNumber": "1111111117", "transactionActivityDate": "2025-03-22", "transactionAmount": 100.06, "transactionDateTime": "2025-03-13T00:00:38.607Z", "transactionId": "6de41c6e-5f74-4bd0-beea-0fa17be4c83e", "transactionReference": "6f713dcf-2867-4087-841f-1c4dcdc1da47", "transactionTraceNumber": "1111111117", "transactionType": "REFUND" }, { "id": "e597cdeb-182c-4b85-b5e3-e97c3ac722cf", "organization": { "id": "ab3d6f2d-9f4f-4731-ab2f-b63b7844ca3f" }, "acceptor": { "businessName": "Operational Heartbeat Acceptor", "reference": "Tesouro Universe Simulation, Inc", "id": "f5f5dc3d-bc68-4f43-bcc5-dd8fe88fda76" }, "accountNumberEndingIn": "9258", "accountOwnerName": "R9GNPr39N", "accountOwnerType": "CONSUMER", "accountType": "SAVINGS", "activityDate": "2025-03-23", "amount": 100.04, "currency": "USD", "reason": "Invalid account number.", "reasonCode": "R05", "routingNumber": "444444444", "traceNumber": "1111111115", "transactionActivityDate": "2025-03-20", "transactionAmount": 100.04, "transactionDateTime": "2025-03-13T00:00:38.607Z", "transactionId": "9e3b8691-b869-4bc4-9a23-75267445c81b", "transactionReference": "63971b91-7e12-4f41-a2c7-d792cb5a5646", "transactionTraceNumber": "1111111115", "transactionType": "SALE" } ] } } } ``` ***
## 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](/acquiring/reference/graphql/types/feeinput) filters, sort order and pagination, and pass it into the query.

To return money movements for just the acceptors or partner, filter by `perspective`. | Filter | Description | | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `acceptorId` | A unique, 36 character identifier created by Tesouro and assigned to the entity providing the goods or services to the customer, such as a Merchant, a Submerchant of a Payment Facilitator, a Seller within a Marketplace, or a Biller of a Consumer Bill Payment Service Provider (CBPS). Historically, processors have called this identifier the Merchant ID (or MID), Outlet ID, or Customer number. | | `activityDate` | The date the allocation was applied. | | `billableEventCurrency` | The currency of the billable event on which the allocation is assessed, formatted in ISO 4217 alphabetic code. | | `feeType` | The [type of allocation](/acquiring/reference/graphql/types/allocationfeetype), e.g., Settlement, Interchange, Network fee, Processor fee, Partner fee, etc. | | `fundingCurrency` | The currency of the funded allocation, formatted in ISO 4217 alphabetic code. | | `fundsReleaseDate` | The date that Tesouro releases the funds from its bank account to the recipient's bank account. | | `fundsTransferid` | A unique identifier created and used by Tesouro, and assigned to the transfer of money to a bank account, to identify a cohort of funded transactions making up the transfer. | | `paymentBrand` | The [payment brand used](/acquiring/reference/graphql/types/paymentbrand), e.g., Visa, Mastercard, Discover, American Express, etc. | | `paymentId` | A unique 36 character identifier created by Tesouro and assigned to a group of transactions in the same payment request cohort. e.g., An authorization request, incremental authorization request, and the final capture would have the same paymentID. NOTE: This field will present a null, not applicable, or empty value if the fee is not tied to a specific transaction. | | `perspective` | The perspective of the allocation, which can be either 'ACCEPTOR' or 'PARTNER'. This field is used to determine the perspective from which the allocation is reported. | 3. List the [allocation](/acquiring/reference/graphql/types/allocationdetail) fields you want returned within the `items` field.
```graphql Query lines expandable theme={null} query ExampleQuery($input: FeeInput!) { allocations(input: $input) { items { organization { id businessName } acceptor { id businessName reference } presenterId rateUnitAmount rateMultiplier allocationType name description allocationCalculatedAmount productPillar activityDate transactionDateTime billableEventAmount accountNumberPrefix accountNumberSuffix paymentFundingSource fundingCurrency billableEventCurrency merchantCategory processingNetwork orderReference transactionReference fundsTransferDescriptor fundsReleaseDate fundsTransferId billableEventType paymentId transactionId billingEventSourceId billingEventSourceType perspective } pageInfo { hasNextPage } } } ``` ```graphql Inputs lines theme={null} { input: { where: { standardFeeFilter: { perspective: { eq: ACCEPTOR } acceptorId: {eq: "2d8b19ee-8830-4a28-964f-9d6c5a54205e"} fundsReleaseDate: { gte: "2025-07-23", lte: "2025-07-23" } } } paging: { take: 100, skip: 0 } } } ``` ```json title="Response with both perspectives for same money movement" lines expandable theme={null} { "data": { "allocations": { "items": [ { "organization": { "id": "c292e6b-8308-4d51-b63b-cab658cf6fbc", "businessName": "EmpirePay" }, "acceptor": { "id": "2d8b19ee-8830-4a28-964f-9d6c5a54205e", "businessName": "Beskar Steelworks", "reference": "EMPIRE_18432902001" }, "presenterId": "05942170-3f93-4d6b-8446-7413e86ff94d", "rateUnitAmount": 0, "rateMultiplier": 100, "allocationType": "ACCEPTOR_SETTLEMENT", "name": "Acceptor Settlement", "description": "Settlement designation for accounting purposes to the acceptor", "allocationCalculatedAmount": -100, "productPillar": "TRANSACTION_PROCESSING", "activityDate": "2025-07-22", "transactionDateTime": "2025-07-22T18:49:08.263Z", "billableEventAmount": 100, "accountNumberPrefix": "414718", "accountNumberSuffix": "8480", "paymentFundingSource": "CREDIT", "fundingCurrency": "USD", "billableEventCurrency": "USD", "merchantCategory": "7399", "processingNetwork": "VISA", "orderReference": "O-5492214952", "transactionReference": "0a00b6e7-06be-4ec7-b1b0-dd5c1235a804", "fundsTransferDescriptor": null, "fundsReleaseDate": "2025-07-23", "fundsTransferId": "1a7e3319-bf7c-4f2f-a894-6ac6b06aecc9", "billableEventType": "CLEARED_REFUND", "paymentId": "49636ae2-5743-11f0-904a-48134c6cd00d", "transactionId": "8d07659e-672c-11f0-a7a5-24cb09b14382", "billingEventSourceId": "8d07659e-672c-11f0-a7a5-24cb09b14382", "billingEventSourceType": "TRANSACTION", "perspective": "ACCEPTOR" }, { "organization": { "id": "c292e6b-8308-4d51-b63b-cab658cf6fbc", "businessName": "EmpirePay" }, "acceptor": { "id": "2d8b19ee-8830-4a28-964f-9d6c5a54205e", "businessName": "Beskar Steelworks", "reference": "EMPIRE_18432902001" }, "presenterId": "05942170-3f93-4d6b-8446-7413e86ff94d", "rateUnitAmount": 0, "rateMultiplier": 100, "allocationType": "ACCEPTOR_SETTLEMENT", "name": "Acceptor Settlement", "description": "Settlement designation for accounting purposes to the acceptor", "allocationCalculatedAmount": 100, "productPillar": "TRANSACTION_PROCESSING", "activityDate": "2025-07-22", "transactionDateTime": "2025-07-22T18:49:08.263Z", "billableEventAmount": 100, "accountNumberPrefix": "414718", "accountNumberSuffix": "8480", "paymentFundingSource": "CREDIT", "fundingCurrency": "USD", "billableEventCurrency": "USD", "merchantCategory": "7399", "processingNetwork": "VISA", "orderReference": "O-5492214952", "transactionReference": "0a00b6e7-06be-4ec7-b1b0-dd5c1235a804", "fundsTransferDescriptor": null, "fundsReleaseDate": "2025-07-23", "fundsTransferId": "1f0a2d74-4695-476c-b180-afa7af9dfed4", "billableEventType": "CLEARED_REFUND", "paymentId": "49636ae2-5743-11f0-904a-48134c6cd00d", "transactionId": "8d07659e-672c-11f0-a7a5-24cb09b14382", "billingEventSourceId": "8d07659e-672c-11f0-a7a5-24cb09b14382", "billingEventSourceType": "TRANSACTION", "perspective": "PARTNER" } ], "pageInfo": { "hasNextPage": false } } } } ```
*** ## 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](/acquiring/reference/graphql/types/authorizationsummaryinput) filters, sort order and pagination, and pass it into the query. | Filter | Description | | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `acceptorId` | A unique, 36 character identifier created by Tesouro and assigned to the entity providing the goods or services to the customer, such as a Merchant, a Submerchant of a Payment Facilitator, a Seller within a Marketplace, or a Biller of a Consumer Bill Payment Service Provider (CBPS). Historically, processors have called this identifier the Merchant ID (or MID), Outlet ID, or Customer number. | | `transactionActivityDate` | **Required.** The date Tesouro recognized the payment request based upon the acceptor cutoff. Formatted as 2024-03-27 | | `transactionCurrency` | The currency specified on the transaction request, in ISO 4217 alpha currency code format. | 3. List the [authorization summary](/acquiring/reference/graphql/types/authorizationsummary) fields you want returned within the `items` field.
**Example query** ```graphql Query lines expandable theme={null} query ExampleQuery($input: AuthorizationSummaryInput!) { authorizationSummaries(input: $input) { items { acceptor { businessName reference id } transactionCurrency transactionCount transactionAmountApproved transactionAmountRequested processorResponseCode processorResponseMessage avsResponse securityCodeNetworkResponse paymentChannel merchantCategory transactionType paymentFundingSource approvalStatus transactionActivityDate paymentBrand processingNetwork } } } ``` ```json Inputs lines expandable theme={null} { "input": { "where": { "transactionActivityDate": { "eq": "2024-11-04" } }, "paging": { "skip": 0, "take": 100 }, "orderBy": [ { "field": "TRANSACTION_ACTIVITY_DATE", "sortDirection": "DESC" } ] } } ``` ```json Response lines expandable theme={null} { "data": { "authorizationSummaries": { "items": [ { "acceptor": { "businessName": "Operational Heartbeat Acceptor", "reference": "Tesouro Universe Simulation, Inc", "id": "f5f5dc3d-bc68-4f43-bcc5-dd8fe88fda76" }, "transactionCurrency": "USD", "transactionCount": 31, "transactionAmountApproved": 422.65, "transactionAmountRequested": 422.65, "processorResponseCode": "A0000", "processorResponseMessage": "Full amount approved.", "avsResponse": "ADDRESS_MATCHED_POSTALCODE_MATCHED", "securityCodeNetworkResponse": "MATCHED", "paymentChannel": "ECOMMERCE", "merchantCategory": "8099", "transactionType": "AUTHORIZATION", "paymentFundingSource": "CREDIT", "approvalStatus": "APPROVED", "transactionActivityDate": "2024-11-04", "paymentBrand": "AMERICAN_EXPRESS", "processingNetwork": "AMERICAN_EXPRESS" }, { "acceptor": { "businessName": "Operational Heartbeat Acceptor", "reference": "Tesouro Universe Simulation, Inc", "id": "f5f5dc3d-bc68-4f43-bcc5-dd8fe88fda76" }, "transactionCurrency": "USD", "transactionCount": 2, "transactionAmountApproved": 38.03, "transactionAmountRequested": 38.03, "processorResponseCode": "D1003", "processorResponseMessage": "Lost or stolen card.", "avsResponse": "ADDRESS_MISMATCHED_POSTALCODE_MATCHED", "securityCodeNetworkResponse": "MISMATCHED", "paymentChannel": "ECOMMERCE", "merchantCategory": "8099", "transactionType": "AUTHORIZATION", "paymentFundingSource": "DEBIT", "approvalStatus": "APPROVED", "transactionActivityDate": "2024-11-04", "paymentBrand": "VISA", "processingNetwork": "VISA" } ] } } } ```
## 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](/acquiring/reference/graphql/types/standardfeefilterinput) filters and pagination, and pass it into your query. | Filter | Description | | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `acceptorId` | A unique, 36 character identifier created by Tesouro and assigned to the entity providing the goods or services to the customer, such as a Merchant, a Submerchant of a Payment Facilitator, a Seller within a Marketplace, or a Biller of a Consumer Bill Payment Service Provider (CBPS). Historically, processors have called this identifier the Merchant ID (or MID), Outlet ID, or Customer number. | | `activityDate` | The date the fee was applied. | | `billableEventCurrency` | The currency of the billable event on which the fee is assessed, formatted in ISO 4217 alphabetic code. | | `feeType` | The [type of fee](/acquiring/reference/graphql/types/allocationfeetype), e.g., Interchange, Network, Processor, Partner, etc. | | `fundingCurrency` | The currency of the funded transaction, formatted in ISO 4217 alphabetic code. | | `fundsReleaseDate` | The date that Tesouro releases the funds from its bank account to the recipient's bank account. | | `fundsTransferid` | A unique identifier created and used by Tesouro, and assigned to the transfer of money to a bank account, to identify a cohort of funded transactions making up the transfer. | | `paymentBrand` | The [payment brand used](/acquiring/reference/graphql/types/paymentbrand), e.g., Visa, Mastercard, Discover, American Express, etc. | | `paymentId` | A unique 36 character identifier created by Tesouro and assigned to a group of transactions in the same payment request cohort. e.g., An authorization request, incremental authorization request, and the final capture would have the same paymentID. NOTE: This field will present a null, not applicable, or empty value if the fee is not tied to a specific transaction. | | `perspective` | The perspective of the allocation, which can be either 'ACCEPTOR' or 'PARTNER'. This field is used to determine the perspective from which the allocation is reported. | 3. List the [fee](/acquiring/reference/graphql/types/fee) fields you want returned within the `items` field. NOTE: [Transaction](/acquiring/reporting/api#transaction)-level fields will present a null, "not applicable", or empty value if the fee is not tied to a specific transaction.
**Example** ```graphql Query lines expandable theme={null} query ExampleFees($input: FeeInput!) { fees(input: $input) { items { name feeType billableEventType fundingCurrency billableEventAmount rateMultiplier rateUnitAmount feeCalculatedAmount activityDate fundsReleaseDate paymentId transactionReference transactionId activityDate orderReference merchantCategory processingNetwork paymentBrand perspective consumerType paymentFundingSource paymentProduct fundsTransferDescriptor fundsTransferId acceptor { businessName reference id } } } } ``` ```json Inputs lines expandable theme={null} { "input": { "where": { "standardFeeFilter": { "activityDate": { "eq": "2024-11-04" } } }, "paging": { "skip": 0, "take": 1000 } } } ``` ```json Response lines expandable theme={null} { "data": { "fees": { "items": [ { "name": "Mastercard Network Access Brand Usage (NABU) - Auth", "feeType": "NETWORK_FEE", "billableEventType": "AUTHORIZED", "fundingCurrency": "USD", "billableEventAmount": 19.3, "rateMultiplier": 0, "rateUnitAmount": 0.0195, "feeCalculatedAmount": -0.0195, "activityDate": "2024-11-02", "fundsReleaseDate": "2024-11-04", "paymentId": "90a533e9-9976-11ef-a458-6421c99e5e24", "transactionReference": "089b488b-faed-e157-dd3e-8fc6a5e44c22", "transactionId": "90a533e9-9976-11ef-a458-6421c99e5e24", "orderReference": "ded61e0a-6dbe-4311-a77d-98f029feb69a", "merchantCategory": "8099", "processingNetwork": "MASTERCARD", "paymentBrand": "MASTERCARD", "consumerType": "CONSUMER", "paymentFundingSource": "CREDIT", "paymentProduct": "MASTERCARD MIXED", "perspective": "PARTNER", "fundsTransferDescriptor": null, "fundsTransferId": "6402afc6-ca70-4a17-b5da-58a216dfabb0", "acceptor": { "businessName": "Operational Heartbeat Acceptor", "reference": "Tesouro Universe Simulation, Inc", "id": "f5f5dc3d-bc68-4f43-bcc5-dd8fe88fda76" } }, { "name": "Interchange Giveback", "feeType": "INTERCHANGE_FEE", "billableEventType": "DISPUTE", "fundingCurrency": "USD", "billableEventAmount": 9.57, "rateMultiplier": 0, "rateUnitAmount": 0, "feeCalculatedAmount": 0, "activityDate": "2024-11-05", "fundsReleaseDate": null, "paymentId": "0022d556-9832-11ef-96a9-9c30b9655b25", "transactionReference": "e01d1abc-1e2d-0295-1669-fcb49b2f463f", "transactionId": "0027b6fc-9832-11ef-9170-a15cf4bb83cc", "orderReference": null, "merchantCategory": "8099", "processingNetwork": "DISCOVER", "paymentBrand": "DISCOVER", "consumerType": "CONSUMER", "paymentFundingSource": "CREDIT", "paymentProduct": "Consumer Credit - Rewards", "fundsTransferDescriptor": null, "fundsTransferId": null, "acceptor": { "businessName": "Operational Heartbeat Acceptor", "reference": "Tesouro Universe Simulation, Inc", "id": "f5f5dc3d-bc68-4f43-bcc5-dd8fe88fda76" } }, {...}, {...} ] } } } ```
*** ## 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](/acquiring/reference/graphql/types/feesummaryinput) filters, sort order and pagination, and pass it to your query.

Note: A date filter, either `feeActivityDate` or `fundsReleaseDate`, is required. | Filter | Description | | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `acceptorId` | A unique, 36 character identifier created by Tesouro and assigned to the entity providing the goods or services to the customer, such as a Merchant, a Submerchant of a Payment Facilitator, a Seller within a Marketplace, or a Biller of a Consumer Bill Payment Service Provider (CBPS). Historically, processors have called this identifier the Merchant ID (or MID), Outlet ID, or Customer number. | | `feeActivityDate` | The date the fee was applied. | | `feeType` | The [type of fee](/acquiring/reference/graphql/types/allocationfeetype), e.g., Interchange, Network, Processor, Partner, etc. | | `fundingCurrency` | The currency of the funded transaction, formatted in ISO 4217 alphabetic code. | | `fundsReleaseDate` | The date that Tesouro releases the funds from its bank account to the recipient's bank account. | | `fundsTransferid` | A unique identifier created and used by Tesouro, and assigned to the transfer of money to a bank account, to identify a cohort of funded transactions making up the transfer. | | `paymentBrand` | The [payment brand used](/acquiring/reference/graphql/types/paymentbrand) used, e.g., Visa, Mastercard, Discover, American Express, etc. | | `perspective` | The perspective of the allocation, which can be either 'ACCEPTOR' or 'PARTNER'. This field is used to determine the perspective from which the allocation is reported. | 3. List the [fee summary](/acquiring/reference/graphql/types/feesummary) values and attributes you want returned under `items`. **-> Example**
```graphql Query lines expandable theme={null} query FeeSummaries($input: FeeSummaryInput!) { feeSummaries(input: $input) { items { acceptor { businessName reference id } feeActivityDate feeType billableEventType fundsReleaseDate feeName feeDescription productPillar feeProfileId fundingCurrency feeCount feeRateMultiplier feeRateUnitAmount feeAmount processingNetwork paymentBrand paymentProduct paymentFundingSource perspective merchantCategory billableEventAmount fundsTransferId } } } ``` ```json Inputs lines expandable theme={null} { "input": { "where": { "fundsReleaseDate": { "eq": "2024-11-04" } }, "paging": { "skip": 0, "take": 100 }, "orderBy": [ { "field": "FUNDS_RELEASE_DATE", "sortDirection": "DESC" } ] } } ``` ```json Response lines expandable theme={null} { "data": { "feeSummaries": { "items": [ { "acceptor": { "businessName": "Operational Heartbeat Acceptor", "reference": "Tesouro Universe Simulation, Inc", "id": "f5f5dc3d-bc68-4f43-bcc5-dd8fe88fda76" }, "feeActivityDate": "2024-10-31", "feeType": "NETWORK_FEE", "billableEventType": "ACCOUNT_VERIFICATION", "fundsReleaseDate": "2024-11-04", "feeName": "Discover Account Verification Service Fee", "feeDescription": "Applies to all Discover authorization requests submitted for account verification through the Discover Account Verification Service.", "productPillar": "TRANSACTION_PROCESSING", "feeProfileId": "116ae48a-4463-4e3f-a0de-966dc4c3c5ce", "fundingCurrency": "USD", "feeCount": 130, "feeRateMultiplier": 0, "feeRateUnitAmount": 0.02, "feeAmount": -2.6, "processingNetwork": "DISCOVER", "paymentBrand": "DISCOVER", "paymentProduct": "Consumer Credit - Rewards", "paymentFundingSource": "CREDIT", "perspective": "PARTNER", "merchantCategory": "8099", "billableEventAmount": 0, "fundsTransferId": "6402afc6-ca70-4a17-b5da-58a216dfabb0" }, { "acceptor": { "businessName": "Operational Heartbeat Acceptor", "reference": "Tesouro Universe Simulation, Inc", "id": "f5f5dc3d-bc68-4f43-bcc5-dd8fe88fda76" }, "feeActivityDate": "2024-10-31", "feeType": "INTERCHANGE_FEE", "billableEventType": "DISPUTE", "fundsReleaseDate": "2024-11-04", "feeName": "Interchange Giveback", "feeDescription": "Stamped interchange that we copied from the original transaction onto the dispute_event and then to the billing_event", "productPillar": "RISK_COMPLIANCE_DISPUTE_MANAGEMENT", "feeProfileId": "47a9570e-f715-402e-90b2-988220e5b612", "fundingCurrency": "USD", "feeCount": 2, "feeRateMultiplier": 0, "feeRateUnitAmount": 0, "feeAmount": 0, "processingNetwork": "VISA", "paymentBrand": "VISA", "paymentProduct": "Visa Business", "paymentFundingSource": "DEBIT", "perspective": "PARTNER", "merchantCategory": "8099", "billableEventAmount": 36.93, "fundsTransferId": "6402afc6-ca70-4a17-b5da-58a216dfabb0" }, {...}, {...} ] } } } ```
*** ## 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](/acquiring/reference/graphql/types/fundingdisputeeventinput) filters, sort order and pagination, and pass it to your query. | Filter | Description | | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `acceptorId` | A unique, 36 character identifier created by Tesouro and assigned to the entity providing the goods or services to the customer, such as a Merchant, a Submerchant of a Payment Facilitator, a Seller within a Marketplace, or a Biller of a Consumer Bill Payment Service Provider (CBPS). Historically, processors have called this identifier the Merchant ID (or MID), Outlet ID, or Customer number. | | `dateOfEvent` | The date the dispute lifecycle event was reported. | | `fundsTransferId` | A unique identifier created by Tesouro and assigned to the transfer of money to a bank account that included funding of this dispute. | | `fundsReleaseDate` | The date the debited or credited funds for the dispute lifecycle were released. | | `paymentBrand` | The [payment brand used](/acquiring/reference/graphql/types/paymentbrand) used, e.g., Visa, Mastercard, Discover, American Express, etc. | | `perspective` | The perspective of the money movement, which can be either 'ACCEPTOR' or 'PARTNER'. This field is used to determine the perspective from which the money movement is reported. | 3. List the [funding dispute event](/acquiring/reference/graphql/types/fundingdisputeeventoutput) fields you want returned within the `items` field.
**Example** ```graphql Query lines expandable theme={null} query ExampleQuery($input: FundingDisputeEventInput!) { fundingDisputeEvents(input: $input) { items { acceptor { id businessName reference } id acquirerReferenceNumber dateOfEvent disputeId fundingAmount fundingCurrency fundsReleaseDate fundsTransferId lifeCycle paymentBrand paymentId perspective processingNetwork } } } ``` ```json Inputs lines theme={null} { "input": { "where": { "dateOfEvent": { "gte": "2025-06-01", "lte": "2025-06-08" } }, "paging": { "skip": 0, "take": 1 } } } ``` ```json Response lines expandable theme={null} { "data": { "fundingDisputeEvents": { "items": [ { "acceptor": { "id": "f5f5dc3d-bc68-4f43-bcc5-dd8fe88fda76", "businessName": "Tesouro Universe Simulation, Inc", "reference": "Tesouro Universe Simulation, Inc" }, "id": "6622b5d7-5e20-48a9-b934-e99686479904", "acquirerReferenceNumber": "70000015157000000000051", "dateOfEvent": "2025-06-08", "disputeId": "bd4c6494-0289-42cc-a48f-0fb3229d1174", "fundingAmount": 4.53, "fundingCurrency": "USD", "fundsReleaseDate": null, "fundsTransferId": null, "lifeCycle": "FIRST_CHARGEBACK", "paymentBrand": "MASTERCARD", "paymentId": "0000046d-42ab-11f0-ae80-38518ed3605a", "perspective": "PARTNER", "processingNetwork": "MASTERCARD" } ] } } } ```
*** ## 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](/acquiring/reference/graphql/operations#funding-summary-input) 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. | Filter | Description | | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `acceptorId` | A unique, 36 character identifier created by Tesouro and assigned to the entity providing the goods or services to the customer, such as a Merchant, a Submerchant of a Payment Facilitator, a Seller within a Marketplace, or a Biller of a Consumer Bill Payment Service Provider (CBPS). Historically, processors have called this identifier the Merchant ID (or MID), Outlet ID, or Customer number. | | `fundingCurrency` | The currency specified on the transaction request, in ISO 4217 alpha currency code format. | | `fundsReleaseDate` | A value created by Tesouro and sent with the funds transfer to the recipient's bank for display on the bank statement. It includes information on who sent the money and the purpose of the payment. The recipient can use this value to help with bank and transaction reconciliation. | | `fundsTransferId` | A unique identifier created and used by Tesouro, and assigned to the transfer of money to a bank account, to identify a cohort of funded transactions making up the transfer. | | `paymentBrand` | The [payment brand used](/acquiring/reference/graphql/types/paymentbrand) used, e.g., Visa, Mastercard, Discover, American Express, etc. | | `paymentChannel` | The [payment channel used](/acquiring/reference/graphql/types/paymentchannel) used, e.g., Ecommerce, Retail, Mail Order Telephone Order, etc. | | `perspective` | The perspective of the money movement, which can be either towards the 'ACCEPTOR' or 'PARTNER'. This field is used to determine the perspective from which the money movement is reported. | | `transactionActivityDate` | **Required.** The date Tesouro recognized the payment request based upon the acceptor cutoff. Formatted as 2024-03-27 | 3. List the [funding summary](/acquiring/reference/graphql/types/fundingsummary) fields you want returned within the `items` field.
**Example** ```graphql Query lines expandable theme={null} query FundingSummaries($input: FundingSummariesInput!) { fundingSummaries(input: $input) { items { fundsReleaseDate transactionActivityDate fundingCurrency salesGrossAmount refundsGrossAmount disputesGrossAmount interchangeFeesAmount networkFeesAmount processorFeesAmount transactorFeesAmount miscAdjustmentsAmount fundingNetAmount acceptor { businessName reference id } fundsTransferProfileName fundsTransferId fundsTransferDescriptor salesCount refundsCount fundedDisputesCount miscCreditsCount miscDebitsCount perspective } } } ``` ```json Inputs lines expandable theme={null} { "input": { "where": { "fundsReleaseDate": { "eq": "2024-11-04" } }, "orderBy": [ { "field": "FUNDS_RELEASE_DATE", "sortDirection": "DESC" } ], "paging": { "skip": 0, "take": 1000 } } } ``` ```json Response lines expandable theme={null} { "data": { "organization": { "fundingSummaries": { "items": [ { "acceptor": { "id": "f5f5dc3d-bc68-4f43-bcc5-dd8fe88fda76", "name": "Tesouro Universe Simulation, Inc.", "reference": "A-1234" }, "fundsReleaseDate": "2024-09-05", "transactionActivityDate": "2024-09-04", "fundingCurrency": "USD", "salesGrossAmount": "13391.31", "refundsGrossAmount": "1000", "disputesGrossAmount": "0", "interchangeFeesAmount": "554.3445", "networkFeesAmount": "91.3038", "processorFeesAmount": "6.5217", "miscAdjustmentsAmount": "0", "fundingNetAmount": "12391.31", "effectiveRate": "0.048701", "perspective": "PARTNER", "fundsTransfer": { "id": "db4049d4-2dc4-4e64-8488-2a0e18804260" } }, {...} {...} ] } } } } ```
*** ## 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](/acquiring/reference/graphql/types/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. | Filter | Description | | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `acceptorId` | A unique, 36 character identifier created by Tesouro and assigned to the entity providing the goods or services to the customer, such as a Merchant, a Submerchant of a Payment Facilitator, a Seller within a Marketplace, or a Biller of a Consumer Bill Payment Service Provider (CBPS). Historically, processors have called this identifier the Merchant ID (or MID), Outlet ID, or Customer number. | | `fundingCurrency` | The currency specified on the transaction request, in ISO 4217 alpha currency code format. | | `fundsReleaseDate` | A value created by Tesouro and sent with the funds transfer to the recipient's bank for display on the bank statement. It includes information on who sent the money and the purpose of the payment. The recipient can use this value to help with bank and transaction reconciliation. | | `fundsTransferId` | A unique identifier created and used by Tesouro, and assigned to the transfer of money to a bank account, to identify a cohort of funded transactions making up the transfer. | | `paymentBrand` | The [payment brand used](/acquiring/reference/graphql/types/paymentbrand) used, e.g., Visa, Mastercard, Discover, American Express, etc. | | `paymentChannel` | The [payment channel used](/acquiring/reference/graphql/types/paymentchannel) used, e.g., Ecommerce, Retail, Mail Order Telephone Order, etc. | | `perspective` | The perspective of the money movement, which can be either towards the 'ACCEPTOR' or 'PARTNER'. This field is used to determine the perspective from which the money movement is reported. | | `transactionActivityDate` | **Required.** The date Tesouro recognized the payment request based upon the acceptor cutoff. Formatted as 2024-03-27 | 3. List the [funding transaction](/acquiring/reference/graphql/types/fundingtransaction) fields you want returned in the `items` field.
**Example** ```graphql Query lines expandable theme={null} query ExampleFundingTransactions($input: FundingTransactionInput!) { fundingTransactions(input: $input) { items { fundsReleaseDate fundingCurrency fundingGrossAmount fundingNetAmount perspective paymentTransaction { transactionType processingNetwork reference id transactionDateTime activityDate paymentId acceptor { businessName reference id } ... on ApprovedCapture { approvedAmount acquirerReferenceNumber currency requestedAmount merchantCategory order { reference customerReference } paymentChannel paymentEntryMode paymentMethod { ... on Card { type brand fundingSource consumerType productName issuerBin last4 expirationDate issuerName issuerCountry acquirerToken } } isFunded feeTotalAmount interchangeFeesAmount networkFeesAmount processorFeesAmount partnerFeesAmount fundingCurrency fundingGrossAmount fundingNetAmount fundsTransfer { estimatedBankPostingDate fundsTransferDescriptor id } } ... on ApprovedRefund { approvedAmount acquirerReferenceNumber currency requestedAmount merchantCategory order { reference customerReference } paymentChannel paymentEntryMode paymentMethod { ... on Card { type brand fundingSource consumerType productName issuerBin last4 expirationDate issuerName issuerCountry acquirerToken } } isFunded feeTotalAmount interchangeFeesAmount networkFeesAmount processorFeesAmount partnerFeesAmount fundingCurrency fundingGrossAmount fundingNetAmount fundsTransfer { estimatedBankPostingDate fundsTransferDescriptor id } } } } } } ``` ```json Inputs lines theme={null} { "input": { "where": { "fundsReleaseDate": { "eq": "2024-11-04" } }, "paging": { "skip": 0, "take": 1000 } } } ``` ```json Response lines expandable theme={null} { "data": { "organization": { "fundingTransactions": { "items": [ { "transaction": { "transactionId": "f591a088-6be2-11ef-a036-a753281832a4", "transactionReference": "T-39025842435", "orderReference": "O-8324092", "acquirerReferenceNumber": "73948254410269670152951", "transactionActivityDate": "2024-09-05", "transactionDateTime": "2024-09-05 23:59:59", "transactionType": "CAPTURE", "transactionCurrency": "USD", "transactionAmount": "10.98", }, "acceptor": { "id": "f5f5dc3d-bc68-4f43-bcc5-dd8fe88fda76", "name": "Tesouro Universe Simulation, Inc.", "reference": "A-1234" }, "fundsReleaseDate": "2024-09-05", "fundsTransferId": "db4049d4-2dc4-4e64-8488-2a0e18804260", "fundingCurrency": "USD", "fundingGrossAmount": "10.98", "interchangeFeesAmount": "0.27999", "networkFeesAmount": "0.046116", "processorFeesAmount": "0.003294", "fundingNetAmount": "10.6506", "perspective": "PARTNER" }, {...}, {...} ] } } } } ```
*** ## 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](/acquiring/reference/graphql/types/paymenttransactionsinput) filters and pagination, and pass it to your query.

Note that `transactionActivityDate` is a required filter. | Filter | Description | | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `acceptorId` | A unique, 36 character identifier created by Tesouro and assigned to the entity providing the goods or services to the customer, such as a Merchant, a Submerchant of a Payment Facilitator, a Seller within a Marketplace, or a Biller of a Consumer Bill Payment Service Provider (CBPS). Historically, processors have called this identifier the Merchant ID (or MID), Outlet ID, or Customer number. | | `paymentBrand` | The [payment brand used](/acquiring/reference/graphql/types/paymentbrand) used, e.g., Visa, Mastercard, Discover, American Express, etc. | | `paymentChannel` | The [payment channel used](/acquiring/reference/graphql/types/paymentchannel) used, e.g., Ecommerce, Retail, Mail Order Telephone Order, etc. | | `paymentFundingSource` | The [source of the customer's funds](/acquiring/reference/graphql/types/fundingsource), e.g., credit, debit, pre-paid, cash. | | `paymentId` | A unique 36 character identifier created by Tesouro and assigned to a group of transactions in the same payment request cohort. e.g., An authorization request, incremental authorization request, and the final capture would have the same paymentID. | | `processorResponseCode` | A [response code provided Tesouro](/acquiring/support/response-codes) indicating whether the transaction was approved or declined. | | `transactionActivityDate` | **REQUIRED.** The date Tesouro recognized the payment request based upon the acceptor cutoff. Formatted as 2024-03-27. The results will be sorted by this field, descending. | | `transactionCurrency` | The currency specified on the transaction request, in ISO 4217 alpha currency code format. | | `transactionId` | A unique 36 character identifier assigned by Tesouro for every transaction request received. | | `transactionType` | The [type of transaction](/acquiring/reference/graphql/types/transactiontype), e.g., Authorization, Refund authorization, or Incremental authorization. | 3. List the pertinent [payment transaction](/acquiring/reference/graphql/types/paymenttransaction) 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** ```graphql Query lines expandable theme={null} query ExamplePaymentTransactions($input: PaymentTransactionsInput!) { paymentTransactions(input: $input) { items { transactionType processingNetwork reference id transactionDateTime activityDate paymentId acceptor { businessName reference id } ... on ApprovedAuthorization { approvedAmount networkApprovalCode automaticCapture conveyedStatus currency requestedAmount responseType networkResponseCode processorResponseCode processorResponseMessage addressVerification nameVerification securityCodeVerification merchantCategory order { reference } paymentChannel paymentEntryMode paymentMethod { ... on Card { fundingSource brand consumerType productName issuerBin last4 expirationDate issuerName issuerCountry acquirerToken type } } } ... on DeclinedAuthorization { declineType processorAdvice currency requestedAmount responseType networkResponseCode processorResponseCode processorResponseMessage addressVerification nameVerification securityCodeVerification merchantCategory order { reference } paymentChannel paymentEntryMode paymentMethod { ... on Card { fundingSource brand consumerType productName issuerBin last4 expirationDate issuerName issuerCountry acquirerToken type } } } ... on ApprovedReversal { approvedAmount currency requestedAmount merchantCategory order { reference } paymentChannel paymentEntryMode paymentMethod { ... on Card { fundingSource brand consumerType productName issuerBin last4 expirationDate issuerName issuerCountry acquirerToken type } } originalAuthorizationTransactionId networkResponseCode processorResponseCode processorResponseMessage } ... on DeclinedReversal { declineType processorAdvice currency requestedAmount merchantCategory order { reference } paymentChannel paymentEntryMode paymentMethod { ... on Card { fundingSource brand consumerType productName issuerBin last4 expirationDate issuerName issuerCountry acquirerToken type } } originalAuthorizationTransactionId networkResponseCode processorResponseCode processorResponseMessage } ... on ApprovedIncrementalAuthorization { previouslyApprovedAmount updatedAuthorizationAmount networkApprovalCode automaticCapture conveyedStatus currency requestedAmount responseType networkResponseCode processorResponseCode processorResponseMessage addressVerification nameVerification securityCodeVerification merchantCategory order { reference } paymentChannel paymentEntryMode paymentMethod { ... on Card { fundingSource brand consumerType productName issuerBin last4 expirationDate issuerName issuerCountry acquirerToken type } } } ... on DeclinedIncrementalAuthorization { declineType processorAdvice currency requestedAmount responseType networkResponseCode processorResponseCode processorResponseMessage addressVerification nameVerification securityCodeVerification merchantCategory order { reference } paymentChannel paymentEntryMode paymentMethod { ... on Card { fundingSource brand consumerType productName issuerBin last4 expirationDate issuerName issuerCountry acquirerToken type } } } ... on ApprovedCapture { approvedAmount acquirerReferenceNumber currency requestedAmount merchantCategory order { reference } paymentChannel paymentEntryMode paymentMethod { ... on Card { fundingSource brand consumerType productName issuerBin last4 expirationDate issuerName issuerCountry acquirerToken type } } isFunded feeTotalAmount interchangeFeesAmount networkFeesAmount processorFeesAmount partnerFeesAmount fundingCurrency fundingGrossAmount } ... on DeclinedCapture { declineType processorAdvice acquirerReferenceNumber currency requestedAmount merchantCategory order { reference } paymentChannel paymentEntryMode paymentMethod { ... on Card { fundingSource brand consumerType productName issuerBin last4 expirationDate issuerName issuerCountry acquirerToken type } } isFunded feeTotalAmount interchangeFeesAmount networkFeesAmount processorFeesAmount partnerFeesAmount fundingCurrency fundingGrossAmount } ... on ApprovedRefund { approvedAmount acquirerReferenceNumber currency requestedAmount merchantCategory order { reference } paymentChannel paymentEntryMode paymentMethod { ... on Card { fundingSource brand consumerType productName issuerBin last4 expirationDate issuerName issuerCountry acquirerToken type } } isFunded feeTotalAmount fundingCurrency fundingGrossAmount } ... on DeclinedRefund { declineType processorAdvice acquirerReferenceNumber currency requestedAmount merchantCategory order { reference } paymentChannel paymentEntryMode paymentMethod { ... on Card { fundingSource brand consumerType productName issuerBin last4 expirationDate issuerName issuerCountry acquirerToken type } } isFunded fundingCurrency fundingGrossAmount } ... on CardVerification { addressVerification nameVerification securityCodeVerification paymentChannel paymentEntryMode paymentMethod { ... on Card { fundingSource brand consumerType productName issuerBin last4 expirationDate issuerName issuerCountry acquirerToken type } } } } } } ``` ```json Inputs lines theme={null} { "input": { "where": { "transactionActivityDate": { "eq": "2024-11-04" } }, "paging": { "skip": 0, "take": 10000 } } } ``` ```json Response lines expandable theme={null} { "data": { "paymentTransactions": { "items": [ { "transactionType": "AUTHORIZATION", "processingNetwork": "VISA", "reference": "ec89f39d-955c-ef52-07fc-5f27076ce56a", "id": "4491bbc0-9b11-11ef-946d-812249c3b901", "transactionDateTime": "2024-11-05T00:59:53.892Z", "activityDate": "2024-11-04", "paymentId": "4491bbc0-9b11-11ef-946d-812249c3b901", "acceptor": { "businessName": "Operational Heartbeat Acceptor", "reference": "Tesouro Universe Simulation, Inc", "id": "f5f5dc3d-bc68-4f43-bcc5-dd8fe88fda76" }, "approvedAmount": 15.34, "networkApprovalCode": "258549", "automaticCapture": true, "conveyedStatus": "NOT_APPLICABLE", "currency": "USD", "requestedAmount": 15.34, "responseType": "APPROVAL", "networkResponseCode": "00", "processorResponseCode": "A0000", "processorResponseMessage": "Full amount approved.", "addressVerification": "AVS_STATUS_NOT_PROVIDED", "nameVerification": null, "securityCodeVerification": "MATCH", "merchantCategory": "8099", "order": { "reference": "6cf86f04-f2e1-45e1-b48b-70e7ec59cb61" }, "paymentChannel": "ECOMMERCE", "paymentEntryMode": "ON_FILE", "paymentMethod": { "type": "CARD", "brand": "VISA", "fundingSource": "DEBIT", "consumerType": "BUSINESS", "productName": "Visa Business", "issuerBin": "411113", "last4": "0848", "expirationDate": "04/2026", "issuerName": null, "issuerCountry": "USA", "acquirerToken": "ab78beb8-a097-4256-a7ea-c3df55248ccb" } }, { "transactionType": "CAPTURE", "processingNetwork": "VISA", "reference": "ec89f39d-955c-ef52-07fc-5f27076ce56a", "id": "4497053d-9b11-11ef-877e-fd4d6b6f9de5", "transactionDateTime": "2024-11-05T00:59:53.892Z", "activityDate": "2024-11-04", "paymentId": "4491bbc0-9b11-11ef-946d-812249c3b901", "acceptor": { "businessName": "Operational Heartbeat Acceptor", "reference": "Tesouro Universe Simulation, Inc", "id": "f5f5dc3d-bc68-4f43-bcc5-dd8fe88fda76" }, "approvedAmount": 15.34, "acquirerReferenceNumber": null, "currency": "USD", "requestedAmount": 15.34, "merchantCategory": "8099", "order": { "reference": "6cf86f04-f2e1-45e1-b48b-70e7ec59cb61" }, "paymentChannel": "ECOMMERCE", "paymentEntryMode": "ON_FILE", "paymentMethod": { "type": "CARD", "brand": "VISA", "fundingSource": "DEBIT", "consumerType": "BUSINESS", "productName": "Visa Business", "issuerBin": "411113", "last4": "0848", "expirationDate": "04/2026", "issuerName": null, "issuerCountry": "USA", "acquirerToken": "ab78beb8-a097-4256-a7ea-c3df55248ccb" }, "isFunded": false, "feeTotalAmount": null, "interchangeFeesAmount": null, "networkFeesAmount": null, "processorFeesAmount": null, "partnerFeesAmount": null, "fundingCurrency": null, "fundingGrossAmount": 0 }, {...}, {...} ] } } } ```
*** ## 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](/acquiring/reference/graphql/types/paymenttransactionsummaryinput) filters, sort order and pagination, and pass it to your query. | Filter | Description | | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `acceptorId` | A unique, 36 character identifier created by Tesouro and assigned to the entity providing the goods or services to the customer, such as a Merchant, a Submerchant of a Payment Facilitator, a Seller within a Marketplace, or a Biller of a Consumer Bill Payment Service Provider (CBPS). Historically, processors have called this identifier the Merchant ID (or MID), Outlet ID, or Customer number. | | `paymentChannel` | The [payment channel used](/acquiring/reference/graphql/types/paymentchannel) used, e.g., Ecommerce, Retail, Mail Order Telephone Order, etc. | | `transactionActivityDate` | **Required.** The date Tesouro recognized the payment request based upon the acceptor cutoff. Formatted as 2024-03-27 | | `transactionCurrency` | The currency specified on the transaction request, in ISO 4217 alpha currency code format. | | `transactionType` | The [type of transaction](/acquiring/reference/graphql/types/transactiontype), e.g., Authorization, Capture, Refund, Reversal, Incremental authorization, Card verification, etc. | 3. List the [transaction summary](/acquiring/reference/graphql/types/paymenttransactionsummary) fields you want returned within the `items` field.
**Example** ```graphql Query lines expandable theme={null} query ExamplePaymentTransactionSummaries($input: PaymentTransactionSummaryInput!) { paymentTransactionSummaries(input: $input) { items { acceptor { businessName reference id } conveyedStatus paymentBrand paymentFundingSource presenterId processingNetwork transactionActivityDate transactionAmount transactionCount transactionCurrency transactionProcessingDecision transactionType } } } ``` ```json Inputs lines expandable theme={null} { "input": { "where": { "transactionActivityDate": { "eq": "2024-11-04" } }, "orderBy": [ { "field": "TRANSACTION_ACTIVITY_DATE", "sortDirection": "DESC" } ], "paging": { "skip": 0, "take": 1000 } } } ``` ```json Response lines expandable theme={null} { "data": { "paymentTransactionSummaries": { "items": [ { "acceptor": { "businessName": "Operational Heartbeat Acceptor", "reference": "Tesouro Universe Simulation, Inc", "id": "f5f5dc3d-bc68-4f43-bcc5-dd8fe88fda76" }, "conveyedStatus": "NOT_APPLICABLE", "paymentBrand": "AMERICAN_EXPRESS", "paymentFundingSource": "CREDIT", "presenterId": "0952fa02-a9e3-4c28-b128-4121869310e4", "processingNetwork": "AMERICAN_EXPRESS", "transactionActivityDate": "2024-11-04", "transactionAmount": 0, "transactionCount": 62, "transactionCurrency": "USD", "transactionProcessingDecision": "APPROVED", "transactionType": "ACCOUNT_VERIFICATION" }, { "acceptor": { "businessName": "Operational Heartbeat Acceptor", "reference": "Tesouro Universe Simulation, Inc", "id": "f5f5dc3d-bc68-4f43-bcc5-dd8fe88fda76" }, "conveyedStatus": "NOT_APPLICABLE", "paymentBrand": "AMERICAN_EXPRESS", "paymentFundingSource": "CREDIT", "presenterId": "0952fa02-a9e3-4c28-b128-4121869310e4", "processingNetwork": "AMERICAN_EXPRESS", "transactionActivityDate": "2024-11-04", "transactionAmount": 83591.29, "transactionCount": 5167, "transactionCurrency": "USD", "transactionProcessingDecision": "APPROVED", "transactionType": "AUTHORIZATION" }, { "acceptor": { "businessName": "Operational Heartbeat Acceptor", "reference": "Tesouro Universe Simulation, Inc", "id": "f5f5dc3d-bc68-4f43-bcc5-dd8fe88fda76" }, "conveyedStatus": "NOT_APPLICABLE", "paymentBrand": "AMERICAN_EXPRESS", "paymentFundingSource": "CREDIT", "presenterId": "0952fa02-a9e3-4c28-b128-4121869310e4", "processingNetwork": "AMERICAN_EXPRESS", "transactionActivityDate": "2024-11-04", "transactionAmount": 454.72, "transactionCount": 35, "transactionCurrency": "USD", "transactionProcessingDecision": "APPROVED", "transactionType": "INCREMENTAL_AUTHORIZATION" }, { "acceptor": { "businessName": "Operational Heartbeat Acceptor", "reference": "Tesouro Universe Simulation, Inc", "id": "f5f5dc3d-bc68-4f43-bcc5-dd8fe88fda76" }, "conveyedStatus": "NOT_APPLICABLE", "paymentBrand": "AMERICAN_EXPRESS", "paymentFundingSource": "CREDIT", "presenterId": "0952fa02-a9e3-4c28-b128-4121869310e4", "processingNetwork": "AMERICAN_EXPRESS", "transactionActivityDate": "2024-11-04", "transactionAmount": 330.76, "transactionCount": 36, "transactionCurrency": "USD", "transactionProcessingDecision": "APPROVED", "transactionType": "REFUND_AUTHORIZATION" }, { "acceptor": { "businessName": "Operational Heartbeat Acceptor", "reference": "Tesouro Universe Simulation, Inc", "id": "f5f5dc3d-bc68-4f43-bcc5-dd8fe88fda76" }, "conveyedStatus": "NOT_APPLICABLE", "paymentBrand": "AMERICAN_EXPRESS", "paymentFundingSource": "CREDIT", "presenterId": "0952fa02-a9e3-4c28-b128-4121869310e4", "processingNetwork": "AMERICAN_EXPRESS", "transactionActivityDate": "2024-11-04", "transactionAmount": 450.25, "transactionCount": 37, "transactionCurrency": "USD", "transactionProcessingDecision": "APPROVED", "transactionType": "REVERSAL" }, {...}, {...} ] } } } ```