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
- 388b0c36b120862247190e186db29c809e662fc73288964cd48f998b5c721d0b
- request
- 435475c5bfdd98844688f3a72bc7785e312eb82fc4394876ee72a43c445da1f2
- transaction
- 290a4a5ce311f4fa691b083dd7715902ef624dd7f59fe12f86effecc7a76774acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38012
the chainentry 38012
- sealed to the entry before
- dae7938df34eb2f278a5aa927956549525f30d8180440d4027611dc5ec7faa25
- this leaf
- 7d35a979969c151be8d0e754032de5466b91085d2b3a14a56d305ee91531f7f2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- niGJ1P+51YgE38cNyOWlbQyaeF4v+VzdfdjbTlQAcd4fRG6DxRt4yIK7/IDe2LXAKIGfNDVfTPchsMiueVlxAg==