Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Massively decrease payment processing fees by bundling orders #6025

Open
darkdragon-001 opened this issue Oct 5, 2022 · 2 comments
Open

Comments

@darkdragon-001
Copy link

darkdragon-001 commented Oct 5, 2022

User story

As financial contributor, I want to donate money to many open source projects (not to payment processors) so that they can build great software.

Best solution for this problem

As many collectives share a common fiscal host and payment processing fees usually contain a fixed amount, by bundling many orders to the fiscal host, the payment processing fees can be split up.

Example:

  • If I want to share $10 among 10 collectives on the same fiscal host, I need to pay 10*$0.30=$3=3% of static payment processing fees to stripe (excluding dynamic porcentual ones).
  • If I could submit all 10 orders in a single API request, you could submit a single payment to the shared collective such that only 1*$0.30=$0.30=0.3% of payment processing fees need to be paid.

MVP

Add mutation createOrders(orders: [OrderCreateInput]]) to submit multiple orders in a single API request and bundle transactions to common fiscal hosts.

Metrics

Reduced payment processing fees.

@znarf znarf changed the title [API] Massively decrease payment processing fees by bundling orders Massively decrease payment processing fees by bundling orders Oct 5, 2022
@znarf
Copy link
Member

znarf commented Oct 5, 2022

We're tracking this here: #1916

Current alternatives:

@darkdragon-001
Copy link
Author

Thanks for the link!

I think this approach here could be used to split up the big and complex task into smaller chunks as it completely avoids the UI part.

It basically involves

  • Adding multiple recipient references to single payments
  • Splitting up received money among the multiple recipients specified in the payment
  • Add the API endpoint

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants