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
- d7e0676ac27a084967393ce461cfbd050738b640170e29d027443a11aa0b8f3a
- request
- d34d940135d10f6070f325da7aab2e4b2965f576c07e7ad5a7c94e1f1009da9e
- transaction
- 28c3657956d25a81f6dd47f0e4f33960fa9839c87232273073df913b1a09493acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69642
the chainentry 69642
- sealed to the entry before
- de437c58f3c82e2e9147f745a6d077f585933c1750a4714a260d8cfc21bb993e
- this leaf
- 41d0a2803a97f622262cc9486c1e21f0aa1cd02ac43594d4bc4983d92a610c9d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Q8iaoZ4BEuYFH7wfJjd8fExsZdJxxFgOZNVpELPm8gwTpMnjx86RvJU+VrjZ78buf0EEU6+rMCLlpyp8susVBQ==