MyBank and IDeal
In case of MyBank and Ideal payment methods, there is one more step for the buyers before being sent to the third-party processor: they must choose their bank from a list of participating banks.
Merchants can embed this phase in their websites, in order to manage the payment method choice and provide their buyers with the same experience of direct connections to the third party processors.
This can be done through a feature called “Payment Type Detail”.
Merchants are free to use this option or not: if they do not use it and they simply set
<paymentType>IDEAL</paymentType> in their call to
Encrypt method of
WsCryptDecrypt web service, then the buyer will find in GestPay a page where it will choose its bank among those available for
that kind of payment.
Merchants who want to use “Payment Type Detail” for MyBank and/or IDeal, must be able to show to their buyers the list of the banks available for that kind of Payment.
They can store the lists of those banks in their local storage (two distinct lists) and keep the lists updated by periodically calling the methods
WsS2S web service.
These methods will return a list of banks made like this:
<BankList> <Bank> <BankCode>Code0001</BankCode> <BankName>Name of Bank 1</BankName> </Bank> ... <Bank> <BankCode>Code0000N</BankCode> <BankName>Name of Bank N</BankName> </Bank> </BankList>
There is no need to update the lists of the banks for each transaction.
One update every week is definitely enough, since the list of the banks partecipating to MyBank and IDeal is not changing so quickly.
The update should consist of a complete replacement of each list with the new values returned by WsS2S web service.
The merchant page should show the list of the BankNames and use the corresponding BankCode.
The BankCode must be used for
paymentTypeDetail tag, while calling the
Encrypt method of
WsCryptDecrypt web service, as a value either for
MyBankBankCode or for
IdealBankCode, depending on the payment method. For example, for a MyBank transaction for which the
buyer has chosen “Name of Bank X”, the merchant should call
encrypt method with, among the others, these values:
... <paymentTypes> <paymentType>MYBANK</paymentType> </paymentTypes> <paymentTypeDetail> <MyBankBankCode>Code0000X</MyBankBankCode> </paymentTypeDetail> ...
and, for an IDeal transaction for which the buyer has chosen “Name of Bank Y”, the merchant should call encrypt method with, among the others, these values:
... <paymentTypes> <paymentType>IDEAL</paymentType> </paymentTypes> <paymentTypeDetail> <IdealBankCode>Code0000Y</IdealBankCode> </paymentTypeDetail> ...
PaymentTypeDetail must be defined as
Merchant Back Office before it can be used by the merchant.
IDeal Credential Test Environment
IDeal do not need any mandatory parameters in a middle page the bank of the buyer will be asked in order to continue the payment.
You can use the following parameters value in order to test Ideal in test (sandbox.gestpay.net) environment. Use low amount like 10.00 EUR.
When landing of Ideal payment page, select the bank you prefer in the middle page and then follow the instruction in order to have a successful test payment.
The maximum payable amount by a customer, for IDeal, is: