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
- fb0d570b1eac3de0152f35aba2a624fee885ecfd584b44e2bce98d5e6fcc5025
- request
- e562c95515a7fba780452005d814a3e89d86e466850888c50384a2b0dee002e6
- transaction
- 95b43de811e7e0461bd85e7ed4225415cdec7f35119f14753b4014644fd6f294computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21074
the chainentry 21074
- sealed to the entry before
- a13eba2651476e22e82a8255d771fb124d3987e5dc06071af06ef373602cc1d1
- this leaf
- 3bb24528df6efa8ad1babf32939d09c3b5834176061a641e0f6be05dcb732e49
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lwmZRCMvp7iycrrOvGQiYmSKH9CWDlRrr+SjWcRpdDbFtlHcImkwNbRT/7x8BIUZbaGL+qDWlzRZ+TRhvejuDg==