Skip to content

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:
  3. A recurring contribution when an unknown Stripe subscription ID is received.
  4. A contribution linked to a recurring contribution when an unknown invoice ID is received.
  5. A contribution when an unknown charge ID is received (that does not have an associated invoice ID).
  6. 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:
  3. Confirm the auto-detected mapping.
  4. Manually find and map contact.
  5. 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.