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
- 0bf463e6e3e36ad81ee8266a159b2c6df86df32d654a7999e374f79acc7307dd
- request
- e5d858796b0525165265b17d390b422da225b3596708cad5d8e298528b4d86ad
- transaction
- f33dd6cf880e2189161a6eb2034c1d3c461707348f1de31fb5c2a425ffb9d8e1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46767
the chainentry 46767
- sealed to the entry before
- d47f3188959599873277a92b31c946c20d070041cf820a72c469c38174a9c4a5
- this leaf
- 3d8aabcdb74e98c07c127c6bb92aa1bab30b33291f89e80aa9cbdc3d9b8ae066
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Bck0M52XBEYRAi3bC5fJFOZ2li/vF9LiCx3cbte8tNeVSl46kcEySXdP9VfPcNk+Cvpq00cNz1lRjHtviEC8Cg==