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
- daa5060d635d9f6fa1a4ec62acc84fbec0a51601b7bd69c37db96f5c7394fda4
- request
- 6a58e3cf81e5092e9d9c5ac56ed53c842894aeffbdb2a12b45e7dea42219b4dd
- transaction
- bd2c13fe0c42ecb9b60259a22485bddad3949593ebbfda50d372fbee775a67b1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69282
the chainentry 69282
- sealed to the entry before
- 7d05335b938c397743b55460ba63adc6cebfdf81095e963efba418aea2c416a1
- this leaf
- 33ccca73aaa948dcdbe0a1d83b09c6c6537e601ebae6d7ff317ac44944b28e0e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GX8OWJSuRqaC8YEGbXZsdBNmQ8nAWnLAVhXZbBJepU4VWius/P8bXNsHVgellI+si2WA5KAZdGZLtd+yFmUCDA==