---
title: "Get Payment Request Status"
method: GET
path: "/v5/devices/{device_id}/payment-requests/{request_id}"
tags: ["Devices"]
---

# Get Payment Request Status

`GET /v5/devices/{device_id}/payment-requests/{request_id}`

Retrieve the status of an asynchronous payment request initiated on a cloud device. The request_id is obtained from the initial payment request response (e.g., from POST /api/v5/devices/{deviceId}/payment-requests/sale). The device_id must match the device that initiated the payment request. This endpoint uses the same underlying functionality as GET /api/asyncstatus.

## Path parameters

- `device_id` string, required
- `request_id` string, required

## Response `200`

Payment request status retrieved successfully

- PaymentRequestStatusResponse — Payment request status response matching the structure returned by GET /api/v5/devices/{deviceId}/payment-requests/{request_id}
  - `object` 'payment-request', required — Resource type identifier
  - `id` string, required — Payment request ID
  - `status` 'pending' | 'completed' | 'error', required — Status of the payment request
  - `transaction` object, required — Transaction details if the payment request has been processed
    - `id` integer, nullable — Transaction ID
    - `type` string — Transaction type (e.g., 'sale', 'auth', 'credit', 'validate')
    - `success` boolean — Whether the transaction was successful
    - `condition` string — Transaction condition/status
    - `approval` string — Approval code
    - `authorized_amount` string — Authorized amount. Format: `x.xx`
    - `auth_code` string — Authorization code
    - `customer_vault_id` string — Customer vault ID associated with the transaction
    - `emv_metadata` object — EMV (chip card) metadata
      - `customer_verification_method` string — Customer verification method used
      - `application_id` string — EMV application ID
      - `application_label` string — EMV application label
      - `application_preferred_name` string — EMV application preferred name
      - `application_pan_sequence_number` string — EMV application PAN sequence number
      - `transaction_status_information` string — EMV transaction status information
      - `masked_merchant_number` string — Masked merchant number
      - `masked_terminal_number` string — Masked terminal number
    - `card_tokens` object[] — Card tokens associated with the transaction
      - `token` string — Card token
      - `type` string — Token type
  - `error` object — Error information if the payment request failed
    - `code` string — Error code
    - `ref_id` string — Error reference ID
    - `message` string — Error message

## Other responses

- `400` — Bad Request - The request was malformed or contained invalid parameters
- `401` — Unauthorized - Authentication credentials were missing or invalid
- `404` — Not Found - The requested resource could not be found
- `500` — Internal Server Error - An unexpected error occurred on the server

---

[API](https://skmtc.net/nmi/apis/embedded-components-api.md) · [All operations](https://skmtc.net/nmi/apis/embedded-components-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/nmi/embedded-components-api/versions/45c2ecda3685/schema)