chore(checkout): update primary sale widget to use sanctions v2 endpoint

[allan-almeida-imtbl]

Summary

Primary sales widget current behaviour:

• Perform a wallet based (V1) sanctions check on widget mount
• Check sanction result and error out if sanctioned
  • when a uses selects credit or debit payment type
  • when a user proceeeds to buy with a token

This PR:

• upgrades the second case to use the V2 sanctions endpoint as the token details are known
  • calculate the sale amount using the same displayed price calculations as done in the UI for the OrderItems list
• removes the first case as we can safely rely on the third party provider (transak) checks of their own
• remove risk assessment from context state as it is no longer used

Screenshots

Requests

Uses the correct total sale price regardless of whether balance is sufficient or not

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 41579b8

Command	Status	Duration	Result
nx affected -t build,lint,test	✅ Succeeded	2m 5s	View ↗
nx run-many -p @imtbl/sdk,@imtbl/checkout-widge...	✅ Succeeded	1m 1s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-09-08 00:49:09 UTC

[jeetparikh]

this information and the address below aren't available in any context or state directly to use? just curious

[allan-almeida-imtbl]

there is top level order quote and order item information is stored in useSaleContext, however the pricing with conversions is done on a per list item basis in OrderItems/OrderItem, which similarly pulls the quote and item information from useSaleContext. I assume its done this way to dynamcially change based on the selected token