/techdocs/payment.txt (b2a3733ec4b62ada3032e2d83a21f42f149be2f1) (2264 bytes) (mode 100644) (type blob)
== How payment works? ==
User selects a plan at sign-up. He is redirect to the home page.
When she hits the homepage, she is invited to select an amount
(based on period: monthly or yearly). Then she press "Pay" button.
We call 'pay_square_create_link' (passing an id which is payments.id)
to create a payment link and we redirect the user to it.
Sample link: https://sandbox.square.link/u/IgOz82xk
The rg id, uid, operator name, 'plan' type and 'y' interval, 'init'
state are inserted by calling 'pay_insert' function.
pay_needed_high_level
pay_square_create_link
pay_insert
We receive an order_id.
Next step is to go to the external payment page.
Payment takes place.
External site redirects back to RocketGit (passing back the payment id).
https://rg.embedromix.ro:9003/user/price1?paid=e09964ef29b3d886
Now, we received the payment id and we thank the user for the purchase.
We need to schedule the checking of the payment, as an event, to be able
to confirm it and mark it as paid. Should we? I think yes, because only now
the user confirmed the payment. Yes, but what if we cannot update the db?
Isn't it better to just check all initiated payments? I think yes.
We connect to the payment provider and we will check the state of the payment.
We also need to be able to compute the last paid day, to not bother the user
earlier than needed.
How should I compute it? And where to store this info?
- case 1, user is paying immediately after sign-up (2023-02-10), pays for 1 month
first day not paid is after exactly 1 month (2023-03-10)
- case 2, user is paying after some days after sign-up (2023-02-10), pays for 1 month
first day not paid is after exactly 1 month (2023-03-10)
- what happens if we suspend the account for not paying?
we still have resources used. Ask user to pay before unlocking resources?
TODO:
- We need to show correctly 12999 euro as 12.99 euro.
1299/12990/USD 1/10/RON -> 1299=12.99/12990=129.90/USD 99=0.99/999=9.99/RON
- What if the user does not pay and does not return to rg? We should
reuse a previous payment if amount/period/plan match.
- What if the user changes the plan on-th-fly?
We need to think to multiple scenarios (cheaper plan or a more expensive one).
- Should we offer one (last?) month free?
-
Mode |
Type |
Size |
Ref |
File |
100644 |
blob |
9 |
f3c7a7c5da68804a1bdf391127ba34aed33c3cca |
.exclude |
100644 |
blob |
108 |
acc2186b1d357966e09df32afcea14933f5f0c78 |
.gitignore |
100644 |
blob |
375 |
1f425bcd2049c526744d449511094fc045ceac74 |
AUTHORS |
100644 |
blob |
1847 |
fd1f7a627adc85dec9ebd72ae9e6b4c941b82f8f |
History.txt |
100644 |
blob |
34520 |
dba13ed2ddf783ee8118c6a581dbf75305f816a3 |
LICENSE |
100644 |
blob |
3624 |
1c4ccf9cceb2e56ae71334442aff3183b242c333 |
Makefile.in |
100644 |
blob |
5325 |
96c40d868ce10b715299085ccffb30f96a730cf3 |
README |
100644 |
blob |
190331 |
0418946bd5fc97da80f0bbd2e918c657536c01e6 |
TODO |
100644 |
blob |
1294 |
f22911eb777f0695fcf81ad686eac133eb11fcc4 |
TODO-plans |
100644 |
blob |
203 |
a2863c67c3da44126b61a15a6f09738c25e0fbe0 |
TODO.perf |
100644 |
blob |
967 |
56bbaa7c937381fb10a2907b6bbe056ef8cc824a |
TODO.vm |
040000 |
tree |
- |
21928e906ad2907a55c2e81c2a8b0502b586b8a0 |
artwork |
100644 |
blob |
5328 |
d5be4cc3f15d059ad8d267d800c602e9774816a8 |
compare.csv |
100755 |
blob |
30 |
92c4bc48245c00408cd7e1fd89bc1a03058f4ce4 |
configure |
040000 |
tree |
- |
811af39b8be55c3a36147dd06b040e86de4e9d4a |
debian |
040000 |
tree |
- |
7108e9538d908ff384482155efcaef836a057a2c |
docker |
040000 |
tree |
- |
f67d3605efbd6422a8acdd953578991139266391 |
docs |
100755 |
blob |
18252 |
e2438615edba7066a730ed6a796a5302263f1f37 |
duilder |
100644 |
blob |
536 |
b791516f9ec08c038e61269e0c5f38446a61e59b |
duilder.conf |
040000 |
tree |
- |
e330b65f3c3eea427853842a05410579de6175bd |
hooks |
040000 |
tree |
- |
e6ef0396dd7f12664ea681377807bdedf09ad13f |
inc |
040000 |
tree |
- |
e255ce234c3993998edc12bc7e93fff555376eda |
misc |
100644 |
blob |
6012 |
7cf5090db19ef7b7a1a4d962f2588464ff4f1c1f |
rocketgit.spec |
040000 |
tree |
- |
85421cbfb018ff4b0eebb1741e2dcfcc72f81ada |
root |
040000 |
tree |
- |
870e96f0afc7d85c97505a878609d386f81748d8 |
samples |
040000 |
tree |
- |
589b9039f8bbb597747e4e78cdfc26be35ead352 |
scripts |
040000 |
tree |
- |
454044f7e286fe13ec18598fce6b613190f52e5e |
selinux |
100755 |
blob |
256 |
462ccd108c431f54e380cdac2329129875a318b5 |
spell_check.sh |
040000 |
tree |
- |
d9260d3cf0d6490be720312893600a8041bf991b |
techdocs |
040000 |
tree |
- |
5dbc11970335b2e208d92e525d2b6ef49dcce3c3 |
tests |
040000 |
tree |
- |
e810d7397575886ef495708d571eb3675f6928ba |
tools |
Hints:
Before first commit, do not forget to setup your git environment:
git config --global user.name "your_name_here"
git config --global user.email "your@email_here"
Clone this repository using HTTP(S):
git clone https://rocketgit.com/user/catalinux/rocketgit
Clone this repository using ssh (do not forget to upload a key first):
git clone ssh://rocketgit@ssh.rocketgit.com/user/catalinux/rocketgit
Clone this repository using git:
git clone git://git.rocketgit.com/user/catalinux/rocketgit
You are allowed to anonymously push to this repository.
This means that your pushed commits will automatically be transformed into a
merge request:
... clone the repository ...
... make some changes and some commits ...
git push origin main