# Checking payment method availability {#en_gate_available_methods}

An article about the capability of obtaining via Gate payment method availability information for processing a specific payment.

When working with different payment methods, in some cases you may need to get updates on their availability, for example, to keep the list of methods available to your customers accurate and up to date. The Ecommpay payment platform supports the capability of checking payment method availability via an API both for individual and for all integrated methods. At the same time, however, keep in mind that even if the payment method is available, the problems when processing payments made with this method can still occur.

To check payment method availability, use requests to the [/v2/info/available-methods/\{payment\_direction\}/list](https://api-developers.ecommpay.com/api.html/v2-info-available-methods-payment-direction-list) endpoints where `payment_direction` indicates the payment category you need: `payin` for purchases of any type and `payout` for payouts. When working with these requests, keep in mind the following:

-   Each request must contain the `general` object with two parameters:
    -   `project_id`—project identifier obtained from Ecommpay during integration.
    -   `signature`—request signaturegenerated after all required parameters are specified \(for details, see [Signature generation and verification](en_platform_signature.md)\).
-   If you need to check payment method availability for one or several specific payment methods, pass the `payment_method_list` array that specifies the [payment method code](en_pm_codes.md) for each method individually as a value of the `payment_method` parameter.

```language-json
{
  "general":{
    "project_id": 50,
    "signature": "qflDO7yiPKCFTyqCAaT+2/f9Gi20aV5woHKyf6J/CGJyuSjq1GH7BYgmil8APKojXw=="
    },
  "payment_method_list": [
        {
            "payment_method":"etoken"
        },
        {
            "payment_method":"google-pay"
        }
        ]
}
```

```language-json
{
  "general":{
    "project_id": 50,
    "signature": "qflDO7yiPKCFTyqCAaT+2/f9Gi20aV5woHKyf6J/CGJyuSjq1GH7BYgmil8APKojXw=="
    }
}
```

A payment method availability request is processed according to the synchronous model of interaction between the web server and the payment platform. This implies that the request is fully processed within one HTTP session and uses only the resources of the payment platform. The response to the correct request contains an HTTP response status code \(`200`\) and the required data without detailed request processing information. If the request is incorrect, or there have been issues with its acceptance and processing, then the response contains an HTTP response status code, request processing status `error` and the detailed description of the error that occurred. To learn more about HTTP response status codes, see [Interaction concepts](en_gate_interaction_organisation.md), and to learn more about the response codes that provide information on operation processing in the payment platform, see [Handling operation processing information](en_platform_payment_info_codes.md).

The body of the response to the correct request contains the project identifier, the signature, and the payment method availability array.

```language-json
{
    "project_id": 50,
    "signature": "qflDO7yiPKCFTyqCAaT+2/f9Gi20aV5woHKyf6J/CGJyuSjq1GH7BYgmil8APKojXw==",
    "available_methods":[
        {
            "payment_method":"etoken",
            "is_available": false
        },   
        {
            "payment_method":"google-pay",
            "is_available": true
        }]
}
```

```language-json
{
    "project_id": 50,
    "signature": "qflDO7yiPKCFTyqCAaT+2/f9Gi20aV5woHKyf6J/CGJyuSjq1GH7BYgmil8APKojXw==",
    "available_methods":[
        {
            "payment_method":"card",
            "is_available": true
        },    
        {
            "payment_method":"etoken",
            "is_available": false
        },    
        {
            "payment_method":"google-pay",
            "is_available": true
        }]
}
```

**Parent topic:**[Additional capabilities](en_Gate_Additional_capabilities.md)