7. Transactions

Get one transaction

GET /api/v2/transactions/{transaction_id}

The path parameter is the numeric transaction_id string returned by a v2 create request. Send X-Api-Key and the signature of an empty body. The endpoint is scoped to your merchant and to transactions created through v2.

GET /api/v2/transactions/12346

Response 200 for a deposit:

{
  "order_id": "DEP-BOB-1001",
  "transaction_id": "12346",
  "status": "SUCCESS",
  "amount": 500,
  "currency": "BOB",
  "method": "your_bob_shop"
}

Field	Type	Meaning
order_id	string	Your identifier from the create request.
transaction_id	string	Payfield transaction ID.
status	string	PENDING, SUCCESS, or FAILED.
amount	JSON number	Transaction amount.
currency	string	Uppercase currency code.
method	string	The method shop code supplied at creation. If omitted, the selected shop's payment-method code when available; otherwise unknown.
account_number	string, optional	Withdrawal recipient account, or deposit payer account when available to the status API. Optional; PAN-shaped values are masked with the first 6 and last 4 digits visible.

For deposits, account_number availability depends on the configured payment channel and supported payer-data mapping. It may be omitted, including for P2P deposits. Supplying an account inside fields does not currently guarantee that it appears in the status response. Confirm support for your channel before depending on it. A transfer destination or beneficiary account is not a substitute for the payer account, and a missing field does not indicate a failed payment.

An unknown, foreign, or v1 transaction returns 404. The v2 API currently has no transaction-list endpoint and no lookup by order_id; store the returned transaction_id. See statuses.