Hi.
I am creating a new payment plugin, but I need to allow customers to choose between more than 1 payment option, without I have to create multiple payment plugins, once it is under same payment provider API.
I mean. Debit Card, Credit Card, Bank Transfer.
Nop 3.7
Can it be done?
Payment Plugin - Multiple Options
MVP
- 11324
- 100972
- 5/22/2011
- United States
Yes, set up the options on the Payment Info page. See the demo store, and choose Credit Card as a payment option, and then note the "Payment information" page that follows.
- 148
- 969
- 9/19/2015
- United States minor outlying islands
Thanks, but it will not work.
As it is, customer will have to select the payment option, like "General Payment" and then on payment info select his preferred option again, like wire transfer or debit card.
We should work with less clicks to checkout and one new step like it would cause several mistakes and misunderstanding.
I have researched about it and I didnt find to much help, once nop works on 1-1 relationship with payment / shipment plugins options.
Some customization will be required, right?
As it is, customer will have to select the payment option, like "General Payment" and then on payment info select his preferred option again, like wire transfer or debit card.
We should work with less clicks to checkout and one new step like it would cause several mistakes and misunderstanding.
I have researched about it and I didnt find to much help, once nop works on 1-1 relationship with payment / shipment plugins options.
Some customization will be required, right?
MVP
Certified Developer
- 558
- 6401
- 7/29/2011
- United Kingdom
iob2000 wrote:
There's a setting called paymentsettings.bypasspaymentmethodselectionifonlyone available from the All settings page that, as it's name suggests, bypasses the payment method selection if there's only one. I think it's set to true by default anyway.
A more flexible approach might be to put the common functionality for working with your payment provider's API into a class library and build each of your payment methods as a separate plugin that references the class library. It would be a bit more work but would mean you could easily introduce other third party payment services at a later date if required.
As it is, customer will have to select the payment option, like "General Payment" and then on payment info select his preferred option again, like wire transfer or debit card.
There's a setting called paymentsettings.bypasspaymentmethodselectionifonlyone available from the All settings page that, as it's name suggests, bypasses the payment method selection if there's only one. I think it's set to true by default anyway.
A more flexible approach might be to put the common functionality for working with your payment provider's API into a class library and build each of your payment methods as a separate plugin that references the class library. It would be a bit more work but would mean you could easily introduce other third party payment services at a later date if required.