# Get payment actions

You can retrieve information about the history and lifecycle of a payment or payout using the payment `id` returned in the response to your payment or payout request.

For the full API specification, refer to the [API reference](https://api-reference.checkout.com/tag/Payments/#operation/getPaymentActions).

> **Information**
>
> Your base URL's `{prefix}` value is unique to your account and environment. To learn how to retrieve your base URLs for the sandbox and production environments, see [API endpoints](https://www.checkout.com/docs/developer-resources/api/api-endpoints.md).

**Production**

`GET` `https://{prefix}.api.checkout.com/payments/{id}/actions`

**Sandbox**

`GET` `https://{prefix}.api.sandbox.checkout.com/payments/{id}/actions`

The response will contain the history and lifecycle of the payment or payout that matches the ID you provided.

> **Note**
>
> If a payment matching the ID you provided is not found, you receive a `404 – Payment not found` error.
>
> An authentication is not considered a payment action. Therefore, you also receive a `404` error if you attempt to retrieve the actions for a payment that you requested authentication for, but has expired, failed, or was canceled before you could continue with the payment.

### Response example

**Pay-in actions**

```json
[
  {
    "id": "act_fd3h6evhpn3uxdoqbuu3lqnqbm",
    "type": "Refund",
    "processed_on": "2024-01-20T10:30:48Z",
    "amount": 1000,
    "approved": true,
    "response_code": "10000",
    "response_summary": "Approved"
  },
  {
    "id": "act_gefycn3jcvuupboxfmqrhk2aym",
    "type": "Capture",
    "processed_on": "2024-01-17T10:30:48Z",
    "amount": 6540,
    "approved": true,
    "response_code": "10000",
    "response_summary": "Approved",
    "processing": {
      "acquirer_reference_number": "24021219099007452440793",
      "acquirer_transaction_id": "00745244079"
    },
    "metadata": {
      "shipping_ref": "MQIBN2"
    }
  },
  {
    "id": "act_y3oqhf46pyzuxjbcn2giaqnb44",
    "type": "Authorization",
    "processed_on": "2024-01-17T09:30:48Z",
    "amount": 6540,
    "approved": true,
    "auth_code": "643381",
    "response_code": "10000",
    "response_summary": "Approved",
    "reference": "ORD-5023-4E89",
    "processing": {
      "retrieval_reference_number": "909913440644",
      "acquirer_transaction_id": "440644309099499894406"
    }
  }
]
```

**Payout actions**

```json
[
  {
    "id": "act_cvrbczl5llgehjzjqdupeezwt4",
    "type": "Return",
    "processed_on": "2024-06-12T13:49:19.145592Z",
    "amount": 1000,
    "approved": true,
    "response_code": "30046",
    "response_summary": "Bank Account Closed"
  },
  {
    "id": "act_rhpascoezcwuxbez3qhsbtgpd4",
    "type": "Payout",
    "processed_on": "2024-06-12T13:49:19.1050138Z",
    "amount": 1000,
    "approved": true,
    "response_code": "10000",
    "response_summary": "Approved"
  }
]
```

---

## Payment action definitions

The history of a payment or payout is described through the payment actions that occurred during its lifecycle.

The following table describes the possible payment actions you may see in your response:

| Payment action | Description |
| --- | --- |
| `Authorization` | The payment request was sent successfully. |
| `Capture` | The authorized payment was captured in full. |
| `Card Verification` | The card verification request has been approved and the cardholder’s details have been saved to their account. |
| `Payout` | The payout request was processed successfully. To check whether the payout itself was successful, check the `approved` field in the response. |
| `Refund` | Part or all of the captured amount was refunded. |
| `Return` | The payout was returned. For example, because the destination account has been closed. |
| `Void` | The payment was voided and never captured; the funds were returned to the customer. |

---

## Payment actions expiry

Some payment actions will expire after a period of time. The following table describes the expiry timelines for each scheme:

> **Information**
>
> You can request a manual partial or full refund within 365 days of the initial payment, or within 180 days for Automated Clearing House (ACH). This applies to all schemes.

| Scheme | Initial authorization | Estimated authorization | Incremental authorization | Final partial captures |
| --- | --- | --- | --- | --- |
| Visa | 10 days or 30 days, depending on your processing configuration | 10 days | 10 days | - No further actions are allowed<br>- [Manual voids](https://www.checkout.com/docs/payments/manage-payments/void-a-payment.md) return a `403` [status code](https://www.checkout.com/docs/developer-resources/testing/codes/api-response-codes.md#HTTP_status_codes)<br>- Automatic void is triggered after 30 days |
| Mastercard | 7 days or 30 days, depending on your processing configuration | 30 days | 30 days | - No further actions are allowed<br>- [Manual voids](https://www.checkout.com/docs/payments/manage-payments/void-a-payment.md) return a `403` [status code](https://www.checkout.com/docs/developer-resources/testing/codes/api-response-codes.md#HTTP_status_codes)<br>- Automatic void is triggered after 30 days |
| American Express | 30 days | Not applicable | Not applicable | Not applicable |
| Cartes Bancaires | 7 days | Not applicable | Not applicable | Not applicable |
| Diners Club International | 30 days | Not applicable | Not applicable | Not applicable |
| Discover | 30 days | Not applicable | Not applicable | Not applicable |

For a full list of authorization validity periods as set by the card schemes, see [Authorization validity period](https://www.checkout.com/docs/payments/manage-payments/authorize-a-payment.md#Authorization_validity_period).