Newer
Older
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
# Roadmap of planned features
This roadmap may not always be up to date but gives an idea of what is planned and where funding/support is required.
## Automatic import of subscriptions / payments
If we already have the Stripe customer in CiviCRM we can import subscriptions and one-off contributions that were
created outside of CiviCRM (eg. via WooCommerce, Stripe Dashboard).
### Specification
1. Add a setting to control whether import should happen automatically.
2. Update Stripe IPN code to automatically create:
- A recurring contribution when an unknown Stripe subscription ID is received.
- A contribution linked to a recurring contribution when an unknown invoice ID is received.
- A contribution when an unknown charge ID is received (that does not have an associated invoice ID).
- A payment linked to a contribution via charge ID / invoice ID.
### Estimate
This would require funding for approximately 12 hours work.
## UI to map customers to CiviCRM contacts
Based on the existing `Stripe.Importcustomers` API we can build a UI in CiviCRM that allows to manually
confirm and map Stripe customer IDs to CiviCRM contacts.
### Specification
1. Build a UI that lists Stripe customers which do not exist in CiviCRM.
2. Provide options to:
- Confirm the auto-detected mapping.
- Manually find and map contact.
- Import all missing subscriptions/contributions for customer (up to certain date?).
### Estimate
This would require funding for approximately 16 hours work.
## Stripe Connect
See https://stripe.com/connect
## Payment Requests (Google / Apple Pay)
See https://lab.civicrm.org/extensions/stripe/-/issues/81
## Stripe ACH/EFT
See https://civicrm.org/make-it-happen/stripe-ach-payments
## Card on File
Stripe supports saving cards and other payment methods. These can be retrieved, re-used and updated.
We would like to provide support for re-using saved cards in CiviCRM.
### Specification
1. Develop a method to deduplicate payment methods (see eg. https://github.com/stripe/stripe-payments-demo/issues/45).
Cards are duplicated by default and we need to clean this up before we can provide a UI to retrieve cards in CiviCRM.
2. Build a UI to allow for selection of cards to use for making payment.
3. Integrate card-selection UI into payment flow (so for example a form validation failure will remember the card you just entered and verified).
### Estimate
This would require funding for approximately 24 hours work.