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
- 563a10af9485fae840522d5f538988eaab2ec8907eba2eb670f2831c942e0a1e
- request
- 89197d28644bc050bcfe2e324638d9bcb7e4911f823eb11aa781105cdf2180dd
- transaction
- ecec369a5f3f6be46c426a15908718b726f8d445c130ba7980be327aa5ab4784computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47660
the chainentry 47660
- sealed to the entry before
- 9077ffde7608c9d30bcd94b140f70eed21c7ddf311b5a30c50bef8783d3785f6
- this leaf
- bd14cd89aea979cdf28258cab7691500671adf8b3bdae7df0a59b416a1f0bfa1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HnETPD9ny5ZRFB1YoSlc2G+HDYY1jGZxVlA54c9noOOlitYM74hZQkabR8lqQOokdtvwR4suDZeNDHvsIGOlDw==