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
- b77ec6ba3a584c8133f3db04d1abecc100b76ee7a6ae1b1584f1f4cabafc49de
- request
- 49ebb4ab41032feb16c42bcfd86be97e3afacc1586d5a5b55453ba97538d757a
- transaction
- cea03b597b376fde45e1e4e743b5651bed0e6b9e635a976ff3e27d4fd66a64d4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44022
the chainentry 44022
- sealed to the entry before
- 0201d5f639dff3a973d0d48aab799d68b690243ee9efa6dba605851229bdfea5
- this leaf
- 0dcf2e112dfae6724906b123097e2274d9b3ec5cfacabcf2984e35e27efa5532
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 029OBBzxjH0Is+WoGuvu3wWZMyra8301HI2qQB1hJu3mn3OuJ3sshdMt3Tr95Rrge6zrIrsYBCgClInOv8bGAQ==