Clarification on Extending MiFinity Payout Support to the In-Process Connector Architecture

[Sahilbhardwj]

Hello maintainers,
while exploring the MiFinity connector and noticed that PR [[#14097] had introduced MiFinity payout support through the Unified Connector Service (UCS) and while examining the codebase, I couldn't find an in-process payout creation implementation in:
crates/hyperswitch_connectors/src/connectors/mifinity.rs

I've been exploring the existing in-process connector architecture and also developed an implementation for MiFinity payout creation and my implementation currently includes:

1. Payout request construction and transformation.
   2.Payout response parsing and status mapping.
   3.Connector registration changes.
   4.Unit tests for request and response transformations.
   Also this implementation has passed the focused tests, connector tests, and cargo check with the payouts,v1,frm features.

Before opening a PR, I wanted to get some guidance from the maintainers regarding:

1. Is a separate in-process MiFinity payout implementation desirable alongside the existing UCS implementation?
2. If so, are there any specific architectural requirements or additional flows I should consider?

I'd be happy to contribute this implementation if it aligns with the project's direction.

Thanks.