Proposal for grocery payments. A dining list owner can initiate a grocery payment using a button on the dining list page that leads to the 'create grocery payment' page.
Pages
Create grocery payment
Page that allows the grocery buyer to create a payment. Components:
List of people who will be charged. Each person has a checkbox 'create transaction', checked by default. For people that can't be charged, the checkbox should be disabled. This can be due to: the person has insufficient balance, or they have disallowed automatic payments in their account settings.
Field for entering the total amount, this will be divided over the people in the list.
Field for payment instructions and contact information. Will be sent to everyone on the list. Should have something like a 'remember instructions for next time' checkbox.
Help text:
People on the list with a check mark at 'create transaction' will automatically be charged from their account balance. You will receive the money in your account, they get a notification and can undo the transaction. Provide payment instructions for the other people, for instance a Tikkie link, and preferably also provide your phone number or e-mail so that they can contact you if necessary. Tip: if you create a Payment Request link (Tikkie) with variable amount, you won't need to create a new link the next time.
To modify the people on this list, add or remove diners on the dining list.
The 'create transaction' checkbox might be disabled if the person has insufficient balance or is not allowing automatic payments.
Grocery payments overview
Similar to the transactions overview, a table with the columns:
Dining list
In the case of grocery buyer (payee):
Grocery cost
Number of people paid / total number of people
Link to the 'update grocery payment' page
In the case of payer:
Amount to pay
If paid or not
Payment instructions (if not yet paid)
Cancel button (if automatically paid), if clicked will cancel the transaction and notify the grocery buyer
It's probably a good idea to use two separate tables, one for payments where the user is the payee and another one for when the user is the payer.
Update grocery payment
Page for the grocery buyer to keep track of who has paid. Components:
Payment details:
Grocery cost
Amount per person
Payment instructions
List of people. Each person has a paid/not paid indication and a button to mark paid or not paid.
A cancel button, if clicked will cancel the payment and all transactions within.
Some way to send a message to everyone or a subset (??).
Help text:
Need to change the amount or people on the list? Cancel the payment and create a new one.
Proposal for grocery payments. A dining list owner can initiate a grocery payment using a button on the dining list page that leads to the 'create grocery payment' page.
Pages
Create grocery payment
Page that allows the grocery buyer to create a payment. Components:
Help text:
People on the list with a check mark at 'create transaction' will automatically be charged from their account balance. You will receive the money in your account, they get a notification and can undo the transaction. Provide payment instructions for the other people, for instance a Tikkie link, and preferably also provide your phone number or e-mail so that they can contact you if necessary. Tip: if you create a Payment Request link (Tikkie) with variable amount, you won't need to create a new link the next time.
To modify the people on this list, add or remove diners on the dining list.
The 'create transaction' checkbox might be disabled if the person has insufficient balance or is not allowing automatic payments.
Grocery payments overview
Similar to the transactions overview, a table with the columns:
It's probably a good idea to use two separate tables, one for payments where the user is the payee and another one for when the user is the payer.
Update grocery payment
Page for the grocery buyer to keep track of who has paid. Components:
Help text:
Need to change the amount or people on the list? Cancel the payment and create a new one.