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
- 964fbd61bb98061139aee6bd8edc6bb160465a5d0886fbe5902438927b7c5267
- request
- 4d50afb193b2b88dceb15845b8a4944e5a4424959b776166ed965c3e14fcfa0f
- transaction
- e85747138c82df2f59c291c039efc9384be40ce1919f66859aea3304b010d8bbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51769
the chainentry 51769
- sealed to the entry before
- 3ec8cfc5b88f2799a8a111e48846863960d24d7d034613c42d0e8d9e96a4e740
- this leaf
- 8dcbeefe58979994ec8448a61209435485c8360777d4716908dcb5aee5293398
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SsQK6jZ8YSxlqKu7xhq3C4u297zJ0HgnBFodTKV59/DvebGZbL9q7TnYML8RfGAwTt7CJ4DsC1f/LyYZ9ef+BA==