Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Stripe
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Extensions
Stripe
Commits
e9f7a1d9
Commit
e9f7a1d9
authored
4 years ago
by
mattwire
Browse files
Options
Downloads
Patches
Plain Diff
Add roadmap for bancontact
parent
77987764
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/roadmap.md
+31
-9
31 additions, 9 deletions
docs/roadmap.md
with
31 additions
and
9 deletions
docs/roadmap.md
+
31
−
9
View file @
e9f7a1d9
...
...
@@ -35,6 +35,24 @@ confirm and map Stripe customer IDs to CiviCRM contacts.
This would require funding for approximately 16 hours work.
## 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.
## Payment Methods
## Stripe Connect
See https://stripe.com/connect
...
...
@@ -47,21 +65,25 @@ See https://lab.civicrm.org/extensions/stripe/-/issues/81
See https://civicrm.org/make-it-happen/stripe-ach-payments
##
Card on File
##
Bancontact
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.
See https://stripe.com/docs/payments/bancontact
### Specification
This is a "Bank Redirect" type of payment.
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).
### Implementation
1.
Create a paymentIntent of type "bancontact" and return the client secret.
2.
Collect payment method details (name) on the client form.
3.
Handle redirect to bancontact to make payment and return to CiviCRM.
4.
Handle payment_intent.succeeded webhook to confirm payment.
### Estimate
This would require funding for approximately 24 hours work.
20 hours. This represents approximately 12 hours for the generic "Bank Redirect" functionality
in the Stripe extension and then 8 hours for the specific payment method "Bancontact".
Adding additional payment methods such as Sofort would then require approximately 8 hours each
to implement.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment