Re: [w3c/payment-request] Alternative 'Pay' button wording options for Browser UI (#701)

@stpeter
> It strikes me that the current flow & API are optimized for one-time, real-time purchases by consumers 

Nods. I am hopeful that covering additional flows can be done without too being too specific like https://github.com/w3c/payment-request/pull/111 or the previous `transactionType` shown on https://github.com/adrianhopebailie/browser-payment-api/commit/e34975023a03ad1c5865b5abed5a363cfa5488ba.

Maybe a fairly clear specs around a new minimal set of enums that cover all or most use cases can work. e.g.
```
PaymenType enum

enum PaymentType {
    "payment",
    "partial",
    "authorization",
    "capture",
    "subscription",
    "reservation",
    "validation"
};
```
They can be of informal value which does necessarily alter the API process beyond display attributes...



-- 
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-request/issues/701#issuecomment-382576500