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
- 8138567dc5a53a8222b5bee952a2bc499f1a9eb68aad7afc07ebb1e3c2f7cdbb
- request
- 086465e25a3a7555839f95ba1bc69390554ff5604c633f31904826a8e097a2d6
- transaction
- e8fcf9ff0faf92736b1299dba878c4e148627471a32ff39bb1ca66c789d5810acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70968
the chainentry 70968
- sealed to the entry before
- f84526984fea0219031e1f7fd481bcac4b46fdb2c0d34066ed6410fcd9a78e65
- this leaf
- 66e174ed1c394d87a34169a58261c339e3a2205c51f76633d0967b4b88be0355
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ilged2ZfNlQ+6g++1J1t0lscV3ntP2ZLKxIapU9GiGqNxm1P0OHqewa531vuNj81Z7Why3U4S5t83k6UTnsyDQ==