feat(connector): [multisafepay] integrated giropay and iDEAL

[devnamrits]

Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

I have added the fields required as per the multisafepay API contract in the below mentioned file.

Additional Changes

• This PR modifies the API contract
• This PR modifies the database schema
• This PR modifies application configuration/environment variables

Changes are done at crates/router/src/connector/multisafepay/transformers.rs.

Motivation and Context

This PR fixes #4218 as mentioned in discussion #4143 .

How did you test it?

I've tested it with multisafepay Postman suite as present in the code. I checked the redirect link that was coming after creating the payment. I've tested Payments-Create and Payments-Retrieve API. I checked the link on the browser. Also, I'm attaching the screenshots for reference.

Checklist

• I formatted the code cargo +nightly fmt --all
• I addressed lints thrown by cargo clippy
• I reviewed the submitted code
• I added unit tests for my changes where possible
• I added a CHANGELOG entry if applicable

[devnamrits]

Please check @sudhirrnanda @c10n3 .

I have a few doubts as well:

• What is the concept of Redirect and Direct? Because for iDEAL, there are three options on the API doc:

1. Redirect
2. Direct
3. QR.
   So if we have to implement all three then we will have to write separate matches for BankRedirectData for obtaining the value of Type::Redirect or Type::Direct.

• I am very new to Rust. Do we have configured some commands in cargo within this project where if there are code changes in the server script reruns itself? As of now, I have to retrigger the command. Also, the build takes too much time. Once the build is completed the server also takes a considerable amount of time to start. Or its the inherent behaviour in this tech stack?