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
- 43ceeb8daa2ab0e0fb6513f11f9c51172a819e26c652e166587ea24c4408265b
- request
- 08090dda3f5e1b9a4cc32ec05dee6e243bf0b764c22f0b18217066a89387b01e
- transaction
- ed56e616ff47ade1db73cda24f7265959e1c5df42035a90466d82ec76f8e82cfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20620
the chainentry 20620
- sealed to the entry before
- 7a54abb93607eadf769e89ea07ec2f80f224a15aa47aad5ce75d3b65908c636a
- this leaf
- a7bd8d8e37d6b162c67665ed2cb755ce11221284e5498ad6a7063a103e17d0dd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9dV5w0cqx4hz1aFpNkgxIGPimDKUImPkx1RyE0WzjjGGMkuff8uURYP1VZlmnFx3EcOa9fzRgy0xS/xV7Fo+Dw==