-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
feat(analytics): Add v2 payment analytics (payment-intents analytics) #5150
Conversation
.add_custom_filter_clause("attempt_count", "1", FilterTypes::Gt) | ||
.switch()?; | ||
query_builder | ||
.add_custom_filter_clause("status", "succeeded", FilterTypes::Equal) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you use the payment intent success type here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
alias: Some("end_bucket"), | ||
}) | ||
.switch()?; | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is status = succeeded
filter required here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes added it
.switch()?; | ||
|
||
filters.set_filter_clause(&mut query_builder).switch()?; | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and this
query_builder | |
.add_custom_filter_clause("attempt_count", "1", FilterTypes::Gt) | |
.switch()?; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added this
…ror-handling-in-cypress * 'main' of github.com:juspay/hyperswitch: fix(auth_methods): Add checks for duplicate `auth_method` in create API (#5161) chore(version): 2024.07.02.0 fix(router): rename the browser name header to `x-browser-name` (#5162) fix(router): mark retry payment as failure if `connector_tokenization` fails (#5114) fix(connector): [Paypal] dispute webhook deserialization failure (#5111) feat(analytics): Add v2 payment analytics (payment-intents analytics) (#5150) feat(globalsearch): Implement tag-based filters in global search (#5151) refactor(connector): Add amount conversion framework to iatapay along with amount conversion code to connector template (#4866) feat(payment_link): add multiple custom css support in business level (#5137) feat(connector): [Bambora Apac] Template for integration (#5062) feat(tls): add support for https in actix web (#5089) chore(ci): fix ci tests failing by removing them (#5167) chore(version): 2024.07.01.0 chore(postman): update Postman collection files ci(postman): log request id for user tests (#5159) chore(euclid_wasm): make field domain optional wasm (#5154)
Type of Change
Description
Added analytics based on
payment intent
Currently supporting 4 metrics
filters
group by
Additional Changes
Motivation and Context
Utilizing payment intents aligns closely with the data needs of merchants, enhancing their ability to manage and process transactions more effectively.
How did you test it?
Tested using local data by sending cURL requests through Postman.
Tested using Postgres data from
payment_intents
table and also using Clickhouse data frompayment_intent
table.Checklist
cargo +nightly fmt --all
cargo clippy