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
- 41675365e6f69ddffe60bfa67404c700dbe992fde3e554da69cc621872071403
- request
- b79a51bd40f405c215ae7b3e880d2b8b84e8d8e4bc3a54fea6f683275bce188f
- transaction
- 140efc61922e20628202eec3465c819708838410d9b22280b072796c7417ce5ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47187
the chainentry 47187
- sealed to the entry before
- 2ca3da4b4bf14ba53bea7e35c70ba3517d36ea5f4d591ffadeaecad157d9c041
- this leaf
- 44a8ff7e3c0aafa84ee5a9bc93bea8046edb77c7eed64a55eb25aabc961234c8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FBv0GMViLMiLCmnz3u67175ALVQzp8+WiPKNJg93szhUj0bEFTa4ERhUonZHzfo+7+0N25+WZRQa4pXqZtooBQ==