Sandeep Kumar

Hey @Rutam21, Can you set this up locally, and try to create a payment. You can test the `PaymentStatus` update when you hit the `Payments - Retrieve` endpoint. Try to...

@Rutam21 I have tested this PR locally, and updated the test cases. Seems to be working fine. This PR looks good to get merged.

With the existing v1 routes flow, the following points can be understood for inviting users to V2 merchant accounts. ### Profile Level Roles: Invite Users to V2 merchant account with...

The V1 and V2 schema tables for merchant_account need to be merged into a global schema, which can be accessed by both v1 and v2 deployments, to enable sign-in for...

Pls check the masking of certain fields like `billing_city`, `billing_state` and `billing_country` when sending the events from kafka to S3, to prevent leaking any sensitive data. cc: @su-shivanshmathur

Hey @hex1c, Please link an issue with this PR. Thanks

> @tsdk02 Can you add the testcases for this PR. > > CC : @gorakhnathy7 @Gnanasundari24 I have added the test case, and it works as expected.

- Merchant account table needs to be moved to the common accounts schema - Need to point v1 deployment to v2 dashboard metadata table if possible or move dashboard metadata...

Updated Response Structures for the Metrics: Payments Processed: - Query Data: - payment_processed_amount - payment_processed_count - payment_processed_amount_without_smart_retries - payment_processed_count_without_smart_retries - time_bucket - Meta Data: - total_payment_processed_amount - total_payment_processed_count - total_payment_processed_amount_without_smart_retries...

Need to create v2 sign-in routes, once the account tables have been moved into a common schema (blocker).