Page Comparison

...

URI needs to add in the url after citizen - “/withoutAuth/pt-mutation/public-search“

https://egov-micro-qa.egovernmentsdigit.org/citizen/withoutAuth/pt-mutation/public-search

...

1. Property should be ACTIVE

2. Due amount should be more than 0

3. If the property is ACTIVE and Advance Payment is enabled then PAY option should present even if the due amount is 0.

On Clicking of PAY button, citizen navigates to common PAY screen. Common PAY screen is existing feature developed and being used across all the module where payment is required. Below is the url to navigate on common pay screen using routing method provided by react. Consumer code and tenant id are dynamic data. Below is the one such example.

/withoutAuth/egov-common/pay?consumerCode=PB-PT-2020-05-30-005181&tenantId=pb.amritsar&businessService=PT

In Public search common pay screen, side bar is hidden since user doesn’t have access to enter other modules without authorization.

Citizen has to pay through payment gateway and all the required service are whitelisted for the payment.

...

After successful payment, citizen navigates to acknowledgment screen. In this screen, the items which required authorization has been hidden. Here user can generate receipt pdf of the payment done. receipt pdf api is whitelisted.

...

Technical Implementation Details

...

1. "/property-services/property/_search"

2. "/billing-service/bill/v2/_search"

3. "/egov-location/location/v11/boundarys/_search?hierarchyTypeCode=REVENUE&boundaryType=Locality"

4. "pg-service/transaction/v1/_create"

5. "pg-service/transaction/v1/_update" + txnQuery

6. "/collection-services/payments/_search"

7. "/pdf-service/v1/_create"

API call details

1. Boundary calls to get the Locality data

   

2. Search API Call

...

queryParams: [{key:”module”, value:”rainmaker-common,rainmaker-pt,rainmaker-pgr”}, {key:”locale”, value:”en_IN”}, {key:”tenantId”, value:”pb”}]

API Call Role Action mapping: