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
- 73aef2470ebba7a060f3d45461ebef728dc6224191d02b9ed28b183691aed6f1
- request
- e6044fc3d7f654bbaccdd789f90ea4abe583599eebf8e02be042a2a9ede156a1
- transaction
- 4b1249b925a5e61e8b9bfba4282193b31f98c05cab9b331660d3c62f4817287ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38295
the chainentry 38295
- sealed to the entry before
- b40bff43ddf6cc89b0d3adf7430060222f9d792ccd64b4eebcf9f5c8b25c9fe6
- this leaf
- 27a9ef46891c3b3ab704bf5eb17a239a44d7d184efa75a5ab68c4daf3af18366
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QN0LzlfYTKZK+HDUsO0MKxZ1YMjMtwoDywet/8EpXacKp0mzMt4B1zSo4/eG4LH1noI8hbVfoQrapTifcddnAg==