koalixcrm icon indicating copy to clipboard operation
koalixcrm copied to clipboard

Define Use-Cases related to automated payment

Open scaphilo opened this issue 7 years ago • 4 comments

Prepare answer to the following questions:

  • What kind of use cases that require automated payment shall be supported by koalixcrm in future

scaphilo avatar Sep 23 '17 18:09 scaphilo

  1. I would like to include payment integration with installing a single submodule from this repo. Something like `koalix.payments'.

  2. This should work out of the box with at least one of the following;

  1. Configuration via os.environ.get(). Each of these platforms has specific configuration. At first it would be easiest and fastest to pick one of the above and fully support it.

  2. Optionally install each one of this in a further submodule... 'koalix.payments.stripe' for example

derek-adair avatar Sep 24 '17 16:09 derek-adair

5.Integration with various transaction types;

  • Subscription
  • Refunds
  • One off payments ... I'm sure therea re more i'm not thinking of.
  1. MAYBE track payment types. It may be useful to have that referenced somewhere on an invoice or order form.

derek-adair avatar Sep 24 '17 16:09 derek-adair

  1. Invoice creation - (using the stripe vocabulary) Creating an invoice should optionally create a charge w/ <payment_gateway>. If a charge is created, create a form and expose it via {{SITE_NAME}}/payments//pay. Send a link to said page to the customer asking to pay.

derek-adair avatar Sep 24 '17 16:09 derek-adair

  1. NICE TO HAVE: Invoice expiration reminders/dates. Given an invoice expiration date, send out an alert to both partiers that something is about to be past due.

derek-adair avatar Sep 24 '17 16:09 derek-adair