Checkout is platform-owned and handles customer, address, shipping, order, and payment state. Any future checkout extension surface therefore needs its own placement targets, context schema, capability allowlist, lifecycle, privacy controls, and performance limits.
Providers are not checkout extensions#
A payment provider such as Razorpay participates through the signed payment-provider protocol and its declared checkout presentation. Its managed payment modal is provider UI, not an App Embed. Checkout extensions would customize only explicitly approved Tringify checkout locations and events.