## Find a payment

Retrieve details about a specific payment in your merchant account.

## Endpoint signature

```http
POST https://api.reservepay.com/merchants/find-payment HTTP/1.1
Content-Type: application/json
Accept: application/json
Authorization: Bearer <token>

{
  payment_id: string,
}
```

Returns: object

## Request arguments

### `payment_id` (string)

**Required**. The unique identifier of the payment to retrieve.

## Response attributes

### `payment_id` (string)

**Always present**. The ID of the payment.

### `external_id` (string)

_Nullable_. The merchant's internal reference for this payment.

### `status` (string)

**Always present**. The current status of the payment.

Possible values:

- `PENDING`
- `AUTHORIZED`
- `SUCCESSFUL`
- `FAILED`
- `REVERSED`
- `VOIDED`
- `EXPIRED`
- `REFUNDED`
- `PARTIALLY_REFUNDED`
- `DISPUTED`

### `amount` (number)

**Always present**. The payment amount in subunits.

### `currency` (string)

**Always present**. The 3-letter ISO currency code (e.g., 'THB').

### `payment_method` (string)

**Always present**. The payment method used (e.g., 'PROMPTPAY', 'CARD').

### `payment_method_display_name` (string)

**Always present**. The display name of the payment method.

### `card_last_digits` (string)

_Nullable_. The ending digits of the card number. Null for non-card payment methods or card payments without a token.

### `card_network` (string)

_Nullable_. The card network, such as visa or mastercard. Null for non-card payment methods or card payments without a token.

### `created_at` (number)

**Always present**. The creation timestamp (Unix timestamp).

### `authorized_at` (number)

_Nullable_. When the payment was authorized (Unix timestamp).

### `captured_at` (number)

_Nullable_. When the payment was captured (Unix timestamp).

### `expires_at` (number)

_Nullable_. When the payment expires (Unix timestamp).

### `capture` (string)

**Always present**. Whether the capture is automatic or manual.

Possible values:

- `AUTOMATIC`
- `MANUAL`

### `customer_id` (string)

_Nullable_. The ID of the customer (contact) associated with this payment.

### `customer_external_id` (string)

_Nullable_. The merchant's external reference for the customer (contact), if set.

### `customer_email` (string)

_Nullable_. The email address of the customer.

### `customer_mobile` (string)

_Nullable_. The mobile phone number of the customer.

### `customer_name` (string)

_Nullable_. The name of the customer.

### `fees` (array)

**Always present**. The fees associated with the payment.

### `ref1` (string)

_Nullable_. The first custom reference (e.g., invoice ID).

### `ref2` (string)

_Nullable_. The second custom reference.

### `ref3` (string)

_Nullable_. The third custom reference.

### `reversible` (boolean)

**Always present**. Whether the payment can be reversed.

### `capturable` (boolean)

**Always present**. Whether the payment can be captured.

### `voidable` (boolean)

**Always present**. Whether the payment can be voided.

### `refundable` (boolean)

**Always present**. Whether the payment can be refunded.

### `fraud_finding` (string)

_Nullable_. Whether the payment is considered risky or safe from a fraud perspective.

Possible values:

- `risky`
- `safe`

### `terminal_id` (string)

_Nullable_. The ID of the terminal that created the payment, if any.

### `payment_link_id` (string)

_Nullable_. The ID of the payment link that created the payment, if any.

### `payment_session_id` (string)

_Nullable_. The ID of the payment session associated with this payment, if any.

## Errors specific to this endpoint

### `NOT_FOUND`

This error occurs when no payment with the provided ID exists in your
merchant account. Double check that you're using the correct payment ID.

## Errors common to all endpoints

### `UNHANDLED_ERROR`

This error occurs when the server encounters an unexpected internal error that
it cannot handle gracefully. This typically happens due to bugs, infrastructure
issues, or edge cases that weren't anticipated during development.

### `INVALID_ARGUMENTS`

This error occurs when the request contains invalid or missing parameters.
Common cases include missing required fields, or values that don't match the
expected format or type.

### `BAD_VERSION`

This error occurs when making requests to an API version that does not exist.
This commonly happens when using an outdated SDK or when the API version
specified in the request URL is incorrect.