juspay/hyperswitch

[REFACTOR] remove redundant fields from webhook_details API and DB models

Open

#8,468 opened on Jun 26, 2025

View on GitHub
 (6 comments) (0 reactions) (1 assignee)Rust (4,676 forks)batch import
good first issue

Repository metrics

Stars
 (42,690 stars)
PR merge metrics
 (Avg merge 6d 22h) (213 merged PRs in 30d)

Description

Below fields are a part of WebhookDetails during merchant account creation / updation AND profile creation / updation.

pub payment_created_enabled: Option<bool>,
pub payment_succeeded_enabled: Option<bool>,
pub payment_failed_enabled: Option<bool>,

These fields are not being used in the backend flows and are redundant. These are needed to be removed for keeping the APIs clean.

Currently, they're being consumed in a few components

  • hyperswitch-control-center
  • hyperswitch postman tests
  • hyperswitch cypress tests

Once dependency on these fields is completely removed, these fields can be removed from API and DB models.

Contributor guide

Research direction
Identify all usages of the fields `payment created enabled`, `payment succeeded enabled`, and `payment failed enabled` across the hyperswitch codebase and in dependent projects (hyperswitch control center, Postman tests, Cypress tests). Ensure all dependencies are removed before deleting the fields from API models, DB models, and migrations. Start by searching for these field names in the repository and linked projects.
Tech stack
rust
Domain
backendapidatabase
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustSQL
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60