…ction

Custom invoice payment is carried by modified _service_paid_by_transaction
function. Funcion has add_days input variable.

Fixes issue: TampereHacklab#270

Signed-off-by: Erkki Hietaranta <[email protected]>

Child subscription paid to date is calculated
from days added to Parrent subscription.
Days that single payment adds are substracted from
days to add to Parent subscription. This is "virtualy" payment
date. Single payment days of child subscription is added to
virtual payment date.

Signed-off-by: Erkki Hietaranta <[email protected]>

Some users might found Dynamic pricing of payments missleading
as normal access fee can be paid with dynamic pricing, but
reorrucing custom invoice recalls flat rate.

This commit changes custom invoice logic so that it allows
dynamic pricing. Minimium payment is calculated from service
minimum payment * service payment times.

It can be disabled from settings.py or constance admin panel

Signed-off-by: Erkki Hietaranta <[email protected]>

Child service is paid by calling funcion again. So now if child
service has childs, they get paid.

Updated calcultaion so that multpile custominvoices
wont break basic idea of child payments.

Updated transaction commenting so that steps of transaction
is easy to read

Signed-off-by: Erkki Hietaranta <[email protected]>

Admin can control if custom invoice can be paid multiple times.

Signed-off-by: Erkki Hietaranta <[email protected]>

Signed-off-by: Erkki Hietaranta <[email protected]>

Signed-off-by: Erkki Hietaranta <[email protected]>

Payment is prevented and transaction will taced unused if
maximum allowed prepayment time is exceeded.

Signed-off-by: Erkki Hietaranta <[email protected]>

Signed-off-by: Erkki Hietaranta <[email protected]>

Signed-off-by: Erkki Hietaranta <[email protected]>

Added transactino comments and userlog enteries for maximum services.
Currently if basic transaction or custominvoice limits are reached
nothing happens. If main service gets paid, child service gets paid
to maximum limit.

Signed-off-by: Erkki Hietaranta <[email protected]>