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
- 870c3442803bafa4e84f61468e3b8acd0e7e6518fe748ecb83acddd723d0d43d
- request
- b29623e4384b3fc4f41cf02d94221ec5d6dd058615f79330206bede0db738474
- transaction
- 87b57c71da49e67889516d1045745d8a9c7780c7498642ac047d275830655fe3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76138
the chainentry 76138
- sealed to the entry before
- f88e456f885ae13d4e036e1709a3a6c9c5577f1c62b6331df9ac0eb9ecffca35
- this leaf
- 5d0839f5e22a6da15282328442895a968ea533d73cc28911c2d346147a8daf76
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MxlWCc8/a+SQG8wOcCSwoTUeRdyfv/SFi5X7ILEaAH1mUBNq0su+32OEyT0ugpAAwJN16NbNWkzt9cQL6s5UBw==