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
- 2a4a7ccbd57e29d89c60ec3427388af580a62faf236271a37a9f78908beae46b
- request
- 564f19f65f2904d18168a828a6c8ca164fcb786ba1abbcca21d5e5caa954ea44
- transaction
- 175d3a55f5ca8f0ed895e2be6d3648c18bb82bda2d2b1a9716e8bf73d0db15cecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43445
the chainentry 43445
- sealed to the entry before
- 2dd8575b3b50f378dd97df203cb6972b81c0e02fc3cf180a86750db912b6b0c5
- this leaf
- 64fccf1afb007a5d78dda8c5af87a7ca4ad86e4b0c5e38da95dfbf045fa496e1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mIhzMNnIx9fzz3USWw/h0rAmZQCCvJr/AraAlVOZl2TM+4U8WvWODadFJId8abTrjtFwl2chSblkJtjYXMNZBw==