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
- 67dbd25ffc4d01d0de3194fcfe22c17349ad0ccc908788a27ec6a18da9449c1a
- request
- 4edb8fcfa4b18092de393f22a868f19803e9b424668b43be3a2a1f1bb639869c
- transaction
- 14ea5c492abc2d99e541237e3c25d393ed990b8e033d8c8e8d11044c1fba8163computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28389
the chainentry 28389
- sealed to the entry before
- 4016782b9d65b84b3d8aaae4c33177601d3ed6b98e7c2dc7677549cee480adbb
- this leaf
- 0ca7e27bb428e21fc89133c5630a857b1884ab343fc37cc56f67ce61fd5a85d7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eJweJarTgt8la9zEgbZtY0twGQjDW3mUduGHh24cJsC0KvaonM9FnmqRnYqS4IFEzELbmkGJH3He5OB4QVR9Aw==