Re: [w3c/webpayments-methods-tokenization] Should the response data include an "expires" field? (#12)

the expires field is nice to have, however, it should not be viewed as an authoritative source of information.

There are many reasons why the token might get expired and the most direct way to know is when a charge is requested.

The tokenization provider will respond with a success or a failure. The failure generally contains an error code which explains why the token is rejected. some of those errors may lead the merchant to evict the token, perhaps ahead of a suggested expiry time.

-- 
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/webpayments-methods-tokenization/issues/12#issuecomment-319282571

Received on Tuesday, 1 August 2017 06:42:52 UTC