# GET /v1/xrpl/payment/verify

Did this settled payment deliver the expected asset and amount to the expected account?

## Purpose

Reads the transaction `hash` once and compares what it delivered with what you expected, returning a derived `verdict` and nothing else about the account. The answer is never an error when the transaction is absent: `not_found` (definitive, the transaction was never validated and no longer can be), `not_found_recent` (not found in the server's history window, not definitive), `beyond_history` (the searched range falls outside the server's history, not definitive) and `not_final` (it can still be validated) are verdicts with a 200. The other verdicts are `not_a_payment`, `failed` (the result was not `tesSUCCESS`), `wrong_recipient`, `wrong_sender` (only with `source`), `wrong_destination_tag` (only with `destination_tag`), `unverifiable` (the ledger does not state what was delivered), `wrong_asset`, `underpaid` (less than `amount` was delivered) and `paid`. The first verdict that matches, in that order, is the one returned.

| Verdict | What settles it | Definitive |
|---|---|---|
| `not_found` | `txnNotFound` with `last_ledger_sequence` given, at or below the latest validated ledger, and the whole range searched: the transaction was never validated and can no longer be | definitive |
| `not_found_recent` | `txnNotFound` without `last_ledger_sequence`: not found in the server's history window | not definitive |
| `beyond_history` | `txnNotFound` with `last_ledger_sequence` at or below the latest validated ledger, but the answer does not confirm the whole range was searched | not definitive |
| `not_final` | the transaction is not validated yet, or `last_ledger_sequence` is above the latest validated ledger: it can still be validated | not definitive |
| `not_a_payment` | the transaction is not a `Payment` | definitive |
| `failed` | the result is not `tesSUCCESS` | definitive |
| `wrong_recipient` | `Destination` differs from `destination` | definitive |
| `wrong_sender` | `source` is given and `Account` differs | definitive |
| `wrong_destination_tag` | `destination_tag` is given and the transaction carries none or another | definitive |
| `unverifiable` | the ledger does not state what was delivered | definitive |
| `wrong_asset` | the delivered asset differs from `asset` | definitive |
| `underpaid` | less than `amount` was delivered | definitive |
| `paid` | none of the above applies | definitive |

`delivered` is always the amount the ledger says was delivered, never the amount the payer asked to send, so a partial payment is reported as it settled and `partial_payment` says whether the payment allowed one. `excess` is what was delivered above `amount` on a `paid` verdict. `valuation` is an informative EUR and USD reference value given only on a `paid` or `underpaid` verdict for a registry stablecoin when an ECB rate on or before the payment date is stored; otherwise it is `null`. The value is an informative reference, not a tax figure. Source: ECB statistics. Pass the `LastLedgerSequence` you signed as `last_ledger_sequence`: without it an absent transaction can only answer `not_found_recent`, which is not definitive. A validated transaction never changes and a definitive `not_found` cannot change, so those answers are fresh for 86400 seconds and served stale for up to 604800; `not_found_recent`, `beyond_history` and `not_final` are fresh for 4 seconds and served stale for up to 30. If the upstream read fails, an answer cached within its stale window is served instead of a 503.

## When to use

After a payment has been submitted: to confirm from the ledger that it delivered the asset and amount you expected to the account you expected, including the partial-payment case.

## When not to use

Before sending a payment (use `/v1/xrpl/payment-readiness`), or to list an account's recent payments (use `/v1/xrpl/account/{address}/transactions`).

## Parameters

| Name | In | Required | Description | Constraints | Example |
|---|---|---|---|---|---|
| `hash` | query | yes | Transaction hash of the payment to verify. | 64 hexadecimal characters, either case (canonicalized to upper case) | `002C12C53476173ABC1001505C40A24CCC90F642480C924C1B748E339FA1B069` |
| `destination` | query | yes | Account the payment had to reach. | Valid classic XRPL address (r..., checksum verified) | `rfaecmugiPaAkFpBT9Bmq8f3n42oXe6m1C` |
| `asset` | query | yes | Asset the payment had to deliver. `XRP`, or `CODE.issuer`: `CODE` is a 3-character standard code or 40 hexadecimal digits, and `issuer` is a classic XRPL address. Standard codes are case-sensitive: `usd` and `USD` are different tokens, so send the exact code. A standard code uses letters, digits or `?!@#$%^&*<>(){}[]\|` and is never `XRP`; percent-encode the symbols in a URL (for example `%3F` for `?`). A 40-hex code is read in any case, and the 40-hex form of a standard code means that code. Or a 48-hex MPT issuance id (hex letters in either case), with `amount` in whole base units. | `XRP`, or `CODE.issuer`: `CODE` is a 3-character standard code or 40 hexadecimal digits, and `issuer` is a classic XRPL address. Standard codes are case-sensitive: `usd` and `USD` are different tokens, so send the exact code. A standard code uses letters, digits or `?!@#$%^&*<>(){}[]\|` and is never `XRP`; percent-encode the symbols in a URL (for example `%3F` for `?`). A 40-hex code is read in any case, and the 40-hex form of a standard code means that code. Or a 48-hex MPT issuance id (hex letters in either case), with `amount` in whole base units. | `XRP` |
| `amount` | query | yes | Amount the payment had to deliver, in units of `asset` (base units for an MPT). | Positive decimal string (no exponent); an XRP amount has at most 6 decimals (1 drop); an MPT amount is a whole number of base units (digits only) | `0.00001` |
| `destination_tag` | query | no | Destination tag the payment had to carry; without it the tag is not compared. | Integer from 0 to 4294967295 | `12345` |
| `source` | query | no | Account the payment had to come from; without it the sender is not compared. | Valid classic XRPL address (r..., checksum verified) | `rEPak6n2CEsQmowqsTMnkooskcLaGW9MzE` |
| `last_ledger_sequence` | query | no | The `LastLedgerSequence` of the transaction the payer submitted. Pass it to get a definitive answer when the transaction is absent. | Integer from 1 to 4294967295 | `108267504` |

## Request example

```sh
curl -s "https://api.criptonlabs.com/v1/xrpl/payment/verify?hash=002C12C53476173ABC1001505C40A24CCC90F642480C924C1B748E339FA1B069&destination=rfaecmugiPaAkFpBT9Bmq8f3n42oXe6m1C&asset=XRP&amount=0.00001&last_ledger_sequence=108267504"
```

## Response example (200)

```json
{
  "verdict": "paid",
  "expected": {
    "asset": "XRP",
    "value": "0.00001"
  },
  "delivered": {
    "asset": "XRP",
    "value": "0.00001"
  },
  "excess": "0",
  "sender": "rEPak6n2CEsQmowqsTMnkooskcLaGW9MzE",
  "partial_payment": false,
  "ledger_index": 108267406,
  "close_time": "2026-11-11T20:15:52.000Z",
  "valuation": null,
  "meta": {
    "ledger_index": 108267406,
    "as_of": "2026-11-11T20:17:31.320Z",
    "age_seconds": 0,
    "cache": "miss",
    "stale": false
  }
}
```

## Errors

- 400 [invalid-parameters](https://api.criptonlabs.com/errors/invalid-parameters.md)
- 400 [bad-request](https://api.criptonlabs.com/errors/bad-request.md)
- 429 [rate-limited](https://api.criptonlabs.com/errors/rate-limited.md)
- 503 [upstream-unavailable](https://api.criptonlabs.com/errors/upstream-unavailable.md)

## Caching

Fresh for 4 seconds; on upstream failure the last good value is served for up to 30 seconds (`meta.stale` is `true`), then the service answers 503. See the [freshness guide](https://api.criptonlabs.com/docs/guides/freshness.md).

## Rate limit

Tier `expensive`. See the [rate-limits guide](https://api.criptonlabs.com/docs/guides/rate-limits.md).

## MCP tool

The MCP tool `xrpl_payment_verify` returns the same data. See the [MCP quickstart](https://api.criptonlabs.com/docs/guides/mcp-quickstart.md).
