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
- 03a5c0125d7727065214dfd687da6de267e093d194bcde67f3e04b151cc68348
- request
- eba66e1df7ee55d046f891b228fa9a3a14f99fb687fbb15176f709b6ced20fa5
- transaction
- 655328ee0cfcef61dd21cc7d669277cf6ce79a3262c923d175d8ce81ac1b070ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22133
the chainentry 22133
- sealed to the entry before
- 62d7f9433b3162038c418823532d752ce7066b99fdac163ecb530613521b3251
- this leaf
- 5385e76bb86879e20462a40e287a197a361349b1756aa873fdbdb04e2ff1a6b4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pQ4HeG+aeT8WVy58fa47EI2GMOXHJBq3SZfWero4rRtX+pXy5i0bwRyXsEtmgQbpymWdmoYI3od6dO8HHTFrBw==