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
- 76bc51b8f9dde6536426cf3cd81dc9246a8920f4bc84b2e7f9e2ee2169bafb40
- request
- b1ffde1715acaa0db93c41127cbd2a3be7b59567099a6e7d847fa8c4e60e65f4
- transaction
- 023ac87ef88c97fda548174caa1e75365727f9d05ab2dde20dc3079da6b5ff79computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17166
the chainentry 17166
- sealed to the entry before
- ec931413aab86266794e270cf18b5b51142b8b5bd763b1b9654e87251e6e0fca
- this leaf
- 860a2349d036652cf0989cb61bdc6c92de9f6ec1b9e5c5193c2e65f35f3ec059
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +CsrCYBzKEpKKY9i/b8xhce2w/8bGgLW6Lj9FDs3G/I4+psu8CksY4vYyWoXI6gLi4I7wNVauReNHbk0RREVCQ==