A summary of transaction counts and amounts by transaction activity date. Use this report to reconcile received transactions against your internal record of submitted transactions.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.
| Field | Description |
|---|---|
ACCEPTOR_ID | The 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). Also referred to as the Merchant ID (MID), Outlet ID, or Customer number. |
ACCEPTOR_NAME | A human readable description used to uniquely label the Acceptor. It is assigned during onboarding of the Acceptor and mapped to the Acceptor ID. Maximum of 255 characters. Other processors may refer to this as a Billing descriptor. |
ACCEPTOR_REFERENCE | A unique identifier created and managed by the entity holding the direct relationship with the Acceptor, and assigned to the Acceptor with a one-to-one mapping to Tesouro’s Acceptor ID. Other processors may refer to this as Location ID, Store ID, Club ID, etc. |
CONVEYED_STATUS | Identifies those transactions that are or will be conveyed to another acquirer |
ORGANIZATION_ID | A unique 36 character identifier created and used by Tesouro, and assigned to the organization holding the relationship with Tesouro. |
PAYMENT_BRAND | The payment brand used, e.g., Visa, Mastercard, Discover, American Express, etc. |
PAYMENT_FUNDING_SOURCE | The source of the customer’s funds , e.g., credit, debit, pre-paid, cash. NOTE: This field will present a null, not applicable, or empty value if the fee is not tied to a specific transaction. |
PROCESSING_NETWORK | The payment network that the transaction was processed on, which may be unaffiliated with the card brand. |
TRANSACTION_ACTIVITY_DATE | The date Tesouro recognized the payment request based upon the acceptor cutoff. Formatted as YYY-MM-DD |
TRANSACTION_AMOUNT | The amount of the transaction request sent to Tesouro. |
TRANSACTION_COUNT | The total quantity of transactions. |
TRANSACTION_CURRENCY | The currency specified on the transaction request, in ISO 4217 alpha currency code format. |
TRANSACTION_PROCESSING_DECISION | Tesouro’s decision to approve or decline, or accept or reject the transaction request. Note, this is different than the Authorization response returned from the payment network. |
TRANSACTION_TYPE | The type of transaction, e.g., Authorization, Refund authorization, or Incremental authorization. |
Report availability
The report is generated daily by 10:00 AM ET, encrypted, and placed in the outbound directory of an SFTP location dedicated for your use. (This schedule can be configured to later cadences to suit your needs, e.g., a later time in the day, every other day, weekly, monthly, etc.) Reports expire and are removed from the SFTP location after 14 calendar days.Report format
- CSV file, following the RFC 4180 standard
- File name:
transaction_summaries_{startdate:YYYYMMDD}-{endDate:YYYYMMDD}_{generationDate:YYYYMMDDThhmmss}.csv - Values are separated using commas.
- Values containing commas are enclosed within double quotes.
- Values containing double-quotes are escaped by two double quote preceding it.