Skip to content

Query transactions

Use GET /v1/reporting/transactions with these parameters:

Parameter Required Behavior
from Yes Inclusive start timestamp
to Yes Exclusive end timestamp; must be after from
country Yes Exact country value; must not be blank
limit No Default: 100; the service restricts the value to 1–1,000
currency No Exact transaction currency code
merchantTransactionId No Exact merchant transaction identifier
transactionId No Exact Net Money public transaction ID, within the authenticated seller’s scope

Use ISO-8601 timestamps with an offset. Use UTC with the Z suffix to avoid ambiguity. For another offset, use --data-urlencode so a plus sign reaches the service unchanged.

Omit optional filters when you do not need them. An empty string is still a filter value. The query does not convert country or currency values to uppercase.

Terminal window
curl --cert merchant.crt --key merchant.key \
--get "$REPORTING_URL/v1/reporting/transactions" \
--data-urlencode 'from=2026-08-01T00:00:00Z' \
--data-urlencode 'to=2026-08-02T00:00:00Z' \
--data-urlencode 'country=DE' \
--data-urlencode 'currency=EUR' \
--data-urlencode 'limit=100'

For certificate requirements, see Authentication.

The service returns a JSON object with a transactions array. An empty response has this form:

{"transactions": []}

Each row can include merchant identifiers, gross amounts, fees, settlement amounts, and invoice details. See the API reference for all fields. Fields without a value can be null.

The entityId field identifies the merchant whose payment is reported. A fee shown in a merchant’s report does not by itself mean that merchant is billed for it; your billing agreement determines who pays Net Money’s fees.

A payment can appear before any fee has been recorded. Its payment amount remains available, while fee, settlement, and invoice fields can be null. A numeric feeAmount of 0 is a recorded zero fee. A missing invoice does not by itself mean that the payment is missing or failed.

The transactionDate and transactionTime fields use UTC. The query selects rows by transaction creation time, not by settlement date.

The service returns the newest rows first. Rows with the same creation timestamp have no defined secondary order.

The limit applies to report rows. A payment with several fee entries can appear in several rows, each repeating its gross amount. Count each transactionId once when calculating payment counts or gross payment totals.

If a response reaches the limit, more rows can exist. You can query smaller time ranges, but this does not guarantee a complete export. The API has no cursor, offset, total count, or truncation flag.

Contact your Integration Manager if you need a guaranteed complete export. Do not advance a cursor from the displayed time: the response time has only second precision.