# Payments, Attempts, Deposits

The payment response is intentionally nested so the merchant can render customer instructions and settlement progress from one object.

## Payment Object

Important fields:

* `id`: Artum payment ID.
* `status`: merchant-facing lifecycle status.
* `order_id`: your order ID.
* `receive`: what the merchant expects to receive.
* `attempts`: customer payment attempts.

## Attempt Object

Important fields:

* `id`: Artum attempt ID.
* `status`: attempt lifecycle status.
* `pay_with`: chain and asset the customer should use.
* `settlement`: settlement mode and merchant payout address.
* `instructions`: customer payment instructions.
* `funding`: pending and finalized funding amounts.
* `deposits`: observed blockchain transfers.
* `source_settlement`: settlement transaction state when available.

## Deposit Object

Important fields:

* `amount`: raw token amount observed.
* `asset`: asset observed.
* `tx_hash`: blockchain transaction hash.
* `status`: `pending`, `confirming`, `finalized`, or `rejected`.
* `confirmations`: current finality progress.
* `confirmations_required`: finality threshold.
* `detected_at`: time Artum observed the transfer.
* `finalized_at`: time the transfer reached finality, when available.

## UI Rule of Thumb

Show customer payment instructions from `attempts[0].instructions` while the payment is `awaiting_payment`.

Once `deposits[0]` appears, show finality progress as:

```
confirmations / confirmations_required
```

For the current mock, this becomes `0/16`, `4/16`, `8/16`, `12/16`, and `16/16`.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.artum.app/concepts/payments-attempts-deposits.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.