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
- 216576b8917c3fefe7a53f2d9f4e9d371ccf747a79ced36610f590cf700c8ebc
- request
- a224a6bee25dd834e99f395ee7a0150603034d57568609ac187d2177f332a24c
- transaction
- 8faf2107c74d1985fd113b7d7edc395ceed00703ce8c2d7bc667db8592da1a5bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58382
the chainentry 58382
- sealed to the entry before
- 43da890e95cf5dbf86c66cd455f5ee32f50f80414acc388ac222357ca4b0d0c6
- this leaf
- cd09063e73165d72059aa0e5a3c9eb160f93ef0070d126cfacd598a9b360e5a1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Eedwz5ewBBS8Y1Hp4XATa86b6GUNn5c+t0VyHOK9cA9UprdZdvRHJU2KMy53EAMa7ROUFwNkAuIbWI1U2ilWAw==