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
- 9684ffaa631bc19ada5a221780f574c4026d1726e546eee8d60ca2b08dfa6115
- request
- bf96db7664f4d2780fffaaaf4ffe0fca6204ca84aeb7af8fa8580000fddc1d5b
- transaction
- 06d57393505d579b8aaa98adc0af9a466da52bf0bd6bad931e54b0bc3fff5fc5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10249
the chainentry 10249
- sealed to the entry before
- a8725cfa1b36ac2eb2501c4ae5814500b9b28912254da07f21c8746ba1a1ecb3
- this leaf
- 2e207a53545b6be085b298b7260fd476f3e039f3fc7470965da479dd792ff5d2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GQgjh8DvvglUskT8kltFgoeG94dH8/iykROAegLLlLGu5lMPD1nXVMtRJWtJSXgjGHTri4EyrNlg98Z/haOaAQ==