A Notification of Change (NOC), notifies the sender of an ACH payment that information related to the customer’s bank account was inaccurate or outdated, and provides the updated information that needs to be corrected before another payment can be sent from (or to) the account.
A summary of authorizations (counts, amounts) for the given transaction date, grouped by acceptor, transaction currency, response code, and payment brand.
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.
A summary of aggregated fees by acceptor and fee name/program for a specified activity date or funds release date, grouped by fee type, and where applicable, payment brand, product, and funding source.
An itemized list of financially impacting ach returns occuring on the pertinent funds release dates. Use this report to track ach return-related money-movements.
An itemized list of financially impacting dispute events occuring on the pertinent funds release dates. Use this report to track dispute-related money-movements.
A summary of financial activity for a given funds release date or transaction activity date. Use this report to understand financial impact of daily sales, reconcile sales activity to your bank deposits, or drill deeper into the composition of your funding.
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.Deprecated: Use businessName instead.
A list of transaction requests (including conveyed) submitted on the pertinent transaction activity dates. Use this report as an operational tool to reconcile against your internal record of submitted transactions.
A summary of transaction aggregates (counts and amounts, including conveyed transactions) by pertinent transaction type, currency, card brand, and transaction activity date.
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.
A summary of authorizations (counts, amounts) for the given transaction date, grouped by acceptor, transaction currency, response code, and payment brand.
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.
A summary of aggregated fees by acceptor and fee name/program for a specified activity date or funds release date, grouped by fee type, and where applicable, payment brand, product, and funding source.
An itemized list of financially impacting ach returns occuring on the pertinent funds release dates. Use this report to track ach return-related money-movements.
An itemized list of financially impacting dispute events occuring on the pertinent funds release dates. Use this report to track dispute-related money-movements.
A summary of financial activity for a given funds release date or transaction activity date. Use this report to understand financial impact of daily sales, reconcile sales activity to your bank deposits, or drill deeper into the composition of your funding.
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.Deprecated: Use businessName instead.
A list of transaction requests (including conveyed) submitted on the pertinent transaction activity dates. Use this report as an operational tool to reconcile against your internal record of submitted transactions.
A summary of transaction aggregates (counts and amounts, including conveyed transactions) by pertinent transaction type, currency, card brand, and transaction activity date.
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.
A unique nine-digit number that identifies a bank and is used for electronic transactions. It’s also known as an ABA routing number, or routing transit number (RTN).
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.
A summary of authorizations (counts, amounts) for the given transaction date, grouped by acceptor, transaction currency, response code, and payment brand.
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.
A summary of aggregated fees by acceptor and fee name/program for a specified activity date or funds release date, grouped by fee type, and where applicable, payment brand, product, and funding source.
An itemized list of financially impacting ach returns occuring on the pertinent funds release dates. Use this report to track ach return-related money-movements.
An itemized list of financially impacting dispute events occuring on the pertinent funds release dates. Use this report to track dispute-related money-movements.
A summary of financial activity for a given funds release date or transaction activity date. Use this report to understand financial impact of daily sales, reconcile sales activity to your bank deposits, or drill deeper into the composition of your funding.
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.Deprecated: Use businessName instead.
A list of transaction requests (including conveyed) submitted on the pertinent transaction activity dates. Use this report as an operational tool to reconcile against your internal record of submitted transactions.
A summary of transaction aggregates (counts and amounts, including conveyed transactions) by pertinent transaction type, currency, card brand, and transaction activity date.
The type of billable event, including, but not limited to: Authorization, Capture, Refund, Reversal, Authentication, Dispute, Funds transfer, Misc. adjustment, Token, Account updater, AVS verification, etc.
The type of entity that the billing event source id references, including, but not limited to: Transaction, Funds Transfer, Boarding Request, Acceptor, ACH Return, ACH Notice Of Change, Dispute.
Specifies the type of account associated with the cardholder’s card, e.g., Consumer, Commercial, Government, etc., which has an impact on the interchange qualification. NOTE: This field will present a null, not applicable, or empty value if the allocation is not tied to a specific transaction.
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.
A unique identifier created by Tesouro and assigned to the transfer of money to a bank account, that identifies a cohort of funded transactions making up the transfer.
Unique ISO four digit values used to classify merchants and their transactions into specific categories based on the type of business, trade or services supplied. https://www.iso.org/standard/79450.html
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 allocation is not tied to a specific transaction.
The product name according to the payment brand (e.g. World Elite Mastercard card) NOTE: This field will present a null, not applicable, or empty value if the allocation is not tied to a specific transaction.
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.
A unique, 36 character identifier created by Tesouro and assigned to the machine user or system entity that is credentialed to make API requests and present payments to Tesouro and the network.
The Tesouro product pillar that this allocation applies to: “Boarding”, “Transaction processing”, “Funding”, “Risk, Compliance, and Dispute management”, or “Reporting”.
A unique identifier created by the entity holding the direct relationship with the Acceptor, and used by that entity for reconciliation and transaction search. Tesouro uses this identifier to manage idempotency.
A summary of authorizations (counts, amounts) for the given transaction date, grouped by acceptor, transaction currency, response code, and payment brand.
A summary of authorizations (counts, amounts) for the given transaction date, grouped by acceptor, transaction currency, response code, and payment brand.
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.
A summary of aggregated fees by acceptor and fee name/program for a specified activity date or funds release date, grouped by fee type, and where applicable, payment brand, product, and funding source.
An itemized list of financially impacting ach returns occuring on the pertinent funds release dates. Use this report to track ach return-related money-movements.
An itemized list of financially impacting dispute events occuring on the pertinent funds release dates. Use this report to track dispute-related money-movements.
A summary of financial activity for a given funds release date or transaction activity date. Use this report to understand financial impact of daily sales, reconcile sales activity to your bank deposits, or drill deeper into the composition of your funding.
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.Deprecated: Use businessName instead.
A list of transaction requests (including conveyed) submitted on the pertinent transaction activity dates. Use this report as an operational tool to reconcile against your internal record of submitted transactions.
A summary of transaction aggregates (counts and amounts, including conveyed transactions) by pertinent transaction type, currency, card brand, and transaction activity date.
The Address Verification Service (AVS) result provided by the payment brand that verifies the entered address information matches the address information on file with the issuing bank.
Unique ISO four digit values used to classify merchants and their transactions into specific categories based on the type of business, trade or services supplied.
The card-present or card-not-present channel from which the customer makes a payment, e.g., In-store using a physical card terminal, online, or over the phone or through mail order.
A request to the cardholder’s issuing bank to confirm that the account is active and has enough credit or funds to make the transaction. If approved, the requested amount is put on hold in the cardholder’s account.
A request to cancel a previous transaction request. Authorization reversals notify the cardholder’s issuer that all or part of a transaction has been canceled and that the authorization hold should be released.
Performs address and card security code checks on a cardholder’s account to ensure it is in good standing, without actually charging an amount to the card.
A summary of authorizations (counts, amounts) for the given transaction date, grouped by acceptor, transaction currency, response code, and payment brand.
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.
A summary of aggregated fees by acceptor and fee name/program for a specified activity date or funds release date, grouped by fee type, and where applicable, payment brand, product, and funding source.
An itemized list of financially impacting ach returns occuring on the pertinent funds release dates. Use this report to track ach return-related money-movements.
An itemized list of financially impacting dispute events occuring on the pertinent funds release dates. Use this report to track dispute-related money-movements.
A summary of financial activity for a given funds release date or transaction activity date. Use this report to understand financial impact of daily sales, reconcile sales activity to your bank deposits, or drill deeper into the composition of your funding.
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.Deprecated: Use businessName instead.
A list of transaction requests (including conveyed) submitted on the pertinent transaction activity dates. Use this report as an operational tool to reconcile against your internal record of submitted transactions.
A summary of transaction aggregates (counts and amounts, including conveyed transactions) by pertinent transaction type, currency, card brand, and transaction activity date.
The type of billable event, including, but not limited to: Authorization, Capture, Refund, Reversal, Authentication, Dispute, Funds transfer, Misc. adjustment, Token, Account updater, AVS verification, etc.
The type of entity that the billing event source id references, including, but not limited to: Transaction, Funds Transfer, Boarding Request, Acceptor, ACH Return, ACH Notice Of Change, Dispute.
Specifies the type of account associated with the cardholder’s card, e.g., Consumer, Commercial, Government, etc., which has an impact on the interchange qualification. NOTE: This field will present a null, not applicable, or empty value if the fee is not tied to a specific transaction.
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.
A unique identifier created by Tesouro and assigned to the transfer of money to a bank account, that identifies a cohort of funded transactions making up the transfer.
Unique ISO four digit values used to classify merchants and their transactions into specific categories based on the type of business, trade or services supplied. https://www.iso.org/standard/79450.html
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.
The product name according to the payment brand (e.g. World Elite Mastercard card) NOTE: This field will present a null, not applicable, or empty value if the fee is not tied to a specific transaction.
The perspective of the fee, which can be either ‘Acceptor’ or ‘Partner’. This field is used to determine the perspective from which the fee is reported.
The Tesouro product pillar that this fee applies to: “Boarding”, “Transaction processing”, “Funding”, “Risk, Compliance, and Dispute management”, or “Reporting”.
A unique identifier created by the entity holding the direct relationship with the Acceptor, and used by that entity for reconciliation and transaction search. Tesouro uses this identifier to manage idempotency.
A summary of aggregated fees by acceptor and fee name/program for a specified activity date or funds release date, grouped by fee type, and where applicable, payment brand, product, and funding source.
A summary of authorizations (counts, amounts) for the given transaction date, grouped by acceptor, transaction currency, response code, and payment brand.
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.
A summary of aggregated fees by acceptor and fee name/program for a specified activity date or funds release date, grouped by fee type, and where applicable, payment brand, product, and funding source.
An itemized list of financially impacting ach returns occuring on the pertinent funds release dates. Use this report to track ach return-related money-movements.
An itemized list of financially impacting dispute events occuring on the pertinent funds release dates. Use this report to track dispute-related money-movements.
A summary of financial activity for a given funds release date or transaction activity date. Use this report to understand financial impact of daily sales, reconcile sales activity to your bank deposits, or drill deeper into the composition of your funding.
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.Deprecated: Use businessName instead.
A list of transaction requests (including conveyed) submitted on the pertinent transaction activity dates. Use this report as an operational tool to reconcile against your internal record of submitted transactions.
A summary of transaction aggregates (counts and amounts, including conveyed transactions) by pertinent transaction type, currency, card brand, and transaction activity date.
A unique identifier created by Tesouro and assigned to the transfer of money to a bank account, that identifies a cohort of funded transactions making up the transfer.
Unique ISO four digit values used to classify merchants and their transactions into specific categories based on the type of business, trade or services supplied. NOTE: This field will present a null, not applicable, or empty value if the fee is not tied to a specific transaction.
Specifies which payment brand was used, e.g., Visa, Mastercard, Discover, American Express, etc. NOTE: This field will present a null, not applicable, or empty value if the fee is not tied to a specific transaction.
Specifies the source of the card customer’s funds , e.g., credit, debit, pre-paid. NOTE: This field will present a null, not applicable, or empty value if the fee is not tied to a specific transaction.
The product name according to the payment brand (e.g. World Elite Mastercard card) NOTE: This field will present a null, not applicable, or empty value if the fee is not tied to a specific transaction.
The perspective of the fee, which can be either ‘Acceptor’ or ‘Partner’. This field is used to determine the perspective from which the fee is reported.
The payment network that the transaction was sent across, which may be unafilliated with the card brand. NOTE: This field will present a null, not applicable, or empty value if the fee is not tied to a specific transaction.
An itemized list of financially impacting ACH returns occurring on the pertinent funds release dates. Use this report to track ACH return-related money-movements.
A summary of authorizations (counts, amounts) for the given transaction date, grouped by acceptor, transaction currency, response code, and payment brand.
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.
A summary of aggregated fees by acceptor and fee name/program for a specified activity date or funds release date, grouped by fee type, and where applicable, payment brand, product, and funding source.
An itemized list of financially impacting ach returns occuring on the pertinent funds release dates. Use this report to track ach return-related money-movements.
An itemized list of financially impacting dispute events occuring on the pertinent funds release dates. Use this report to track dispute-related money-movements.
A summary of financial activity for a given funds release date or transaction activity date. Use this report to understand financial impact of daily sales, reconcile sales activity to your bank deposits, or drill deeper into the composition of your funding.
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.Deprecated: Use businessName instead.
A list of transaction requests (including conveyed) submitted on the pertinent transaction activity dates. Use this report as an operational tool to reconcile against your internal record of submitted transactions.
A summary of transaction aggregates (counts and amounts, including conveyed transactions) by pertinent transaction type, currency, card brand, and transaction activity date.
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.
A unique identifier created by Tesouro and assigned to the transfer of money to a bank account for this ach return, that identifies a cohort of funded transactions making up the transfer.
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.
The perspective of the money movement, which can be either ‘Acceptor’ or ‘Partner’. This field is used to determine the financial perspective from which the ACH return is reported.
A unique nine-digit number that identifies a bank and is used for electronic transactions. It’s also known as an ABA routing number, or routing transit number (RTN).
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.
An itemized list of financially impacting dispute events occuring on the pertinent funds release dates. Use this report to track dispute-related money-movements.
A summary of authorizations (counts, amounts) for the given transaction date, grouped by acceptor, transaction currency, response code, and payment brand.
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.
A summary of aggregated fees by acceptor and fee name/program for a specified activity date or funds release date, grouped by fee type, and where applicable, payment brand, product, and funding source.
An itemized list of financially impacting ach returns occuring on the pertinent funds release dates. Use this report to track ach return-related money-movements.
An itemized list of financially impacting dispute events occuring on the pertinent funds release dates. Use this report to track dispute-related money-movements.
A summary of financial activity for a given funds release date or transaction activity date. Use this report to understand financial impact of daily sales, reconcile sales activity to your bank deposits, or drill deeper into the composition of your funding.
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.Deprecated: Use businessName instead.
A list of transaction requests (including conveyed) submitted on the pertinent transaction activity dates. Use this report as an operational tool to reconcile against your internal record of submitted transactions.
A summary of transaction aggregates (counts and amounts, including conveyed transactions) by pertinent transaction type, currency, card brand, and transaction activity date.
The Acquirer Reference Number (ARN) is a unique 23 digit number created by Tesouro, that was assigned to the original transaction and provided to the acquiring and issuing banks for their purpose of tracing the transaction through the full process until it is funded to the bank.
The funded amount of the dispute, which may be different from the “dispute amount” if the original transaction’s amount was presented in a different currency than its funding currency.
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.
A unique identifier created by Tesouro and assigned to the transfer of money to a bank account for this dispute, that identifies a cohort of funded transactions making up the transfer.
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.
The perspective of the dispute, which can be either ‘Acceptor’ or ‘Partner’. This field is used to determine the perspective from which the dispute is reported.
A unique transaction identifier created by the entity holding the direct relationship with the Acceptor. Tesouro uses this identifier to manage idempotency.
A summary of financial activity for a given funds release date or transaction activity date. Use this report to understand financial impact of daily sales, reconcile sales activity to your bank deposits, or drill deeper into the composition of your funding.
A summary of authorizations (counts, amounts) for the given transaction date, grouped by acceptor, transaction currency, response code, and payment brand.
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.
A summary of aggregated fees by acceptor and fee name/program for a specified activity date or funds release date, grouped by fee type, and where applicable, payment brand, product, and funding source.
An itemized list of financially impacting ach returns occuring on the pertinent funds release dates. Use this report to track ach return-related money-movements.
An itemized list of financially impacting dispute events occuring on the pertinent funds release dates. Use this report to track dispute-related money-movements.
A summary of financial activity for a given funds release date or transaction activity date. Use this report to understand financial impact of daily sales, reconcile sales activity to your bank deposits, or drill deeper into the composition of your funding.
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.Deprecated: Use businessName instead.
A list of transaction requests (including conveyed) submitted on the pertinent transaction activity dates. Use this report as an operational tool to reconcile against your internal record of submitted transactions.
A summary of transaction aggregates (counts and amounts, including conveyed transactions) by pertinent transaction type, currency, card brand, and transaction activity date.
The total number of dispute debits and credits applied on your account. Calculated as [Dispute credits count - Dispute debits count]Deprecated: Use disputesCount instead.
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.
A unique identifier created by Tesouro and assigned to the transfer of money to a bank account, that identifies a cohort of funded transactions making up the transfer.
A reusable identifier created and used internally by Tesouro, and assigned to the configuration of funding profiles specifying who and/or where the funds transfer is sent.
A reusable, descriptive name specified by the transactor, labeling who and/or where the funds transfer is going. E.g., the name of a specific acceptor, a group of acceptors, a bank account, etc.
Specifies which payment brand was used, e.g., Visa, Mastercard, Discover, American Express, etc. NOTE: This field will present a null, not applicable, or empty value if the fee is not tied to a specific transaction.
The perspective of the funds transfer, which can be either ‘Acceptor’ or ‘Partner’. This field is used to determine the perspective from which the funds transfer is reported.
The processing network that the transaction was sent across, which may be unaffiliated with the card brand. NOTE: This field will present a null, not applicable, or empty value if the fee is not tied to a specific transaction.
A summary of authorizations (counts, amounts) for the given transaction date, grouped by acceptor, transaction currency, response code, and payment brand.
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.
A summary of aggregated fees by acceptor and fee name/program for a specified activity date or funds release date, grouped by fee type, and where applicable, payment brand, product, and funding source.
An itemized list of financially impacting ach returns occuring on the pertinent funds release dates. Use this report to track ach return-related money-movements.
An itemized list of financially impacting dispute events occuring on the pertinent funds release dates. Use this report to track dispute-related money-movements.
A summary of financial activity for a given funds release date or transaction activity date. Use this report to understand financial impact of daily sales, reconcile sales activity to your bank deposits, or drill deeper into the composition of your funding.
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.Deprecated: Use businessName instead.
A list of transaction requests (including conveyed) submitted on the pertinent transaction activity dates. Use this report as an operational tool to reconcile against your internal record of submitted transactions.
A summary of transaction aggregates (counts and amounts, including conveyed transactions) by pertinent transaction type, currency, card brand, and transaction activity date.
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.
A unique identifier created by Tesouro and assigned to the transfer of money to a bank account, that identifies a cohort of funded transactions making up the transfer.
Unique ISO four digit values used to classify merchants and their transactions into specific categories based on the type of business, trade or services supplied.
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.
Partially approved. The transaction was approved for an amount less than the original request because the cardholder’s account balance was insufficient to cover the full amount.
A unique transaction identifier created by the entity holding the direct relationship with the Acceptor. Tesouro uses this identifier to manage idempotency.
The last 4 digits of the tax identification number (TIN), which is a unique identifier created by the national government and associated with the acceptor at the time the transaction was submitted.
A request to the cardholder’s issuing bank to confirm that the account is active and has enough credit or funds to make the transaction. If approved, the requested amount is put on hold in the cardholder’s account.
A request to cancel a previous transaction request. Authorization reversals notify the cardholder’s issuer that all or part of a transaction has been canceled and that the authorization hold should be released.
Performs address and card security code checks on a cardholder’s account to ensure it is in good standing, without actually charging an amount to the card.
The perspective of the transaction, which can be either ‘Acceptor’ or ‘Partner’. This field is used to determine the perspective from which the transaction is reported.
A list of payment transaction requests (including conveyed) submitted on the pertinent transaction activity dates. Use this report as an operational tool to reconcile against your internal record of submitted transactions.
A summary of authorizations (counts, amounts) for the given transaction date, grouped by acceptor, transaction currency, response code, and payment brand.
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.
A summary of aggregated fees by acceptor and fee name/program for a specified activity date or funds release date, grouped by fee type, and where applicable, payment brand, product, and funding source.
An itemized list of financially impacting ach returns occuring on the pertinent funds release dates. Use this report to track ach return-related money-movements.
An itemized list of financially impacting dispute events occuring on the pertinent funds release dates. Use this report to track dispute-related money-movements.
A summary of financial activity for a given funds release date or transaction activity date. Use this report to understand financial impact of daily sales, reconcile sales activity to your bank deposits, or drill deeper into the composition of your funding.
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.Deprecated: Use businessName instead.
A list of transaction requests (including conveyed) submitted on the pertinent transaction activity dates. Use this report as an operational tool to reconcile against your internal record of submitted transactions.
A summary of transaction aggregates (counts and amounts, including conveyed transactions) by pertinent transaction type, currency, card brand, and transaction activity date.
A SKU, or Stock Keeping Unit, is a unique alphanumeric code assigned by a retailer to identify and track each distinct product or product variation within their inventory.
The metric used for understanding the quantity of a given line item. e.g., for quantities, use “each” or “piece” for length, use “meter” or “inch” for volume, use “liter” or “gallon” and for weight, use “gram” or “pound”, etc.
Unique ISO four digit values used to classify merchants and their transactions into specific categories based on the type of business, trade or services supplied.
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.
The acquirer token on file for this payment card, if the card has been used before and the transactor is subscribed to Tesouro’s tokenization services. Otherwise, this field’s value will be null.
Partially approved. The transaction was approved for an amount less than the original request because the cardholder’s account balance was insufficient to cover the full amount.
A unique transaction identifier created by the entity holding the direct relationship with the Acceptor. Tesouro uses this identifier to manage idempotency.
The last 4 digits of the tax identification number (TIN), which is a unique identifier created by the national government and associated with the acceptor at the time the transaction was submitted.
A request to the cardholder’s issuing bank to confirm that the account is active and has enough credit or funds to make the transaction. If approved, the requested amount is put on hold in the cardholder’s account.
A request to cancel a previous transaction request. Authorization reversals notify the cardholder’s issuer that all or part of a transaction has been canceled and that the authorization hold should be released.
Performs address and card security code checks on a cardholder’s account to ensure it is in good standing, without actually charging an amount to the card.
A summary of transaction aggregates (counts and amounts, including conveyed transactions) by pertinent transaction type, currency, card brand, and transaction activity date.
A summary of authorizations (counts, amounts) for the given transaction date, grouped by acceptor, transaction currency, response code, and payment brand.
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.
A summary of aggregated fees by acceptor and fee name/program for a specified activity date or funds release date, grouped by fee type, and where applicable, payment brand, product, and funding source.
An itemized list of financially impacting ach returns occuring on the pertinent funds release dates. Use this report to track ach return-related money-movements.
An itemized list of financially impacting dispute events occuring on the pertinent funds release dates. Use this report to track dispute-related money-movements.
A summary of financial activity for a given funds release date or transaction activity date. Use this report to understand financial impact of daily sales, reconcile sales activity to your bank deposits, or drill deeper into the composition of your funding.
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.Deprecated: Use businessName instead.
A list of transaction requests (including conveyed) submitted on the pertinent transaction activity dates. Use this report as an operational tool to reconcile against your internal record of submitted transactions.
A summary of transaction aggregates (counts and amounts, including conveyed transactions) by pertinent transaction type, currency, card brand, and transaction activity date.
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.
A request to the cardholder’s issuing bank to confirm that the account is active and has enough credit or funds to make the transaction. If approved, the requested amount is put on hold in the cardholder’s account.
A request to cancel a previous transaction request. Authorization reversals notify the cardholder’s issuer that all or part of a transaction has been canceled and that the authorization hold should be released.
Performs address and card security code checks on a cardholder’s account to ensure it is in good standing, without actually charging an amount to the card.
A summary of authorizations (counts, amounts) for the given transaction date, grouped by acceptor, transaction currency, response code, and payment brand.See AuthorizationSummaryCollection
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.
A summary of aggregated fees by acceptor and fee name/program for a specified activity date or funds release date, grouped by fee type, and where applicable, payment brand, product, and funding source.See FeeSummaryCollection
An itemized list of financially impacting ach returns occuring on the pertinent funds release dates. Use this report to track ach return-related money-movements.See FundingAchReturnOutputCollection
An itemized list of financially impacting dispute events occuring on the pertinent funds release dates. Use this report to track dispute-related money-movements.See FundingDisputeEventOutputCollection
A summary of financial activity for a given funds release date or transaction activity date. Use this report to understand financial impact of daily sales, reconcile sales activity to your bank deposits, or drill deeper into the composition of your funding.See FundingSummaryCollection
An itemized list of funded transactions (captures, sales, and refunds) for the selected transaction activity date or funds release date.See FundingTransactionCollection
The descriptive name for the acceptor that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.Deprecated: Use businessName instead.
A list of transaction requests (including conveyed) submitted on the pertinent transaction activity dates. Use this report as an operational tool to reconcile against your internal record of submitted transactions.See PaymentTransactionCollection
A summary of transaction aggregates (counts and amounts, including conveyed transactions) by pertinent transaction type, currency, card brand, and transaction activity date.See PaymentTransactionSummaryCollection
The descriptive name for the organization that is different from its legal entity name. Also known
as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.
The descriptive name for the organization that is different from its legal entity name. Also known as “Doing Business As” (DBA), “trade name”, “assumed name”, or “fictitious name”.Deprecated: Use businessName instead.
Unique ISO four digit value used to classify merchants and their transactions into specific categories based on the type of business, trade or services supplied.
Indicates whether acceptor boarding is enabled for the organization.Deprecated: Use the organization-level capabilities field instead. Check for ACQUIRING in capabilities.
Indicates whether underwriting applications are enabled for the organization.Deprecated: Use the organization-level capabilities field instead. Check for UNDERWRITING in capabilities.