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
- af8320752790d149e2e7f2f3f266d0ec1b0abb27020750461c833ea52c24c3b8
- request
- d5f1e6d5ed2a88955bbcd44d3741c2d4ed1dd3d4e920846afed4f9dca2179250
- transaction
- f6c3631dfffeb87f5edca63332b1e13c7c58d8c79ff65ac47d1c6e6cd222e5e2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25332
the chainentry 25332
- sealed to the entry before
- b632139625ddc8cb84edc7eed2ca44d5fe42d1d44cc906c803d9aa4481429f46
- this leaf
- 6d958ac6862ae3c707f877960ee901d4682c07817c5d118b4c0f238c27c14133
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lzDmOK1L1FfDbBorszKOsvybITdxiLC/Eg1OWCIAz3EiGK83OnGbfdbbaa/bMH0IL6oCgKam6blbJMxuD3e0Dg==