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
- a407439b98b5017c500073026809c61ef934b48e316654404fb692c853bc8711
- request
- 67d638b0fe14d71ff4242e081e4e2cb3a15d086442800c56ed62946ce420be51
- transaction
- f4909ab2c68d55a868b0146bff8af70b8a7bced37bb623c4e320bbd0d950ea9fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26983
the chainentry 26983
- sealed to the entry before
- 039a07d22f25100fbcbbfb7a3eab21634b5fb1984ede7cee00acecd412d55aae
- this leaf
- 6345b74270eeede77c22c2a39203311e65182993e2e618bc5931a3d39886ada8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fxq1u01pjueYCz5r5JjMi62zbmkQmfD7+BgFkDp759eSacYAxy07w2Ka3T6M/aZQMG3JT0njMU70sZAhEy+BBw==