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
- f7fc2d81bf47f8b338498882420468ef4c8ac2be2ca8cb86cde6538bee5723de
- request
- 5897c223b16bd9407677935a791414cf31eecaf9a260efad125fc8bae38f3740
- transaction
- 64e96cf49c6cb55d2bd59d25cac76b3adaecc879d31959c641e7bdf8ac1a6d82computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1545
the chainentry 1545
- sealed to the entry before
- 0783f41d1707d002f95ff3f64b3e23ffdb586ca75192324bbb3b0d25d017c97f
- this leaf
- 31b33916735003465ba9df0625b160b5f145de406a3fcd627cc0d4026f45965a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vqIGC3uRfuDm7sCtIkel82aRt7fk8uodxAnZF+9t0jBpF5ShjkUgIgoKKyO4sgzcYwydAzvw2XTMXsnI4rU8Cg==