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
- f1db6fdafa5945ee6329f31f50c38f4c27056132b02d0d4344dba7423a706c3b
- request
- 2eee0cf4f148bd8e889af209983fdf64a2f5e89b08a574b7f4f9fa13813dd774
- transaction
- b3c74948c1cdd6ad4b9edf0b896e000812ddc154c08d6a05f868f6e966d120eecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43397
the chainentry 43397
- sealed to the entry before
- 8099f85d75b5e02d589a013bc3d81eff587571f2202ea9e13d884ca8f2a1e3db
- this leaf
- 4e539b74b019e06e9e218ac2ba890e955926d309fdda82da30e3dea35b0430a4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7ldjrhCxFV6NgkkLYxNrEvoYh8rMdGWjtr7iJNTXKMLZZvymU27Eu7JL/HXlZXM1Mx39Cye3oN9fIeKER1DiDQ==