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.

Sign up for GitHub

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

Jump to bottom

Nivesh(TRV13)-Compliance Check #1932

Open

sourabhsaini11 opened this issue Feb 6, 2025 · 1 comment

sourabhsaini11 commented Feb 6, 2025

on_search

for add_ons defined additionally apart from api-contract (COMPRIHENSIVE_INSURANCE, THIRD_PARTY_INSURANCE, NEW_INSURANCE, TRANSFER_INSURANCE, OWN_DAMAGE), send only descriptor.code

common_issue

remove empty add_ons if not selected (/select onwards)
for tag OFFER_VALIDITY, correct format is P15D
bap_uri ishould remain same throughout transaction journey
How can item.price possibly be 0
How can params.amount & SETTLEMENT_AMOUNT be 12505 if item.price is 0

init_1

xinput.status should be SUCCESS

on_init_1

missing VAHAN_DETAILS
xinput.descriptor.name should be "Vehicle & Nominee Details"

on_init_2

missing VAHAN_DETAILS
xinput.descriptor.name should be "Personal Info"

Claim-Flow

missing on_status with fulfillment.type CLAIM
on_update calls representing CLAIM flow are incorrect, payload is incomplete & missing calls as well

on_update_1

incorrect payload, missing CLAIM payload

sourabhsaini11 mentioned this issue

Open

AkhileshNivesh commented Feb 7, 2025

@sourabhsaini11
As we are buyer's side, how did we fix the callback logs on_search / on_init / on_update?

Whatever status we are getting in on_status we are passing on init call for xinput.status should be SUCCESS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment