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
- de5a477030d1fc44e1f5f8e0b05adb5172cbcffd84bd25b35b503f1194d313a0
- request
- fe8d935990aa1c02efd350e6964b8ad81e5df9f7cd9cb6a2719dc3edb3aca8e7
- transaction
- 3fd8981b808f5035e9d339a23acdb40af9dedc1c7a0ed9ae70f9df55c73a9bfbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45203
the chainentry 45203
- sealed to the entry before
- 986b0f406bb51aa6d8c224672b4bb08f01e86006b0ea05ae964c8142c3732fa7
- this leaf
- 615f8d7717185932d5ec0893058d09854bc7d48c78601b299ab82ec65f8196c5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3m/pyLpp3sEPb6svZEMmxq659hRbRklLIo8VL/rZsgqCnmsb0H4FGOVGr/pCk2/CJX20+Pi3Dtjx5RAQTbnvDQ==