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
- f19e5c9855805da4039a5f72f2d0a8bb348d6352453682e654584c9792000f2f
- request
- 7e72fe2deeefda6ac650addaee05281512cfcfc25256ced669e1241f2dc86ba2
- transaction
- 7a38971c5618791ec48dde53a9e508d0f40f91c43fdad88eff223fdeac40e95dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21044
the chainentry 21044
- sealed to the entry before
- 19af38597acbc0440e842be4e11a9bfade69d0203e24bc5a3a2a90a1f8b4c854
- this leaf
- 8a95fa0a4c411bf3a05a386cedb18218aa5d97922bec1a997e7fb14ad213bc4f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- L07qMUYYXQ6r3rjoliietySanoAfWN2NOIfcS4ltOmzbC6u5FXNFL1S1XO06Pl4fAZoKUuMQ7smIqlWZ8A9gAQ==