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
- 1629e33e7efbc3a4dad01fb00c1fdab05862074fd35e8e96b06914f57cab95e3
- request
- 6cb3dfd3b4a876b0daf3a08920f01ca11f2bc6e9023b0553fd999a260a97d761
- transaction
- 96ebfdb42a6ce4f16536f947fb342b6b02d5bfc0ec38ce9696a5742940fb9d82computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1230
the chainentry 1230
- sealed to the entry before
- bd487b445424d8b1800b6bad1d04ff0656d4ca68cc965434187a68bee51b2859
- this leaf
- 68a82946f0cd445ffec7b76acaaa5d7a21610a0dd0c75747f7d8cc1210f0b9ae
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tHmlO1vK8jE1lggm682uhN00zCmejggpjhhP2LClznwAQ8b0FKKJUmSUaaOIPdXbG/7fyXzdsrzeKS01Haj/CA==