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
- 2ebbc307d00c9cd3ad81f7200c403e66fa91396e17e4cdf70a896c154f95d699
- request
- 8f56bbe920bab2750d730a72da66cb32ab978263880efb73ecf9a86e90e86217
- transaction
- b070243437614ee7a805d27ddae401c61c8f40363d1490678d65993d4361564bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6204
the chainentry 6204
- sealed to the entry before
- 9c008218e44e276242164a841cd8e84697cae2fa8524c858c8ad991e45073ba4
- this leaf
- ce9a4918451a10bc608d3b3374a70e612451cbd4ea1ccc2bb34fec4724ddfed2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DPLYDoKzfrJqIrytQ+6DljkpoSsVoQf5xvDpzQvtxkaBvDVacPgcEy+eD4ojXitXqhN3pmZyxHzhLbbzH0rjDQ==