Skip to main content
The Authentication fails when:
  • Test credentials are used in the production environment or vice versa.
  • Client ID and Client Secret are passed in the request body instead of as headers.
To troubleshoot this issue, follow these steps:
  • Use test credentials in the test environment and production credentials in the live environment.
  • Pass the Client ID and Client Secret as headers, not in the request body.
This scenario covers multiple concerns, such as server-to-server (S2S) feature is enabled for you, but it isn’t approved for your account or vice versa.To troubleshoot this issue, follow these steps:
  • The prerequisite for S2S is that it requires PCI DSS compliance.
  • To enable it, contact your Account Manager or fill in the Support Form. Once your account is reviewed and approved, this feature will be enabled.
The payment mode that the merchant is trying to make the payment isn’t enabled for the respective account.To troubleshoot this issue, follow these steps:
  • Log in to the Merchant Dashboard and go to Settings > Payment Methods to enable the mode.
  • Alternatively, contact your Account Manager or fill in the Support Form.
If you’re encountering null or empty objects in the Get Order API response, please consider below cases.
  • When no payment is associated with the order yet. ie a payment has not yet been attempted against the Order.
  • If there’s a delay in the payment being recorded due to bank or network delays.
  • You are hitting the Get payments for an order API before your end customer has tried to pay.
To troubleshoot this issue, follow these steps:
  • Please Configure webhooks to receive real-time payment updates.
  • Use the Get Payments for Order API, as the Get Order Status API will only return the order’s current state and not the payment specifics.
The Get Payments for an Order API (GET /pg/orders/{order_id}/payments) returns an empty array ([]) when no payment attempt exists for the order. This happens if the customer opens checkout and then exits, closes the page, or goes back without selecting a payment method such as UPI, card, or netbanking. Cashfree creates a payment object only after the customer selects a method and starts an attempt.Handle the response as follows:
  • Empty array ([]): no payment attempt. Do not treat this as USER_DROPPED. USER_DROPPED appears on a payment object after the customer selected a method and then left the flow.
  • One or more payment objects: use payment_status on each object. Possible values are SUCCESS, FAILED, PENDING, NOT_ATTEMPTED, USER_DROPPED, VOID, and CANCELLED.
The Get Payments for an Order API requires the following headers:
  • x-api-version: the API version you integrate with. Latest is 2026-01-01.
  • x-client-id: your App ID.
  • x-client-secret: your Secret Key.
Platforms that call the API on behalf of merchants use x-partner-apikey and x-partner-merchantid instead of x-client-id and x-client-secret. See API authentication.
Pass the dummy mobile number 9999999999 in the customer_phone field of your Create Order API request to avoid storing payment instrument details such as cards or UPI handles. Cashfree does not store instrument details against this dummy number.
If you’re encountering this issue, please consider below cases.
  • More than two decimal places have been provided for the ‘order_amount’ field. Eg: 10.123
  • Order Amount is 0 or negative.
  • You have exceeded the maximum amount limit set for your MID.
To troubleshoot this issue, follow these steps:
  • Please configure order_amount with only two decimal places maximum.
  • A minimum amount of one rupee is required.
  • Kindly get the maximum amount limit raised for your Merchant ID. Please contact your Account Manager or fill in the Support Form
If you’re encountering this issue, please check if your Merchant Category Code (MCC) is under the blocked list for UPI Intent. This feature is not allowed for certain categories of business due to RBI regulations.To troubleshoot this issue, please contact your Account Manager or fill in the Support Form