-
Notifications
You must be signed in to change notification settings - Fork 107
Kotak - compliance check #224
Comments
Flow 1/init
/confirm
/status
/update
Flow 2
/init
/confirm
/cancel
Flow 3
Flow 4, 5
|
@BLR-0118 @bluecypher All fixed except these two below. I need discussion on these points. I will raise PR now for other fixes.
|
all done here @BLR-0118 |
Flow 1, 4
Flow 2
Flow 5/cancel
|
@bluecypher Refund flow is already there. can you look into it here
seller unsolicited cancellation is missing use one of the non-deprecated |
/init
Flow 2
Flow 4
Flow 5/cancel
|
@bluecypher @BLR-0118 /cancel "004" is a deprecated cancellation_reason_id (use "006" instead) . We are sending 006 only. Closely see the request. refund flow is missing We have shared this update and unsolicited log in PR and in call you have seen that. Can you share what is missing in it? /init door is an optional attribute in /billing/ and /fulfillments/end/location/address/ , |
Flow 1
After fixing the above, request QC testing to verify the following:
|
+Shishir Jindal ***@***.***> +Santosh Adsul
***@***.***> +Pooja Pawar ***@***.***> +Abhinandan
Satpute ***@***.***>
Megha
…On Mon, 29 May 2023 at 00:04, Supriyo Ghosh ***@***.***> wrote:
Flow 1
1. /update_refund: API call & refund amount calculation are wrong;
2. curious why message_id is in one format until /init and then has a
different format?
After fixing the above, request QC testing to verify the following:
1. serviceability
2. store timings & holidays
3. handling of out-of-stock items
4. processing of status updates
5. processing of cancel from seller
6. processing of refunds for return, cancel
@jainneerajnj <https://github.com/jainneerajnj> @bansalmeghaa
<https://github.com/bansalmeghaa> @bluecypher
<https://github.com/bluecypher>
—
Reply to this email directly, view it on GitHub
<#224 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4RKYE3E3F2H4F4FQAYZUXLXIOLD7ANCNFSM6AAAAAAYBJTRCA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Flow 1 Fixed |
Rechecked logs. |
There are issues with your logs. Request you to verify with the log validation utility here before resubmitting
The text was updated successfully, but these errors were encountered: