769793 - Most definitely do not ignore receipt expiration

Status: RESOLVED WONTFIX

(Marketplace Graveyard :: Payments/Refunds, defect, P2)

Description

[Andy McKay]

We are ignoring certificate expiration, because we don't have replace receipt yet.

When bug 757226 we should most definitely stop ignoring it and undo the changes we did in bug 769739.

Comment 1

[Wil Clouser [:clouserw]]

We should be respecting dates on receipts.  blocking+.  Note the dependency which is also blocking.

Comment 2

[Jason Smith [:jsmith]]

bug 757226 isn't going to be fixed for basecamp. Is this still a blocker?

Comment 3

[Jason Smith [:jsmith]]

Not an on-device bug. Removing nom.

Comment 4

[Andy McKay]

Replace receipt has landed. Bugs have been filed.

What dates should we pick for receipts? An earlier proposal was that receipts would back off, for example:

- 30 mins for first receipt
- 1 week for second
- 4 weeks for third

and so on.

But this was based on the idea that there would be the possibility of a quick refund. That currently doesn't exist. Should we still structure them on that schedule or go longer?

Currently we still have to rotate the certs for the receipts every 2 weeks, so I think that is the longest we can do them for.

Comment 5

[Raymond Forbes[:rforbes]]

ok, just seeing this.  as far as the question about the expiration schedule.  how hard would it be to change in the future?

Comment 6

[Andy McKay]

(In reply to Raymond Forbes[:rforbes] from comment #5)
> ok, just seeing this.  as far as the question about the expiration schedule.
> how hard would it be to change in the future?

There are two expirations. The one that we create in the marketplace code is pretty easy to edit. The harder one is the certificate, which will expire in 2 weeks and I'm not sure how to do that, perhaps multiple certificates?

Comment 7

[David Durst [:ddurst]]

Payments are trending to close...