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
- 431c33f498bc49ff9d86b7408447c7efe28fd8ecf82e49bace1a631c51cd5e28
- request
- ead9304891759fcc66e547988d34d5aa8b9ff9aabe50ddd131d896b5946d16e1
- transaction
- 2de706379efb616838a5501cbb5447f1b94f5cf403fb82b82551bd747d3c773ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16894
the chainentry 16894
- sealed to the entry before
- 0cddd6e09a59cc316b75d67375bc4ff0ceb0f637a64a147066e2fa7ee9e61795
- this leaf
- 1025e56c0ff62326ae0a0e49ebeb5eb9c40740856ea04d7a7af1a9b38e97d9aa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VMBUDExQIc+jcrub1aNYppSske/CxG9UpYrk2hnc8Oi77chwFP2vMNSLSNVtIKjwo0h013dt+XVaeQmhu78mCA==