-
Notifications
You must be signed in to change notification settings - Fork 18
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
Find how we can implement Payment #366
Comments
What is the status on this ? Do we have an idea of which paiment service we want to use and how to integrate them ? |
I started exploring the possibility to use opencollective as a solution for this. Since data are publics we could use their grapheql api to figure out if a user has made a paiement to our opencollective and allow or deny access to the service depending on that. Here is the repository I am exploring this solution. I will try to have something ready for next week. |
I also realised today that we could use a payment provider like flutterwave or stripe and send the money received directly to our open collective fiscal host. This could also be an option |
Paiement solution flow:
Exploratoin todo list:
Then Implement the paiement solution in the jobsika api. |
I used these websites to convert json data to golang structs and maps: |
During our telegram call we decided only to create a single jobsika tier; the user won't be able to select from a list of features.
Now the add-job page will have 2 steps: |
After this #397 is merged, we should try to do:
|
No description provided.
The text was updated successfully, but these errors were encountered: