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
- f5a120a24c2063ce96ea7d26f0eb5842f17a0e28926ff7399332610ce8d9bd90
- request
- ba30dff5ccb10657cc9d2f31f9b7227e9b79ad84063adfadd52a32388dda7592
- transaction
- a61e69d086c565e819a3b657b340af76518be2e11895772a571cae43e46c62f4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47124
the chainentry 47124
- sealed to the entry before
- fbaf2a6ab11d01c130a039d2c76051b9419710e80f08793b199da3d5ca1674f0
- this leaf
- 37569cecfaeedab8e14bad3bd60e07903be28ebbe7c0bc1a9ffc76fbba75a9fa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cQPKJ+0xhotR5t5fuqZ/T6wgJjBAebkWnyz0t8pUZrno+J0k2fM9SyqQIoHjR3af9oeMHYEIemGO4TfHyaPBAQ==