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
- 1b80c8666a89d40d36ac54a29bbfab998e76e7cea8804a229c78e771e5962bc4
- request
- 35be5edd64926d9c92cdb59913ddec3124f2ecd51f2f029a37deaca2542d9d8c
- transaction
- 0cb584fcae1f63dcf1935db420e257ccffa92ecaeb3992f79839ec3c9b0825bacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35095
the chainentry 35095
- sealed to the entry before
- e925257bdc077606bffea40a73f6db181e3c0159deedb3998a436c4f38f73785
- this leaf
- fff5a980dd1f65bd85bffc6d291c8c445f9b309049efb07cca8fa7c304da08ae
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rj+S6V06kLEP9A2sT1LCCZoRjaTWFzQKqcRIXTHpukfth7SZalPfwIHRK15tm4r0Tdj0uIG5hPKwzXkmVx8yAg==