why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- f0e2f3260e55048ee3847b436cebce707b57cc4c835a9447af1f65a297a3ba28
- request
- 28895bdbd8e9bbc683c82c6e95adc129e17e9ac3ead1a660409ffb226d88b63f
- transaction
- a03ae755c2c9cc6837f2f9365ecca0b5d4bb6a2b84dc5b1fed296e0697684b2ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 161
the chainentry 161
- sealed to the entry before
- 225cffc73503b90b904a6ea38eee86f0f62ea5a4ac69e8ba3b3c1aba4fd72dfc
- this leaf
- 23833d575a40fbc07e4cccf4402bc7eac1dfd7087de911e9ee14511d8a42d8ee
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- b+ByRsqJ+0gn0xIJrz69H3rDwVPfu9PoD75jcCN2+IIJaeo3pUKrcC+MtutpU1yP1k/9CBDmvJFOI3tIzUfmAw==