Spicemoney | B2B | v2.0.2

[tanya-ondc]

Flow 1

search (and onwards)

• buyer_id_code should not be others. Lets use enums for that, otherwise the counterparty will never be able to validate it.
• stops/0/location/gps Incorrect gps value (minimum of six decimal places are required)

/on_search

• items.tags.attributes is missing. Buyer app should send NACK in this case.
• Reverse Geocoding for location ID L1 failed. Area Code 682028 not matching with 10.197500,76.214700 Lat-Long pair

/select

• I was told Spicemoney has implemented Non-RFQ flow. Then how TTL is 2D?

/init:

• Incorrect city name in billing object.

/confirm:

• Does not include below details in payments object: "@ondc/org/settlement_basis": "", "@ondc/org/settlement_window": "", "@ondc/org/withholding_amount": ""

/status:

• Is status API implemented?

/on_status

• billing/address mismatches from /init (c-205 Madhupushpa Pune Maharashtra India)

Flow 2

• similar issues as above

/confirm

• transaction id should be provided in payments/params if the payment status is 'PAID' for 'PRE-FULFILLMENT'

/on_status

• payments/0/type mismatch, should be equal to 'PRE-FULFILLMENT'

Flow 3 & 4

• similar issues

[abhinavv245]

All flows

/search

• Reverse Geocoding for end failed. Area Code 560027 not matching with 12.972442,77.580643 Lat-Long pair.

/select

• provider/ttl and items/tags (BUYER_TERMS) are not required for Non-RFQ flow

/on_select

• payments/0 must have required property 'collected_by' (BAP should perform schema validation)
• delivery charges are missing in quote/breakup

/init

• how is BAP collecting payment for 'ON-FULFILLMENT' order?

/on_init

• Buyer Finder Fee amount mismatches from /search (BAP should send NACK)
• payments/0 must have required property 'type', 'collected_by', '@ondc/org/settlement_basis', '@ondc/org/settlement_window', '@ondc/org/withholding_amount', '@ondc/org/settlement_details'

[abhinavv245]

Flow 1

/on_search

• code = 'attribute' is required in items/tags for domain - ONDC:RET14 and provider/id - 7907561761 (Is BAP accepting payloads without attributes for this domain?)

/on_select

• Delivery charges should be provided in quote/breakup when fulfillment is 'Serviceable'

/on_init

• @ondc/org/TAT is different from the one provided in /on_select (P2D) (BAP should validate)
• Buyer Finder Fee amount mismatches from /search (BAP should send NACK)

Flow 3

• similar issues as above

/on_select

• why is BPP collecting the payment and how is BAP handling this case?

/on_select

• settlement details should be provided in /on_status if provided earlier

Flow 4 & 5

• similar issues as above

[abhinavv245]

Non RFQ with Delivery

Flow 1

/on_search

• all mandatory attributes should be listed in items.tags.attribute (as per the taxonomy)
• Variant mapping is not correct, items/parent_item_id should map to the categories/id (both should not be same)
• In categories/tags, item.tags.attribute.colour is not defined in items.tags.attribute

/confirm

• In order/tags bpp_terms and its acceptance (bap_terms) are missing

/on_status

• payments/0 must have required properties '@ondc/org/settlement_basis', '@ondc/org/settlement_window', '@ondc/org/withholding_amount'

Flow 3

• similar issues

/on_init

• For prepaid payment collected by BAP, Seller NP should be sending its setllment details for buyer app to settle the amount
• "@ondc/org/settlement_basis","@ondc/org/settlement_window","@ondc/org/withholding_amount" are not required and will be set by the buyer app

/confirm

• why is buyer app sending its settlement details in /payments when it is collecting the payment
• @ondc/org/settlement_basis indicates from when settlement window starts, enum - "delivery" (from delivery), "shipment" (from shipment)
• why is payments/params/transaction_id kept same as context/transaction_id (how will buyer NP handle in case of multiple payments)

Flow 4 & 5

• similar issues

/on_select (reject)

• Delivery charges are not required in quote/breakup when fulfillment is 'Non-serviceable' (Flow 5)

[tanyamadaan]

Flow 1

/on_search

• All mandatory attributes are not being sent.
• tags.g3.brand value is incorrect.
• Brand cannot be a variant for Smartphones. Probably it should be Ram and storage.

/on_status

• When it is a non RFQ, non PO flow, there would be no Proforma invoice as well.

Flow5

/on_select

• When location is not serviceable, delivery charges should not be a part of quote.

@sanushilshad

[tanya-ondc]

Logs are approved with exceptions, based on dates provided for certain features enablement.

[abhinavv245]

Buyer Cancellation

/on_search

• code = 'attribute' is missing in /items/tags for domain ONDC:RET14
• providers/payments/collected_by must be equal to one of the allowed values (BAP,BPP)

Seller Cancellation

• similar issue as above

/on_cancel

• cancellation/cancelled_by should be of the seller app (BAP should check)
• In case of merchant cancellation, does the buyer app accept the quote provided by seller app?

Are thorough validations being conducted for both the schema and the business logic?

@sanushilshad

[sanushilshad]

@abhinavv245

• code = 'attribute' is missing in /items/tags for domain ONDC:RET14: they were not searching products that were having all the correct values in the on_searh payload (samsung).
• providers/payments/collected_by must be equal to one of the allowed values (BAP,BPP) : This was fixed a few days ago.
• cancellation/cancelled_by should be of the seller app (BAP should check): This was fixed 2 days when you pointed it out.