Search areas

Override

Buy Points Improvements

Igor Nikonoroff

I propose the following changes to the points purchasing service.
1. Add a minimum payment amount setting (default: 0 - unlimited).
This can be very important when using certain payment systems, especially given the fees.
There should be a validation alert with a "Minimum amount 100 units" alert.
I haven't considered a maximum amount, but perhaps that's also important.
2. The point amount should depend on the amount of money.
An additional field is required: amount of money - points input coefficient.
For example:
0-100 1
101-300 1.3
301-500 1.5
500+ 2

If points are used for payment on the website, this is a very good marketing tool.

When entering the amount, the points should be recalculated as you enter the data.

Perhaps it would be worthwhile to place these terms above the form (optional) so that the client understands the benefits and the transparency of the terms.

3. The payment button should be inactive until the terms and conditions are accepted (checkbox).
Why is this important? For example, I specify the procedure for crediting and spending points in legal documents, and this element provides additional protection against disputes.
The checkbox can also be added to the settings (required or not).

4. In the transaction history, the description should include the amount spent.
1000 points purchased for 500 USD

5. I don't use the Buy Points module with a fixed amount (the input field is a more flexible tool), but I understand that it could be easier to refine.

In any case, these are just my wishes, which I will still implement in hacks, which is not good.

I invite you to discuss this feature.

0

2 Replies

#1

Thanks - good ideas. Here are my thoughts.

The variable point factor (points per currency unit) could build in minimum and maximum in this way:

100 1.0
250 1.2
500 1.5
1000 0

The idea being that the first point count can be zero, but if it is non-zero (as in the example of 100) then that is the minimum point purchase. Likewise, if the last point count has a rate of zero, then it is treated as the upper limit for point purchase. The number of lines would be variable.

Maybe it would be helpful to have two text areas for terms and conditions - a summary and the complete document. The summary could be shown immediately on the points purchase page, with a link to a popup of the complete terms. The checkbox to accept terms seems reasonable. And yes, information could probably go into the activity history.

There's no reason for you to use the fixed amount modules if they don't suit your situation. Unlike you, one early user was very much against asking the user to specify a number of points. He wanted to create panels that offered a bundle of points that people could buy. Neither approach is wrong!

Can't promise instant delivery, but I'm willing to try to incorporate these - how do they sound to you? And I'd be interested if anyone else has related thoughts.

 

0
#2

Thanks for the reply!
I’m glad you understood the idea correctly; the implementation can take any form, including the one you suggested. I was thinking the input field should have a placeholder instead of a zero.
For example: "Enter any amount between 100 and 1000."
Ideally, this should be configurable in the settings, but if that’s difficult to implement, a language variable would work.

0

Explore Repository

open all | close all

Fighting Spam

We run our own mail server, but we have front ended it with a spam blocker by MX Guard Dog. This enables us to run our mail server with much lower resources, because it does not need anti-spam or anti-virus software. If you want help to do the same, get in touch.