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
- 97000f26b4550ab560ab801aa3dad73bf887045b666771300c677257e7649838
- request
- 0c38d342c5fa14eb2c8e986b28cf145049929e4c615ed760829620d7a13e3ff2
- transaction
- 87c13e35c634625702277ba940df12ff41a41a605172e0325104751af98f8b83computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66343
the chainentry 66343
- sealed to the entry before
- b4780952b5170cae46c336b218c235d259ad4b9efa48c74e3430d4c16a37c309
- this leaf
- 8bd3e9e4b7b28808e1a74d5b1a84786eef0852d3a46b0a8347c75bd3112f58f7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MkIW6+Amn6IjleVUsj+KN5xuNwRLsgsv64aYe8lw78gKaA+JBeeb3GMCN8zOUHtpl0CQKsld/Glfj1ysYnPwBg==