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
- ebeb031e25b73d596b8adcbefaba55955097b4a1417723eed98671b4c479c092
- request
- 86f307f544d5532425f70070a4e334dbf6c835dc0e19b73bb1c28c2ce729cca0
- transaction
- d27abb095561d6985b912e10b306dfe2c64bd368945e3985aa6fb9f143cc2010computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49970
the chainentry 49970
- sealed to the entry before
- 91dc6b32ae76e769ec0f86df012ba3989cb461f936d6dbea950ab9ef6c4224f4
- this leaf
- e76c250cc2cda589def19266e897a0f96d30ba2b1c9473720d5388231b49fd97
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kXM0P24QBkFvyaVkWLdLlpVGErHi0pzdG1+efkuPkCOesxJrRspwTRcSdB+cGm4wi7vGSXV9LnQfV+xUIj4YDQ==