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
- 8f2e0a1e5ef5a9d012eab6ba36187eb599ce23671715b1a159ed50277af9d81d
- request
- 6638a3ed106387f6baf5b5b0061803c515e5297d65fa030bac685e872715b87a
- transaction
- f6b883ae14d123009b935e9bae15dfcdf2c0165cfdd1084477c8465982b72acdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36854
the chainentry 36854
- sealed to the entry before
- 99d31261ad318e9312331e589e2961b6a41625b909cabf335f1fba77841c65d4
- this leaf
- f375f92be08db155daa54e742273e89d5301e8357e7b9c43b94e814dca87e8a7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yOrygbbh1GkjcnlaHgGuBPIPo6Zz6jwFCpIAZtFSVD1bvCCW30vLrhOzElwUy1tXvY7aecT9oJ3nfX0yOlCZCA==