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
- 31d6bf20d08cf50ce78a54c019c79d61033c3d8e2a8861616b9605513ce64229
- request
- 0314df4bbdcf6e289594133574e3944d37c4aff7146b0250ed0739d77904f4bd
- transaction
- ad90b89c2c31531c14e91b91e1626268fbd6c7ba573351e8c78a93dad21640e0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50241
the chainentry 50241
- sealed to the entry before
- 2a08966c408496fcbfec58686dacea97a0d8b933c1f73513549395641e8d3607
- this leaf
- c7f96354cee4a41f7e32ab9d8e1a20581f51b5e5f67a3c82ed17f54c90448d7d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8eE9HoytkhcADNJ5PvA3msDAIRSgDE8LTqDEB04tB8oHVVhc74goaZ87Q8rUnpLHwlpr8Ft9fiAGJljSaqyICA==