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
- 2566dde3b1d067d05763759972e233dd4313fb5635fbf0e4993aba85ebce641d
- request
- 09f94d1c5317a8afe9ce426fe6602bbfed616e8b0d79e200dad5ce164e315653
- transaction
- 85ce21f2963d43f11ab50607141f33c6db55c5e2485e7883d826258e9d97da12computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10507
the chainentry 10507
- sealed to the entry before
- 3d54fb4564cf09c9ce548a70261954a67c5be93b3e40ee068f752bf3f4227f36
- this leaf
- 04d912be17e352ee93788771caac42c9c10d709c8b9f9f97f2492a6c742b9a20
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jl5CCpUkmClqP1+jbz0dd2ZfbAWyYP0g7AQ1zAcICt8CaoKFI8VGwwknK7v1zjKrJaYmekvaBFeyifasmCmlDA==