[FEATURE] Implementing iDEAL and Giropay payment methods with Multisafe #4397
Labels
C-feature
Category: Feature request or enhancement
S-awaiting-triage
Status: New issues that have not been assessed yet
Feature Description
Add iDEAL and Giropay payment processors in Multisafepay connector.
Whole description can be found in #4143 discussion.
Possible Implementation
Proposal: Implementing iDEAL and Giropay payment methods with Multisafe #4143
Objective
Add iDEAL and Giropay payment processors in Multisafepay connector.
Background
Currently multisafepay provides various payment processors from Banking Methods, BNPL, Credit and Debit cards, Prepaid cards and Wallets segment. From these hyperswitch's multisafepay connector provides support for credit cards and debit cards, mendate payements, GooglePay, Paypal and Klarna only. iDEAL and Giropay are from "Banking Methods" category.
iDeal
iDeal has direct and re-directed flow which is showed below:
direct: given iDEAL issuer code user customer will be directly redirected to the bank’s
page
redirect: Redirect customer to payment’s page to select their bank.
Giropay
giropay has only redirect flow which is exactly same flow as iDEAL’s redirect flow.
Approach
For iDeal deciding direct or re-direct payment type:
If bank name is provided in
PaymentMethodData
then direct path should be used otherwise redirect. If direct flow is selected then inMultisafepayPaymentsRequest
’sgateway_info
must haveissuer_id
field.List of iDEAL issuers and respective code is given below (source)
PaymentMethodData
for iDEAL.Implementation
All the changes will be in
connector/multisafepay.rs
file and in the enums and traits for request objectIdeal
andGiropay
inGateway
enumimpl TryFrom<&CheckoutRouterData<&T>> for MultisafepayPaymentsRequest
for
payment_type
: add pattern for redirect “giropay” and “iDeal” and direct “iDeal” paymentsfor
gateway
: addBankRedirectData::Ideal
andBankRedirectData::Geropay
patternfor
gateway_info
: Only for direct “iDeal” payments,issuer_id
: get issuer id from the table aboveThere are also optional
gateway_info
fields for modifying payment behaviours likeallow_change_amount
,min_amount
andmax_amount
which are related to QR code payment in direct flop.Have you spent some time checking if this feature request has been raised before?
Have you read the Contributing Guidelines?
Are you willing to submit a PR?
Yes, I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: