Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]: Cashfree Integration Issue with Webhook and Payment Flow #3105

Closed
AyushChothe opened this issue Jan 25, 2025 · 0 comments · Fixed by #3106
Closed

[BUG]: Cashfree Integration Issue with Webhook and Payment Flow #3105

AyushChothe opened this issue Jan 25, 2025 · 0 comments · Fixed by #3106

Comments

@AyushChothe
Copy link
Contributor

Describe the bug
After testing the Cashfree integration in the Test environment, I encountered an issue where the Lago Cashfree webhook URL could not be added to the Cashfree Dashboard. Additionally, the payment flow was not functioning as expected.

Expected behavior
Users should be able to copy the webhook URL generated in the Lago UI, add it to the Cashfree Dashboard, and receive a valid 200 response for webhook triggers. This ensures that Cashfree recognizes the URL as a valid webhook endpoint.

Additional Context
The issue arises due to Cashfree using two different sets of webhook headers:

  1. Headers for the "Test and Add Webhook" button in the Cashfree Dashboard.
  2. Headers for actual webhook triggers during live operations.
  • Test/Add Webhook Payload: Uses X-Webhook-Signature and X-Webhook-Timestamp headers.
  • Actual Webhook Payload: Uses X-Cashfree-Signature and X-Cashfree-Timestamp headers.

This discrepancy prevents users from successfully adding webhook URLs to the Cashfree Dashboard.

Version

  • Lago: v1.19.1
@AyushChothe AyushChothe changed the title [BUG]: Cashfree Integration Issue with Webhook Addition and Payment Flow [BUG]: Cashfree Integration Issue with Webhook and Payment Flow Jan 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant