missing api functionality

• How do we group payments

  The API currently uses the payment_group_code meta field to group payments. Is this sufficient or do we need to make this a first class citizen?

  As a first class object we could search across it and store meta data such as associating buyers and sellers together before an initial charge occurs or the title for the payment.

  First pass:

  • Store any meta information in the dashboard (auth) itself with a progression path towards storing it on the payments resource that will eventually be created.
  • May need to expose a resource that is materialized once mocks are done.
  • Will not show up in the search results. Balanced API backend needs to index an association table for payment_group_code

• How do does the dashboard calculate fees?

  Our new mocks show the ability to calculate and collect revenue. How is this done?

  • Fixed fee versus % fee
  • Is the fee refunded? What about after a credit is sent out? What about partial refunds?

  First pass:

  • No fees in the first pass, create an issue, come back and solve later.