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

Find how we can implement Payment #366

Open
wdjopa opened this issue Feb 19, 2023 · 7 comments
Open

Find how we can implement Payment #366

wdjopa opened this issue Feb 19, 2023 · 7 comments
Assignees

Comments

@wdjopa
Copy link
Collaborator

wdjopa commented Feb 19, 2023

No description provided.

@wdjopa wdjopa added this to Jobsika Feb 19, 2023
@wdjopa wdjopa moved this to Todo in Jobsika Feb 19, 2023
@elhmn
Copy link
Member

elhmn commented Mar 25, 2023

What is the status on this ? Do we have an idea of which paiment service we want to use and how to integrate them ?

@elhmn
Copy link
Member

elhmn commented Mar 26, 2023

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.

@elhmn
Copy link
Member

elhmn commented Mar 26, 2023

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

@wdjopa wdjopa moved this from Todo to In Progress in Jobsika Apr 1, 2023
@rakici
Copy link
Contributor

rakici commented May 5, 2023

Paiement solution flow:

  • The user selects their tier (a tier refers to a jobsika tier)
  • The user provide us with their email
  • We create an opencollective tier
  • We display or redirect them to the opencollective tier so they can pay
  • The webhook wait for a paiement to be done
  • We check that the unique tier was paid
  • Then send an email to the client with the URL of the joboffer they created so they can modify it before and after submission

Exploratoin todo list:

  • We want to be able to create a new tier
  • Delete a tier
  • Setup the opencollective webhook
  • Verify that a paiement was done

Then Implement the paiement solution in the jobsika api.

@rakici
Copy link
Contributor

rakici commented May 5, 2023

I used these websites to convert json data to golang structs and maps:

@rakici
Copy link
Contributor

rakici commented May 5, 2023

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.
Instead, the single-tier will provide them with basic features such as:

  • Company logo (+2.000XAF)
  • Diffusion on OSS Groups and accounts ( (8 x users in our databases) XAF)

Now the add-job page will have 2 steps:
1 - Fill in the form
2- Paiement page that will redirect the user to opencollective or just show a paiement widget from opencollective
We need to add to the opencollective tier, explanation about what will happen once the payment is done.

@rakici
Copy link
Contributor

rakici commented May 23, 2023

After this #397 is merged, we should try to do:

  • Deploy a working version of the api to the staging environment
  • Send an email to the user that performed the payment
  • Delete the tier after 30 minutes

@Zaker237 Zaker237 moved this from In Progress to Done in Jobsika Jul 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

5 participants