Skip to main content
POST
Run in Postman: You can also try this API in our Postman Collection.

Client environment headers

Cashfree requires information about the customer’s device environment to enforce NPCI rules. You must include the following headers in your Order Pay API and Get Eligible Payment Methods request:
x-client-rendering-type is required only when x-client-device is set to mobile. For desktop and tablet devices, this header is optional.

Authorizations

x-client-id
string
header
required

Client app ID. You can find your app id in the Merchant Dashboard.

x-client-secret
string
header
required

Client secret key. You can find your secret key in the Merchant Dashboard.

Headers

x-api-version
string
default:2026-01-01
required

API version to be used.

x-request-id
string

Request ID for the API call. Can be used to resolve tech issues. Communicate this in your tech related queries to Cashfree.

x-idempotency-key
string<UUID>

An idempotency key is a unique identifier you include with your API call. If the request fails or times out, you can safely retry it using the same key to avoid duplicate actions.

x-client-device
enum<string>

Accepted values are mobile, desktop, and tablet. Required for UPI Collect requests.

Available options:
mobile,
desktop,
tablet
x-client-os
enum<string>

The client device's operating system. This header is required for UPI Collect requests. The only accepted value is ios.

Available options:
ios
x-client-rendering-type
enum<string>

Accepted values are mweb, webview, and native. Required for UPI Collect requests when x-client-device is mobile. mweb renders the payment in a mobile browser, webview renders it inside an in-app browser, and native renders it natively inside a mobile app using SDKs.

Available options:
mweb,
webview,
native
x-client-browser
enum<string>

Accepted values are safari, chrome, firefox, and edge. Required for UPI Collect requests.

Available options:
safari,
chrome,
firefox,
edge

Body

application/json

Request Body to get eligible payment methods for an account and order.

eligibilty request to find eligible payment method.

queries
PaymentMethodsQueries · object
required

Payment Method Query Object.

Example:
filters
PaymentMethodsFilters · object

Filter for Payment Methods.

Example:

Response

OK

eligibility
boolean
Example:

true

entity_type
string
Example:

"payment_methods"

entity_value
string
Example:

"netbanking"

entity_details
object
Example: