My branch isn't complete yet, but it's progressing well. I should have something push-able by tomorrow.
FWIW, I chatted with Ben earlier today, and bounced the following table names off him (the interface might not follow these names *exactly*, but they should be kept as close as possible): fine_reversal, reversal_payment, account_adjustment, adjustment_payment. I was partial to fine_reversal, but Ben liked the "adjustment" names better. I am running with "adjustment_payment" for the table name (for now), but would be happy with a "reversal" name as well (it is less generic, which can be seen as either good or bad depending on how many cases we want this type to cover).
My branch isn't complete yet, but it's progressing well. I should have something push-able by tomorrow.
FWIW, I chatted with Ben earlier today, and bounced the following table names off him (the interface might not follow these names *exactly*, but they should be kept as close as possible): fine_reversal, reversal_payment, account_adjustment, adjustment_payment. I was partial to fine_reversal, but Ben liked the "adjustment" names better. I am running with "adjustment_ payment" for the table name (for now), but would be happy with a "reversal" name as well (it is less generic, which can be seen as either good or bad depending on how many cases we want this type to cover).