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
- b7f57f615fdab695f365cdcb4a251aa98cedd93d5ebe82f756f4fb5d5399cb64
- request
- bd9e0b7a640808bc454cf46c9adfc6273e9bc015672a982345cf3628551798f2
- transaction
- b3f28ade701e13f9814631c39d4f25ccd6472ef18934b405da47c1b1281d386ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29614
the chainentry 29614
- sealed to the entry before
- b293245b978888767dd1140c75258cb4600b54ee993b056813a62b3813cf1810
- this leaf
- 5da80b33642c251d0c467e609e0a9df516c603a899a43ec8d792edac59fb2f8e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- g0pDjBFJW2ZA/ap5wWVj6VzXHqr2aFwYDDszkw4ObG4+JHzbpuwk4Mh+61LVVUnDXTtrttYqzWon1zjxVJPxAw==