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
- 375cec557c27b715a9d48baec77ae42b2ff16f7d3efe1096dff81887e55f66eb
- request
- 1e816122f32db55ee7e07d40f4f528ef7560ff9a590f209db6c69f445efd2960
- transaction
- 283c81303ea551d2b3051cc866252449c22604edbfe8652a70e8d90ee3004289computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41757
the chainentry 41757
- sealed to the entry before
- 3f451452fa00e14f305b054afa95f0f4ec19ff034848ca5fe16acf4554caab53
- this leaf
- 3ecd148e92d1271f2e3c76c3890bc5b8da88b228687d4a35da846e483acd5228
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9rWfjHNPKUY4W7cfrradwYnMJfQ41z28VVPqcarIxVZMU/d1VobgAXoU8dvQay8fKOUxYJLJzEOlTHXgkzz2AA==