Allow an in-transaction condition for billing

Change multiline chain style

CustomerPlan.extract

To allow building from a hash with extra keys. Makes the CustomerRepo more readable.

Postgres#query_one

Helper for queries that only return a single row.

Allow finishing admin command

Say what customer was affected

NoCustomer is not registered

Merge branch 'max-call-length'

* max-call-length:
  Calculate the maximum allowable call length

Merge branch 'credit-card-blacklist'

* credit-card-blacklist:
  Credit card blacklist

Credit card blacklist

Any card on the list is just treated as though it is not present, preventing it
from being used.

Calculate the maximum allowable call length

Asterisk could use this to actually limit the call, for example.

Merge branch 'trustlevel-repo'

* trustlevel-repo:
  TrustLevel{,Repo}

TrustLevel{,Repo}

To determine how much permission a customer account should have to take risky
actions.  Seperate from their plan, this is not how much they could do in
theory, but how much the system will allow in practise due to perceived risk.

Starts out with a simple model based on amount of settled payments, and being
used to decide what is an "expensive" route for outbound calls.

Merge branch 'insert-settled-after'

* insert-settled-after:
  Credit card transactions settle after 90 days, bills instantly

Update to schema with settled_after

Merge branch 'bill-with-note'

* bill-with-note:
  Add a note when billing account

Add a note when billing account

Credit card transactions settle after 90 days, bills instantly

Merge branch 'activate-with-balance'

* activate-with-balance:
  If customer already has enough balance, just bill them and finish
  New BillPay registration step
  Save plan to DB as soon as it is selected
  Move credit_to lookup into relevant class

If customer already has enough balance, just bill them and finish