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
- d936b5c7a11d032600b692fc756d18fe1c16c987b9b3922e96885d3c8f68b216
- request
- b502d5c200d496bb105bc89af6adff2564f8d5a4eb7614a8f8e3e2a9dfef8e26
- transaction
- 11442cf0e4ff3e0b619d914b1e48cc1d5c362f78f814e8903932690e66cb735acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8378
the chainentry 8378
- sealed to the entry before
- c4c3218dff79bf9ae2d8c3a33f1d47326bc604f4dd90ad00d89544b6e96b1b6f
- this leaf
- 4abc4941001534a979923b7b0eb65817dacde899eae8a2b2ac7bd8f1fe24bf06
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1+5kAZpy3I4q5K05S1aZmSvMuFfdoH2jK/sq1fxfRwvex+ZNFNfIh+eV70T3U+XP7rUCJVUMOHc+bQWSLX+DBA==