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
- af491e713fc339b54492de3f8645c023118674c80e0af8f06c46835074afafd1
- request
- 8377f9042a96471a833fca98e1f6c87a9128eee8b2a8334331076139b4ce1534
- transaction
- 888e07b5c66dc918ca69c0708157d5e17b6d1175b55a4e3171776d02eebda9a7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14026
the chainentry 14026
- sealed to the entry before
- df8c5b8408af33ca01000c3298fb3c9bfef69d1442cb4eb87938e1e810adf4cc
- this leaf
- 80df10c919f6354d46522bdc12c63debee51e0237a6af4ad87da226a7b94b904
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- foXzleMDJXW2YB8BhHPPEb/M33rCXE8YAzdrA64+rjhakk/c1eNTULETpEtTmaA45M8XDWJJJfet+TJgFDtBCw==