Proxtera B2B BAP v2.0.2 - compliance check

[abhinavv245]

Flow 1

/on_search

• why is proxtera sending on_search(1 & 2), with the same message_id as rapidor, also, the schema is not compliant with v2.0.2

Flow 4

• is not on the v2.0.2

Flow 5

/confirm

• bpp_terms cannot be changed by BAP, acceptance should be provided in bap_terms in order/tags

Note: Cancellation flows are missing.

@ashok-ai

[ashok-ai]

@abhinavv245

We as a buyer app generating the transaction_id and message_id. This has been returned by the Rapidor seller app and our own PX seller App in the on_search call.

on_search(1) is Rapidor and on_search(2) is PX Seller App. Later can be ignored in this case.

We haven't submitted the Flow 4.

Flow 5 issues have been resolved now.

[abhinavv245]

Flow 1

/search

• valid buyer_id_no should be provided in buyer_id tag

/select

• payment/type - POST-FULFILLMENT is not enabled yet
• Communication channel link is already provided by seller app in /on_search, why is buyer app sending its own link here

/confirm

• @ondc/org/provider_name, @ondc/org/category, @ondc/org/TAT are not required in fulfillments
• invalid bap_terms in order/tags, acceptance to bpp terms should be provided

Flow 4

• on what basis PO is rejected? Also, Error object missing in /on_confirm.

Note: Buyer Cancellation and Merchant Cancellation terms along with Flow 5 needs to be provided.

@ashok-ai

[tanyamadaan]

• How do you verify the zip codes. For ex. is "area_code": "0213280" a valid ghana zip code?
• on_search - "platform_id" - invalid attribute in providers.items
• on_search - provider.tags.seller_id - cannot be gst. Probably, it would be tin.
• on_search - provider.tags.seller_terms.gst_credit_invoice - cannot be Y.
• on_select - "@ondc/org/TAT" = P1D. Are you validating this?

Flow 2 and 4 are not valid as prepaid payment is not yet enabled for B2B Exports

@ashok-ai

[tanyamadaan]

Logs cleared for Proxtera Buyer App. - B2B Exports.