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
- 23f1da066f2a65906f7c6be0745e2cf8aebfeaf4f5cb1b1839df11d755c72468
- request
- 8226bd481480a1402b506fa6ead0a2279cc80862b856d9196f29d672390045fa
- transaction
- 15a7c5d49bbfe619023d2ab927b5aad71cdf3d22be8e056daa8f73dd4ca9578dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63044
the chainentry 63044
- sealed to the entry before
- a1acfc413a738f979b9d8de3180d06378c85cba5a770e14ab85360c10087c2d7
- this leaf
- 6ea168851cce518983de88c0e220311ce36d98604c173193f98b4069f5658073
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ELr1IAdq0iwFVwXefmvRkwMB6UGNO28NUKC0plIAP9aG/o7vuim4zXHO9U9eBPxfzDhwd6/blXVIwVsoXVxmCA==