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
- fc759ccb2ee113b5f44fac81181d252526f2b3858e181eddd569fabf33b1abdd
- request
- d3df474baee50eb0f869944efc8a4d5ca5336289a278669322502fdc3dea907f
- transaction
- affeabbd2f9ce9eca3024e4098d2cdcebfa72ad90cc9f73c4b71695dd99db18acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56163
the chainentry 56163
- sealed to the entry before
- 1ff5929d208923da14fd4073f04b74d50a98ad6b5a61f3cc0b90d0f49158091a
- this leaf
- b6f908fc864d1a3d8259dc826d0ea90cc5579295276bd46ef0e189169c94bc05
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ptLEfOlXbFzD7NdCbcSajum63D97yKtBN+Lp3r1WqdU4MZmJICnOCq3O5uWVvx5Gn2F7GsF+J1WphiVCZ9c3AA==