Project

General

Profile

Actions

Feature #33094

open

Train Module Integration

Added by Sadique P 2 months ago. Updated 2 months ago.

Status:
In Progress
Priority:
Normal
Assignee:
Target version:
-
Start date:
02/03/2026
Due date:
02/10/2026 (about 2 months late)
% Done:

80%

Estimated time:
Spent time:
remarks:

NIL

DB Changes:

NIL

Keys & Permissions:

NIL

Areas Affected:

NIL

Files Changed:

NIL


Description

Train Module Search to Ticket


Files

IMG_3611.png (218 KB) IMG_3611.png Sadique P, 02/10/2026 07:01 PM
IMG_3612.png (269 KB) IMG_3612.png Sadique P, 02/10/2026 07:01 PM
Actions #1

Updated by Sadique P 2 months ago

  • Due date changed from 02/03/2026 to 02/06/2026
Actions #2

Updated by Sadique P 2 months ago

  • Status changed from Assigned to In Progress
Actions #3

Updated by Sadique P 2 months ago

  • % Done changed from 0 to 20
  • remarks updated (diff)
  • DB Changes updated (diff)
  • Keys & Permissions updated (diff)
  • Areas Affected updated (diff)
  • Files Changed updated (diff)

Train search page integration completed, Result page integration just started

Actions #4

Updated by Sadique P 2 months ago

Trains module result page and filter page integration completed

Actions #5

Updated by Sadique P 2 months ago

  • % Done changed from 20 to 40
Actions #6

Updated by Sadique P 2 months ago

Train Pax page integration integration and payment page integration 70% completed

Actions #7

Updated by Sadique P 2 months ago

  • % Done changed from 40 to 60

The integration of the transfer payment page has been successfully completed. The ticket page integration is partially completed and currently uses static JSON data. Couldn't proceed from payment page didn't get payment gateway url this case already communicate Api team

Actions #8

Updated by Sadique P 2 months ago

  • Due date changed from 02/06/2026 to 02/09/2026
  • % Done changed from 60 to 80

The train ticket page integration has been completed using a static JSON response. Ticketing via the normal flow is required. However, due to the absence of the payment gateway URL from the API response, this case could not be verified.

Actions #9

Updated by Sadique P 2 months ago

  • Due date changed from 02/09/2026 to 02/10/2026

Updated by Sadique P 2 months ago

The MPGS payment gateway integration for the Train module has been partially completed. The API-side integration is still pending, so the app-side integration is currently on hold, This case already communicate to Api team. The normal booking flow has been successfully ticketed. Screenshot attached. When the user is logged in, the [GetPax] response is not being received in the staging and 100

Actions

Also available in: Atom PDF