Re: [w3c/payment-handler] Payment Instrument architecture clarification (#381)

Hi @ianbjacobs ,

Thank you for your explanation.
>That payment handler's job would be to enroll new instruments.

By enroll new instrument you assume the next construction:
![image](https://user-images.githubusercontent.com/71703038/102132008-bab06300-3e5b-11eb-9e58-f96a70256210.png)

>If you redirect the user (in the "add" payment handler) to your origin (e.g., pay.com), then you can install a new payment handler for the newly added instrument.

I'm I right understand you? From "add" payment handler (payment handler which should just display payment instruments) I need to redirect user to my origin "pay.com"?  Could you please share the demo?

Hi @rsolomakhin the demo which you shared with me just present two **separate**  custom payment handlers. My goal is to be able to have these custom payment handlers in the another payment handler.

What I want to achieve: 
Payment Handler **A** has two instruments **B** and **C** (each of mentioned instruments links on corresp payment handler in **method** attr). When user open payment handler **A** and click on payment instrument **B**, user redirects to payment handler **B**. 
Could you please let me know if it is clear?

Best,
Roman.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/payment-handler/issues/381#issuecomment-744697296