Payments Troubleshooting

Common integration errors and solutions for Payments

Authentication failed

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.

S2S_enabled_not_approved or POST/orders/pay is not enabled or approved

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.

Payment mode not enabled for merchant

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:

• Navigate to Settings > Payment Methods in your merchant dashboard to enable the mode.
• Alternatively, contact your Account Manager or fill in the Support Form.

Unable to delink existing AmazonPay wallet and add a new one

To troubleshoot this issue, follow these steps:

• The user needs to log out of the Amazon account from that system, clear the browser cache and try once again.

Null objects in Get Order / Payment API response

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.

Order Amount Invalid

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

UPI Intent not visible on checkout

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