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
- a56cf9eb05e370857738fefb228de3588c78036657aef65da7570fdc09277e3b
- request
- e3b5fd0792839eb87e52cb136a3445d3b6a9adb39f7799663a6c92c8ab9a9f4b
- transaction
- b865b0f12fdfbe5664cd050e9d61f3f055326d96747897363dc48b51adcc1db0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16165
the chainentry 16165
- sealed to the entry before
- 4a7d1dc6931262718fc62a3473ece2348be671b46df2b035aaee1f4ee08d2070
- this leaf
- 6083139f05e07de84e6be3fa9a412e30c32854aaa5a3fac13cfe4f64893f251b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 664SlnzzodFywUZ5A8Gf2xLFycQiniPQOgxDakrDorydO+SFUTIAxzpLReygyRepkJ2Vgax70TBkASfQ764SBg==