This API allows you to retrieve various transaction and settlements data for a given mid.
Reporting API (1.0)
Request
This endpoint allows you to retrieve BECs-cleared settlement details for a specific merchant on a given date.
- Productionhttps://api.tyro.com/connect/reporting/merchants/{mid}/settlements?settlementDate={settlementDate}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://api.tyro.com/connect/reporting/merchants/{mid}/settlements?settlementDate=2019-08-24' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'Settlements response
The merchant ID associated with the Tyro account. Used to identify the merchant whose settlement data is being retrieved.
Requested settlement date (YYYY-MM-DD). Must be within the past 3 years.
List of settlements for the specified merchant on the given date. If the array is empty, it may indicate that the merchant does not settle via BECS, or no settlement occurred on that date.
ID of the clearing payment run used to bundle transactions for a settlement.
Multiple settlement entries may be returned due to settlement splits by scheme, by location, or due to additional settlement destinations such as loan repayments or ATO garnishees.
Settlement type indicating the destination account for the payment or transfer. More values may be added in the future.
Name of the institution receiving the settlement.
Account number of the settlement destination, partially masked.
Name associated with the settlement destination account.
Signed amount settled, in cents.
Indicates the time of the latest settlement status update. The format of the date time is the notation as defined by RFC 3339, section 5.6
Status of the settlement.
SENT- The settlement has been successfully sent from Tyro to the merchant’s destination financial institution. Note: The actual deposit time into the merchant’s account is determined by their bank and is not known by Tyro.PENDING- The settlement process has been initiated by Tyro, but funds have not yet left Tyro’s systems.ON_HOLD- The settlement is currently withheld. This may occur due to account suspension, suspected fraud, or participation in a net settlement arrangement. Funds are retained by Tyro until resolution.RESUBMISSION_INITIATED- The settlement got returned back by customer's bank and Tyro initiated its resubmission.RESUBMISSION_SENT- The settlement got returned back by customer's bank and resubmission was successfully sent from Tyro.RESUBMISSION_ON_HOLD- The settlement got returned back by customer's bank and resubmission is on hold and funds are withheld by Tyro.WITHHELD_BY_ACQUIRER- The settlement failed and funds are withheld by Tyro.WITHHELD_BY_BANK- The settlement failed and funds are withheld by the customer's bank.
- Single Settlement Returned
- Multiple Settlements Returned
{ "mid": "111", "settlementDate": "2021-07-01", "settlements": [ { … } ] }
Request
This endpoint allows you to retrieve a merchant's list of transactions for a given terminal business day.
- Productionhttps://api.tyro.com/connect/reporting/merchants/{mid}/transactions?transactionDate={transactionDate}&limit=100&page=1
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://api.tyro.com/connect/reporting/merchants/{mid}/transactions?transactionDate=2019-08-24&limit=100&page=2' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'Transactions response
The date (YYYY-MM-DD) that the terminal has processed the requested transactions.
Details of the merchant for whom the transactions are reported.
List of transactions for the specified merchant and date.
Unique identifier for the transaction.
The local date and time on the terminal when the transaction was processed.
Status of the transaction. Possible values include APPROVED, DECLINED, CANCELLED, TIMED_OUT, VOIDED, PRE_AUTHORISED.
Description of the transaction.
A unique identifier used to represent a specific location of a merchant.
A unique identifier of the terminal used to process the transaction.
Type of device used to process the transaction.
Mobile platform type if applicable.
Payment method type. Possible values include GOODS_AND_SERVICES, REFUND_GOODS_AND_SERVICES, GOODS_AND_SERVICES_WITH_CASH, CASH_WITHDRAWAL, CREDIT_ADJUSTMENT.
Fee structure applied. Possible values include DEBIT_EFTPOS_CASHOUT, DEBIT_EFTPOS_NO_CASHOUT, CREDIT_SWIPED, CREDIT_COMMERCIAL_AND_PREMIUM, INTERNATIONAL, MASTERCARD_INTERNATIONAL, UNION_PAY_INTERNATIONAL_DEBIT, DEBIT_SCHEME_SWIPED, AMEX_JCB_FEES, ALIPAY, NO_FEES, UNKNOWN.
Source account type. Possible values include DEFAULT, SAVINGS, CHEQUE, CREDIT.
Whether this was an express payment (i.e. Visa or Mastercard purchases under $35).
Card type/scheme. Possible values include VISA, MASTERCARD, EFTPOS, UNION_PAY, AMEX, JCB, DINERS.
Masked card number, with only the last four digits visible.
How the card payment was processed. Possible values include CHIP, CONTACTLESS, CONTACTLESS_MAG_STRIPE, MAG_STRIPE, CHIP_ERROR_MAG_STRIPE_USED, MANUAL, UNKNOWN.
Whether this is an e-commerce transaction.
E-commerce order id if applicable.
Reason for reversal if applicable.
Whether the transaction was processed with in a foreign currency.
Details for a Dynamic Currency Conversion (DCC) transaction.
Foreign currency code for DCC transaction.
Amount in foreign currency (in cents).
Refund amount (negative value, in cents).
Surcharge amount (in cents).
Amount to be paid to merchant (in cents).
Net settlement amount after fees (in cents).
Acquiring fee charged to merchant (in cents).
Action code from acquirer. Possible values include APPROVED, DECLINED, CALL_ISSUER, CAPTURE_CARD.
Tyro transaction reference number. Maximum six digits.
Pagination details for the transaction results.
The maximum number of transactions that can be returned per page.
{ "terminalBusinessDay": "2025-05-26", "merchantDetails": { "mid": "122", "tradingName": "Test Merchant" }, "transactions": [ { … }, { … }, { … } ], "pagination": { "page": 1, "size": 3, "limit": 100, "total": 3 } }