[Payments] Stripe Integration MVP
@commoddity is already working on this.
Since Sep 6, 2024.
Assessment
This issue has not been assessed yet.
Description
Objective
Integrate with Stripe to bill users (in fiat) based on how many relays they sent.
Origin Document
The following two tickets
- #10
- #11
Goals
- Enable any gateway operators to have a stripe payments solution out-of-the-box
Deliverables
- Implementation that integrates with stripe that involves:
- Billing users on a monthly basis based on the number of relays sent
- Parity with how Grove's portal works today (i.e. free plan + $2/1M plan)
- Documentation
- Updated tooling and documentation (env variables, hooks, etc) of how to test & develop locally
- 1-2 pager design doc (to be turned in 🦖 docs in the future) on how the system works
Non-goals / Non-deliverables
- Crypto payments
- Integrations with payment processors other than stripe
- General purpose configuration for payment plans that Grove does not offer
General deliverables
- Comments: Add/update TODOs and comments alongside the source code so it is easier to follow.
- Testing: Add new tests (unit and/or E2E) to the test suite.
- Makefile: Add new targets to the Makefile to make the new functionality easier to use.
- Documentation: Update architectural or development READMEs; use mermaid diagrams where appropriate.
Creator: @Olshansk
Co-Owners: @commoddity @fredteumer
- Dominant language
- Go
- Stars
- 12
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pokt-network/path
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
pokt-network/path#509 ·
-
bug gateway
Difficulty 4/5 3-5 days Newbie friendliness 45/100
pokt-network/path#477 ·
-
config documentation evm portal-db portal-ui qos
Difficulty 4/5 3-5 days Newbie friendliness 48/100
pokt-network/path#475 · 1 comment ·
-
[RADIX][TRON][SUPPLIER] Suppliers should not have to append additional API paths in their RM configMay be free again @adshmh claimed this 406 days ago, and no pull request is open. Openqos
pokt-network/path#443 · 1 comment · 3 assignees ·
-
[PORTALDB][CONFIG] Surface sanctions settings and thresholds as configurables in both the Config files and Portal DBMay be free again @commoddity claimed this 429 days ago, and no pull request is open. Openconfig documentation portal-ui qos
pokt-network/path#409 · 1 assignee ·
All issues in pokt-network/path
Similar issues
-
🕷️ bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
sysadminsmedia/homebox#1805 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
router-for-me/CLIProxyAPI#6851 ·
Maintainers usually reply within 1 day
-
usage: a custom provider's balance meters ("…%" in the balance path) ignore the Left/Used switchOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
[bug]: docs: Update webhook delete examples to use the correct flag (--webhook-id)Possibly taken @MuhammadHassan968 claimed this today. Openbug
Difficulty 1/5 Under an hour Newbie friendliness 84/100
goharbor/harbor-cli#1127 ·
Maintainers usually reply within 12 days