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
- 32e64d0e238c9591c85321b7baa27a8287f4a951e536dfe92a3c522534fad65f
- request
- 9744e61142db01bcb75ccad674990fd5c6c537a05946548bc2e480d30a76c14d
- transaction
- f5560bd0263d617caf1e0e95facec98bc8b088a44895fed570c8ac40e71cc1c9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36082
the chainentry 36082
- sealed to the entry before
- 8f6c3d863ae63dcc8c21ff3a9c8d07e4e86d0e5a224210b8fa4727cdfcf7b33a
- this leaf
- 30e52351e470a8ac9b69e5678cb8e7ae36aaca5ead7ef13ffccb7e0168f4164f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bkeW7D2qYpF79gZcL1q1AO8+Y0RyAR9e/nDMcqrOJD1c+j6NtYwcBsE/GPkcmgsRNJe5TyJp/4670T1OJiVjBQ==