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
- 7b5bec9c9977749d038adfe75cee5b79d8252da9a4a2aab84d60dc46e3cc0068
- request
- 910a2e829e54f73949a05b3331e9b69847cae8ab99ef3f20d68101ea894999b2
- transaction
- faab88e346a1b0039cfd3a0320717e12de859957ed69153b098d764e787de10bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52859
the chainentry 52859
- sealed to the entry before
- 06ebf33f2ac2b043432f520be3f5b9ce9f6db5670f5a12cf7612aca4af0b07d3
- this leaf
- e05c9e9055d78580f56df6ded7867486d8dac5074f17c7eccfc53a7302e828fe
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yc2DsqCnmjmGOGL970oH8pfDatMPI7PPuv0tZLDe+blaAtJOUFxAWbMLJZJtErRKGtbyC+Ma9J43ZaRVWScSBg==