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
- 4cecb79c4f8fedf58f88e66f66fbc6705ac9f575b98cd24deedba0a55b1dd501
- request
- a04f38c1f01d643f335cca0c16b57de206eb438b493f4e7071d2e887ce6abee1
- transaction
- ae1f2cb3acb4dfd1ee382aa54085c8d691c1439b7d38d6500ff5dd775fc8f166computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28885
the chainentry 28885
- sealed to the entry before
- 5e5440ac0400025854387be98eaefd8eb5874e7ce9b4dba3589c272a741baf8d
- this leaf
- a3145762b723dfcfc1b5a5103f2b6ed20aef9596e525a195334614efa245a72d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9oH5M56bR2uA7cqcSvKTWyZqYT7JkMqqGg34x6bB4SRJRzDTNSYWN+o5J2MmZ1BY4zfZjxHi62nnizQTsIPyBg==