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
- f5db40dd2d03d46cc1e56fa391dde66147085ecb1beb0ab73ec069d1e24844b4
- request
- 5ce1a4bcbc813a451639ecb278d36cbd9fe9cc9370c8fc66a2eff584b990695c
- transaction
- 37da9b2da9f86878dd4e5cbfec3a499cadd8a7fa188b8ea04374960f198570dbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 431
the chainentry 431
- sealed to the entry before
- 579e3d4511d9cf6ed87966660d99d6461749c1df81babdba91809a29133a190e
- this leaf
- 312102d0764ac01f5b86e03e1ae11cdeb8c5c19843ba9252699e10e9c612280f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 44eSliWUGWdW9skyVd7g35Vq+nVn3a/PzRva8/Otrg77UxA+510V71EN/j4bKhkLDhntOjWd8Di6wbNoiGE4AA==