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
- e5c48759b973ba58cf5134bbff9ea7d5e46e544574a37eff05e7012d0b86b9f1
- request
- 2b1f6764f31c4a2c47636fd97441c68ce625c81be1658be7ba5b92bed1077008
- transaction
- 0ace6c814891e25e67b274e0fe6a9e7f6fd606a9c8d47905890f25a450e36c3ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10642
the chainentry 10642
- sealed to the entry before
- 8c214684f3313d00e63f83a40c36f4688b70d388e838ec3d8c43bb045d6619b1
- this leaf
- 8ca66a0e180067681f7bbe29d83b5723f511eb1139ac9edfc7d329f03afce568
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fIJrws8R1nYyR2WdL7PBwAZFxcmv6aZlCzQJN08MacqYYLeL1tY8yHErjBwffU2PVIPu2Q74vbhhm2XzON6sAw==