Agent does not ask for billing details while initiating the order

[mayurvir]

Description

Billing details are required for initiating an order (In beckn, making the init call), however the current version of agent (the version after the rearchitecture) does not ask for the billing details.

Here is a screenshot of agent's message:

Here, the agent says : "Would you like to proceed and initiate the order for booking this hotel?". Whereas it should have asked for the billing details as they are not available in user's profile.

Checkout this PR for the full video.

Goals

• If the user shares billing details, they should be stored in the session under profile in a relevant structure so that they can be used later. Remember that user might want to use different billing details so we may want to design for multiple billing details to be stored.
• If the user has selected the order, the call to action should be based on whether or not user's billing details are available. If yes, it should ask for init else ask for init with billing details.
• If the billing details are shared, they should be used and saved in the profile at the same time.
• If the billing details are available in profile and hence not shared by the user, it should take the details from user profile and use them for init call.
• If the user's billing details are available , it might be a good idea for agent to share the billing details with user for confirmation.

Expected Outcome

User should be asked for billing details when necessary and correct billing details should be used for each order.

Acceptance Criteria

• If the user shares the billing details for the first time, they should be stored and used correctly
• If the user has shared their billing details, they should not be asked to share them again.
• If the user wants to change the billing details for the next order, they should be able to do so
• In case billing details are not shared the first time, agent should ask for billing details instead of initiating the order with incorrect details.

Implementation Details

[List any technical details about the proposed implementation, including any specific technologies that will be used.]

Mockups / Wireframes

[Include links to any visual aids, mockups, wireframes, or diagrams that help illustrate what the final product should look like. This is not always necessary, but can be very helpful in many cases.]

---

[Please note that the below section of the ticket has to be in the format as mentioned as it is key to enabling proper listing of the project. Please only choose the options mentioned under the headings wherever applicable.]

Product Name

[Product Name: For eg: Beckn, Sunbird Obsrv etc]

Project Name

[Project Name: Descriptive of the ticket]

Organization Name:

[Organization Name]

Domain

[Area of governance]

Tech Skills Needed:

[Required technical skills for the project]

Complexity

Pick one of [High]/[Medium]/[Low]

Category

Pick one or more of [CI/CD], [Integrations], [Performance Improvement], [Security], [UI/UX/Design], [Bug], [Feature], [Documentation], [Deployment], [Test], [PoC]

Sub Category

Pick one or more of [API], [Database], [Analytics], [Refactoring], [Data Science], [Machine Learning], [Accessibility], [Internationalization], [Localization], [Frontend], [Backend], [Mobile], [SEO], [Configuration], [Deprecation], [Breaking Change], [Maintenance], [Support], [Question], [Technical Debt], [Beginner friendly], [Research], [Reproducible], [Needs Reproduction].