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
- 67ef609f0531e83086cfebb8816c80381daf84b574c92f5b980f6d89c37b2e08
- request
- 43ed29b88ecb7d1d2097ad73158af4b8b132959f92994df9330d590bac0c71f0
- transaction
- f74cc56c139757aa92d4536fc8c9efce9cd0283daeafa05d43ffcd8143888257computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52588
the chainentry 52588
- sealed to the entry before
- 93c18318ba453bff9f5a9b4aa46c0542a114f7fb2addd89083a47dfb11385e61
- this leaf
- a21400539fc334091d6090a036877a567aff70ef41149656f09a0daa35276a90
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8BE6543xXp7n5bEjzk/4eeqAgA7cnJ+1/ohYiWyF0OPjYPXDEZn/wo53xdmf5wRFuPpLbgRQDF7UL9iAdvUZBg==