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
- f52073906251a20c88f352ebfa8afd8fdad65aaf8cd6775b8b958898ebf0035f
- request
- 7b393f08d8df7827c044d7415860a8c77535cacb4a6e7a93d2e2c464d4b1ff16
- transaction
- f0080dcfe8d1eeba2c877cf5581e2f562a225881f0c11752559d7cb78345889ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56177
the chainentry 56177
- sealed to the entry before
- 29cfaa5937d09977332878bae5b3e3a0eb222da9fa2a0b2a409e80b017e3c1a1
- this leaf
- 74c13e0ca5cf58cfa8f7f99d567be8be5b0f46e248cf612b65460fea0d9f9d21
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rziJnF92TRU15xD8WJO7WEU4gGCE7gKTg3s2Ms61zqHeVCd/5LsBLzudmpkI3KvHU0JVnmq48TffODug01sGCw==