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
- 4a8a92ddd8f10ac96194646e798db1fa4a5877ac77c1eb1e3f85aeac8ed10dc1
- request
- 985492494c942983225a55e5be79a2284e65c13a4692fa75a91bb31c99ba39e4
- transaction
- 8525d13b88ecde791a17006c5cbbb5576f52a17385f3015c2ea6ce9ec657dc1bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68327
the chainentry 68327
- sealed to the entry before
- 0203d60a2c536f57bb3b260f19285cc2c4208fe645ae99cf42a2fdd80c282be8
- this leaf
- c03038d89d4353c71635493a3b560ddd2a7db2bfa54f4ea407e3c3e2f0dd4a3e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RJG0eUehM2l6ngPqTxa3GoK305KFiIbw7WvZM61qKjZ0yjgl3Unipf3BAjEmBD1Qq7fjjQhjGi1syvoYMU9eCg==