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
- 3beeaf5f9239bec33abe7d30a7c158584705830cce37a85ca32428d991dd8879
- request
- 2d7b2a134a9be261b93bf63522dd27c0828bd2476863492238020ec44d738c28
- transaction
- b1029ae75f70c9d9eac902910c7725ced1905690acb703f1eef940ff0ecb3788computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17161
the chainentry 17161
- sealed to the entry before
- 2e0c8fe697c291ac77e740391f3678e87099b75e75461d177246234c561dd4f3
- this leaf
- 10cf81811b74db16abeb74a3c03610efcb7841532de93d97001a17eefaf019fd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Aa/wpfDCzs1rBX957NFcPu3+QiU7qS45EWSNiX1wdGDVLRUfutCPTfrF71lij2FmpaChf3p/i8eimhH65NPrBQ==