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
- 529490d584518db5689a0234e0dccba9463edd00ba566b2ba5ac298435385323
- request
- 65c0321a47d0321c0e4c059339cf06462eabed27417bffbc98657c2ee35beef1
- transaction
- d833c28a811810dcfb1371a6a5e780bc988f565fadf0b5ec2c812955ad7c40cfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54253
the chainentry 54253
- sealed to the entry before
- e9ba0b071bb9506f5df7151f4aed28507dbd4eff8429053e48244e03691959b5
- this leaf
- aadf68b4a8a04915267b580058f414464f7714f345875c2148641376d1c4a018
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QRhrdSGsrlH31v3C+ZTXqLGwHCIcHtfCg51VSXnUyNemubLTGikzar5CoKm6CPV8MZGMZ1keK72PkagLEe2MDQ==