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
- 0a72b51ebcbcf9a528fa597be717c804eeacb92998ee4f78682a16aef2a3aa6e
- request
- 8d67026a4fab3521ad26e0d0fa0d46b9fff2fe03fcc89dff6178f80e917286bc
- transaction
- 25cdb5e7dbbbadcb315fc01830d84a948f10b61b2ffc71c37769b2be4daf23d9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12450
the chainentry 12450
- sealed to the entry before
- ba4afa66668c67b7650ea4120d2539c856789bc58f3d3d253b6aff9559c12eb0
- this leaf
- 3541ab32bb6590483c02b0e9a353d67f97f2ee39b993ad15c633cbfd0731280b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2LINOBjapjkrtZuCrIzMuVrHNX3TOlp9pW8/6UP63+JFYY8UjU2YCvDpxiy3OEUshEm1PF/cM0OjJyZcO/EABA==