---
title: "Search Transaction Using Transaction Code"
method: GET
path: "/v3/transactions/{code}"
tags: ["Search API"]
---

# Search Transaction Using Transaction Code

`GET /v3/transactions/{code}`

Retrieves detailed information about a transaction processed by PagSeguro using the provided `code`.  This endpoint allows merchants to check the status, payment details, and refund history of a specific transaction.

## Path parameters

- `code` string, uuid, required

## Response `200`

Transaction details retrieved successfully.

- object
  - `code` string — Unique transaction identifier (UUID) assigned by PagSeguro.
  - `status` string — Current status of the transaction.
  - `refundable` boolean — Indicates whether the transaction is eligible for a refund.
  - `integration` object — Details related to the merchant's store and order reference.
    - `reference` string — Unique order reference assigned by the merchant.
    - `store` integer — Identifier of the merchant's store.
    - `project` integer — Project ID provided by the merchant during integration.
    - `notification_url` string — URL where PagSeguro sends transaction status updates.
  - `charge` object — Information about the payment method used for the transaction.
    - `country` string — Country where the payer is located.
    - `type` string — Payment type used by the payer.
    - `method` string — Specific payment method used for the transaction.
    - `credit_card` object
      - `installments` integer — Number of installments selected by the payer.
      - `bin` string — The first 6 digits of the credit card number.
      - `last_four` string — The last 4 digits of the credit card number.
      - `expiration_date` string — Credit card expiration date in YYYY-MM format.
      - `card_on_file` object
        - `id` string — The ID of the stored card.
    - `initiated_by` string — Indicates who initiated the transaction.
    - `recurrence` object
      - `id` string — The recurrence ID.
      - `type` string — The type of recurrence.
      - `scheduling` string — The scheduling type for the recurrence (e.g., INITIAL, SUBSEQUENT).
    - `payment_response` object — Contains details of a failed payment attempt due to issues with card processing. This object is only returned for certain transactions. Contact your Account Manager for more details.
      - `code` integer — Error code indicating the reason for transaction failure.
      - `message` string — Description of the error or failure reason.
  - `checkout` object — Details of the checkout process.
    - `language` string — Language used at the checkout by the payer.
  - `payer` object — Information about the customer who made the purchase.
    - `email` string — Payer's email address.
  - `order` object — Details of the order associated with the transaction.
    - `date` string, date-time — Date and time when the transaction was created (UTC format).
    - `currency` string — Currency in which the order was processed (ISO 4217 code).
    - `items` object[] — List of products or services included in the transaction.
      - `quantity` integer — Number of units purchased for this item.
      - `description` string — Description of the item.
      - `unit_price` number, float — Price per unit of the item.
  - `payment` object
    - `type` string — The type of payment.
    - `method` string — The payment method used.
  - `refunds` object[] — List of refunds associated with the transaction.
    - `id` integer — Unique identifier of the refund request.
    - `reference` string — Refund reference assigned by the merchant.
    - `status` string — Current status of the refund request. Possible values: - `REQUESTED`: Refund has been requested. - `PROCESSING`: Refund is being processed. - `PROCESSED`: Refund has been successfully completed. - `REJECTED`: Refund request was denied.
    - `amount` number, float — Amount requested for the refund.
    - `date` string, date-time — Date and time when the refund request was created (UTC format).
    - `processing_date` string, date-time — Date and time when the refund was processed (UTC format).

## Other responses

- `400` — Bad Request - The request was malformed or contained invalid data.
- `401` — Unauthorized - Authentication failed due to missing or invalid credentials.
- `404` — Not Found - The requested resource was not found.

---

[API](https://skmtc.net/pagseguro/apis/pagseguro-international-api.md) · [All operations](https://skmtc.net/pagseguro/apis/pagseguro-international-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pagseguro/pagseguro-international-api/versions/032af0550731/schema)