-
Notifications
You must be signed in to change notification settings - Fork 1
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
close #238 follow order state machine for payway_v2 #239
Conversation
0f08882
to
43f4b82
Compare
4bd9170
to
3e6f86c
Compare
43f4b82
to
2b3f867
Compare
3e6f86c
to
597f4a0
Compare
3e347cd
to
30df585
Compare
be24ac1
to
575bd4a
Compare
597f4a0
to
3c49421
Compare
0e6eb98
to
1ef147f
Compare
24f1005
to
5a3c639
Compare
c05bb44
to
10e8efb
Compare
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
15789919 | Triggered | Generic High Entropy Secret | 4501d6f | spec/services/vpago/payment_url_constructor_spec.rb | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
10e8efb
to
e3dac49
Compare
373e736
to
fd475fb
Compare
bcc2d98
to
a265735
Compare
With 4 api routes for all payment methods. This will help integrating spree_vpago much easier. - GET: /vpago_payments/checkout (HTML) - GET: /vpago_payments/processing (HTML) - GET: /vpago_payments/success (HTML) - POST: /vpago_payments/process_payment (JSON) - (This is API to process the payment, can call from ABA or our app)
a265735
to
4501d6f
Compare
Processing Flow
After paid, ABA push back to BookMe+, then it will process payment & order in queue with following steps:
Demo
Screen.Recording.2025-02-05.at.11.20.53.in.the.morning.mp4