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
- 6f0250fb29ac58b32dfe86946ac522a6bc3492c9c46e350547249bfbd186fda0
- request
- 5401222bdc51221a8f99ac79def578f5a71f68ac2615cd1d78358a63903bdf07
- transaction
- 8e6bb2044d07fb7bce69feb4f16b97a23e22ced01d5cb4ee980649b4c788d8e8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52634
the chainentry 52634
- sealed to the entry before
- 59ab2f345e55def3e54b5ebdb747703902da10c92b9c4ee5de4fe3768117c20b
- this leaf
- 5e8fa392ca1ce6e30f4ac7e3a86fc26c1e9b5e05715fd6ce14296374e090ef7e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- p+/r73SKTsdRhuXXBDZ1twX7hz8ypXVj4C6mg4CsqA9sPEwFsnHO5TRoamtF1KApCLfOVg3Lf9Ikv+z9+I5fAA==