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
- 1a3c166776457ce3165b1dec109a5ffedc325a072b1bf62680a87e3f3fdc6203
- request
- 84c3f1bccc94934399ee159d31ad74026bdb252ca4cb246c2bf54a52aa44dcb3
- transaction
- d7c8df1b844125b50d835cfadfd2d456eb6fc43c1eca45e928791a8d480e52dccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63706
the chainentry 63706
- sealed to the entry before
- 7a5a11e55622a71212c3d5e125bf616ab153608e7777bdb9f7042361db1ed76c
- this leaf
- 2ae8f8f97673b22eabacde7792b41a07cbdb79f680007c8e7675bd9600821ee3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oBuP4kdnUAlCRFQgGoPJVvLMBbsYikC1id17gfulq9VZRZsc+9fZ30gCYgJcRP/Usqq+XbuZJK5MCAqI2bh4Dw==