# Verify a payment

> Check the final status of a Paystack transaction using the Verify Transaction endpoint.

After a customer completes (or abandons) a payment, use the Verify Transaction endpoint to confirm the final outcome before delivering value. This is distinct from the API-level `status` field, which tells you whether the API call succeeded, not whether the payment succeeded.

> **Prefer webhooks for automated fulfilment.** Webhooks push updates to your server as soon as a payment settles. The verify endpoint is best for callback handling, manual reconciliation, and cases where you need to confirm state on demand.

## Transaction statuses

Only fulfil the order when `data.status` is `success`. For what every other status means and how to handle it, see [Transaction statuses](/payments/concepts/transaction-statuses).

## Call the Verify endpoint

Make a `GET` request from your server using the transaction reference. Use your **secret key**; never call this from the browser.

<localized-snippet src="payments/channels/verify-transaction">



</localized-snippet>

<callout type="warning">

`response.status` is the API call status (true/false). The transaction outcome is in `response.data.status`. Do not confuse the two.

</callout>

## Check the amount

Always verify the amount returned in `data.amount` matches the expected charge. The amount is in the smallest denomination of the currency (<localized-value page-key="markets" path="subunit">



</localized-value>

).

```js
const { status, amount } = result.data

if (status === 'success' && amount === expectedAmount) {
  // safe to deliver
}
```

## How to get the reference

<table>
<thead>
  <tr>
    <th>
      Integration method
    </th>
    
    <th>
      How to get the reference
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Popup / mobile SDKs
    </td>
    
    <td>
      Send it from the frontend to your server after checkout
    </td>
  </tr>
  
  <tr>
    <td>
      Redirect Checkout
    </td>
    
    <td>
      Read from the <code>
        reference
      </code>
      
       query parameter on your callback URL
    </td>
  </tr>
  
  <tr>
    <td>
      Charge API
    </td>
    
    <td>
      Use the <code>
        reference
      </code>
      
       returned when you created the charge
    </td>
  </tr>
</tbody>
</table>

## Store the authorization for recurring charges

A successful verify response includes `data.authorization` when the payment used a card. You can store the `authorization_code` and the customer email to charge the card again without going through checkout.

```json
{
  "data": {
    "status": "success",
    "amount": 50000,
    "authorization": {
      "authorization_code": "AUTH_8dfhjjdt",
      "channel": "card",
      "reusable": true
    }
  }
}
```

Only store authorizations where `reusable` is `true`. See [recurring charges](/payments/recurring/charge-authorization) for how to use them.
