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
- dda021da81d7efc6bc2aeb35920ba3a1a1b3c16570b979ace4624d15124870ce
- request
- 363d70ab037e1dc3bd023f6d28d05bc2333399f7f4b5f56976c786a9e13cecd5
- transaction
- d352cd0132ada3c48d06207c9225f92cd48bb264079182d0d587fe3aab7affcacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40586
the chainentry 40586
- sealed to the entry before
- 7562dc8e12805d15dd61fa499e5bcde08d8d8cb945267a96228fe34025cd3cdb
- this leaf
- 34f0ef20f792471079eaca5863c4bfe3dfb5bdde6052e379f14897ef23eb9bb9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AKQ1VWPVUYqb4D+r5ROciB1cmsj26zntVjYe+FQcbuhjKEoj1YIVc0pFuDaeRNTbhOLPARrQK6pX/OKSuobGDA==