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
- f0b147d5367791a53ae5bd75c3fb799b2668d53a086b7d36e98596e0ff342651
- request
- f5c1238fce833d2eb22113ce03c6f7896c11cdd080097f51f5b088d83dc36d45
- transaction
- 28c50e7acf1c6ad79cd7fac5da3d3e31a50921e588f924d96f3700a16f48beb3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48966
the chainentry 48966
- sealed to the entry before
- 10cdc1f692184c7a41825442ce6965142e4358cf39e7e56dd13fe7c33ccc250d
- this leaf
- 6d46a0733d28103ca31aec540f6204b3be2591c7007426fdda16da394adaf402
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0Wvtc0E9taauxTwF0dX70hot8Wi23hguOY87q3S+BFwwyjKFQTr+pZJrc9goawODL7eRzXg0b/pQxl3SFzBwAw==