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
- bf4cfce71c1b28078841884f5de6f22ad1c0bd0568ed92a2b9753c334ce078c3
- request
- 23d2412a7d2bcd5b94896139c9105b07b06bb50d44fe4377c1c04b0be24ea07e
- transaction
- bd3c978dfaafaaa0cc82f31ba8bbf3fc7a8782361874c2835f73cbaabe259a47computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 256
the chainentry 256
- sealed to the entry before
- cb460573c394fa3a3053b01e98b6e5d942c9f80663f26b2fe8b56ac9f9ce6b70
- this leaf
- f95229a0e4f831379f3888a3ef997ca9b39049d52538614153f3ac9136cede46
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6+HNESmwZsepXqzXvsVP/cZvpHGGtC6IUwuJwl6mDSetz8fk1Kyj410UbqoR5X7tSHzUnIgJKTOgBZwrSAqXAQ==