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
- a7661de2533c24122ab9f8af1177b278ac81037e4730ca477baa78e68222c7e2
- request
- dfd6fa87b59d272019b62e7b31dc3a21680b4bcbf2f52e9c199da0b380107f62
- transaction
- 31e16446efaae48c0a2e53b7a234642dd4e289358fb6714b937ebed6295a22a6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2635
the chainentry 2635
- sealed to the entry before
- cd72cbafaf3ea255a9ccb841ee17058e6ad9c8af66e832e0e51fc3c86be4642c
- this leaf
- 1fd012f92e9b402b6a81ecdb26cd6a7318c9c21fcec88f461489563ce3614c1c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dGoeb0FRA/kNJExX2ZZvxOEeW2Y7wyAA0syn0PLfP6DtzQSvUPHAqa4TAy4Y0mcMYNC6xjXh1uz/ulQw99bIAQ==