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
- e076bae70213e011ff01988c468fa4af87fc98b1dcbd5525fbc2f1ebeaf9d99c
- request
- 5775e2317ef5252663e3a6a8c6ece3436ead23a4f146316338ebda3e5b44f6aa
- transaction
- 8a0bb2931d356e31e05c69af8d368c1c77af4dba8ebcb70b709f75c165381d5ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36169
the chainentry 36169
- sealed to the entry before
- d9d0eaddc68c4668337df440283795df6a6929c27de3bcce64499cd916d19e49
- this leaf
- 77b4b44f8bd9ebc06b011ccba1920b94f7e5964675ef90c67db4c7f0ec384b91
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7zJWLA6nZpXTxRFNNS1hujqYEFM4CefUGaU4pkFXZyZa+Olnr31D+jI5hvCAcUyLfkk02T4u6+nc95PUlIkfCg==