> ## Documentation Index > Fetch the complete documentation index at: https://docs.cleo-pay.com/llms.txt > Use this file to discover all available pages before exploring further. # Get a payment > GET /v1/payments/{paymentId} reads one payment: status, rail, source, hold and return reasons, expected arrival and a dashboard link. ``` GET /v1/payments/{paymentId} ``` **Scope:** `payments:read` or `payables:read` The payment's `id`, from `POST /v1/payments`, `GET /v1/payments` or the `data.id` of a `payment.*` event. ## Response `200` with the [payment](/concepts/payments#the-payment-object). `pending`, `scheduled`, `processing`, `held`, `completed`, `failed`, `returned`, `cancelled`, `refund_pending` or `refunded`. Accept values you do not know. `DWOLLA` or `CLEO_PAY`. `null` for a payment recorded outside Cleo. `BALANCE` or `BANK` on Cleo Pay. `null` on Dwolla. `vendor_invitation_pending` or `vendor_bank_missing`, when held. Cleo Pay only, once the payout is sent. Why a bank sent the money back, in plain words. Why the payment failed. The bill's page in the Cleo web app. This payment's amount. The bill. The vendor. The payer bank the payment pulled from, when there is one. When it runs or ran. When it was processed. A payment from another business answers `404 not_found`. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.