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
- cb70ab1855f4d849263a336881332fd90d909c102ec29081ebfb92bf0b655e85
- request
- e425ac026e75ecfde1156b32b41bf0b583ef0532035820d526305d36608f748b
- transaction
- 4950e5bc2d94837bdb32d0cb2c2a6cfa67e26728b079aee8355cfdaaf1620804computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31803
the chainentry 31803
- sealed to the entry before
- 294d6cfc336ae8c959ce117ada50a15762bb795155031c39c268c228a4beb20a
- this leaf
- 455e4959ea464e6f7965158748914d56abdd8cef093585bdd8473f9a751a6932
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- z5/KAslrjmLbh1n6hTdNVQMeTVAWCjtalGU1gU541VeB6l9KVx6mnL1JcxkCDZ+kgShsRHOExBkt97Tv0pBGDw==