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
- fc58d175f288cd9efcc9202fb4dc6ff72a4a66ba339e55ae021148c23a1a8898
- request
- 4bbcca1c1cb17476c8ccbeae3ecad6e2f9096b779b60b011b7018bb1ba738c78
- transaction
- a8d766a53ef7283a791be737535fa6e761b748b4deec8472bffe44cee290f2eecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15728
the chainentry 15728
- sealed to the entry before
- 1be927c34c07506b6846c50e1cdb6ffd91ae9220e8ed306fe232f7bd77a9e3a6
- this leaf
- dd52ce4313f3f11a926a2ee7599775dc27d99f55fff6894823b37bcfbfe17297
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fhtusjuynODh9p/Ee4Kybdaa8tHtDh7xQCASqqa20Gwu7v6AMBArTrBkOTnUeoUdzRrrZUqgdQlYuVwI4hMVAw==