Skip to main content
Use this endpoint to fetch the details of a specific transaction by its unique identifier. This is particularly important in post-payment flows — for example, after receiving a webhook notification, you should always retrieve the transaction directly from the API to confirm its status before fulfilling an order or granting access to a product.

​
Endpoint

GET https://v2.certopaybrasil.com/api/transactions/{transactionId}

​
Authentication

All requests must include your secret API key in the X-Api-Key header.
​
X-Api-Key
string
required
Your CertoPay secret API key (e.g. sk_live_sua_chave_aqui).

​
Path Parameters

​
transactionId
string
required
The unique UUID of the transaction you want to retrieve. You can obtain this from the List Transactions endpoint or from a webhook payload.

​
Example Request

curl https://v2.certopaybrasil.com/api/transactions/uuid-da-transacao \
  -H "X-Api-Key: sk_live_sua_chave_aqui"

​
Response

Returns a single transaction object corresponding to the provided ID.

​
200 — Success

{
  "id": "uuid-da-transacao",
  "orderId": "uuid-do-pedido",
  "method": "PIX",
  "amount": 29700,
  "status": "PAID",
  "createdAt": "2026-06-26T10:00:00Z",
  "updatedAt": "2026-06-26T10:05:00Z"
}

​
Response Fields

​
id
string
Unique identifier (UUID) for this transaction.
​
orderId
string
UUID of the order associated with this transaction.
​
method
string
Payment method used. Possible values: PIX, BOLETO, CARD.
​
amount
integer
Transaction amount in centavos (e.g. 29700 = R$ 297,00).
​
status
string
Current status of the transaction (e.g. PAID, PENDING, FAILED, REFUNDED).
​
createdAt
string
ISO 8601 timestamp for when the transaction was created.
​
updatedAt
string
ISO 8601 timestamp for when the transaction record was last updated.
Always call this endpoint after receiving a transaction.paid webhook to verify the status before granting access. Never rely solely on the webhook payload to make access decisions — always confirm the current state directly from the API.