User Flow Description (General) The user selects a ticket and adds it to the cart in the Passo mobile application. At the payment step, the user is redirected from the application to a secure web-based payment page. This redirection is performed via the domains xyz.com or 1111.com. The user completes the payment by entering credit card information on this web page. Functional Requirement (Requirements Document) After adding a ticket to the cart in the Passo mobile application and proceeding to the checkout step, the user must be redirected to an external web-based payment page. The payment page must be hosted under the domains xyz.com or 1111.com and must support credit card payments. Upon completion of the payment process, the user must be redirected back to the Passo mobile application based on the transaction result. User-Facing Informational Text You will be redirected to a secure payment page to complete your purchase. Your credit card details will be processed securely outside of the Passo mobile application. Technical Flow Description (Analyst / Developer Oriented) During the checkout step in the Passo mobile application, the user is redirected via an in-app browser or an external browser to a payment page hosted on the domains xyz.com or 1111.com. The payment is processed on this page using credit card and 3D Secure support. Based on the payment result, the user is redirected back to the mobile application via success or failure callback URLs. Acceptance Criteria (Optional – for Jira / Test Cases) The user can add a ticket to the cart in the Passo mobile application. The user is redirected to the external payment page at checkout. The payment page is accessible via xyz.com or 1111.com. The user can complete the payment using a credit card. After payment completion, the user is redirected back to the mobile application with the correct transaction status