Skip to main content
You can query a specific transaction to retrieve detailed information about it. This is useful when a Paybyrd webhook is not received or a technical issue prevents your software from receiving a payment response. Without this response, your staff may be unable to verify whether the transaction was processed or what its result was. They may also attempt to cancel or refund the transaction, or inadvertently create a duplicate.

Query a transaction

Example request and response for the Query transactions endpoint:

Shift code and tip

For POS transactions, the response can include the shiftCode and tip fields. Use them to reconcile your POS shifts, for example to total the sales and tips of each shift. Both fields are optional:
  • shiftCode appears only when the transaction is linked to a shift. When there is no shift, the response doesn’t include the shiftCode key.
  • tip appears only when the transaction has a tip. When there is no tip, the response doesn’t include the tip key.
tip.amount uses the currency exponent, like the top-level amount field. For example, a tip with isoAmount 250 in EUR is "2.50", 300 in JPY is "300" and 1250 in BHD is "1.250".
The top-level amount and isoAmount include the tip. To get the amount without the tip, calculate isoAmount - tip.isoAmount. When there is no tip, the amount without the tip is isoAmount.

Query a transaction by acquirer custom identifier

Example request and response for querying a transaction by acquirer custom identifier:

See the Query transactions API endpoint for more details. The status field indicates whether the transaction was processed successfully. See the Transaction statuses table for the full list of possible values.