Open muratcakir opened 10 years ago
muratcakir
commented
10 years ago A note... that requires data migration to eliminate the percentage checkbox and to switch and convert absolute values entered in the old field.
Migrated from CodePlex: written by mgesing, on 8/4/2014 12:10:26 PM
muratcakir
commented
10 years ago actually no need to eliminate or change a thing. As i outlined, we need TWO elements to describe paypal fees, and currently we only have 1. We only need another that allows for the second. I can manage with leaving the first one as is for easier migrations.
Migrated from CodePlex: written by wdcurry, on 8/4/2014 4:05:53 PM
muratcakir
commented
10 years ago some users are using absolute other are using relative values. so data migration is required otherwise things are getting ugly.
Migrated from CodePlex: written by mgesing, on 8/4/2014 4:47:39 PM
muratcakir
commented
10 years ago regardless of how this is perceived in its' impact, the fact remains, the current implementation is wrong. Paypal charges at least two types of fees and we can only assign one.
Migrated from CodePlex: written by wdcurry, on 8/4/2014 5:02:53 PM
muratcakir
commented
10 years ago it's not "wrong". the current fee option it intended to charge your own fees for payments and not to pass the one from the payment gateway to your customers. however, your suggestion is good because both intentions can be combined in one option.
Migrated from CodePlex: written by mgesing, on 8/4/2014 6:26:55 PM
Paypal, like many other such providers, charge a % AND a flat fee. Currently we only have one area to enter fees for a payment. So, we either jack up the % past what paypal charges and appear to "fleece" our clients, or we absorb the flat fee. Either way, this is easily correctable with one more attribute: Flat fee ____
cheers, drew..