---
title: "Retrieve payment"
method: GET
path: "/smart-transfers/payments/{id}"
tags: ["Smart Transfer"]
---

# Retrieve payment

`GET /smart-transfers/payments/{id}`

Recovers the smart transfer payment resource by its id

## Path parameters

- `id` string, uuid, required

## Response `200`

Retrieve a payment

- SmartTransferPayment — Smart transfer payment
  - `id` string, required — Payment primary identifier
  - `preauthorizationId` string, required — Payment primary identifier
  - `status` 'CONSENT_AUTHORIZED' | 'CONSENT_REJECTED' | 'PAYMENT_PENDING' | 'PAYMENT_PARTIALLY_ACCEPTED' | 'PAYMENT_SETTLEMENT_PROCESSING' | 'PAYMENT_SETTLEMENT_DEBTOR_ACCOUNT' | 'PAYMENT_COMPLETED' | 'PAYMENT_REJECTED' | 'ERROR' | 'CANCELED', required — Lifecycle of a Smart Transfer payment. Narrower than `PaymentIntentStatus`: Smart Transfer payments operate under an already-authorized preauthorization, so consent-collection statuses (`STARTED`, `ENQUEUED`, `CONSENT_AWAITING_AUTHORIZATION`) and consent-revocation statuses (`REJECTED`, `REVOKED`, `CONSUMED`) do not apply. - `CONSENT_AUTHORIZED`: the payment was accepted under the preauthorization and is ready to be processed. - `CONSENT_REJECTED`: the preauthorization was rejected at execution time. - `PAYMENT_PENDING`: the payment was submitted to the institution and is awaiting confirmation. - `PAYMENT_PARTIALLY_ACCEPTED`: the payment was accepted but still needs an additional authorization. - `PAYMENT_SETTLEMENT_PROCESSING`: the settlement is being processed. - `PAYMENT_SETTLEMENT_DEBTOR_ACCOUNT`: the funds were debited from the payer account; awaiting clearing. - `PAYMENT_COMPLETED`: the payment was confirmed by the institution. - `PAYMENT_REJECTED`: the payment was rejected after consent was authorized. - `ERROR`: an unexpected error occurred during the flow. - `CANCELED`: the payment was canceled.
  - `amount` number, required — Payment amount
  - `description` string — Payment description
  - `recipient` PaymentRecipient — Bank-account payment recipient. Returned by `/payments/recipients` endpoints and embedded inside payment requests when the request targets a registered recipient.
    - `type` 'BANK_ACCOUNT', required — Recipient discriminator. Always `BANK_ACCOUNT` for this schema.
    - `id` string, required — Primary identifier
    - `taxNumber` string, required — Account owner tax number. Can be CPF or CNPJ (only numbers).
    - `name` string, required — Account owner name.
    - `paymentInstitution` PaymentInstitution, required — Response with information related to a payment institution
      - `id` string, required — Primary identifier
      - `name` string, required — Payment institution name
      - `tradeName` string, required — Payment institution trade name
      - `ispb` string, required — Payment institution ISPB
      - `compe` string — Payment institution COMPE
      - `createdAt` string, date-time, required — Date when the payment institution was created
      - `updatedAt` string, date-time, required — Date when the payment institution was updated
    - `isDefault` boolean, required — Indicates if the recipient is the default one
    - `account` PaymentRecipientAccount, required — Payment receiver bank account information
      - `branch` string, required — Receiver bank account branch (agency)
      - `number` string, required — Receiver bank account number
      - `type` string, required — Receiver bank account type, could be: 'CHECKING_ACCOUNT', 'SAVINGS_ACCOUNT' or 'GUARANTEED_ACCOUNT'
    - `pixKey` string — Pix key associated with the payment recipient
    - `createdAt` string, date-time, required — Date when the payment recipient was created
    - `updatedAt` string, date-time, required — Date when the payment recipient was last updated
  - `clientPaymentId` string — Client payment identifier
  - `createdAt` string, date-time, required — Date when the payment was created
  - `updatedAt` string, date-time, required — Date when the payment was updated
  - `errorDetail` object — Error detail
    - `code` 'INFRASTRUCTURE_FAILURE' | 'PAYMENT_DIFFERENT_FROM_CONSENT' | 'UNKNOWN_ERROR' | 'INVALID_PAYMENT_DETAIL' | 'PAYMENT_REJECTED_BY_HOLDER' | 'PAYMENT_REJECTED_BY_SPI' — Error code. - INFRASTRUCTURE_FAILURE: Indicates a failure in the infrastructure of the institution holding the information or resources. - PAYMENT_DIFFERENT_FROM_CONSENT: Payment data differs from consent data. - UNKNOWN_ERROR: Unknown error. - INVALID_PAYMENT_DETAIL: The payment detail is invalid. - PAYMENT_REJECTED_BY_HOLDER: The payment was rejected by the account holder. - PAYMENT_REJECTED_BY_SPI: The payment was rejected by the SPI.
    - `description` string — Error description
    - `detail` string — Error detail

## Other responses

- `404` — Smart Transfer Payment not found

---

[API](https://skmtc.dev/pluggy/apis/pluggy-api.md) · [All operations](https://skmtc.dev/pluggy/apis/pluggy-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/pluggy/pluggy-api/revisions/75e87ec7f9cd/schema)