Forum Replies Created
-
AuthorPosts
-
in reply to: Connection Strim #16889
Hello Andrey,
Thanks for revising the budget. I have discussed the revised amount with our accounts team, and their feedback is that the proposed budget is still too low considering the effort and development time involved.
Based on their assessment, the minimum budget required for this work is NZD 1,000.I have requested NanoM to provide the complete requirements, all required and optional parameters, and a consolidated summary of our previous discussions in one message. I will proceed with the integration once they provide all the necessary information.
In the meantime, I will prioritize your task and do my best to complete it as soon as possible. I understand that you are flexible with the timeline when there is no immediate urgency, and I appreciate that. Considering the urgency, I will put in my best effort to finish it at the earliest.in reply to: NanoTelecom Imrpovment Ideas #16888Hello NanoM,
Please reshare the complete request specifications, including all required and optional fields, based on our previous discussions and the updates you have made, so I can proceed with a clear understanding of the integration requirements.
I understand your point that the API endpoint has been updated, while the API token, request parameters, and response parameters remain the same.
However, I would request you to consolidate everything into one message, including the complete requirements and expected request parameter specifications. In particular, please explain how you expect us to handle scenarios where a single order contains multiple numbers, with each number potentially having a different status.
For example, within the same order, one number could be cancelled, another refunded, and the remaining numbers could still be active.
Please include the expected request structure and the handling of these scenarios so there is no ambiguity during development.
Once you provide the complete details, I will proceed with the integration.
in reply to: Connection Strim #16883Hello Andery,
I needed to clarify a additional points based on the message received from the NanoM team today.
Once I receive the necessary clarification from NanoM, I will proceed with the development. I cannot and should not start working without having clarity.Meanwhile, please revise the project budget to reflect the additional development time and scope so I can inform my accounts team accordingly. I need to communicate the revised budget to them in advance.
in reply to: NanoTelecom Imrpovment Ideas #16881Hello NanoM,
Please explain this below point so i can proceed with clarity:
Status changes can occur at both the order level and the individual number level.
Refunds and cancellations can also be applied to individual numbers within the same order. For example, if an order contains five numbers, the EN team may cancel or refund one, two, or multiple numbers from that order. It is also possible to cancel one number and refund another number within the same order.
I would like to understand how you are handling these scenarios on your side, particularly when different numbers within the same order have different statuses, such as cancelled and refunded.in reply to: Connection Strim #16879Hello Andrey,
As I have already mentioned, the development will take at least 8–10 days, so completing it by Monday is not possible.
I have also raised a few questions with the NanoM team to clarify certain points before proceeding.
Additionally, I am expecting the project budget to be revised accordingly, considering the development time and additional work involved.in reply to: NanoTelecom Imrpovment Ideas #16878Hello NanoM,
* Please send en_status exactly as the label reads in EN, such as “Payment Received”, so the portal shows Nano’s staff the same words they see in your admin.
The status provided is the same as the label displayed in the EN admin panel. Therefore, the status will remain exactly as I mentioned in post #16870.* Is the status kept per number or only per order? Your note on refunds sounds like one number can be Refunded while the rest of the order stays Completed. If so, I’d like each event to carry that number’s own status.
Status changes can occur at both the order level and the individual number level.
Refunds and cancellations can also be applied to individual numbers within the same order. For example, if an order contains five numbers, the EN team may cancel or refund one, two, or multiple numbers from that order. It is also possible to cancel one number and refund another number within the same order.
I would like to understand how you are handling these scenarios on your side, particularly when different numbers within the same order have different statuses, such as cancelled and refunded.in reply to: NanoTelecom Imrpovment Ideas #16870Hello NanoM,
Below is the status and events EN site have for numbers :
Rejected
Awaiting Payment
Pending
Payment Received
Completed
Cancelled
Declined
Refunded-
This reply was modified 1 day, 1 hour ago by
Nishit Shan.
-
This reply was modified 1 day ago by
Nishit Shan.
in reply to: Mobile View #16869Hello Andrey,
I can see post #16828 in the discussion forum, where they have provided API details for testing through Postman. However, they haven’t mentioned anywhere that we should start the integration.
I have sent them a message asking whether they want us to proceed with the integration, and I’m waiting for their response. I’ll proceed according to their advice. I have also shared the timeline and integration points, as I previously shared with you.I also understand your point that this work is not related to NanoTelecom, where I have previously worked. This is a separate portal.
in reply to: Connection Strim #16868Hello Andrey,
This forum is accessible .
in reply to: NanoTelecom Imrpovment Ideas #16867Hello NanoM,
Please advise me when i need to integrate on EN site , i am currently waiting for your further instruction for the implimentation .
Based on my initial review, the integration will take at least 8–10 days to complete.
To achieve what you is requesting, I will need to work on the following areas:
1. Order Creation Flow (Frontend): Implementing the order creation process on the frontend.
2. Admin Orders: Handling and managing orders from the admin panel.
3. Custom Telecom Orders (API): Integrating the custom telecom order functionality through the API.
4. Port-Out Statuses: Handling and synchronizing different port-out statuses.
5. Refunds: Implementing refund handling. A return should be able to mark an individual order line as refunded without changing the overall order status. The full-order cancellation/refund process will be handled separately.in reply to: Mobile View #16856Hello Andrey,
No, I am unable to access the “en-tn-string” forum. I keep getting redirected to the login page and am asked to log in repeatedly. I was trying to access it for the same reason.
Regarding posts #16853 and #16854: No, those were test APIs that I had specifically requested from their team so I could test the integration from my side. They have provided the test API details.
However, you can coordinate internally with team and let me know if there is anything I can help with at this stage.Regarding the timeline, it will remain the same as I previously mentioned in post #16807. There may be a difference of a day or two, but that’s fine. I’ll manage accordingly.
in reply to: NanoTelecom Imrpovment Ideas #16852Hello NanoM,
Just to inform you , i have tested the API and getting response:
{
“received”: 1,
“duplicate”: true
}
and
{
“received”: 1,
“duplicate”: false
}in reply to: Mobile View #16839Hello Andrey,
Yes , You can pay on paypal id (info @ geniusedusoft) on office page .
in reply to: NanoTelecom Imrpovment Ideas #16833Hello NanoM,
Thanks for the details. I’ll review everything and let you know if I need any further assistance.
in reply to: Mobile View #16827Hello Andrey,
I don’t think there are any pending tasks remaining from the corrections. However, I have requested testing feedback and am currently waiting for it from your side.
-
This reply was modified 1 day, 1 hour ago by
-
AuthorPosts