Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9)

If you want to pass arbitrary data through the API, the correct syntax `object`. For example, that's how payment-specific `optional object data` works in [PaymentRequest constuctor](https://w3c.github.io/browser-payment-api/specs/paymentrequest.html#paymentrequest-interface).The spec describes in words what the `data` contains.

> 5 - If data is not a JSON-serializable object, then throw a TypeError.
> 6 - If the name of any top level field of data does not match one of the payment method identifiers in supportedMethods, then throw a TypeError.
> 7 - If the value of any top level field is not a JSON-serializable object, then throw a TypeError.

---
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/browser-payment-api/issues/9#issuecomment-200547999