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
- a88a222e1f585ea861fa66d32a8d2d27f41795de81235e507c8958a8e4976f1b
- request
- 07c90e0b4a494c9c538317e157d62e9b92b4ee3353da67531b4505bbdd74fe9c
- transaction
- 7e97b0d7031333f5d8e0b43d116a4ada44c81389b60e958ac6d6f00093f78d82computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63919
the chainentry 63919
- sealed to the entry before
- ff5e69b6b3ada46997e5dfd9ebd55fb4d7d03948e9873f568be12060a0dacffb
- this leaf
- 3a2a8b7ec229656de90ee573b82f586e299ae0194c2703a83478991432c81bab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0aortkjyzoxXTNpf2aftPqjcSORDxHyTU1vhkCaeALy+/VyJaUnbFgNRKxndQeJVeVfaxMU92c0Ho8srgtEhAw==