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
- 9f7de79061d70fc1113f4d79a789abfe7694a948b697400d7c5ba9c1cf9153f6
- request
- ebc2811ca977a78c998b97deba81073198d4a4249137ca8729900b13c28ee062
- transaction
- c0c20989ae3c07952b8b9fc053caa8c2775d879b51be521204589d238593848acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53774
the chainentry 53774
- sealed to the entry before
- 9a3ea0823177fc49d169995e5d73b49f740248d29468916553ec317ebded7e99
- this leaf
- 1612d099204730f50b41af34964afc9be7aa2f2a52a8eda299ef3878d19a06c6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iT0xV3L7tMNZk7e9OsOL11yo3h5i6Tk6NpGPx7eO0PL8oghzZmCCQHc6QcjedUXeR1usiQUsrGs9cKrmvZ5CBQ==