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
- 228035059e0faaab6ccd4eca1b1dd3634e7eac5316f39a60f935e976584778b2
- request
- 54750a46723c31fea0a1031cb967925b1f7b828339b08e87256f75df2b44a903
- transaction
- c3fd8bb9a377c4f2672cce58140eaff9da9078d75ac88cd698ed0eebc511235ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70482
the chainentry 70482
- sealed to the entry before
- 343cdff97d930e0f64ed334de532daa5f560d193bacdc7348cc655537e73316a
- this leaf
- c0438ba46d941c1df4f5f903df0b8017ed5105cde8ec5157ba2a7c50862eabcd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jYucvuKFFvA/24A5u2/KmGLBuALuAZzu/Nsl1UIsJDBabIPfklmRaCDkXBg3ijl231KnCjLac4PBtLJAGtIGCQ==