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
- 53616820be92d0e83c24caa68fe99047b8421e6a96b246c9a7a0e344d25afbb4
- request
- cb39b0cff701f3c60b6934c6c6a31ac251985f92444f39f77b98acfa4a6a2429
- transaction
- d7effe36bcaf11e493fc04a693c24c1d70e62adcfd09fc5905f07c1bcf5b4a22computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41240
the chainentry 41240
- sealed to the entry before
- a6cdfba24fb9fe465410270d27aa0c2610b499157364247c14e00ca464dd1af1
- this leaf
- 6ded31299a6a122e67fc04c13001a429463c22054007b7b1b002bd8d1087e180
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kh6qdMiHMbnmPiK15TCC0h1N/fWzySRpR5pFaOSEvNfOZhJhqU5lK4mPZMPA8sobnuo9iHoLnPuP1MyyFr9FBQ==