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
- 9357b10bc334d3b2230956e80a7d7b81ad2515cab7ed9f3521ecb5f065d57633
- request
- 497cc1ac5ab1d69a582c463027396991bc2fd8130f30a502014624c111f427e4
- transaction
- 339e6579f55e979faf03c1708b9bed7d2c10bc537e9717ed4829b6f380808943computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13335
the chainentry 13335
- sealed to the entry before
- 8a4f7f5a57b9feb2fce12ff053c3dec479282832315054f3dd4552f116aa11ef
- this leaf
- 50fda8c6400077a17aaa654e96bfcc3298086edf897348069044c790e7de8e23
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NdO6Ssd8RUvJGqX2xw4ShUzIjwuKyYKW5BIgxJflFKZubMHsgHWPsBzVTgXkBf2g3hoIbX+G84xGLBFUM3p0DA==