I wonder if instead Stripe could have routed calls through itself, filling in the secret info. Perhaps it was discussed? For example, imagine Joe Biden buys a

I wonder if instead Stripe could have routed calls through itself, filling in the secret info. Perhaps it was discussed? For example, imagine Joe Biden buys a widget from WidgetsR.us and wants it shipped to his home address of 1600 Penn Ave in DC. WidgetsR.us -> Fedex.com/order_XYZ/ship-to/Joe Biden at 1600 Penn Ave in DC WidgetsR.us <- Fedex.com "201 CREATED" Instead they could route through Stripe (where 123_joe corresponds to Joe Biden's identity docs in Stripe), which fills in the missing info. WidgetsR.us -> Stripe.com/identity/123_joe?redirect=Fedex.com/order_XYZ/ship-to/$NAME at $ADDRESS Stripe.com -> Fedex.com/order_XYZ/ship-to/Joe Biden at 1600 Penn Ave in DC Stripe.com <- Fedex.com "201 CREATED" WidgetsR.us <- Stripe.com '"201 CREATED"' That way WidgetsR.us never knew the $NAME or $ADDRESS of user 123_joe, but was still able to use them. (Yes, they could send that info to themselves, but then they're on the hook for protecting it.) The huge downside here is putting Stripe in your business's critical path. But if it's already there for payments, then why not for identity?