[REFACTOR] Integrate the card expiration month/year and security code newtypes in request/response types
- Dominant language
- Rust
- Stars
- 43.6k
- Forks
- 5.1k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 210
Description
### Feature Description
Our API models (request/response types) need to be refactored to use the card security code and expiry month/year newtypes added in PR #874.
2 such locations in our codebase are:
https://github.com/juspay/hyperswitch/blob/897250ebc3ee57392aae7e2e926d8c635ac9fc4f/crates/api_models/src/payments.rs#L152
https://github.com/juspay/hyperswitch/blob/897250ebc3ee57392aae7e2e926d8c635ac9fc4f/crates/api_models/src/payment_methods.rs#L77-L83
In other types, the fields might be called `cvc`, `cvv`, `expiry_month`, `expiry_year`, `exp_month`, `exp_year`, etc.
_For external contributors, clarify any questions you may have, and let us know that you're interested in picking this up. We'll assign this issue to you to reduce duplication of effort on the same task._
Contributor guide
Assessment
This issue has not been assessed yet.