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
- 5d06163c9b9497854860f50052eb16a77f370c97bd1570d4cad2e955c5d4bb76
- request
- 8790508e6d4c4eabf06bf086dddcccb5ef24004980b19b1afe6073fda7482e64
- transaction
- 4f3104f4857f7d10dcdea018b5c11a3a0405033bc84fe6aaf24baf11d29bbd33computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27446
the chainentry 27446
- sealed to the entry before
- da63dd87055de74262015f8456d9912fbd62e6fe3e6cb3055c4bf92327bc14c0
- this leaf
- 9ed16e2b58598b2a2e540d695b6adc6a0507e45ba49bcd9552c590db5a202ea6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- t3UD5aXdWASl9Hcee58wDmAtOxs9cTAmSSKGON70ChjzTHeqBLqMG61pnuoGefKZGRm9h9OC6P9tYSk9djEQDw==