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
- e6938cb21069c30823941fbbbf05f0ee32e71fe739aea104ba4eb924cfe5cf59
- request
- d13f066f077f4b6ad258250241297ad34d1cd93930545f7557eb01c8703805bd
- transaction
- 687a72e48c772c4416b621d28a7f5c3739c1e0a240a5cfac404523336c0549eecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63424
the chainentry 63424
- sealed to the entry before
- 55e8c4b869e4e3d0c425d06808e3a3e4411e024506ed7d09b3d195179727d246
- this leaf
- 26fc1fd1eccae3e634ad8745c1f76c061df09004c66ade437331b5fa9e994d82
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hntICqIjvd4cBYuqLTLq8FyVpWa92Prvn3w5s7/gUm0wa5mseIpSSPEoJn/ZjTm0yCovr4/biUTW1dodAmLFDw==