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
- d2b95ea6ad7a5a0891109f709e556936552724fc216d839ac7bb4bca76332ba0
- request
- 424a05d85f28a3b857c4aa9bdd8071ec7f32e5cd40d269524d58d26c93c24ad3
- transaction
- fb7a189faa78aa07a28f54c14964920ad3589c9635077912c6f8825fb8f6464dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11914
the chainentry 11914
- sealed to the entry before
- ecdfca57990746fd62d70f6b8ad7917b02d8b2ea0f86001cf331e41f8a485db3
- this leaf
- 55e1cc6fff244b5484b3dbe9c908504a9fce38fb8909e64a42a8359768668087
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5r85oDss67VwsuI3CaNI6TEd9EU+6VmOtThnk7T6O+edlBRJiQMyjk3RM6tUJ/wVYamoTPoFSbFXrcmDveNMAA==