Get Eligible Payment Methods for Orders
Fetch the payment instruments a Cashfree order is eligible to use, including UPI, cards, netbanking, wallets, and EMI rails for personalised checkouts.
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:Client environment headers
Client environment headers
| Header | Accepted values | Requirement | Description |
|---|---|---|---|
x-client-device | mobile, desktop, tablet | Required | Type of device used by customer |
x-client-os | android, ios, windows, macos, linux, others | Required | Operating system of customer’s device |
x-client-rendering-type | mweb, webview, native | Required when x-client-device is mobile | Rendering method used for the checkout experience |
x-client-browser | safari, chrome, firefox, edge, others | Required | Browser used by the customer |
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
Client app ID. You can find your app id in the Merchant Dashboard.
Client secret key. You can find your secret key in the Merchant Dashboard.
Headers
API version to be used.
Request ID for the API call. Can be used to resolve tech issues. Communicate this in your tech related queries to Cashfree.
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.
Body
Request parameters to get eligible Payment Methods.
Response
Success response for getting eligible Payment Methods.
true
"payment_methods"
"netbanking"
{
"payment_method_details": [
{
"nick": "motak_kahindra_bank",
"display": "Motak Kahindra Bank",
"eligibility": true,
"code": 3032
},
{
"nick": "bank_of_india",
"display": "Bank Of India",
"eligibility": true,
"code": 3031
}
]
}