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
- bd25aa032286204000d8fe917a98077e05ef6ff81b1aa0c3270e8f5a9684f896
- request
- 5181d443c164d9a736110f4956ee9f47db5edf7519662831d5f1cc6c425652d3
- transaction
- d370b1663947ae8d79f90e61b82013abdab6ce85c435408e692e229cdc870bcccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63161
the chainentry 63161
- sealed to the entry before
- 31291ce3f7c82a78293994e7bf2e93c497061d45ae234be5375f22d5d80d1dc3
- this leaf
- 3b94bfe508911df8b8a294a00702f3880d9ecf06e8e97cd05bc89354ccede2aa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- r1szapXJQYuj024Xw55vAx8WtgR+UgmejSl5VpCLxNVIseEAd5BLQYOqU3nPWS/wXwNL3Zd9dE8poFoM6eNMAA==