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
- 9cc9ff6de40ed024eb293bb8b9a7398926401299c088ff4eed3e39601302f801
- request
- 2b7232ee535b4f60ff513052008f4c27ffcf343d5dd04d9099edb44c57be4072
- transaction
- a25036d562f3f9e1ef080ce8e2d02c867e206d6b01e213e31bd22c96bd4d4e78computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63481
the chainentry 63481
- sealed to the entry before
- 27c6528e74948a2dfb3d6ffe4e4284db4949b7c9aae3f95d2585e0cc0948c368
- this leaf
- 8e0c6035b7ab57e58abc593c6d9e0b34b114a0956370e2859a202396e3eb94be
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hCffSsos+jyCZwXOadVuGfXepBf6etg3wujJoFDSEk1FDWuL9OCaHM1ZrG6+6FCp8fVdfbzDTLAY8du115j4Bg==