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
- 47b133216410e810534fc934dd23922ab7e583815f56b7ed6ed09f853b967cc0
- request
- 32b4e36e892fabd0e11306cbb224bcd15808d2deafea15850585560fc41d125b
- transaction
- e0b479c745decf58ca2de991cd6c720cd1493791b37bc0994b44c36324f71f36computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2080
the chainentry 2080
- sealed to the entry before
- cbf63277fc67dbb9491d37069b8627a2d3f2dfef2feda0e6c1b79b2a650b22a1
- this leaf
- da8945811a41b22ac11c273f423637abcf6b7fd1d406449f495fdcd98dd0985a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AnDEWIQ+eCUQaPrFIs/1mg6F9q0GBDSxJHUESUi6nlYSLjMsacImpM8amTaNOZ/PGF20Epc+wREfFudlNW/4Bw==