Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PuneMetroLog #1879

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

shubhamPatil-paycraft
Copy link

No description provided.

@92shreyansh 92shreyansh added the TRV-11 Unreserved-Ticket label Jan 8, 2025
@sharique827
Copy link

FLOW-1 (Ticket Booking)

on_search1:

  • schemaErr0: "/message/catalog/providers/0/time/range/start must match format "date-time""
  • schemaErr1: "/message/catalog/providers/0/time/range/end must match format "date-time""
  • timestamp_err: "Timestamp not in RFC 3339 (YYYY-MM-DDTHH:MN:SS.MSSZ) Format"
  • message_id: "Message Id for /search and /on_search api should be same."
  • code: "descriptor.code should be one of TICKET,PASS"
  • provider_0_fulfillment_0type: "Fulfillment type should be 'ROUTE' in provider."
  • Fulfillment 0:
  • stops_1.gps: "GPS coordinates must be precise upto six decimal places only in longitude."
  • stops_9.gps: "GPS coordinates must be precise upto six decimal places only in latitude."
  • provider_0_fulfillment_1type: "Fulfillment type should be 'ROUTE' in provider."
  • Fulfillment 1:
  • stops_2.gps: "GPS coordinates must be precise upto six decimal places only in longitude."
  • stops_4.gps: "GPS coordinates must be precise upto six decimal places only in longitude."
  • stops_7.gps: "GPS coordinates must be precise upto six decimal places only in longitude."
  • stops_8.gps: "GPS coordinates must be precise upto six decimal places only in latitude."
  • stops_10.gps: "GPS coordinates must be precise upto six decimal places only in latitude."
  • stops_12.gps: "GPS coordinates must be precise upto six decimal places only in latitude."
  • provider_0_fulfillment_2type: "Fulfillment type should be 'ROUTE' in provider."
  • fulfimment[2].stops: "stops are missing or empty at fulfillment[2]"
  • provider_0_fulfillment_3type: "Fulfillment type should be 'ROUTE' in provider."
  • fulfimment[3].stops: "stops are missing or empty at fulfillment[3]"
  • provider_0_fulfillment_4type: "Fulfillment type should be 'ROUTE' in provider."
  • fulfimment[4].stops: "stops are missing or empty at fulfillment[4]"
  • provider_0_fulfillment_5type: "Fulfillment type should be 'ROUTE' in provider."
  • fulfimment[5].stops: "stops are missing or empty at fulfillment[5]"
  • provider_0_fulfillment_6type: "Fulfillment type should be 'ROUTE' in provider."
  • fulfimment[6].stops: "stops are missing or empty at fulfillment[6]"
  • provider_0_fulfillment_7type: "Fulfillment type should be 'ROUTE' in provider."
  • fulfimment[7].stops: "stops are missing or empty at fulfillment[7]"
  • provider_0_fulfillment_8type: "Fulfillment type should be 'ROUTE' in provider."
  • fulfimment[8].stops: "stops are missing or empty at fulfillment[8]"
  • provider_0_fulfillment_9type: "Fulfillment type should be 'ROUTE' in provider."
  • fulfimment[9].stops: "stops are missing or empty at fulfillment[9]"
  • provider_0_fulfillment_10type: "Fulfillment type should be 'ROUTE' in provider."
  • fulfimment[10].stops: "stops are missing or empty at fulfillment[10]"
  • provider_0_fulfillment_11type: "Fulfillment type should be 'ROUTE' in provider."
  • fulfimment[11].stops: "stops are missing or empty at fulfillment[11]"

search2: "Payload is missing"

on_search2:

  • on_search2: "Payload is missing"

select:

  • tmpstmp: "Timestamp for /on_search api cannot be greater than or equal to /select api"
  • item[0].item_id: "/message/order/items/id in item: I333-AND-DDI should be one of the /item/id mapped in previous call"

on_select:

  • schemaErr0: "/message/order/provider/time/range/start must match format "date-time""
  • schemaErr1: "/message/order/provider/time/range/end must match format "date-time""
  • timestamp_err: "Timestamp not in RFC 3339 (YYYY-MM-DDTHH:MN:SS.MSSZ) Format"
  • message_id: "Message Id for /select and /on_select api should be same."
  • Fulfillment 0:
  • stops_1.gps: "GPS coordinates must be precise upto six decimal places only in longitude."
  • stops_9.gps: "GPS coordinates must be precise upto six decimal places only in latitude."
  • Fulfillment 1:
  • stops_2.gps: "GPS coordinates must be precise upto six decimal places only in longitude."
  • stops_4.gps: "GPS coordinates must be precise upto six decimal places only in longitude."
  • stops_7.gps: "GPS coordinates must be precise upto six decimal places only in longitude."
  • stops_8.gps: "GPS coordinates must be precise upto six decimal places only in latitude."
  • stops_10.gps: "GPS coordinates must be precise upto six decimal places only in latitude."
  • stops_12.gps: "GPS coordinates must be precise upto six decimal places only in latitude."
  • fulfimment[2].stops: "stops are missing or empty at fulfillment[2]"
  • fulfimment[3].stops: "stops are missing or empty at fulfillment[3]"
  • fulfimment[4].stops: "stops are missing or empty at fulfillment[4]"
  • fulfimment[5].stops: "stops are missing or empty at fulfillment[5]"
  • fulfimment[6].stops: "stops are missing or empty at fulfillment[6]"
  • fulfimment[7].stops: "stops are missing or empty at fulfillment[7]"
  • fulfimment[8].stops: "stops are missing or empty at fulfillment[8]"
  • fulfimment[9].stops: "stops are missing or empty at fulfillment[9]"
  • fulfimment[10].stops: "stops are missing or empty at fulfillment[10]"
  • fulfimment[11].stops: "stops are missing or empty at fulfillment[11]"
  • item[0].item_id: "/message/order/items/id in item: I333-AND-DDI should be one of the /item/id mapped in select"

init:

  • tmpstmp: "Timestamp for /on_search api cannot be greater than or equal to /init api"
  • item[0].item_id: "/message/order/items/id in item: I333-AND-DDI should be one of the /item/id mapped in previous call"

on_init:

  • schemaErr0: "/message/order/provider/time/range/start must match format "date-time""
  • schemaErr1: "/message/order/provider/time/range/end must match format "date-time""
  • timestamp_err: "Timestamp not in RFC 3339 (YYYY-MM-DDTHH:MN:SS.MSSZ) Format"
  • message_id: "Message Id for /init and /on_init api should be same."
  • prvdrStartFormat: "Range.start Time Format is Invalid in /on_init"
  • prvdrEndFormat: "Range.end Time Format is Invalid in /on_init"
  • Fulfillment 0:
  • stops_1.gps: "GPS coordinates must be precise upto six decimal places only in longitude."
  • stops_9.gps: "GPS coordinates must be precise upto six decimal places only in latitude."
  • Fulfillment 1:
  • stops_2.gps: "GPS coordinates must be precise upto six decimal places only in longitude."
  • stops_4.gps: "GPS coordinates must be precise upto six decimal places only in longitude."
  • stops_7.gps: "GPS coordinates must be precise upto six decimal places only in longitude."
  • stops_8.gps: "GPS coordinates must be precise upto six decimal places only in latitude."
  • stops_10.gps: "GPS coordinates must be precise upto six decimal places only in latitude."
  • stops_12.gps: "GPS coordinates must be precise upto six decimal places only in latitude."
  • fulfimment[2].stops: "stops are missing or empty at fulfillment[2]"
  • fulfimment[3].stops: "stops are missing or empty at fulfillment[3]"
  • fulfimment[4].stops: "stops are missing or empty at fulfillment[4]"
  • fulfimment[5].stops: "stops are missing or empty at fulfillment[5]"
  • fulfimment[6].stops: "stops are missing or empty at fulfillment[6]"
  • fulfimment[7].stops: "stops are missing or empty at fulfillment[7]"
  • fulfimment[8].stops: "stops are missing or empty at fulfillment[8]"
  • fulfimment[9].stops: "stops are missing or empty at fulfillment[9]"
  • fulfimment[10].stops: "stops are missing or empty at fulfillment[10]"
  • fulfimment[11].stops: "stops are missing or empty at fulfillment[11]"
  • payment_params: "params object must be present and non-empty in /on_init"

confirm:

  • tmpstmp: Timestamp for /on_search api cannot be greater than or equal to /confirm api
  • item[0].item_id: /message/order/items/id in item: I333-AND-DDI should be one of the /item/id mapped in previous call
  • payments[0]_id: payments.id must be present in confirm
  • payment_params_bank_code: params.bank_code must be present in /confirm
  • payment_params_bank_account_number: params.bank_account_number must be present in /confirm
  • payment_params_virtual_payment_address: params.virtual_payment_address must be present in /confirm

on_confirm:

  • schemaErr0: /message/order/provider/time/range/start must match format "date-time"
  • schemaErr1: /message/order/provider/time/range/end must match format "date-time"
  • timestamp_err: Timestamp not in RFC 3339 (YYYY-MM-DDTHH:MN:SS.MSSZ) Format
  • message_id: Message Id for /confirm and /on_confirm api should be same.
  • Fulfillment 0:
  • stops_1.gps: GPS coordinates must be precise upto six decimal places only in longitude.
  • stops_9.gps: GPS coordinates must be precise upto six decimal places only in latitude.
  • Fulfillment 1:
  • stops_2.gps: GPS coordinates must be precise upto six decimal places only in longitude.
  • stops_4.gps: GPS coordinates must be precise upto six decimal places only in longitude.
  • stops_7.gps: GPS coordinates must be precise upto six decimal places only in longitude.
  • stops_8.gps: GPS coordinates must be precise upto six decimal places only in latitude.
  • stops_10.gps: GPS coordinates must be precise upto six decimal places only in latitude.
  • stops_12.gps: GPS coordinates must be precise upto six decimal places only in latitude.
  • fulfimment[2].stops: stops are missing or empty at fulfillment[2]
  • fulfimment[3].stops: stops are missing or empty at fulfillment[3]
  • fulfimment[4].stops: stops are missing or empty at fulfillment[4]
  • fulfimment[5].stops: stops are missing or empty at fulfillment[5]
  • fulfimment[6].stops: stops are missing or empty at fulfillment[6]
  • fulfimment[7].stops: stops are missing or empty at fulfillment[7]
  • fulfimment[8].stops: stops are missing or empty at fulfillment[8]
  • fulfimment[9].stops: stops are missing or empty at fulfillment[9]
  • fulfimment[10].stops: stops are missing or empty at fulfillment[10]
  • fulfimment[11].stops: stops are missing or empty at fulfillment[11]
  • item[0].item_id: /message/order/items/id in item: I333 should be one of the /item/id mapped in /on_init
  • payments[0]_id: payments.id must be present in on_confirm
  • payment_params_bank_code: params.bank_code must be present in /on_confirm
  • payment_params_bank_account_number: params.bank_account_number must be present in /on_confirm
  • payment_params_virtual_payment_address: params.virtual_payment_address must be present in /on_confirm
  • created_at: created_at must match with context.timestamp in /on_confirm
  • updated_at: updated_at must match with context.timestamp in /on_confirm

status:

  • tmpstmp: Timestamp for /on_init api cannot be greater than or equal to /status api

on_status:

  • schemaErr0: /message/order/provider/time/range/start must match format "date-time"
  • schemaErr1: /message/order/provider/time/range/end must match format "date-time"
  • timestamp_err: Timestamp not in RFC 3339 (YYYY-MM-DDTHH:MN:SS.MSSZ) Format
  • message_id: Message Id for /status and /on_status api should be same.
  • item[0].item_id: /message/order/items/id in item: I333 should be one of the /item/id mapped in /on_status
  • payment_params_bank_code: params.bank_code must be present in /on_status
  • payment_params_bank_account_number: params.bank_account_number must be present in /on_status
  • payment_params_virtual_payment_address: params.virtual_payment_address must be present in /on_status

FLOW-2 (Cancel Flow)

on_search1:

  • schemaErr0: /message/catalog/providers/0/time/range/start must match format "date-time"
  • schemaErr1: /message/catalog/providers/0/time/range/end must match format "date-time"
  • timestamp_err: Timestamp not in RFC 3339 (YYYY-MM-DDTHH:MN:SS.MSSZ) Format
  • message_id: Message Id for /search and /on_search api should be same.
  • code: descriptor.code should be one of TICKET,PASS
  • provider_0_fulfillment_0type: Fulfillment type should be 'ROUTE' in provider.
  • Fulfillment 0:
  • stops_1.gps: GPS coordinates must be precise upto six decimal places only in longitude.
  • stops_9.gps: GPS coordinates must be precise upto six decimal places only in latitude.
  • provider_0_fulfillment_1type: Fulfillment type should be 'ROUTE' in provider.
  • Fulfillment 1:
  • stops_2.gps: GPS coordinates must be precise upto six decimal places only in longitude.
  • stops_4.gps: GPS coordinates must be precise upto six decimal places only in longitude.
  • stops_7.gps: GPS coordinates must be precise upto six decimal places only in longitude.
  • stops_8.gps: GPS coordinates must be precise upto six decimal places only in latitude.
  • stops_10.gps: GPS coordinates must be precise upto six decimal places only in latitude.
  • stops_12.gps: GPS coordinates must be precise upto six decimal places only in latitude.
  • provider_0_fulfillment_2type: Fulfillment type should be 'ROUTE' in provider.
  • fulfimment[2].stops: stops are missing or empty at fulfillment[2]
  • provider_0_fulfillment_3type: Fulfillment type should be 'ROUTE' in provider.
  • fulfimment[3].stops: stops are missing or empty at fulfillment[3]
  • provider_0_fulfillment_4type: Fulfillment type should be 'ROUTE' in provider.
  • fulfimment[4].stops: stops are missing or empty at fulfillment[4]
  • provider_0_fulfillment_5type: Fulfillment type should be 'ROUTE' in provider.
  • fulfimment[5].stops: stops are missing or empty at fulfillment[5]
  • provider_0_fulfillment_6type: Fulfillment type should be 'ROUTE' in provider.
  • fulfimment[6].stops: stops are missing or empty at fulfillment[6]
  • provider_0_fulfillment_7type: Fulfillment type should be 'ROUTE' in provider.
  • fulfimment[7].stops: stops are missing or empty at fulfillment[7]
  • provider_0_fulfillment_8type: Fulfillment type should be 'ROUTE' in provider.
  • fulfimment[8].stops: stops are missing or empty at fulfillment[8]
  • provider_0_fulfillment_9type: Fulfillment type should be 'ROUTE' in provider.
  • fulfimment[9].stops: stops are missing or empty at fulfillment[9]
  • provider_0_fulfillment_10type: Fulfillment type should be 'ROUTE' in provider.
  • fulfimment[10].stops: stops are missing or empty at fulfillment[10]
  • provider_0_fulfillment_11type: Fulfillment type should be 'ROUTE' in provider.
  • fulfimment[11].stops: stops are missing or empty at fulfillment[11]

search2:

  • search2: Payload is missing

on_search2:

  • on_search2: Payload is missing

select:

  • tmpstmp: Timestamp for /on_search api cannot be greater than or equal to /select api
  • item[0].item_id: /message/order/items/id in item: I333-AND-BPI should be one of the /item/id mapped in previous call

on_select:

  • schemaErr0: /message/order/provider/time/range/start must match format "date-time"
  • schemaErr1: /message/order/provider/time/range/end must match format "date-time"
  • timestamp_err: Timestamp not in RFC 3339 (YYYY-MM-DDTHH:MN:SS.MSSZ) Format
  • message_id: Message Id for /select and /on_select api should be same.
  • Fulfillment 0:
  • stops_1.gps: GPS coordinates must be precise upto six decimal places only in longitude.
  • stops_9.gps: GPS coordinates must be precise upto six decimal places only in latitude.
  • Fulfillment 1:
  • stops_2.gps: GPS coordinates must be precise upto six decimal places only in longitude.
  • stops_4.gps: GPS coordinates must be precise upto six decimal places only in longitude.
  • stops_7.gps: GPS coordinates must be precise upto six decimal places only in longitude.
  • stops_8.gps: GPS coordinates must be precise upto six decimal places only in latitude.
  • stops_10.gps: GPS coordinates must be precise upto six decimal places only in latitude.
  • stops_12.gps: GPS coordinates must be precise upto six decimal places only in latitude.
  • fulfimment[2].stops: stops are missing or empty at fulfillment[2]
  • fulfimment[3].stops: stops are missing or empty at fulfillment[3]
  • fulfimment[4].stops: stops are missing or empty at fulfillment[4]
  • fulfimment[5].stops: stops are missing or empty at fulfillment[5]
  • fulfimment[6].stops: stops are missing or empty at fulfillment[6]
  • fulfimment[7].stops: stops are missing or empty at fulfillment[7]
  • fulfimment[8].stops: stops are missing or empty at fulfillment[8]
  • fulfimment[9].stops: stops are missing or empty at fulfillment[9]
  • fulfimment[10].stops: stops are missing or empty at fulfillment[10]
  • fulfimment[11].stops: stops are missing or empty at fulfillment[11]
  • item[0].item_id: /message/order/items/id in item: I333-AND-BPI should be one of the /item/id mapped in select

init:

  • tmpstmp: Timestamp for /on_search api cannot be greater than or equal to /init api
  • item[0].item_id: /message/order/items/id in item: I333-AND-BPI should be one of the /item/id mapped in previous call

on_init:

  • schemaErr0: /message/order/provider/time/range/start must match format "date-time"
  • schemaErr1: /message/order/provider/time/range/end must match format "date-time"
  • timestamp_err: Timestamp not in RFC 3339 (YYYY-MM-DDTHH:MN:SS.MSSZ) Format
  • message_id: Message Id for /init and /on_init api should be same.
  • prvdrStartFormat: Range.start Time Format is Invalid in /on_init
  • prvdrEndFormat: Range.end Time Format is Invalid in /on_init
  • Fulfillment 0:
  • stops_1.gps: GPS coordinates must be precise upto six decimal places only in longitude.
  • stops_9.gps: GPS coordinates must be precise upto six decimal places only in latitude.
  • Fulfillment 1:
  • stops_2.gps: GPS coordinates must be precise upto six decimal places only in longitude.
  • stops_4.gps: GPS coordinates must be precise upto six decimal places only in longitude.
  • stops_7.gps: GPS coordinates must be precise upto six decimal places only in longitude.
  • stops_8.gps: GPS coordinates must be precise upto six decimal places only in latitude.
  • stops_10.gps: GPS coordinates must be precise upto six decimal places only in latitude.
  • stops_12.gps: GPS coordinates must be precise upto six decimal places only in latitude.
  • fulfimment[2].stops: stops are missing or empty at fulfillment[2]
  • fulfimment[3].stops: stops are missing or empty at fulfillment[3]
  • fulfimment[4].stops: stops are missing or empty at fulfillment[4]
  • fulfimment[5].stops: stops are missing or empty at fulfillment[5]
  • fulfimment[6].stops: stops are missing or empty at fulfillment[6]
  • fulfimment[7].stops: stops are missing or empty at fulfillment[7]
  • fulfimment[8].stops: stops are missing or empty at fulfillment[8]
  • fulfimment[9].stops: stops are missing or empty at fulfillment[9]
  • fulfimment[10].stops: stops are missing or empty at fulfillment[10]
  • fulfimment[11].stops: stops are missing or empty at fulfillment[11]
  • payment_params: params object must be present and non-empty in /on_init

confirm:

  • tmpstmp: Timestamp for /on_search api cannot be greater than or equal to /confirm api
  • item[0].item_id: /message/order/items/id in item: I333-AND-BPI should be one of the /item/id mapped in previous call
  • payments[0]_id: payments.id must be present in confirm
  • payment_params_bank_code: params.bank_code must be present in /confirm
  • payment_params_bank_account_number: params.bank_account_number must be present in /confirm
  • payment_params_virtual_payment_address: params.virtual_payment_address must be present in /confirm

on_confirm:

  • schemaErr0: /message/order/provider/time/range/start must match format "date-time"
  • schemaErr1: /message/order/provider/time/range/end must match format "date-time"
  • timestamp_err: Timestamp not in RFC 3339 (YYYY-MM-DDTHH:MN:SS.MSSZ) Format
  • message_id: Message Id for /confirm and /on_confirm api should be same.
  • Fulfillment 0:
  • stops_1.gps: GPS coordinates must be precise upto six decimal places only in longitude.
  • stops_9.gps: GPS coordinates must be precise upto six decimal places only in latitude.
  • Fulfillment 1:
  • stops_2.gps: GPS coordinates must be precise upto six decimal places only in longitude.
  • stops_4.gps: GPS coordinates must be precise upto six decimal places only in longitude.
  • stops_7.gps: GPS coordinates must be precise upto six decimal places only in longitude.
  • stops_8.gps: GPS coordinates must be precise upto six decimal places only in latitude.
  • stops_10.gps: GPS coordinates must be precise upto six decimal places only in latitude.
  • stops_12.gps: GPS coordinates must be precise upto six decimal places only in latitude.
  • fulfimment[2].stops: stops are missing or empty at fulfillment[2]
  • fulfimment[3].stops: stops are missing or empty at fulfillment[3]
  • fulfimment[4].stops: stops are missing or empty at fulfillment[4]
  • fulfimment[5].stops: stops are missing or empty at fulfillment[5]
  • fulfimment[6].stops: stops are missing or empty at fulfillment[6]
  • fulfimment[7].stops: stops are missing or empty at fulfillment[7]
  • fulfimment[8].stops: stops are missing or empty at fulfillment[8]
  • fulfimment[9].stops: stops are missing or empty at fulfillment[9]
  • fulfimment[10].stops: stops are missing or empty at fulfillment[10]
  • fulfimment[11].stops: stops are missing or empty at fulfillment[11]
  • item[0].item_id: /message/order/items/id in item: I333 should be one of the /item/id mapped in /on_init
  • payments[0]_id: payments.id must be present in on_confirm
  • payment_params_bank_code: params.bank_code must be present in /on_confirm
  • payment_params_bank_account_number: params.bank_account_number must be present in /on_confirm
  • payment_params_virtual_payment_address: params.virtual_payment_address must be present in /on_confirm
  • created_at: created_at must match with context.timestamp in /on_confirm
  • updated_at: updated_at must match with context.timestamp in /on_confirm

soft_cancel:

  • tmpstmp: Timestamp for /on_confirm api cannot be greater than or equal to /soft_cancel api

confirm_cancel:

  • cancel: Payload is missing

soft_on_cancel:

  • schemaErr0: /message/order/provider/time/range/start must match format "date-time"
  • schemaErr1: /message/order/provider/time/range/end must match format "date-time"
  • timestamp_err: Timestamp not in RFC 3339 (YYYY-MM-DDTHH:MN:SS.MSSZ) Format
  • message_id: Message Id for /soft_cancel and /soft_on_cancel api should be same.
  • order_id: order_id should be same as in /on_confirm
  • Fulfillment 0:
  • stops_1.gps: GPS coordinates must be precise upto six decimal places only in longitude.
  • stops_9.gps: GPS coordinates must be precise upto six decimal places only in latitude.
  • Fulfillment 1:
  • stops_2.gps: GPS coordinates must be precise upto six decimal places only in longitude.
  • stops_4.gps: GPS coordinates must be precise upto six decimal places only in longitude.
  • stops_7.gps: GPS coordinates must be precise upto six decimal places only in longitude.
  • stops_8.gps: GPS coordinates must be precise upto six decimal places only in latitude.
  • stops_10.gps: GPS coordinates must be precise upto six decimal places only in latitude.
  • stops_12.gps: GPS coordinates must be precise upto six decimal places only in latitude.
  • fulfimment[2].stops: stops are missing or empty at fulfillment[2]
  • fulfimment[3].stops: stops are missing or empty at fulfillment[3]
  • fulfimment[4].stops: stops are missing or empty at fulfillment[4]
  • fulfimment[5].stops: stops are missing or empty at fulfillment[5]
  • fulfimment[6].stops: stops are missing or empty at fulfillment[6]
  • fulfimment[7].stops: stops are missing or empty at fulfillment[7]
  • fulfimment[8].stops: stops are missing or empty at fulfillment[8]
  • fulfimment[9].stops: stops are missing or empty at fulfillment[9]
  • fulfimment[10].stops: stops are missing or empty at fulfillment[10]
  • fulfimment[11].stops: stops are missing or empty at fulfillment[11]
  • item[0].item_id: /message/order/items/id in item: I333 should be one of the /item/id mapped in /on_cancel
  • breakup: quote.breakup is missing
  • price: price.value is missing in quote
  • cancellation: cancellation is missing in /on_cancel

confirm_on_cancel:

  • on_cancel: Payload is missing

NOTE

  • Please use the correct format of json.
  • Please remove signature from the paylaod.

@shubhamPatil-paycraft

@shubhamPatil-paycraft
Copy link
Author

shubhamPatil-paycraft commented Jan 8, 2025 via email

@sourabhsaini11
Copy link

@shubhamPatil-paycraft, it's a gentle reminder to provide updated logs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TRV-11 Unreserved-Ticket
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants