​

Troubleshooting

This guide covers common issues you might encounter while integrating fype and how to resolve them.

​

Authentication Errors

​

401 Unauthorized

• Cause: The API key provided is invalid, revoked, or missing.
• Solution: Check your Authorization header. Ensure it follows the format Bearer fype_test_.... Verify in the dashboard that the key has not been revoked.

​

403 Forbidden

• Cause: You are trying to access a resource that doesn’t belong to your merchant account, or you are using a Test key for a Live resource (or vice-versa).
• Solution: Ensure you are using the correct key for the environment (Test vs Live).

​

Payment Creation Errors

​

400 Bad Request: Amount too small

• Cause: The amount field must be at least 100 subunits (e.g., ₹1.00).
• Solution: Increase the amount in your request.

​

400 Bad Request: Invalid Idempotency Key mismatch

• Cause: You sent a request with an Idempotency-Key that was previously used, but the request body is different.
• Solution: Use a unique key for every unique payment intent. If you are retrying a failed request, ensure the body is exactly the same.

​

Webhook Issues

​

Webhooks not being delivered

• Cause: The endpoint URL is incorrect, your server is down, or fype’s IPs are blocked.
• Solution:
• Check the Webhook Deliveries log in the dashboard.
• Verify your server is returning a 200 OK.
• Test your endpoint using the Trigger Test utility in the dashboard.

​

Signature Verification Failed

• Cause: The whsec_ secret is incorrect, or you are not using the raw request body for hashing.
• Solution:
• Double-check the signing secret for the specific endpoint.
• Ensure your framework isn’t modifying the body (e.g., removing whitespace) before you verify the signature.

​

Checkout Page Issues

​

”Provider not configured”

• Cause: You are trying to load a Live checkout session but haven’t connected a provider (like Razorpay) in the Providers tab.
• Solution: Connect your gateway credentials in the dashboard for the Live environment.

​

Checkout session expired

• Cause: Checkout sessions typically expire after 1 hour of inactivity.
• Solution: Create a new payment and redirect the customer again.

​

Need More Help?

If you can’t find the answer here:

• Check our API Reference.
• Search the Dashboard Logs.
• Contact our developer support team at support@fype.dev.